Public-sector design-system router

Choose the authoritative system before writing interface code.

Route the request

1. Identify the government owner, product, and channel. Distinguish a statewide system from an agency- or product-specific system.
2. Read references/catalog.md for the current public evidence and corresponding implementation skill.
3. If a matching implementation skill is installed, read and follow that skill. If it is not installed, tell the user its exact skill name and continue only from the public material available in this router.
4. If the row is guidance-only, internal, legacy, or not found, say so before producing code. Do not invent component names, tokens, packages, or source availability.
5. Use USWDS as a fallback only when the official system inherits USWDS or the user explicitly authorizes that fallback.

Source precedence

Use evidence in this order: