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

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]].
Otherwise scan the MOCs below, pick the cluster, and open its MOC-*.md for the atomic nodes under it.
Read only the atomic nodes that match. Each node is standalone — you don't need siblings.
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]], [[marketing-vs-product-ui]], [[states-are-the-work]], [[data-is-content]], [[dependency-discipline]], [[pointing-beats-describing]], [[articulate-precisely]]