What problem does it solve? When a product spec is complete but the visual direction is undefined, teams get vague requests like "make it premium" that designers and developers cannot execute. This Skill turns vague style preferences into a concrete, structured Design-Brief.md that design tools and coding agents can act on. ## Core Features & Use Cases - Structured Design Interview: Guides the user through a four-phase workflow (Startup, Interview, Translation, Output) using a 10-field discovery questionnaire, dimension checklists, and this-or-that choice strategies anchored to real reference products. - Visual Direction Presets: Offers five selectable style presets (Editorial Monocle, Modern Minimal, Warm Soft, Tech Utility, Brutalist Experimental) when the user cannot articulate a style. - Quality Gates: Enforces sufficiency judgment, an anti-AI-slop checklist, and an 8-item scoring rubric before the brief is finalized. - Use Case: After finishing a Product-Spec.md for a developer chat app, run the interview to lock mood keywords, color direction, information density, and state designs, then output a Design-Brief.md ready for mockup generation. ## Quick Start Ask the assistant to run /design-brief-builder to interview you about visual preferences and produce a Design-Brief.md from your existing Product-Spec.md.
