animation-motion-design — Claude Code skill for UI motion
animation-motion-design — a Claude Code skill for interface animation with Motion and the View Transitions API. It comes into play for page changes, gesture-driven controls, and prefers-reduced-motion support.
MIT 228 installs ★ 305 updated 2026-11-21
npx skills add yonatangross/orchestkit --skill animation-motion-design -a claude-codeWhat animation-motion-design does
This skill gives patterns for animating components and page changes with Motion and the View Transitions API. Its rules cover gestures, exit effects, accessibility, and animation performance, along with micro-interactions and coordinated sequences.
Use Motion for component lifecycle effects, gestures, and more involved animations; the browser API handles page transitions. React examples use AnimatePresence, useReducedMotion, and viewTransition. The Motion patterns require version 13.4.6 or later, and the skill requires Claude Code 2.1.277+.
What it helps with
- animate components as they enter or leave a list
- add page changes with the View Transitions API
- build drag and other gesture interactions
- respect the
prefers-reduced-motionsetting
Example prompts for the agent
- Animate cards as they appear in and leave the list.
- Add page transitions with the View Transitions API.
- Make list items draggable and account for
prefers-reduced-motion.
How to install animation-motion-design
1Skills CLI (Vercel)
npx skills add yonatangross/orchestkit --skill animation-motion-design -a claude-code2Manually: put the files in place
~/.claude/skills/animation-motion-design/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/animation-motion-design/
1Skills CLI (Vercel)
npx skills add yonatangross/orchestkit --skill animation-motion-design -a codex2Manually: put the files in place
.agents/skills/animation-motion-design/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add yonatangross/orchestkit --skill animation-motion-design -a cursor2Manually: put the files in place
.cursor/skills/animation-motion-design/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install yonatangross/orchestkit src/skills/animation-motion-design2Manually: put the files in place
.github/skills/animation-motion-design/SKILL.md1Skills CLI (Vercel)
npx skills add yonatangross/orchestkit --skill animation-motion-design -a gemini-cli2Platform CLI
gemini skills install https://github.com/yonatangross/orchestkit --path src/skills/animation-motion-designManually: put the files in place
.devin/skills/animation-motion-design/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add yonatangross/orchestkit --skill animation-motion-design -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about animation-motion-design
How do I install animation-motion-design in Claude Code?
Run npx skills add yonatangross/orchestkit --skill animation-motion-design -a claude-code. The skill file is placed at ~/.claude/skills/animation-motion-design/SKILL.md.
What does animation-motion-design do?
It provides patterns for UI motion using Motion and the View Transitions API, including gestures, page changes, exit effects, and reduced-motion support.
Which Motion version does animation-motion-design require?
The skill targets Motion 13.4.6 or later.
Source text
SKILL.md · MIT
---
name: animation-motion-design
license: MIT
compatibility: "Claude Code 2.1.277+."
description: 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.
user-invocable: false
targets:
- library: motion
version: ">=13.4.6"
metadata:
archive-candidate: "pending an outside usage signal"
owner-agent: "frontend-ui-developer"
category: document-asset-creation
version: "1.0.0"
author: "OrchestKit"
complexity: "medium"
tags: "animation, motion, framer-motion, view-transitions, micro-interactions, gestures, layout-animation, AnimatePresence, prefers-reduced-motion, spring-physics"
allowed-tools: "Read Glob Grep WebFetch WebSearch"
path_patterns: ["**/animation/**", "**/motion/**", "*.motion.*", "*.framer.*"]
---
# 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
```tsx
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
```tsx
// 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
```tsx
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
1. **60fps or nothing** — Only animate `transform` and `opacity` (composite properties). Never animate `width`, `height`, `top`, or `left`.
2. **Centralized presets** — Define animation variants in a shared file, not inline on every component.
3. **AnimatePresence for exits** — React unmounts instantly; wrap with AnimatePresence to animate out.
4. **Spring over duration** — Springs feel natural and are interruptible. Use `stiffness`/`damping`, not `duration`.
5. **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](references/motion-vs-view-transitions.md) | Comparison table, browser support, limitations |
| [references/animation-presets-library.md](references/animation-presets-library.md) | Copy-paste preset variants for common patterns |
| [references/micro-interactions-catalog.md](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
© OrchestKit · MIT · yonatangross/orchestkit