Design

A router over design sub-skills and reference guides, organised by situation. Sub-skills live at sub-skills/<sub-skill>.md, references at sub-skills/references/<name>.md.

Project reference directory

Use project-root docs/branding/ by default for project-specific design reference files and deliverables. Look there first and link to existing assets at their current paths. Root PRODUCT.md and DESIGN.md are explicit exceptions for tool discovery. Use a location specified by the user when given.

PRODUCT.md owns confirmed product facts. docs/branding/BRANDKIT.md owns brand identity and brandkit.html presents it. DESIGN.md owns the applied UI system and its tokens. A brand value used in UI should agree with the approved brand kit; record any intentional UI adaptation in DESIGN.md. If an older project has .agents/design-context.md, use it as migration evidence, then treat DESIGN.md as authoritative. Do not maintain two independently editable token records.

Steps

Pick the sub-skill.
- Argument names a sub-skill: use it.
- Otherwise match the task to a situation below, taking the first row that fits. When two fit equally, ask once.
Follow it. Read sub-skills/<sub-skill>.md and follow it as if it were the skill.
No sub-skill fits: read the reference for the surface below. For implementation, read existing DESIGN.md and relevant product or brand context, then design-context for token discovery and fallbacks when needed. Each reference links its neighbours; follow those instead of loading the whole set.

Read PRODUCT.md for work involving users, jobs, positioning, or product constraints; DESIGN.md for UI design and implementation; and BRANDKIT.md for brand identity. Create a missing document when the user requests it or durable decisions made in the task need recording. Routine edits do not require creating every file.