Skip to main content
skill CX Codex

animation-principles · owl-listener — Claude Code skill for UI motion

A skill that tunes one specific UI animation: picks easing, duration and the order in which related elements move.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add Owl-Listener/designer-skills --skill animation-principles -a claude-code
Open on GitHub

What animation-principles does

This skill fixes a single animation rather than a whole motion system. It walks through the principles: easing for entering, exiting and moving elements, duration by the scale of the change, and the sequence for related elements. Entering elements take ease-out, exiting ones ease-in, and linear is reserved for progress bars. Durations come in bands: 50–100 ms for button states and toggles, 150–250 ms for tooltips and small shifts, 250–400 ms for modals and page transitions, 400–700 ms for complex choreography.

Grouped elements get their own rhythm. Stagger neighbours by 30–50 ms, lead with the most important one, and keep the whole sequence under 700 ms. Related movements should share a direction. Animations are meant to be interruptible, since they can be cancelled mid-flight.

The skill advises supporting prefers-reduced-motion and testing on a low-powered device. For performance it points to will-change or transform. Product-wide duration and easing tokens are a different job — that is motion-system from design-systems, and a full interaction spec belongs to micro-interaction-spec. Reach for this one when a particular transition stutters or feels sluggish.

What it helps with

  • pick an easing curve for an element entering or leaving
  • keep a transition duration inside a sensible band
  • sequence a list of cards as they appear
  • make an animation cancellable mid-flight
  • support prefers-reduced-motion in a transition

Example prompts for the agent

  • tune the modal entrance: easing, duration and element order
  • this page transition feels sluggish — review it against the animation principles
  • stagger the card list as it appears and check prefers-reduced-motion

How to install animation-principles

1Skills CLI (Vercel)

npx skills add Owl-Listener/designer-skills --skill animation-principles -a claude-code

2Manually: put the files in place

~/.claude/skills/animation-principles/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/animation-principles/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about animation-principles

How do I install animation-principles in Claude?

Run npx skills add Owl-Listener/designer-skills --skill animation-principles -a claude-code. The skill lands at ~/.claude/skills/animation-principles/SKILL.md.

What does animation-principles do?

It applies animation principles — easing, duration, staging, follow-through — to one specific UI motion. Use it when tuning how an animation feels.

How is animation-principles different from motion-system?

animation-principles handles a single animation. For product-wide duration and easing tokens use motion-system from design-systems, and for a full interaction spec use micro-interaction-spec.

Source text

SKILL.md · MIT
---
name: animation-principles
description: Apply animation principles — easing, staging, follow-through — to one specific UI motion. Use when tuning how an animation feels. For product-wide duration and easing tokens use `motion-system` (design-systems); for a full interaction spec use `micro-interaction-spec`.
---
# Animation 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

© Owl-Listener · MIT · Owl-Listener/designer-skills

Similar skills

Everything for Design →

animation-principles by other authors comes first.

From the same set109

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor