animation-motion-design — скилл для Claude Code: анимации
Скилл animation-motion-design для Claude Code с паттернами анимации интерфейсов на Motion и View Transitions API. Подключается при работе над переходами страниц, жестами и поддержкой prefers-reduced-motion.
MIT 228 установок ★ 305 обновлён 2026-11-21
npx skills add yonatangross/orchestkit --skill animation-motion-design -a claude-codeЧто делает animation-motion-design
Скилл описывает, как добавлять анимацию компонентов и переходов между страницами с помощью Motion и View Transitions API. Внутри — правила для жестов, анимации при удалении компонентов, доступности и производительности; также разобраны микровзаимодействия и последовательности анимаций.
Для появления и удаления компонентов используются возможности Motion, а для простых переходов страниц — View Transitions API. В примерах для React показаны AnimatePresence, useReducedMotion и viewTransition. Для Motion нужна версия 13.4.6 или новее; совместимость скилла ограничена Claude Code 2.1.277+.
Какие задачи решает
- добавить анимацию появления и удаления компонентов
- связать переход между страницами с View Transitions API
- обработать перетаскивание и другие жесты
- учесть настройку
prefers-reduced-motion
Примеры запросов агенту
- Добавь анимацию появления и удаления карточек в списке.
- Сделай переход между страницами через View Transitions API.
- Добавь перетаскивание элементов и учти
prefers-reduced-motion.
Как установить animation-motion-design
1Через Skills CLI (Vercel)
npx skills add yonatangross/orchestkit --skill animation-motion-design -a claude-code2Вручную: положить файлы
~/.claude/skills/animation-motion-design/SKILL.mdПапка скилла целиком; для одного проекта — .claude/skills/animation-motion-design/
1Через Skills CLI (Vercel)
npx skills add yonatangross/orchestkit --skill animation-motion-design -a codex2Вручную: положить файлы
.agents/skills/animation-motion-design/SKILL.mdДля всех проектов — ~/.agents/skills/
1Через Skills CLI (Vercel)
npx skills add yonatangross/orchestkit --skill animation-motion-design -a cursor2Вручную: положить файлы
.cursor/skills/animation-motion-design/SKILL.mdCursor читает и .agents/skills/, и .claude/skills/
1GitHub CLI
gh skill install yonatangross/orchestkit src/skills/animation-motion-design2Вручную: положить файлы
.github/skills/animation-motion-design/SKILL.md1Через Skills CLI (Vercel)
npx skills add yonatangross/orchestkit --skill animation-motion-design -a gemini-cli2Командой платформы
gemini skills install https://github.com/yonatangross/orchestkit --path src/skills/animation-motion-designВручную: положить файлы
.devin/skills/animation-motion-design/SKILL.mdСтарый путь .windsurf/skills/ тоже читается
Через Skills CLI (Vercel)
npx skills add yonatangross/orchestkit --skill animation-motion-design -a opencodeClaude.ai
Упакуйте папку в zip и загрузите в Settings → Capabilities → Skills
По шагам, с командами для каждой платформы: Как установить скилл в Claude Code: пять способов
Вопросы об animation-motion-design
Как установить animation-motion-design в Claude Code?
Запусти npx skills add yonatangross/orchestkit --skill animation-motion-design -a claude-code. Файл скилла появится по пути ~/.claude/skills/animation-motion-design/SKILL.md.
Что делает animation-motion-design?
Скилл даёт правила и примеры анимации интерфейсов с Motion и View Transitions API: от жестов и переходов страниц до поддержки prefers-reduced-motion.
Какая версия Motion нужна для animation-motion-design?
В скилле указана Motion версии 13.4.6 или новее.
Исходный текст
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