Skip to content
cccskills
FreePublished on GitHub

animation-principles

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`.

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md1.9 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Design an A/B experiment — hypothesis, variants, primary metric, and sample size. Use when a change can be measured quantitatively at scale. For observing behaviour qualitatively, use `test-scenario`.

The English summary is being prepared. Showing the original description.

Owl-Listener/designer-skills3KUpdated Sep 6, 2026

Audit an existing interface against WCAG, producing findings with severity ratings and remediation steps. Use when you have a design or build to assess now. Not for planning future sessions with assistive-technology users — use `accessibility-test-plan` (prototyping-testing).

The English summary is being prepared. Showing the original description.

Owl-Listener/designer-skills3KUpdated Sep 6, 2026

Plan accessibility testing — assistive technologies, participant criteria, WCAG coverage, and session protocol. Use when scheduling testing with real AT users. Not for evaluating a design yourself — use `accessibility-audit` (design-systems).

The English summary is being prepared. Showing the original description.

Owl-Listener/designer-skills3KUpdated Sep 6, 2026

Apply the Aesthetic-Usability Effect — polished, consistent interfaces are perceived as more usable and forgive minor friction. Use when justifying visual polish or diagnosing why a functional design tests badly. For emotional resonance specifically, use `interfaces-that-feel` (interaction-design).

The English summary is being prepared. Showing the original description.

Owl-Listener/designer-skills3KUpdated Sep 6, 2026

Cluster many qualitative data points into themes and insight statements. Use when synthesising across multiple sessions or sources. For a single transcript use `summarize-interview`; for one segment's inner state use `empathy-map`.

The English summary is being prepared. Showing the original description.

Owl-Listener/designer-skills3KUpdated Sep 6, 2026

Read funnels, retention curves, and event data as a designer — separating a design problem from a tracking artefact. Use when handed product data you did not design and asked why people drop off. For choosing what to measure, use `metrics-definition` (ux-strategy); for running a controlled test, use `a-b-test-design` (prototyping-testing).

The English summary is being prepared. Showing the original description.

Owl-Listener/designer-skills3KUpdated Sep 6, 2026

See all skills by Owl-Listener

Report a problem with this skill