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:

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.