What is the Animation Motion Design skill?
Animation Motion Design is a skill in the yonatangross/orchestkit repository. It gives an AI coding agent patterns for the Motion library and the View Transitions API, with six rules covering layout animations, gestures, exit animations, page transitions, reduced motion accessibility and 60fps performance.
Animation Motion Design is a skill inside OrchestKit, a plugin set of skills and agents. Its SKILL.md covers performant, accessible animation with the Motion library, formerly Framer Motion, and the browser View Transitions API.
The skill file sets the library target at Motion 13.4.6 or newer and marks itself as not user-invocable, so it loads as background guidance. It routes the agent to six rule files by scenario.
What it changes in the agent's output
- The agent picks Motion or View Transitions from a decision table instead of defaulting to one.
- Only transform and opacity are animated, never width, height, top or left.
- Exit animations are wrapped in AnimatePresence so unmounting components do not vanish instantly.
- Springs use stiffness and damping, and presets live in a shared file.
- prefers-reduced-motion is checked and an instant alternative is provided.
Who the skill is for
Best for
- React projects adding component animation, gestures or shared layout transitions.
- Sites that want page transitions through the View Transitions API with little JavaScript.
- Teams that need a reduced motion rule and a frame budget enforced on every animation.
Not for
- Non-React stacks. The examples use React components and a React Router prop.
- Timeline-heavy work with GSAP or Lottie. The skill covers Motion and View Transitions only.
- Anyone who needs it to run on its own, since it is background guidance.
Use it with UiChemy
This skill targets React code. For WordPress, UiChemy Composer writes HTML, CSS and JS inside Elementor or Gutenberg pages, so motion ideas from here would need to be rewritten as CSS or JavaScript. Click Get Started on uichemy.com.
How to install Animation Motion Design Skill: Motion and View Transitions
claude plugin marketplace add yonatangross/orchestkit && claude plugin install ork@orchestkitThe skill file declares Claude Code 2.1.277 or newer as its compatibility. Which OrchestKit plugin carries this skill is not stated in the files read.Add the marketplace
In Claude Code, run
/plugin marketplace add yonatangross/orchestkit.Install the plugin
Run
/plugin install ork. The README gives the one line CLI equivalent shown above.Run setup
Run
/ork:setup. The wizard scans the repository, recommends skills and writes MCP config.Use other hosts
The README lists Cursor, Codex and others with their own install routes, so follow its host table instead of the Claude commands.
Check that it loaded
Ask the agent to animate a list of cards entering and leaving. It should use AnimatePresence, transform and opacity only, and a reduced motion check.
Key features
- Motion versus View Transitions tableA decision table matches eight scenarios to a tool, for example AnimatePresence for mount and unmount, and View Transitions for page navigation with built-in browser support.
- Layout animationsThe motion-layout rule covers FLIP based layout animations with the layout prop and shared element transitions through layoutId.
- Gesture interactionsThe motion-gestures rule covers drag, hover and tap with spring physics and gesture composition.
- Exit animationsThe motion-exit rule explains AnimatePresence, because React unmounts instantly and exit animations are silently lost without it.
- View Transitions API ruleCovers document.startViewTransition, cross-document transitions, the viewTransitionName property and the viewTransition prop in React Router v7.
- Reduced motionThe motion-accessibility rule is marked critical. It uses useReducedMotion to switch to a duration of zero and warns about vestibular disorders.
- 60fps performanceThe motion-performance rule keeps animation on the compositor and avoids layout thrash, with a budget of transitions under 400ms and under 5% dropped frames.
- Spring over durationTells the agent to use stiffness and damping because springs are interruptible, and to avoid mixing in duration based settings.
- Anti-pattern listNames six things to avoid, from animating layout properties to inline transition objects that break memoization and unawaited startViewTransition calls.
- Preset and micro-interaction referencesPoints to files with copy-paste preset variants and a catalog of button press, toggle, checkbox, loading and success states.
Frequently asked questions
What is the Animation Motion Design skill?
It is the animation-motion-design folder in OrchestKit. Its SKILL.md gives an AI coding agent patterns for the Motion library and the View Transitions API, split into six rule files plus references on presets and micro-interactions.
How do I install the Animation Motion Design skill?
Add the OrchestKit marketplace and install its plugin: claude plugin marketplace add yonatangross/orchestkit, then claude plugin install ork@orchestkit. Run /ork:setup afterwards. The README has separate install routes for Cursor, Codex and other hosts.
Does it work with Cursor and Codex?
The OrchestKit README says its skills and agents run in Claude Code, Cursor, Codex and five more coding agents, with hooks only in Claude Code. This skill file itself declares Claude Code 2.1.277 or newer under compatibility.
When should I use the View Transitions API instead of Motion?
The skill's table prefers View Transitions for page navigation, simple crossfades and shared elements across routes, where the browser does the work. It prefers Motion for mount and unmount, drag, scroll triggers and interruptible spring animation.
What does the skill say about accessibility?
It marks prefers-reduced-motion as critical. The pattern uses useReducedMotion and swaps spring transitions for a duration of zero. The anti-pattern list calls ignoring the preference a cause of vestibular problems for users sensitive to motion.
What are Animation Motion Design alternatives?
For performance fixes on existing animation, see fixing-motion-performance. For a broader rule set on speed, see animation-performance. For route transitions in React, vercel-react-view-transitions is narrower and limited to route changes in React apps.
Is it only for React?
The examples use React components, AnimatePresence and a React Router prop, so yes in practice. The View Transitions concepts are browser features, but the skill's rules are written for React with the Motion library.
Is the skill free?
OrchestKit's README calls it free and open source under MIT with no account, and the skill file lists MIT. The skill file also carries a note that it is an archive candidate pending an outside usage signal.


