design-engineering

# design-engineering > This skill is a graph, not a file. The body below is the **Map of Content**. Follow the `[[wikilinks]]` only as needed — that's the whole point of progressive disclosure. ## How to use this skill 0. `/design-engineering` is a router before it is a library: `[[skill-router]]` resolves the design contract, classifies the phase (undecided → build → refine → check → name), and hands the job to one owner — a node here, a subagent, or an installed companion skill (AgentsORG `design`, impeccable, HyperFrames, ElevenLabs, transitions-dev, the shadcn CLI). One or two owners, never five. 1. Route first: `[[routing-table]]` maps intent → entry node for most single questions. If two intents blur, `[[disambiguation]]` names the tiebreaker. Multi-cluster jobs follow `[[stacking-chains]]`. 2. Otherwise scan the MOCs below, pick the cluster, and open its `MOC-*.md` for the atomic nodes under it. 3. Read only the atomic nodes that match. Each node is standalone — you don't need siblings. 4. Before reviewing UI code, also load `[[gotchas]]` and `[[pov]]`. If the user asks for a UI code review, use the format defined in `[[review-format]]` and scan against `[[review-checklist]]`. ## Philosophy — when, where, and why polish matters How to think about taste, delight, and the difference between marketing and product UI. - `[[MOC-philosophy]]` → [[taste-is-trained]], [[unseen-details-compound]], [[beauty-is-leverage]], [[delight-impact-curve]], [[feeling-right]], [[mar...