motion-design
Motion Design
Animation serves four purposes. If it doesn't serve one of them, remove it.
How to use
/motion-designApply motion design constraints to this conversation.
Constraints
The Four Purposes
- Feedback (50-150ms): Confirms an action was received. Button press, toggle, form submit.
- Orientation (200-400ms): Shows spatial relationships. Sidebar slides in, modal scales from trigger.
- Emphasis (300-600ms): Draws attention. Notification pulse, new element fade-in. Rare and meaningful.
- Delight (variable): Emotional effect. Loading personality, completion celebration. Brief, skippable, never blocking.
- MUST categorize every animation by purpose. If it fits none, remove it.
Taste Signals in Motion
- Restraint. The best-animated interfaces are ones where you don't notice the animation.
- Consistent easing curves across the entire system.
- Physics-based movement (ease-out for arrival, ease-in for departure, never linear for UI).
- Duration proportional to purpose: more functional = faster.
Anti-Patterns
- Loading animations that last longer than the actual load
- Page transitions that delay content access
- Hover effects on every element (motion should guide attention, not create noise)
- Bouncy/elastic easing on functional elements (playful easing is for celebrations, not navigation)
- Motion for motion's sake
More from dragoon0x/taste-skills
visual-audit
The 10-second design audit. Look at any design and name what's working and what's not within seconds. Trains rapid pattern recognition for hierarchy, spacing, type, and color. Use when evaluating designs quickly, giving first-impression feedback, or building perception speed.
21taste-as-strategy
Use taste as a competitive moat and business advantage. In the AI and vibe-coding era, execution is commoditized. Taste is the defensible edge. Use when advising founders on product differentiation, building product culture, evaluating why some products win despite fewer features, or understanding taste as a strategic asset.
15teaching-taste
Help other designers develop judgment without imposing your style. Use when mentoring designers, running design education, or building team-wide quality standards.
15tradeoff-assessment
Name what was prioritized, what was sacrificed, and whether the tradeoff was right. Every design decision trades something. Use when evaluating design decisions, defending choices, or helping teams understand what they're giving up.
14field-notes
Structured taste breakdowns of real products. The format for making taste observations legible and shareable. Use when analyzing products, writing case studies, documenting design observations, or teaching through example.
14system-deconstruction
Break a design system into its constituent decisions and evaluate each one. Use when auditing design systems, evaluating consistency, or understanding how a product maintains quality at scale.
14