product-design-routerlisted

# Product design router Inspect durable artifacts and the running product before routing. ## 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-intake` before 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, route `emil-design-eng` as the f