product-design-router
Skill1 starsChanged 2 months agoMITView on GitHub
Select the minimum valid product-design phases for substantial UI/UX work. Use for new products, ambiguous features, redesigns, inherited interfaces, agentic experiences, or frontend changes where discovery, strategy, system, implementation, audit, or critique readiness is uncertain.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- jiayuewangjavy/product-designer-skills-ostheir own version, first seen Oct 28, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- jiayuewangjavy/product-designer-skills-os★ 4same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository34 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- accessibility-auditSkill
- agentic-uxSkill
- benchmarkSkill
- capability-routerSkill
- codex-adapterSkill
- context-handoffSkill
- create-prdSkill
- creative-direction-sprintSkill
- decompose-prdSkill
- design-criticSkill
- design-engineering-qualitySkill
- design-intakeSkill
- design-opsSkill
- design-system-auditSkill
- design-systemSkill
- design-tokensSkill
- discoverSkill
- harness-evolutionSkill
- interaction-designSkill
- loop-engineeringSkill
- parallel-planSkill
- performance-uxSkill
- polishSkill
- project-onboardingSkill
- research-ledgerSkill
- responsive-auditSkill
- security-gateSkill
- self-improvement-loopSkill
- specialist-routerSkill
- strategizeSkill
- token-auditSkill
- user-needsSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 1 is distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
If .agentic/project-brief.json exists and product scope is still captured, start with project-onboarding.
- Very specific: line 43
When palette/type, generated-asset, or motion implementation needs are unresolved, run ./agentic design resources with the matching --need.
- Very specific: line 47
Before release: route applicable audits, performance-ux, independent design-critic, polish, and design-ops.
- Distinctive: line 49
Never rerun a phase merely because a skill exists.
- Very specific: line 57
Do not route canonical design-system or token changes while DESIGN_DIRECTIONS.md remains Needs approval.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Product design router
Inspect durable artifacts and the running product before routing.
If .agentic/project-brief.json exists and product scope is still captured,
start with project-onboarding. Resume saved answers; do not select a bundled
direction or implement a renamed reference app on the owner's behalf.
Phase order
discover → user-needs → benchmark → strategize → interaction-design → design-intake → design directions → human approval → design-system → design-tokens → component/Figma translation → implementation → live iteration → responsive/accessibility/system/token audits → performance-ux → design-critic → polish → design-ops → ship
Route by evidence
- Ambiguous 0→1 work: start with
discover. - Solution-focused requirements: add
user-needs. - Unfamiliar or strategically crowded category: add
benchmark. - Missing experience principles or differentiation: add
strategize. - Missing flows, states, feedback, failure, or recovery: add
interaction-design. - Agent/coprocessor behavior: add
agentic-ux. - Unclear brand, palette, type, density, geometry, motion, platform, or
accessibility constraints: add
design-intakebefore directions. - Missing product-specific aesthetic: create comparable directions, obtain
explicit human approval, then invoke
design-system. - Approved direction without reusable encoding: add
design-tokens. - Existing mature UI: inspect first; use extraction/documentation externally when available.
- Approved Figma: translate through Figma MCP/Code Connect when installed.
- Substantial design-critical implementation or refinement: add
design-engineering-quality; when Emil Kowalski's suite is installed, routeemil-design-engas the first external design implementation/craft pass and only the smallest relevant specialist. Do not start implementation with Anthropicfrontend-design. - Existing implementation refinement: skip upstream phases that remain valid; iterate live.
- Motion work: route the exact motion capability only after purpose, interruption, performance, and reduced-motion behavior are clear. “Do not animate” is a valid result.
- When palette/type, generated-asset, or motion implementation needs are
unresolved, run
./agentic design resourceswith the matching--need. This read-only plan may route Realtime Colors, Haikei, or Motion Primitives; it never opens, submits, downloads, installs, or approves anything. - Before release: route applicable audits,
performance-ux, independentdesign-critic,polish, anddesign-ops.
Never rerun a phase merely because a skill exists. State:
- task type;
- evidence inspected;
- phases skipped and why;
- phases required and expected outputs;
- approval/evaluation gates.
Do not route canonical design-system or token changes while
DESIGN_DIRECTIONS.md remains Needs approval.
The project design system is authoritative. Anthropic frontend-design is one
optional input during design-direction exploration, never the default aesthetic.
It is secondary and opt-in; emil-design-eng is the preferred first external
design implementation skill for substantial design-critical web UI.
Emil Kowalski's external collection is an optional design-engineering craft
layer, not a replacement for discovery, strategy, approved directions, tokens,
accessibility, Playwright evidence, or the independent evaluator. Outside a fresh
custom or existing-brand creative-direction sprint, prototype,
pick-ui-library, and review-animations require explicit human invocation.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

