From design-kit
Orchestrates the 4-stage design sprint pipeline. Stages 1-2 produce briefs and specs; Stages 3-4 dispatch to the active stack profile. Reads design-kit.config.json for stackProfile and confirmBeforeStages.
How this skill is triggered — by the user, by Claude, or both
Slash command
/design-kit:design-sprint-runnerThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Orchestrates a design sprint end-to-end.
Orchestrates a design sprint end-to-end.
Read confirmBeforeStages from design-kit.config.json (default: true).
true — pause at every stage transition. Print what was produced, then ask the user to review and confirm before the next stage begins. This is the default and recommended setting.false — run all stages end-to-end without pausing. Only use this for automated or CI workflows.At each pause, print:
Stage N complete. Artifacts written:
- <file-path>
- <file-path>
Review the files above, then reply "continue" (or "yes") to proceed to Stage N+1, or "stop" to save state and exit.
Do not proceed to the next stage until the user explicitly confirms.
data-analyst agent if GA4 or analytics are available.marketResearch from design-kit.config.json (default: "light"):
"off" — skip market researcher entirely."light" — invoke market-researcher in Stage 1 Contribution Mode (training knowledge only, no web search, 200 words max)."full" — invoke market-researcher with web search enabled for current competitive data.ux-designer in research mode (qualitative signals only — not full design work):
"Contribute the Qualitative Signals section to
01-data-intent.mdfor [project]. Focus on persona-grounded observations and user signals. This is research intake, not a full UX analysis — that comes in Stage 2."
<project-path>/01-data-intent.md with R fields stage: 1, project, intent_statement.01-data-intent.schema.json.STATUS.md → state: wip, last_stage: 01-data-intent.confirmBeforeStages: true: pause here. Ask user to review 01-data-intent.md before continuing.1.5. Stage 1.5 — Ideation (optional)
STATUS.md has ideation: done, skip without asking.brainstorming-design skill with this context:
"We're exploring design directions for [project]. Research intake is at
01-data-intent.md— read it for signals and competitive context. Explore the problem space, challenge assumptions, surface non-obvious directions, and help decide which approach to take before committing to a design brief." When brainstorming concludes, writeideation: donetoSTATUS.md. IfconfirmBeforeStages: true: pause here. Ask user to review explored directions before Stage 2.
ux-designer agent for user flows and edge cases.product-designer agent for business framing.<project-path>/02-brief.md (R: problem, target_users) AND <project-path>/02-design-spec.md (R: layout_pattern, components_needed).STATUS.md → state: spec-ready, last_stage: 02-design-spec.confirmBeforeStages: true: pause here. This is the critical review gate — the user should read 02-brief.md and 02-design-spec.md and confirm the design direction before any code is written. Make this explicit in the prompt.2.5. Stage 2.5 — Design Explore (diverge pass)
design-explore skill with the locked spec as input.design-explore command, dispatch to it to build cheap throwaway implementations in the browser (real DS components, no tests, no polish).<project-path>/02.5-design-explore.md with all options and (after user picks) ## Chosen Direction.confirmBeforeStages — direction selection requires human judgment. Ask: "Which direction (or hybrid) should we take into prototyping? You can also say 'revise the brief first'."02.5-design-explore.md.explorations/ throwaway files after direction is chosen.STATUS.md → state: explore-done, last_stage: 02.5-design-explore.design-kit.config.json → stackProfile.02.5-design-explore.md as context./design-kit-{stackProfile}:prototype <project-path>.STATUS.md → state: prototype-ready, last_stage: 03-prototype.confirmBeforeStages: true: pause here. Ask user to review the prototype before Stage 3.5.3.5. Stage 3.5 — Design Iterate (stakeholder review loop)
design-qa automatically on the prototype URL (if available).confirmBeforeStages — stakeholder sign-off is required before handoff.STATUS.md under ## Iteration Log with date and summary.design-qa after fixes.STATUS.md → state: review-approved, last_stage: 03.5-design-iterate./design-kit-{stackProfile}:handoff-prep <project-path>.04-handoff/ and updates STATUS.md → state: handed-off.If STATUS.md exists, resume from last_stage rather than starting over. The orchestrator decides:
wip → finish Stage 1 first, then check ideationwip + ideation: done → skip ideation, proceed to Stage 2spec-ready → run Stage 2.5 (design explore)explore-done → run Stage 3 (prototype)prototype-ready → run Stage 3.5 (design iterate / stakeholder review)review-approved → run Stage 4 (handoff prep)handed-off → ask the user if they want to re-run anythingBefore each stage, validate the prior stage's outputs against their schemas. If R-tier fields are missing, run a fix-loop: tell Claude what's missing, re-run the prior stage's agents to repair, then re-validate.
STATUS.md and exit gracefully.npx claudepluginhub anindhitavidia/design-agent-kit --plugin design-kitCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.