design-engineering-qualitylisted

# Design engineering quality Use this contract after product intent, interaction logic, and an approved design direction exist. It adds frontend craft; it does not invent product strategy or visual identity. ## Authority Read the approved design brief, directions, `DESIGN_SYSTEM.md`, token contract, and task criteria first. The project contract wins every conflict. External skills are perspectives, not authority, and their output still requires normal review and verification. ## Route the smallest capability Do not invoke the entire collection. Select one primary capability and at most one focused specialist unless the human explicitly requests broader exploration. For substantial design-critical web UI, `emil-design-eng` is the first external design implementation/refinement skill when installed. Do not start with Anthropic `frontend-design`; keep it secondary and opt-in. | Need | Route when installed | |---|---| | Substantial design-critical UI implementation or refinement | `emil-design-eng` | | Implement one justified animation | `animate` | | Strictly review animation code or a motion-heavy diff | `review-animations` — explicit only | | Audit existing animation quality and plan improvements | `improve-animations` | | Find a few missing purposeful motion opportunities | `find-animation-opportunities` | | Name or classify a motion pattern | `animation-vocabulary` | | Approved tactile, gesture, spring, material, or Apple-platform direction | `apple-design` | | Compare