Design System

Use this skill when the main question is "what shared UI rules should govern this product or product family before we design or refactor individual screens?"

This is the repo's canonical frontend UI-system anchor. It should:

1. classify the system problem,
2. choose the right design-system mode,
3. route neighboring frontend work out early,
4. define a compact system packet another human or agent can execute.

Read references/system-modes.md before choosing an approach. Read references/token-and-governance-checklist.md before changing shared tokens, primitives, or naming rules. Read references/scope-boundaries.md when deciding whether the work belongs here, ui-component-patterns, responsive-design, web-accessibility, or web-design-guidelines. Read references/design-system-packet-template.md before writing the final handoff.