Development logo

Development

OrganizationPopular
agent0ai
Development

Build new browser modules in the layered Space Agent runtime and use the extension, component, and Alpine store patterns correctly.

Overview

Publisheragent0ai
Repositoryspace-agent
Skill nameDevelopment
Stars
1.4K
Forks
323
Bundled files
Instructions only
LicenseMIT
Links
Skill sourceRepository
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by agent0ai on GitHub. Read the source before you install it.

Installation

Install the Development AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/agent0ai/space-agent.git /tmp/space-agent
mkdir -p .claude/skills
cp -r /tmp/space-agent/app/L0/_all/mod/_core/admin/ext/skills/development .claude/skills/Development
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Development in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Development on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Development is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Use this skill when the user asks how to build a module, where code should live, how layers work, or how the extension/component/Alpine runtime composes the frontend.

Layer Model

  • L0 is firmware. Repo-owned first-party code belongs here.
  • L1 is group customware. Use it for group-level overrides and additions.
  • L2 is user customware. Use it for per-user overrides and additions.
  • First-party source for this repository should normally live under app/L0/_all/mod/_core/....
  • L1 and L2 are runtime state, not the home for durable repo-owned product code.

Module Layout

  • Browser modules are namespaced as mod/<author>/<repo>/....
  • A first-party module usually lives at app/L0/_all/mod/_core/<feature>/.
  • Keep real implementation files in the module folder.
  • Keep ext/html/ adapter files and ext/js/ hook files thin. They should usually mount a real component or provide a focused hook, not hold the whole feature.

How The Frontend Composes

  1. Page shells in server/pages/ stay thin and expose <x-extension id="..."> anchors.
  2. Matching HTML extension files live under mod/<author>/<repo>/ext/html/<anchor>/....
  3. Those extension files usually mount a real component with <x-component path="/mod/...">.
  4. <x-component> loads the component HTML, styles, scripts, and nested components.
  5. Alpine stores and small module utilities own the behavior.

Example pattern:

html
<x-extension id="page/admin/body/start"></x-extension>
html
<x-component path="/mod/_core/admin/views/shell/shell.html"></x-component>

Alpine And Store Pattern

  • Component HTML owns structure and bindings.
  • Stores created through space.fw.createStore(...) own state, async work, persistence, and API calls.
  • Small utility modules own parsing and rendering helpers.
  • Do not move large feature logic into long inline x-data blocks.

JS Extension Hooks

  • Use space.extend(import.meta, async function name(...) { ... }) for behavioral extension seams.
  • /start hook files run before the wrapped function.
  • /end hook files run after the wrapped function.
  • JS hook files live under mod/<author>/<repo>/ext/js/<extension-point>/....
  • Use HTML anchors for structural seams and space.extend(...) for behavioral seams.

Layer Resolution And Overrides

  • Admin UI asset resolution is clamped to L0 with maxLayer=0.
  • Normal module resolution composes L0, then L1, then L2.
  • If two layers provide the exact same extension file path, the higher layer overrides the lower one.
  • If two layers provide different filenames under the same extension point, both contributions compose together.
  • Prefer additive composition before exact-path replacement.

Practical Workflow

  • For a new repo-owned feature, create a module under app/L0/_all/mod/_core/<feature>/.
  • Add a thin ext/html/.../*.html adapter that mounts the feature into an existing anchor.
  • Put surface markup in component HTML, surface styling in a nearby stylesheet, and behavior in a store module plus small utilities.
  • Keep page shells minimal and avoid bypassing the extension system.
  • When the task needs more detail, treat app/AGENTS.md as the canonical deep reference for layers, components, hooks, and ordering.

Frequently asked questions

What does the Development AI skill do?

Build new browser modules in the layered Space Agent runtime and use the extension, component, and Alpine store patterns correctly.

Why use Development on TypingMind?

Because you install it once and use it with any model. Development is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Development in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/agent0ai/space-agent/tree/main/app/L0/_all/mod/_core/admin/ext/skills/development. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Development?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Development?

As many as you like. As long as a model supports skills, you can use Development with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Development AI skill free?

Yes. It is published on GitHub by agent0ai under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

Related AI Skills

View all
affaan-m logo

Golang Testing

affaan-m
CommunityPopular

Patrones de pruebas Go incluyendo pruebas basadas en tablas, subpruebas, benchmarks, fuzzing y cobertura de código. Sigue la metodología TDD con prácticas idiomáticas de Go.

39.1K
261.1K
Instructions
View
affaan-m logo

Jpa Patterns

affaan-m
CommunityPopular

Patrones JPA/Hibernate para diseño de entidades, relaciones, optimización de consultas, transacciones, auditoría, indexación, paginación y pooling en Spring Boot.

39.1K
261.1K
Instructions
View
affaan-m logo

Kotlin Patterns

affaan-m
CommunityPopular

Patrones idiomáticos de Kotlin, buenas prácticas y convenciones para construir aplicaciones Kotlin robustas, eficientes y mantenibles con coroutines, null safety y builders de DSL.

39.1K
261.1K
Instructions
View
affaan-m logo

Kotlin Testing

affaan-m
CommunityPopular

Patrones de pruebas Kotlin con Kotest, MockK, pruebas de coroutines, pruebas basadas en propiedades y cobertura con Kover. Sigue la metodología TDD con prácticas idiomáticas de Kotlin.

39.1K
261.1K
Instructions
View

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇