design-system-interviewlisted

# Design System Interview Turn a vague frontend brief into buildable decisions: study evidence, recommend a point of view, and ask only questions that materially change the build. ## Start with direction, not questionnaire Inspect product job, audience, content, marks, constraints, locales, and visual references before asking. Open with: ```markdown What I see: <the strongest signal in the brief> My recommendation: <a specific direction> Why it fits: <the product consequence> Choose: <fork A and trade-off> / <fork B and trade-off> / redirect me ``` Ask one high-consequence fork at a time; combine only when one answer settles several decisions. Reflect each answer in one line for correction without rereading. ## Interview loop 1. **Read the room.** Separate current evidence from residue. If an existing direction covers five dimensions, confirm it and ask only for gaps. 2. **Propose a fork.** Give two brief-compatible outcomes that look or behave materially differently. Recommend one and name its trade-off. 3. **Turn language into consequences.** Translate “clean,” “premium,” or “bold” into hierarchy, density, material, type, color, or rhythm; do not debate adjectives. 4. **Record the decision.** Mark `committed`, `assumption awaiting confirmation`, or `blocked by contradiction`, with supporting evidence. 5. **Stop when buildable.** All nine dimensions are decided, delegated, or blocked; then write artifact and handoff. Use 4–10 exchanges for a full inter