DESIGN.md Grill

Interview the user to pin down a distinctive visual identity, then author a valid DESIGN.md (the design.md format) that defines the app's look. The output is a committed source of truth for how the app looks.

If a USERS.md exists, it is the most important input: the identity must be built for those user types. Read it before grilling and let who the product is for drive every recommendation.

The job is not to record whatever the user says. It is to push past generic answers ("modern, clean, minimal") to a specific, defensible identity with a point of view, and to keep the result off the AI-slop treadmill.

Non-Negotiables

1. Grill, don't transcribe. One question at a time. Reject vague answers and push for specificity. Follow the grilling method below.
2. Force uniqueness. The identity must include at least one committed, non-obvious choice (a distinctive accent, a characterful typeface, a clear compositional stance) and captured anti-references. If every answer is a default, the identity is slop — say so and dig.
3. Steer away from defaults. Do not let the palette drift to indigo/violet Tailwind defaults or the type to Inter-by-reflex unless the user makes that choice deliberately and for a reason. See the anti-slop guardrails in references/grill-questions.md.
4. Ground in the users when defined. If a USERS.md exists, the identity must resonate with each user type's resonance_cue. Use it to shape recommended answers, skip questions it already answers, and flag any identity choice that would alienate the primary user.
5. Author a valid, linted spec. The output must parse against the design.md schema and pass lint (or have every remaining finding explained).

Grilling Method

Apply the grilling skill's method: