skills/design/references/brief.md

# Project design brief

Use for `setup` or when the project needs durable design context. Create `.design/brief.md`; merge with existing content rather than replacing valid decisions.

Include only known facts and clearly labeled assumptions:

- Product name and category.
- Target users and the pressures they face.
- Primary jobs and critical task flows.
- Core domain artifacts and credible proof.
- Brand character, voice, imagery, and explicit anti-goals.
- Required content and routes.
- Existing visual assets, tokens, components, and stack constraints.
- Accessibility, localization, browser/device, and performance requirements.
- Decisions already made, open questions, and dated rationale.

Keep it concise enough to reread before every design pass. Do not invent research findings, brand rules, metrics, or user preferences. If a missing decision truly changes product scope, ask only that decision.