Animation & Motion Design
Patterns for building performant, accessible animations using Motion (formerly Framer Motion, 18M+ weekly npm downloads) and the View Transitions API (cross-browser support in 2026). Covers layout animations, gesture interactions, exit transitions, micro-interactions, and motion accessibility.
Quick Reference
| Rule |
File |
Impact |
When to Use |
| Layout Animations |
rules/motion-layout.md |
HIGH |
Shared layout transitions, FLIP animations, layoutId |
| Gesture Interactions |
rules/motion-gestures.md |
HIGH |
Drag, hover, tap with spring physics |
| Exit Animations |
rules/motion-exit.md |
HIGH |
AnimatePresence, unmount transitions |
| View Transitions API |
rules/view-transitions-api.md |
HIGH |
Page navigation, cross-document transitions |
| Motion Accessibility |
rules/motion-accessibility.md |
CRITICAL |
prefers-reduced-motion, cognitive load |
| Motion Performance |
rules/motion-performance.md |
HIGH |
60fps, GPU compositing, layout thrash |
Total: 6 rules across 3 categories
Decision Table — Motion vs View Transitions API
| Scenario |
Recommendation |
Why |
| Component mount/unmount |
Motion |
AnimatePresence handles lifecycle |
| Page navigation transitions |
View Transitions API |
Built-in browser support, works with any router |
| Complex interruptible animations |
Motion |
Spring physics, gesture interruption |
| Simple crossfade between pages |
View Transitions API |
Zero JS bundle cost |
| Drag/reorder interactions |
Motion |
drag prop with layout animations |
| Shared element across routes |
View Transitions API |
viewTransitionName CSS property |
| Scroll-triggered animations |
Motion |
useInView, useScroll hooks |
| Multi-step orchestrated sequences |
Motion |
staggerChildren, variants |
Quick Start
Motion — Component Animation
import { motion, AnimatePresence } from "motion/react"
const fadeInUp = {
initial: { opacity: 0, y: 20 },
animate: { opacity: 1, y: 0 },
exit: { opacity: 0, y: -10 },
transition: { type: "spring", stiffness: 300, damping: 24 },
}
function Card({ item }: { item: Item }) {
return (
<motion.div {...fadeInUp} layout layoutId={item.id}>
{item.content}
</motion.div>
)
}
function CardList({ items }: { items: Item[] }) {
return (
<AnimatePresence mode="wait">
{items.map((item) => (
<Card key={item.id} item={item} />
))}
</AnimatePresence>
)
}
View Transitions API — Page Navigation
// React Router v7+ with View Transitions
import { Link, useNavigate } from "react-router"
function NavLink({ to, children }: { to: string; children: React.ReactNode }) {
return <Link to={to} viewTransition>{children}</Link>
}
// CSS for the transition
// ::view-transition-old(root) { animation: fade-out 200ms ease; }
// ::view-transition-new(root) { animation: fade-in 200ms ease; }
Motion — Accessible by Default
import { useReducedMotion } from "motion/react"
function AnimatedComponent() {
const shouldReduceMotion = useReducedMotion()
return (
<motion.div
animate={{ x: 100 }}
transition={shouldReduceMotion
? { duration: 0 }
: { type: "spring", stiffness: 300, damping: 24 }
}
/>
)
}
Rule Details
Layout Animations (Motion)
FLIP-based layout animations with the layout prop and shared layout transitions via layoutId.
Load: rules/motion-layout.md
Gesture Interactions (Motion)
Drag, hover, and tap interactions with spring physics and gesture composition.
Load: rules/motion-gestures.md
Exit Animations (Motion)
AnimatePresence for animating components as they unmount from the React tree.
Load: rules/motion-exit.md
View Transitions API
Browser-native page transitions using document.startViewTransition() and framework integrations.
Load: rules/view-transitions-api.md
Motion Accessibility
Respecting user motion preferences and reducing cognitive load with motion sensitivity patterns.
Load: rules/motion-accessibility.md
Motion Performance
GPU compositing, avoiding layout thrash, and keeping animations at 60fps.
Load: rules/motion-performance.md
Key Principles
- 60fps or nothing — Only animate
transform and opacity (composite properties). Never animate width, height, top, or left.
- Centralized presets — Define animation variants in a shared file, not inline on every component.
- AnimatePresence for exits — React unmounts instantly; wrap with AnimatePresence to animate out.
- Spring over duration — Springs feel natural and are interruptible. Use
stiffness/damping, not duration.
- Respect user preferences — Always check
prefers-reduced-motion and provide instant alternatives.
Performance Budget
| Metric |
Target |
Measurement |
| Transition duration |
< 400ms |
User perception threshold |
| Animation properties |
transform, opacity only |
DevTools > Rendering > Paint flashing |
| JS bundle (Motion) |
~16KB gzipped |
Import only what you use |
| First paint delay |
0ms |
Animations must not block render |
| Frame drops |
< 5% of frames |
Performance API: PerformanceObserver |
Anti-Patterns (FORBIDDEN)
- Animating layout properties — Never animate
width, height, margin, padding directly. Use transform: scale() instead.
- Missing AnimatePresence — Components unmount instantly without it; exit animations are silently lost.
- Ignoring prefers-reduced-motion — Causes vestibular disorders for ~35% of users with motion sensitivity.
- Inline transition objects — Creates new objects every render, breaking React memoization.
- duration-based springs — Motion springs use
stiffness/damping, not duration. Mixing causes unexpected behavior.
- Synchronous startViewTransition — Always await or handle the promise from
document.startViewTransition().
Detailed Documentation
| Resource |
Description |
| references/motion-vs-view-transitions.md |
Comparison table, browser support, limitations |
| references/animation-presets-library.md |
Copy-paste preset variants for common patterns |
| references/micro-interactions-catalog.md |
Button press, toggle, checkbox, loading, success/error |
Related Skills
ork-extras:ui-components — shadcn/ui component patterns and CVA variants
ork-extras:responsive-patterns — Responsive layout and container query patterns
ork:performance — Core Web Vitals and runtime performance optimization
ork-extras:accessibility — WCAG compliance, ARIA patterns, screen reader support
1---2name: animation-motion-design3license: MIT4compatibility: "Claude Code 2.1.277+."5description: Animation patterns with Motion (formerly Framer Motion) and the View Transitions API. Use when implementing component animations, page transitions, micro-interactions, gesture-driven UIs, or prefers-reduced-motion support.6user-invocable: false7targets:8 - library: motion9 version: ">=13.4.6"10metadata:11 source: https://skillmd.com/skills/yonatangross/animation-motion-design12 owner-agent: "frontend-ui-developer"13 category: document-asset-creation14 version: "1.0.0"15 author: "OrchestKit"16 complexity: "medium"17 tags: "animation, motion, framer-motion, view-transitions, micro-interactions, gestures, layout-animation, AnimatePresence, prefers-reduced-motion, spring-physics"18allowed-tools: "Read Glob Grep WebFetch WebSearch"19path_patterns: ["**/animation/**", "**/motion/**", "*.motion.*", "*.framer.*"]20---2122# Animation & Motion Design2324Patterns for building performant, accessible animations using **Motion** (formerly Framer Motion, 18M+ weekly npm downloads) and the **View Transitions API** (cross-browser support in 2026). Covers layout animations, gesture interactions, exit transitions, micro-interactions, and motion accessibility.2526## Quick Reference2728| Rule | File | Impact | When to Use |29|------|------|--------|-------------|30| Layout Animations | `rules/motion-layout.md` | HIGH | Shared layout transitions, FLIP animations, layoutId |31| Gesture Interactions | `rules/motion-gestures.md` | HIGH | Drag, hover, tap with spring physics |32| Exit Animations | `rules/motion-exit.md` | HIGH | AnimatePresence, unmount transitions |33| View Transitions API | `rules/view-transitions-api.md` | HIGH | Page navigation, cross-document transitions |34| Motion Accessibility | `rules/motion-accessibility.md` | CRITICAL | prefers-reduced-motion, cognitive load |35| Motion Performance | `rules/motion-performance.md` | HIGH | 60fps, GPU compositing, layout thrash |3637**Total: 6 rules across 3 categories**3839## Decision Table — Motion vs View Transitions API4041| Scenario | Recommendation | Why |42|----------|---------------|-----|43| Component mount/unmount | Motion | AnimatePresence handles lifecycle |44| Page navigation transitions | View Transitions API | Built-in browser support, works with any router |45| Complex interruptible animations | Motion | Spring physics, gesture interruption |46| Simple crossfade between pages | View Transitions API | Zero JS bundle cost |47| Drag/reorder interactions | Motion | drag prop with layout animations |48| Shared element across routes | View Transitions API | viewTransitionName CSS property |49| Scroll-triggered animations | Motion | useInView, useScroll hooks |50| Multi-step orchestrated sequences | Motion | staggerChildren, variants |5152## Quick Start5354### Motion — Component Animation5556```tsx57import { motion, AnimatePresence } from "motion/react"5859const fadeInUp = {60 initial: { opacity: 0, y: 20 },61 animate: { opacity: 1, y: 0 },62 exit: { opacity: 0, y: -10 },63 transition: { type: "spring", stiffness: 300, damping: 24 },64}6566function Card({ item }: { item: Item }) {67 return (68 <motion.div {...fadeInUp} layout layoutId={item.id}>69 {item.content}70 </motion.div>71 )72}7374function CardList({ items }: { items: Item[] }) {75 return (76 <AnimatePresence mode="wait">77 {items.map((item) => (78 <Card key={item.id} item={item} />79 ))}80 </AnimatePresence>81 )82}83```8485### View Transitions API — Page Navigation8687```tsx88// React Router v7+ with View Transitions89import { Link, useNavigate } from "react-router"9091function NavLink({ to, children }: { to: string; children: React.ReactNode }) {92 return <Link to={to} viewTransition>{children}</Link>93}9495// CSS for the transition96// ::view-transition-old(root) { animation: fade-out 200ms ease; }97// ::view-transition-new(root) { animation: fade-in 200ms ease; }98```99100### Motion — Accessible by Default101102```tsx103import { useReducedMotion } from "motion/react"104105function AnimatedComponent() {106 const shouldReduceMotion = useReducedMotion()107108 return (109 <motion.div110 animate={{ x: 100 }}111 transition={shouldReduceMotion112 ? { duration: 0 }113 : { type: "spring", stiffness: 300, damping: 24 }114 }115 />116 )117}118```119120## Rule Details121122### Layout Animations (Motion)123124FLIP-based layout animations with the `layout` prop and shared layout transitions via `layoutId`.125126> **Load**: `rules/motion-layout.md`127128### Gesture Interactions (Motion)129130Drag, hover, and tap interactions with spring physics and gesture composition.131132> **Load**: `rules/motion-gestures.md`133134### Exit Animations (Motion)135136AnimatePresence for animating components as they unmount from the React tree.137138> **Load**: `rules/motion-exit.md`139140### View Transitions API141142Browser-native page transitions using `document.startViewTransition()` and framework integrations.143144> **Load**: `rules/view-transitions-api.md`145146### Motion Accessibility147148Respecting user motion preferences and reducing cognitive load with motion sensitivity patterns.149150> **Load**: `rules/motion-accessibility.md`151152### Motion Performance153154GPU compositing, avoiding layout thrash, and keeping animations at 60fps.155156> **Load**: `rules/motion-performance.md`157158## Key Principles1591601. **60fps or nothing** — Only animate `transform` and `opacity` (composite properties). Never animate `width`, `height`, `top`, or `left`.1612. **Centralized presets** — Define animation variants in a shared file, not inline on every component.1623. **AnimatePresence for exits** — React unmounts instantly; wrap with AnimatePresence to animate out.1634. **Spring over duration** — Springs feel natural and are interruptible. Use `stiffness`/`damping`, not `duration`.1645. **Respect user preferences** — Always check `prefers-reduced-motion` and provide instant alternatives.165166## Performance Budget167168| Metric | Target | Measurement |169|--------|--------|-------------|170| Transition duration | < 400ms | User perception threshold |171| Animation properties | transform, opacity only | DevTools > Rendering > Paint flashing |172| JS bundle (Motion) | ~16KB gzipped | Import only what you use |173| First paint delay | 0ms | Animations must not block render |174| Frame drops | < 5% of frames | Performance API: `PerformanceObserver` |175176## Anti-Patterns (FORBIDDEN)177178- **Animating layout properties** — Never animate `width`, `height`, `margin`, `padding` directly. Use `transform: scale()` instead.179- **Missing AnimatePresence** — Components unmount instantly without it; exit animations are silently lost.180- **Ignoring prefers-reduced-motion** — Causes vestibular disorders for ~35% of users with motion sensitivity.181- **Inline transition objects** — Creates new objects every render, breaking React memoization.182- **duration-based springs** — Motion springs use `stiffness`/`damping`, not `duration`. Mixing causes unexpected behavior.183- **Synchronous startViewTransition** — Always await or handle the promise from `document.startViewTransition()`.184185## Detailed Documentation186187| Resource | Description |188|----------|-------------|189| [references/motion-vs-view-transitions.md](references/motion-vs-view-transitions.md) | Comparison table, browser support, limitations |190| [references/animation-presets-library.md](references/animation-presets-library.md) | Copy-paste preset variants for common patterns |191| [references/micro-interactions-catalog.md](references/micro-interactions-catalog.md) | Button press, toggle, checkbox, loading, success/error |192193## Related Skills194195- `ork-extras:ui-components` — shadcn/ui component patterns and CVA variants196- `ork-extras:responsive-patterns` — Responsive layout and container query patterns197- `ork:performance` — Core Web Vitals and runtime performance optimization198- `ork-extras:accessibility` — WCAG compliance, ARIA patterns, screen reader support