What problem does it solve? Adding a new template screen to the portfolio site requires more than writing the component: the screen must follow the design system's composition rules and be registered in three separate lists (navigation, chromeless routes, corpus exclusions), where a missed entry fails silently or breaks the build. ## Core Features & Use Cases - Convention-guided composition: Reads design.md's template and composition rules plus live exemplar implementations before writing any code, so the new screen matches the family's established patterns. - Complete implementation scaffolding: Creates the template component with CSS module, the route's page.tsx and layout.tsx, and viewport sizing via the --layout-viewport-height token. - Three-list registration: Adds the screen to templatesSidebarLinks, CHROMELESS_ROUTES, and EXCLUDED_ROUTES in one change, satisfying the build-time coverage gates. - Use Case: Ask to add a kanban template, and the skill mirrors the nearest exemplar, builds the screen with fictional demo data, wires the route, and registers it so the index carousel, sitemap, and chat-corpus validation all pick it up. ## Quick Start Ask the assistant to add a new template screen, for example: add a kanban board template to the site.
