website-building

Routing ambiguous website-building requests requires evaluating the subject against defined child boundaries to select the narrowest match among informational, webapp, or game categories. The router applies domain guidance to prevent misrouting to broader capabilities.

The difference between informational, webapp, and game website categories lies in their defined child boundaries and intended output. The router uses subject matter analysis to select the narrowest matching category, applying domain-specific guidance to each.

You need the website-building router when a request could fit more than one web child. It applies when ambiguous requests span multiple categories, ensuring the narrowest child is selected and correct domain guidance is enforced.

The router validates internal references and metadata by enforcing frontmatter consistency and checking that all linked targets exist within the skill's scope. This maintains alignment across nested skills and prevents broken references during routing.

For requests clearly matching a single category like informational or webapp, direct routing to that child is appropriate. The router specifically handles ambiguous requests where more than one web child could fit, applying domain guidance to select the narrowest match.

When a request falls outside defined child boundaries, the router cannot select a valid target among informational, webapp, or game categories. The routing logic requires requests to match at least one defined child scope to apply domain guidance correctly.