Design System

Use when creating or changing shared UI primitives, tokens, patterns, component defaults, or reusable interaction rules.

Read

The core below is the required contract. Open references/current-guidance.md only for an unresolved in-scope question:

• ## Layers to decide which layer (token, primitive, composed, product pattern, screen) owns a decision.
• ## Existing product evidence when control reuse or screen-section ownership is unclear.
• ## Caller and visual-variant gate before changing a shared card, row, button, token, or default.
• ## Component Structure for folder split and file ownership.
• ## Token Modeling, ## Component Contract for token naming or a component API checklist.
• ## Previews And Examples for the state/variant coverage list.
• ## Do Not for the full prohibition list.

Also use common/skills/reusable-code-design/SKILL.md, and component-api-design.md for API shape, slots, controlled state. For visual quality (type scale, spacing, color, depth, motion) without an existing brand system, use common/skills/minimal-visual-design/SKILL.md.

Must