website-building

Website-building routing targets game, webapp, or informational child skills based on project type and domain guidance. If the optimal child skill is missing, the router instructs you to install it before proceeding with the routing decision.

A router is needed when website-building requests fit multiple child skills, like a SaaS dashboard or content-focused landing page. It disambiguates by selecting the narrowest child using a domain-aware decision order mapped in references.

Yes, the router validates references and provides installation guidance for missing child skills. It enforces frontmatter naming validation and checks children.json to ensure a clean, testable routing decision before proceeding with the workflow.

The website-building router aligns with shared design tokens so child skills inherit a coherent design system. This maintains visual consistency across game, webapp, and informational projects by enforcing frontmatter and references validation.

Validation fails when frontmatter naming or references/children.json are inconsistent. The router enforces strict validation to ensure a clean routing decision, requiring correct naming and valid child references before proceeding with the workflow.

The router supports browser games and SaaS dashboards by applying domain-aware decision logic. It maps project types to specific child skills, ensuring each website-building request follows its intended specialization accurately through validated routing.