Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →dkeken/product-design
Orchestrator for the Product Design skill set — turn early ideas into reviewable prototypes. Routes to the right sub-skill (get-context, research, audit, ideate, image-to-code, url-to-code, prototype, qa, share) based on where you are in the design process.
Passed 19 of 22 test cases with the skill, and 7 of 22 without it.
and 14 more in the full report
12 fixed7 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
We have built individual static screens for our registration flow (Welcome, Account Details, Verification, Confirmation). Now we need to make the flow clickable and wire button transitions between screens. Which sub-skill should handle this?
| Checked | Without skill | With skill |
|---|---|---|
| The interactivity wiring task is routed to design-prototype | Passed | Passed |
| The prototyping step is positioned after screen building and before QA gating | Missed | Passed |
The instructions your model reads when the skill loads.
The umbrella for the 9 design-* skills. Your job: read the request, locate it in the design process, route to the right sub-skill. Don't do the work here — dispatch. You're the design lead sequencing the work, not the IC executing each step.
creative-production orchestrator.FRAME EXPLORE BUILD SHIP
design-get-context ─► design-research ──► design-ideate ─► design-image-to-code ─┐
design-audit design-url-to-code ├─► design-prototype ─► design-qa ─► design-share
Frame the problem → explore options → build the chosen one → gate quality → ship for review.
| User intent / phrasing | Route to |
|---|---|
| new design task, brief unclear | design-get-context (almost always start here) |
| "how do others do X", competitor/pattern scan | design-research |
| "what's wrong with this UI", review existing | design-audit |
| "give me layout options/directions" | design-ideate |
| "build this mockup/screenshot" | design-image-to-code |
| "clone/rebuild this live site" | design-url-to-code |
| "make it clickable", "wire the flow" | design-prototype |
| "does it match the design/spec" | design-qa |
| "share it", "give me a link", "publish" | design-share |
./design/context.md already exists, start with design-get-context. The cheapest fix is the question asked before building.research/audit as needed, then ideate directions.image-to-code (from a mockup) or url-to-code (from a live site), then prototype to wire interactivity.design-qa before design-share. Don't ship HIGH-severity drift.context.md is the shared source of truth — every sub-skill reads it; keep it current.test cases passed, vs 7 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.