modules-routing
Place first-party modules correctly, make them routable, and use router seams instead of hardwiring features into shells.
Best for platform teamsWorks with GitHubLow risk
⌘source
- author
@agent0ai- language
- JavaScript
★1.1kstars
249forks
May 5, 2026
✦overview.md
Key Features
- ·Module namespacing: mod/<author>/<repo>/...
- ·First-party modules under app/L0/all/mod/core/<feature>/
- ·Routed features own view.html under module root
- ·ext/html/ files as thin adapters into seams
- ·Custom pages vs. spaces: page for feature UI, space for widget canvas
- ·Panel manifests in ext/panels/<name>.yaml
Use Cases
- →Place a new first-party module in the correct directory structure
- →Decide whether to build a custom routed page or a space for a feature
- →Wire a feature into the authenticated app shell using router seams
- →Add a panel entry to the Dashboard Panels section
Best for
- ✓platform teams
- ✓module authors
Not ideal for
- !external modules
- !unauthenticated apps
FAQs
name
Modules And Routing
description
Place first-party modules correctly, make them routable, and use router seams instead of hardwiring features into shells.
Use this skill when creating or updating routed modules, deciding where files belong, or wiring a feature into the authenticated app shell.
If the user wants a reusable app surface, tool UI, settings panel, or workflow screen, prefer a custom routed page module over a space. Spaces are for persisted user-authored widget canvases; custom pages are for feature-owned interfaces.
First-Party Module Placement
- Browser modules are namespaced as
mod/<author>/<repo>/.... - Repo-owned first-party modules should normally live under
app/L0/_all/mod/_core/<feature>/. - A routed feature should usually own its own
view.htmlunder that module root. - Keep the module root as the real implementation location and use
ext/html/...files only as thin adapters into existing seams.
Custom Pages Instead Of Spaces
- Build a custom routed page when the extension should behave like a first-class feature screen instead of a widget on a persisted space canvas.
- Use spaces when the user wants a configurable board of widgets that lives under
~/spaces/.... - Use a routed page when the feature owns its own layout, state, and navigation flow.
$install
1-click copynpx skills add agent0ai/space-agent --skill modules-routingSafety assessment
★
Clarity score
How clear and easy to understand the SKILL.md instructions are, rated from 1 to 5.
3/ 5
goodMostly clear, but there are still a few confusing or poorly structured parts.
◎
Actionability score
How directly an agent can act on the SKILL.md instructions, rated from 1 to 5.
3/ 5
mediumPartially actionable with several concrete steps, but still missing important details.