What problem does it solve?
This Skill prevents first-party app routing bugs and feature sprawl by guiding you to place modules in the correct locations and wire them into routable seams instead of hardwiring UI into shells.
Core Features & Use Cases
- First-Party Module Placement: Places browser modules under
mod/<author>/<repo>/... and recommends first-party _core modules under app/L0/_all/mod/_core/<feature>/, with view.html as the routed entry.
- Custom Pages Instead of Spaces: Helps you choose between routed pages (feature-owned layouts/state/navigation) and spaces (persisted widget canvases), including how to surface pages in the dashboard via
ext/panels/<name>.yaml.
- Router Resolution & Seams: Explains hash routing resolution rules (e.g.,
#/dashboard → /mod/_core/dashboard/view.html) and the approved router-owned anchor points for safe shell integration.
- Reusable Panel Navigation Helpers: Uses
panel-tools.js to list panels, resolve panel route paths, generate hrefs, and navigate via space.router with hash fallback.
Quick Start
When adding a new routable feature page, create app/L0/_all/mod/_core/<feature>/view.html and add an ext/panels/<feature>.yaml manifest so it can be discovered and navigated by panels tools.