Design System Interview
Design-system interview before new frontend builds or redesigns. Use for vague site/app/landing/dashboard requests, generic-looking UI, direction-setting, aesthetic choices, type/color/density decisions, and DESIGN-SYSTEM.md tokens.
Get the complete skill folder, including its scripts and reference files.
When to use this skill
Use Design System Interview when an AI agent needs a reusable SKILL.md workflow for this job: Design-system interview before new frontend builds or redesigns. Use for vague site/app/landing/dashboard requests, generic-looking UI, direction-setting, aesthetic choices, type/color/density decisions, and DESIGN-SYSTEM.md tokens.
When not to use it
Skip Design System Interview when the task is outside the creativity category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/design-system-interview # Save SKILL.md to ~/.claude/skills/design-system-interview/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/design-system-interview/SKILL.md. For a shared project, commit the folder at .claude/skills/design-system-interview/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Design System Interview skill for this task: Use Design System Interview when this documented workflow matches the task. Confirm any required inputs or files before making changes.
What supports this recommendation?
69/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 77/100
- Practical detail
- 68/100
- Source evidence
- 52/100
- Source signals
- 72/100
Model compatibility evidence
- claudeuntested
No model-specific signal or recorded compatibility test was found.
- chatgptuntested
No model-specific signal or recorded compatibility test was found.
- geminiuntested
No model-specific signal or recorded compatibility test was found.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
# 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 interview. For urgent internal work, offer a short approval pass. In a one-shot/interrupted run, save the decision snapshot and first resume question; assumptions are not approval.
## Decisions
Use adaptively; `references/interview-contract.generated.md` is canonical session/dimension authority. Examples teach format, never taste.
| Canonical ID | Close with | | --- | --- | | `reference` | a real artifact and what it earns | | `personality` | a chosen pole, not a middle | | `aesthetic` | one concrete phrase predicting hierarchy/material | | `type` | binding evidence, display/body stance, language/measure risk | | `color_mode` | dominant hue, accent job, and light/dark commitment | | `density_shape` | density, numeric radius range, elevation | | `structure_rhythm` | composition, motif, and sectional cadence | | `signature` | one memorable move | | `imagery_iconography` | source/treatment or absence; one icon system |
Optionally set motion level.
## User receives
Write `DESIGN-SYSTEM.md` from `assets/DESIGN-SYSTEM.template.md`, then give an approvable build handoff:
1. **Direction:** sentence predicting the interface. 2. **Decisions:** completed decision map. 3. **Refusals:** three to five defaults this product will not use. 4. **Build contract:** semantic tokens, structural rhythm, responsive/accessibility constraints. 5. **Next move:** first implementation step, or exact blocker and owner.
Read `references/session-protocol.md` for readiness/resume rules.
```markdown | Dimension / conflict | Evidence | Decision or assumption | Consequence | Confirmation / owner | | --- | --- | --- | --- | --- | | Alert hierarchy | ... | committed / assumed / blocked | ... | ... | ```
Use `approved` only when confirmed and buildable. Use `approval-ready` when recommendations and tokens await confirmation; do not hand it to implementation. Use `blocked` when contradiction or missing authority prevents a safe recommendation. Cite non-obvious choices; each token needs a real build job.
``` The committed direction in one line: "<source-derived aesthetic phrase> — <chosen hierarchy>, <color role>, <type stance>, <shape/density>, signature = <specific move>." ```
Hand hue to `color-system`, type to `web-typography`, modes to `theming`, tokens to implementation skills, and the spec to `deslop-ui`. Keep one `DESIGN-SYSTEM.md` source of truth.
## Reference files
- `references/interview-bank.md` — forks and abstention. - `references/structure-and-rhythm.md` — composition/rhythm. - `references/tokens.md` — token architecture. - `references/decision-records.md` — novel cases. - `references/session-protocol.md` — shortcut, contradiction, resume. - `references/interview-contract.generated.md` — generated authority.
## Ready-to-build check
Report rows with direct evidence, reason, remediation, and `pass`/`fail`/`n/a`.
| Check | Status | Evidence / provenance | Reason | Remediation | | --- | --- | --- | --- | --- | | Nine required dimensions decided | | | | | | Existing-direction shortcut or full interview justified | | | | | | Contradictions and trust-critical rationale resolved | | | | | | DESIGN-SYSTEM.md and canonical token block complete | | | | | | Downstream handoff is explicit | | | | |
Build-ready requires every row passing and artifact `approved`. `approval-ready` or `blocked` is a resumable checkpoint: name unresolved owner and next confirmation; do not start implementation. Deliver one-line direction, link artifact, then state next action.
<!-- contract:v1:start --> ## Contract (generated)
Canonical detail: [contract.json](contract.json).
- Route: A new interface or redesign lacks a committed visual direction (+1 in contract.json); avoid: An existing site has sufficient evidence to improve without a new direction interview (+1 in contract.json) - Exclude: Do not begin implementation before direction is resolved or explicitly assumed (+1 in contract.json) - Stop / handoff: Pause when contradictory or trust-critical direction is unresolved (+1 in contract.json); receives [none] -> sends [art-direction, color-system, component-states, data-viz, deslop-ui, empty-states, form-ux, humanize-copy, micro-motion, responsive-layout, spacing-system, tasteroll, theming, web-typography] - Output: A decision-complete design-system artifact with explicit assumptions and readiness state - Evidence: `table_with_evidence` with `status`, `reason`, `remediation`, `evidence`, `provenance`. <!-- contract:v1:end -->
Intended uses
- Use Design System Interview when this documented workflow matches the task.
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.