design-motionlisted

# design-motion Motion is not decoration applied after the design. It is how the interface explains itself: where things came from, what is connected to what, and whether the product heard you. Two rules sit above everything else here: 1. **Motion answers a question or it does not ship.** Where did this come from, where did it go, did my action register, what changed, what is connected. Animation that answers nothing is latency you added on purpose. 2. **The user's time is not yours to spend.** Every animation is a delay you chose. A transition seen twice is delightful. The same transition seen four hundred times is a tax. ## Engine ```bash DS=$(ls "${CLAUDE_PLUGIN_ROOT:-/nonexistent}/engine/dstack.py" "$HOME/.claude/dstack/engine/dstack.py" 2>/dev/null | head -1) python3 "$DS" "<symptom>" --motion # search 80 motion practices python3 "$DS" --categories --motion # list motion categories python3 "$DS" --audit --motion # full motion checklist by severity python3 "$DS" --audit --motion -c performance # one area ``` Categories: timing, easing, choreography, interaction-feedback, scroll, page-transitions, gestures, performance, accessibility-motion, text-animation, layout-animation, video-pacing, remotion, audio-sound, export-delivery. Query before you write a duration or a curve. The numbers in the base are the point of this skill. --- ## The defaults, memorized You should not have to look these up. Everything else, query. **Duration