Development

Guides building Space Agent browser modules using layered architecture and extension/component/Alpine store patterns.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/maximoseo/space-agent --skill development-maximoseo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Development
Source: https://github.com/maximoseo/space-agent/tree/main/app/L0/_all/mod/_core/admin/ext/skills/development
Command: npx skills add https://github.com/maximoseo/space-agent --skill development-maximoseo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides guidance to design and structure browser modules in Space Agent, clarifying where code lives and how layered architecture and the extension/component/Alpine patterns come together.

Core Features & Use Cases

  • Layer Model: L0 firmware, L1 group customware, L2 user customware, and guidance on what belongs in each layer.
  • Module Layout: conventions for module placement under app/L0/_all/mod/_core/, and how to connect HTML extension points and components.
  • Frontend Composition: how shells, extensions, components, and Alpine stores collaborate to render features.
  • Practical Workflow: instructions for creating new repo-owned features and referencing app/AGENTS.md for deeper references.

Quick Start

Create a new module under app/L0/_all/mod/_core/<feature>/, wire it into the HTML extension point, and follow the Layer Model guidelines.

Frequently Asked Questions about Development

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure browser modules in Space Agent using layered architecture?▼

Browser modules in Space Agent follow a Layer Model: L0 firmware, L1 group customware, and L2 user customware. Modules are placed under app/L0/_all/mod/_core/<feature>/ and structured using HTML extension points and components to compose UI features.

What is the Layer Model for frontend module development?▼

The Layer Model organizes frontend module development into L0 firmware, L1 group customware, and L2 user customware. It defines what code belongs in each layer to enforce separation of concerns and guide proper module layout.

How do I wire an Alpine store into a frontend module?▼

Alpine stores collaborate with shells, extensions, and components to render UI features. You wire stores into frontend modules by connecting them through HTML extension points and following the module layout conventions for the Space Agent runtime.

Where should new browser modules be placed in the repository?▼

New browser modules should be placed under app/L0/_all/mod/_core/<feature>/. This placement follows the Layer Model conventions and connects to HTML extension points and components for frontend composition.

Can I use ext/html and ext/js hooks to compose UI features?▼

Yes, ext/html and ext/js hooks are used to compose UI features in browser modules. These hooks enforce adherence to the Layer Model and module layout conventions within the Space Agent runtime.

What are the limitations of building browser modules without following the Layer Model?▼

Without the Layer Model, code placement across L0-L2 layers becomes ambiguous, breaking the collaboration between shells, extensions, components, and Alpine stores. This disrupts frontend composition and prevents proper UI feature rendering in Space Agent.