space-agent

Read the supplemental project documentation module

Frontend development router. Load deeper skills before editing

Use the frontend API surface correctly for app files, discovery, identity, and permission-aware browser data access.

Inspect, navigate, and interact with open browser surfaces through space.browser

Open or close stand-alone browser windows

Editable frontend runtime rules for framework pages, stores, shared runtime namespaces, and reusable visual patterns.

Create, patch, inspect, and remove widgets in the current space

Open, create, remove, or edit spaces

Use HTML adapters, JS hook seams, and component loading correctly in the layered module system.

Author or update onscreen agent skills under ext/skills

Read-only reference for the backend contracts that the frontend depends on, including routing, APIs, auth, layers, and module resolution.

Persist user-scoped behavior and notes through prompt-include memory files

Create, update, and remove users and memberships

Place first-party modules correctly, make them routable, and use router seams instead of hardwiring features into shells.

Download app files, generated blobs, or external URLs

Create and download browser-generated PDFs from structured data or HTML

Capture the current page or a DOM target as a PNG

Explain and manage group membership, manager inheritance, special groups, and canonical group.yaml storage as an admin.

Admin-only router skill for users, groups, passwords, and account storage in the layered Space Agent runtime.

Create, update, remove, and explain user accounts, password verifiers, sessions, and user-root storage as an admin.

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

Trigger browser file downloads from app filesystem paths, runtime-generated in-memory content, or external URLs.

Create, update, and remove users by editing the canonical L2 user files and related group membership files.

Understand L0 or L1 or L2 placement, group and user structure, permissions, and layered override order before storing or overriding frontend assets.