What problem does it solve?
It prevents misplaced code and brittle frontend composition by teaching how to build new browser modules in the layered Space Agent runtime.
Core Features & Use Cases
- Layer-aware module placement: Keeps repo-owned first-party implementation in the correct L0 folder, while treating L1/L2 as runtime override layers.
- Correct extension/component composition: Guides how page shells expose extension anchors, how matching
ext/html adapters mount components, and how <x-component> loads HTML/styles/scripts and nested components.
- Alpine store and hook patterns: Establishes which logic belongs in Alpine stores versus small utilities, and when to use
space.extend(...) for deterministic behavioral seams.
- Practical workflow for new features: Provides a repeatable process to scaffold a module, keep adapters thin, and avoid bypassing the extension system.
- Use Case: When extending the admin UI, follow the resolution and override rules so the intended extension files compose across L0/L1/L2 without conflicts.
Quick Start
Ask an AI to explain where to put each file for a new admin browser module (page shell, ext/html adapter, component, Alpine store, and any JS hook) using the Space Agent layer and composition rules.
