Design Context

Build the smallest reliable context brief needed to make consistent design decisions. Use this before substantial interface creation or redesign when the product intent is scattered, implicit, or missing.

Do not use it for a narrow visual critique when the product context is already clear. Do not invent brand strategy, research findings, or user needs.

Workflow

1. Inspect available copy, routes, components, tokens, screenshots, requirements, and prior design notes.
2. Separate confirmed evidence from assumptions. Ask only for missing choices that would materially change the design; otherwise state a bounded assumption and continue.
3. Capture the product and surface, primary users and job, desired action, content realities, brand character, constraints, patterns to preserve, problems to change, success signals, and unresolved decisions.
4. Convert vague adjectives into usable tensions. Explain what a phrase such as "premium but friendly" changes in type, density, color, imagery, and motion.
5. Produce a concise context brief. Update a canonical context file only when the user requested an edit.

Output

Return confirmed context, explicit assumptions, design implications, and open decisions. Keep the brief specific enough to guide later skills without turning it into a universal style specification.