mcpField
C
css-animation-patterns

css-animation-patterns

github.com/oakossDesign & UI20179 installsUpdated 10w ago
Repository

About css-animation-patterns

A reference skill for building CSS interface motion with transitions, keyframes, scroll-driven animations, and view transitions. It emphasizes composited-property performance, reduced-motion accessibility, and fallbacks for newer APIs.

Key features

  1. 01Transitions and keyframe animations
  2. 02Scroll- and view-driven timelines
  3. 03SPA and MPA view transitions
  4. 04Compositor-focused performance guidance
  5. 05Reduced-motion handling and fallbacks

Use cases

  1. 01Animate interface state changes
  2. 02Create scroll-linked reveal effects
  3. 03Add animated page or route transitions
  4. 04Build motion-aware loading indicators

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/oakoss/agent-skills --skill css-animation-patterns

After installing, type/css-animation-patternsin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

references/
scroll-driven.md
transforms-and-performance.md
transitions-and-keyframes.md
view-transitions.md

Details

From the project README

CSS Animation Patterns

Overview

CSS animations and transitions provide hardware-accelerated motion for web interfaces using keyframes, transitions, transforms, and modern scroll-driven and view transition APIs. Animate only composite properties (transform, opacity, filter) for smooth 60fps performance, and always respect prefers-reduced-motion.

The browser rendering pipeline has four stages: Style, Layout, Paint, and Composite. Animating composite-only properties skips Layout and Paint entirely, running on the GPU compositor thread. This is the single most important performance principle for CSS animation.

Modern CSS adds two powerful APIs: scroll-driven animations link keyframe progress to scroll position or element visibility instead of time, and the View Transitions API creates snapshot-based animated transitions between DOM states for both SPAs and MPAs.

When to use: Element state changes, page transitions, scroll-linked effects, loading indicators, micro-interactions, route change animations, reveal-on-scroll patterns, parallax effects, progress indicators tied to scroll.

When NOT to use: Complex physics simulations (use a JS animation library), canvas/WebGL rendering, animations requiring frame-by-frame scripted control (use Web Animations API directly), highly interactive drag-and-drop (use pointer events with JS).

Browser Support Summary

FeatureChromeFirefoxSafari
Transitions, keyframes, transformsFullFullFull
Individual transform properties104+72+14.1+
@starting-style117+129+17.5+
transition-behavior: allow-discrete117+129+17.4+
Scroll-driven animations115+Not yet26+
Same-document view transitions111+144+18+
Cross-document view transitions126+Not yet18+
view-transition-class125+144+18+

Use @supports for progressive enhancement with newer features. Always provide a functional non-animated fallback.

Quick Reference

PatternAPIKey Points
State transitiontransition: property duration easingTriggers on property change, composite-only for performance
Discrete transitiontransition-behavior: allow-discreteEnables transitions on display, visibility
Entry animation@starting-style { ... }Initial state for elements appearing in DOM
Keyframe animation@keyframes name + animation shorthandMulti-step sequences, supports forwards fill mode
Transformtransform: translate() scale() rotate()GPU-composited, no layout recalculation
Individual transformstranslate, rotate, scaleIndependently animatable with different timings
Scroll progressanimation-timeline: scroll()Links animation to scroll position of a container
View progressanimation-timeline: view()Links animation to element visibility in scrollport
Animation rangeanimation-range: entry 0% entry 100%Controls which timeline segment drives animation
Named scroll timelinescroll-timeline-name + scroll-timeline-axisReusable scroll timeline across elements
Named view timelineview-timeline-name + view-timeline-axisReusable view timeline for visibility tracking
View transition (SPA)document.startViewTransition(callback)Snapshot-based animated DOM updates
View transition (MPA)@view-transition { navigation: auto }Cross-document transitions, same-origin only
Transition namingview-transition-name: heroIdentifies elements for independent transition groups
Transition classesview-transition-class: cardGroups named elements for shared transition styles
Transition typesstartViewTransition({ types: [...] })Conditional styling based on navigation direction
GPU hintwill-change: transformPromotes element to compositor layer, use sparingly
Motion preference@media (prefers-reduced-motion: reduce)Disable or simplify animations for accessibility
Custom easingcubic-bezier() or linear()Fine-tuned timing curves, linear() for multi-point easing
Step easingsteps(n, jump-term)Frame-by-frame discrete animation
Animation compositionanimation-composition: accumulateControls how multiple animations combine on same property
Staggered delayanimation-delay: calc(var(--i) * 60ms)Per-element delay using CSS custom properties
Render containmentcontain: layout styleIsolates rendering scope for better animation perf
Content visibilitycontent-visibility: autoSkips rendering of off-screen content

Common Mistakes

MistakeCorrect Pattern
Animating width, height, top, leftUse transform: translate() and scale() for layout-free animation
Adding will-change to every elementApply only to elements that animate frequently, remove after animation
Missing prefers-reduced-motion handlingWrap motion in @media (prefers-reduced-motion: no-preference)
Using translateZ(0) hack everywhereUse will-change instead, and only when needed
Declaring animation-timeline before animation shorthandDeclare animation-timeline after animation (shorthand resets it to auto)
Setting animation-duration for scroll-driven animationsDuration is scroll-controlled; use auto or omit, set 1ms for Firefox compat
Forgetting view-transition-name must be uniqueEach participating element needs a distinct name per page snapshot
Not providing fallbacks for scroll-driven animationsUse @supports (animation-timeline: scroll()) for progressive enhancement
Animating background-color expecting GPU compositingOnly transform, opacity, and filter are reliably GPU-composited
Using transition: allSpecify exact properties to avoid unexpected transitions and performance hits
Interleaving DOM reads and writes in JS animationsBatch reads first, then writes, or use requestAnimationFrame
Not using flushSync with React view transitionsReact batches updates; wrap navigate() in flushSync inside the callback
Calling startViewTransition without feature checkAlways guard with if (!document.startViewTransition) fallback

Delegation

  • Animation implementation: Use Explore agent to discover patterns in reference files
  • Performance audit: Use Task agent to review animation performance across components
  • Accessibility review: Use Task agent to verify prefers-reduced-motion coverage
  • Code review: Delegate to code-reviewer agent for animation-related PR reviews

If the ux-designer skill is available, delegate visual motion design decisions to it. Otherwise, recommend: npx skills add oakoss/agent-skills --skill ux-designer

References

Comments

Markdown supported