What problem does it solve? Adding a new demo site template to the apps/demos monorepo involves coordinated changes across Sanity schemas, design tokens, React components, and routing, and mistakes like shared palettes or portal scoping bugs silently break the multi-template architecture. ## Core Features & Use Cases - Template architecture rules: Enforces one independent template per visual lane, with clear guidance on what to reuse (FisioNavMobile, FisioContactForm, types, urlFor) versus what must be built per-template (Nav, Hero, tokens). - Step-by-step workflow: Covers schema enum updates, sanity schema deploy, scoped token files, component structure, page.tsx wiring, and build verification. - Documented gotchas: Includes the createPortal token-scope fix via templateScope, mobile nav breakpoint overrides, BookingFlow scroll hijack fix, and patterns for private branded demos and multipage ecommerce templates. - Use Case: When asked to create a new dental or consultancy demo site, follow this Skill to add the template enum value, create scoped tokens, build components, and populate Sanity content without breaking existing demos. ## Quick Start Use the demos-template-system skill to add a new dental template to apps/demos with its own tokens, components, and Sanity content.
