What problem does it solve? Apps built by different sessions drift apart visually: some lack a way back home, some hand-roll their own navigation bars that diverge from the shared standard, and prototypes end up outside the shell entirely. This Skill enforces one shared app shell so every app and prototype in the platform has identical navigation, context bar, app title, and footer. ## Core Features & Use Cases - Shared AppShell component: All apps must render src/components/platform/app-shell.tsx (SiteHeader, context bar, app title block, PlatformFooter) instead of writing custom navigation. - Prototype mode: Prototypes at /prototype/<name> use <AppShell app={app} mode="prototype"> to get the shell without entitlement badges or registry claims (per ADR 0014/0015). - Three-level wayfinding: Every app must provide exit-to-platform, app-home, and back-one-level navigation, with labels sourced from landingActionContract and platformApps, never hardcoded. - Use Case: When creating a new app or adding a page, wrap the layout in AppShell, pull the app name and description from the platform registry, and run the completion checklist (no custom nav bars, no emoji, Edge browser width checks, reduced-motion states). ## Quick Start Use the app-shell skill to scaffold a new app page wrapped in the shared AppShell component with standard navigation and footer.