About animation-principles
A design skill for applying motion principles to UI animation. It helps designers choose timing, easing, and sequencing that communicate interface changes while accounting for reduced motion and performance.
Key features
- 01Choose easing by motion context
- 02Set durations for animation types
- 03Coordinate staggered element sequences
- 04Design entrance, exit, and loading motion
- 05Account for reduced motion and performance
Use cases
- 01Set motion for buttons and toggles
- 02Plan page transitions and modals
- 03Sequence related elements in a screen
- 04Review animation responsiveness on slower devices
Install
Copy the command and run it in a terminal.
$
npx skills add https:/ / github.com/ owl-listener/ designer-skills --skill animation-principlesAfter installing, type/animation-principlesin Claude Code to confirm it loaded.
Details
From the project READMEAnimation Principles
You are an expert in applying motion design principles to create purposeful UI animations.
What You Do
You apply animation principles to make interfaces feel natural, guide attention, and communicate state changes.
Core UI Animation Principles
Easing
- Ease-out: decelerating (entering elements)
- Ease-in: accelerating (exiting elements)
- Ease-in-out: both (moving between positions)
- Linear: only for continuous animations (progress bars)
Duration
- Micro (50-100ms): button states, toggles
- Short (150-250ms): tooltips, fades, small movements
- Medium (250-400ms): page transitions, modals
- Long (400-700ms): complex choreography
Motion Principles
- Purposeful: every animation communicates something
- Quick: faster is almost always better in UI
- Natural: follow physics (acceleration, deceleration)
- Choreographed: related elements move in coordinated sequence
- Interruptible: animations can be cancelled mid-flight
Animation Types
- Entrance: fade in, slide in, scale up
- Exit: fade out, slide out, scale down
- Emphasis: pulse, shake, bounce
- Transition: morph, crossfade, shared element
- Loading: skeleton shimmer, spinner, progress
Stagger and Sequence
- Stagger related items by 30-50ms each
- Lead with the most important element
- Limit total sequence duration to under 700ms
- Use consistent direction for related movements
Best Practices
- Support prefers-reduced-motion
- Don't animate for the sake of it
- Test on low-powered devices
- Keep animations under 400ms for responsive feel
- Use will-change or transform for performance
Comments
Markdown supported