design-intakelisted

# Design intake Do not ask the user to design the token system. Gather intent and constraints, then translate them into reviewable directions. ## Route the intake - Existing brand: inventory exact assets, licensed fonts, colors, Figma sources, restrictions, and the authority that may approve changes. Preserve exact brand inputs; do not approximate them from screenshots. - Greenfield design-critical product: collect preferences, research references, and produce two or three materially different directions. - Redesign: inspect the running product and current tokens first. Separate what must remain compatible from what may change, and capture baseline evidence. - Design is not a competitive advantage: use one restrained accessible baseline; skip expressive questions and unnecessary alternatives. Read `.agentic/project.json` and ask only about active platforms. Do not ask mobile questions for a web-only product or require a Figma workflow when Figma is not part of the project. ## Interview adaptively Ask one to three short groups at a time. Do not make every question mandatory. Resolve, in this order: 1. **Authority and mode** — existing brand, greenfield, or redesign; approver; fixed assets and non-negotiable constraints. 2. **Experience intent** — audience, task, context, desired feelings, density, and qualities the product must avoid. 3. **Color constraints** — exact existing colors or preferred/forbidden hue families, neutral temperature, restrained/