design-brief-builder

---

name: design-brief-builder description: Used when the user wants to define a design style or visual direction, or says something vague like 'I want a premium/sleek/modern look'. Guides the user through a design interview to clarify visual preferences and outputs Design-Brief.md. After Brief is saved, MUST run Next Step Gate and recommend /design-maker — do not silently end the design phase. version: 1.2.1 updated: 2026-06-21 requires: []

[Task] Through a designer-interviews-client approach, guide the user to define the product's visual direction and output a well-structured Design-Brief.md that can be used both by design tools and by dev-builder for coding.

[Not For] - Generating actual mockups or design files -> use /design-maker instead - Writing code -> use /dev-builder instead - Defining product features -> use /product-spec-builder instead

[Dependency Check] Automatically executed as the first step when the Skill starts:

Required:
- Product-Spec.md → If missing, prompt the user to call /product-spec-builder first

Optional (fallback mode):
- Design tool MCP → If not connected, mark as "manual design mode". The Design Brief is still generated, and the user feeds it to the design tool on their own.

[First Principles] Brief 前必读 references/first-principles.md

[Shared Discipline] Karpathy 四原则 → ../_shared/karpathy-discipline.md（Web-First / 不猜）

[Output Style] → references/output-style.md（设计师访谈人格）

[File Structure] design-brief-builder/ ├── SKILL.md ├── commands/design-brief-builder.md ├── templates/design-brief-template.md └── references/ ├── first-principles.md ├── output-style.md ├── workflow.md # 四阶段完整流程（必读） ├── interview-dimension-checklist.md ├── interview-strategies.md ├── sufficiency-judgment.md ├── design-discovery-questionnaire.md ├── visual-direction-presets.md ├── anti-ai-slop-checklist.md └── anti-rationalization.md ../_shared/

[Gotchas] Open-ended questions instead of choices: Always give concrete options (Linear or Notion? Dark or light?). Relying on memory for design trends: WebSearch before recommending. Skipping accessibility: Contrast, hierarchy, touch targets belong in Brief. Copying without thinking: Adapt reference products; don't clone blindly. Missing refinement preference: Ask whether the user wants a single delivery or graduated tiers (layout → interaction → edge cases). Gradual refinement catches structural issues early when they're cheap to fix. No-UI products: If Product-Spec has no UI Layout / API-only / library — do not run full interview or mockup Gate; see references/surface-routing.md.

[Anti-Rationalization Checklist] → references/anti-rationalization.md 遇 skipping interview / skipping WebSearch 等场景时读取。

[Output Artifacts] - Design-Brief.md — Design specification document containing mood direction, color direction, information density, interaction style, etc. - .forge/design-next-step.json — User's post-Brief choice (mockup / skip / planner-first); required before closing session when not invoking design-maker immediately

[Next Step Gate — HARD-GATE] Brief 落盘后 MUST 先读 references/surface-routing.md： - 无 UI（C 类） → 不跑 Gate；design-next-step.json + 推荐 /dev-planner - 有 UI（A 类） → 执行 references/next-step-gate.md（三选一，推荐 mockup） - 轻 CLI（B 类） → 简化 Gate，不推荐 design-maker