hegemonart
hegemonart/get-design-done
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/hegemonart/get-design-done --skill using-gdd命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Master design pipeline for Claude Code. 5-stage workflow: Brief → Explore → Plan → Design → Verify. Run 'brief' first in any new project to capture the design problem, then 'explore' to inventory the codebase and interview for context. Invoke without arguments for status and auto-routing.
Run the pipeline with optional agents skipped for speed. Skips: phase-researcher, design-assumptions-analyzer, design-integration-checker. Keeps: planner, executor, verifier, auditor. Activates for requests involving a lightweight design pass, a fast iteration, or a quick low-ceremony change.
Routes a /gdd command to fast|quick|full path + S|M|L|XL complexity_class and returns {path, complexity_class, model_tier_overrides, resolved_models, estimated_cost_usd, cache_hits}. A SKILL.md prompt the model executes to emit a routing-decision JSON from rule tables (no separate agent spawn). Optional/advisory - invoked only by the skills that opt into routing; the budget-enforcer hook tolerates its absence. Read by hooks/budget-enforcer.ts.
基于 SOC 职业分类
正在显示 SKILL.md
| name | using-gdd |
| description | Use when starting any GDD session - establishes how to find and apply GDD skills. |
| disable-model-invocation | true |
This is the bootstrap discipline contract for every Get Design Done session. Read it first; it tells you how to find and apply the right GDD skill before you act.
If you think there is even a 1% chance a skill might apply, you ABSOLUTELY MUST invoke the skill.
In GDD, almost every request maps to a pipeline stage - brief, explore, plan, design, verify - or to a cross-cutting skill (discuss, audit, style, darkmode). When in doubt, search for and read the skill's body. The cost of reading a skill is trivial; the cost of free-handing a stage is rework, scope creep, and a broken pipeline state.
When you catch yourself thinking any of the following, STOP and check for a skill.
| Thought | Reality |
|---|---|
| This is just a simple design question. | Questions are tasks. Check for a skill. |
| I'll just tweak the CSS directly. | Token changes go through the pipeline - check /gdd:design. |
| I already know the codebase, skip explore. | Explore probes connections you haven't re-checked this cycle. |
| This change is too small to plan. | Plan-skipped tasks blow scope per cycle telemetry. Run /gdd:plan. |
| I can write the brief later. | No brief means no shared problem statement - /gdd:brief comes first. |
| The user clearly wants X, I'll skip discuss. | Ambiguity hides here. /gdd:discuss surfaces the real constraint. |
| I'll verify by eyeballing it. | Verification is a stage with criteria - run /gdd:verify, don't guess. |
| It's obviously a dark-mode tweak. | Color-scheme work has its own skill - check /gdd:darkmode. |
| Let me just compare these two designs quickly. | Comparison is an audit task - /gdd:compare has the rubric. |
| This is a one-off, no skill needed. | "One-off" is the most common rationalization in the telemetry. Check anyway. |
| I'll refactor the style tokens by hand. | /gdd:style owns token edits so the pipeline stays consistent. |
| The audit can wait until after I ship. | An un-audited cycle is an unverified cycle - /gdd:audit before close. |
When more than one skill could apply, resolve in this order:
Never run an Implementation skill before the Process skills that gate it have produced their artifact. Never declare a cycle complete without an Audit skill.
When instructions conflict, obey this precedence (highest first):
If a GDD skill contradicts the user's CLAUDE.md, the CLAUDE.md wins and you flag the conflict. If your instinct contradicts a GDD skill, the skill wins.
The core flow is Brief → Explore → Plan → Design → Verify, with branch points:
/gdd:brief). Branch: a rough idea can sketch or spike
off the brief before exploration; a changed problem loops back via --re-brief./gdd:explore) - even on a familiar
repo, because connections drift each cycle./gdd:plan). Skipping it is the top cause of scope
blow-up; small tasks still get a plan./gdd:design, with /gdd:style and /gdd:darkmode as
implementation peers). Implementation never runs ahead of an approved plan./gdd:verify), then /gdd:audit / /gdd:compare
close the loop. On pass the cycle completes; on fail it loops back to the failing stage./gdd:discuss runs alongside any stage to resolve ambiguity before it propagates.