Figma Implement Motion skill
Figma's skill for turning animations made in Figma into code: motion.dev for React, CSS keyframes for other sites, with exact timing and easing.
Official · Figma| Author | Figma |
|---|---|
| Licence | No licence file; Figma Developer Terms apply |
| Source | figma/mcp-server-guide · SKILL.md on GitHub |
| Project website | developers.figma.com/docs/figma-mcp-server |
| Works in | Claude Code · Codex, Gemini CLI, Cursor, Copilot |
| Read from the source on |
The figma-implement-motion skill is Figma's official agent skill for turning animation designed in Figma into code in your project. When a frame uses Figma Motion keyframes or animation styles, the agent fetches the motion data with the Figma MCP server's get_motion_context tool and the layout with get_design_context, then merges the two by node ID into working motion.dev (React) or CSS keyframe code.
Its job is fidelity: keep Figma's exact timing, easing curves, springs and transform origins, animate only what Figma says animates, and respect the visitor's reduced-motion setting. It writes code, not Figma layers; to create or edit the animation inside Figma itself, Figma's figma-use-motion skill is the one to use. Figma Motion is an open beta, and this skill pairs naturally with figma-design-to-code for the static part of the design.
From the skill's SKILL.md: Translates Figma motion and animations into production-ready application code.
What it does
- Gets the static structure of the frame with get_design_context (or reuses an earlier call), then the motion with get_motion_context, recursively for every animated layer.
- Treats the motion response as the complete list of what animates and matches each animated node to the design code by node ID, wrapping plain elements in motion elements where needed.
- Uses Figma's ready-made snippets verbatim (motion.dev for React, CSS @keyframes otherwise) instead of regenerating them, and applies text-group stagger timing and shared timelines (once, loop or boomerang) from the response.
- Handles the hard cases: a static rotation plus an animated one on the same layer, path-level SVG animation (inlining the SVG to animate the real path), and layout transforms that would clash with animated ones.
- Adapts to the motion library your project already uses (Framer Motion, React Spring, GSAP, anime.js) and, for SwiftUI, maps easing to real SwiftUI APIs.
- Adds a prefers-reduced-motion fallback, checks one animation end to end before doing the rest, and flags any motion that cannot be exported with a TODO comment instead of dropping it.
What you get
- Animation code in your repository: motion.dev components, CSS keyframes or adapted code for your motion library, with downloaded assets.
- No changes to the Figma file.
When to use it
- A designer animated a component or screen in Figma and you need the same motion in your app.
- get_design_context mentions motion or tells the agent to call get_motion_context.
- Hand-copied easing and durations never quite match the design and you want Figma's exact values.
When not to use it
- You want to create or change the animation in Figma: that is figma-use-motion.
- The design has no Figma Motion animation: use figma-design-to-code for static screens (the skill will not invent motion).
- The animation relies on component variant transitions, animated masks or arc paths: the skill's own reference lists these as not exporting cleanly yet and suggests video or Lottie fallbacks.
What it needs
- The Figma MCP server connected and signed in (the plugin uses the remote server; get_motion_context is also on the desktop server).
- A Figma file whose frame uses Figma Motion, which Figma describes as an open beta on all plans. This skill only reads it, so no Full seat is needed, but read calls are rate-limited (up to 20 a month on the Starter plan or a View or Collab seat).
- Your codebase, so it can match your existing motion library and components. For React without one, it uses motion.dev (the motion package).
- A link to the animated frame or layer.
Files in the skill
| File or folder | What it is for |
|---|---|
SKILL.md | Tool roles, the five-step workflow (structure, motion, merge, apply, validate), interleaved transforms and seven critical rules. |
references/examples-and-anti-examples.md | Worked merges and failure patterns, such as rebuilding the DOM or losing per-element transform origins. |
references/gotchas.md | Figma-specific motion bugs: pivots on nested groups, hold easing, custom springs, colour interpolation. |
references/svg-and-path-motion.md | Animating an SVG path itself (stroke reveals, path length) rather than its wrapper. |
references/framework-recommendations.md | Default libraries per stack, SwiftUI easing mapping, and which library to prefer for confetti, particles, scroll-linked motion and more. |
references/unsupported-and-fallbacks.md | What does not export cleanly yet and the video or Lottie fallbacks. |
references/motion-lint-rules.md | Known export limitations the agent must tell you about. |
Licence as found in the repository on 2026-11-15: No licence file; Figma Developer Terms apply.
Example prompts
Type one of these after installing; naming the skill makes sure it is used.
- Implement the animation in this Figma frame in our React app with motion.dev: <frame URL>.
- Add the loading animation from this Figma component to Spinner.tsx; we already use Framer Motion.
- Turn this animated hero from Figma into plain HTML with CSS keyframes, and respect prefers-reduced-motion.
- The card flip in Figma doesn't match our implementation. Pull the motion data and fix the easing and timing in Card.tsx.
How to install figma-implement-motion
Connect the Figma MCP server
In Claude Code, Figma's plugin from Anthropic's official marketplace adds the remote MCP server and this skill with the rest of Figma's skills; then run /mcp and sign in to Figma. Copying just this folder also works: it needs no companion skill, though figma-design-to-code is a sensible partner for the static layout.
claude plugin install figma@claude-plugins-official
# or, by hand:
claude mcp add --transport http figma https://mcp.figma.com/mcpCursor, Gemini CLI and VS Code
Figma's guide installs the same plugin in Cursor (/add-plugin figma) and Gemini CLI (an extension, then /mcp auth figma), and connects VS Code through an HTTP MCP server with the same URL.
/add-plugin figma
gemini extensions install https://github.com/figma/mcp-server-guideNot for claude.ai uploads or the Claude API
The skill depends on the Figma MCP server's motion and design-context tools. The Claude API skills sandbox has no network access and we have not verified a claude.ai setup.
A skill is a folder with a SKILL.md file. You install it once; the agent reads its short description at the start of each session and loads the full instructions only when a request matches. Pick the place you use:
Claude Code: from the plugin marketplace
- Start Claude Code in a terminal with
claude. - This plugin is in Anthropic's official marketplace, which Claude Code adds for you the first time you start it.
- Install the plugin. Claude Code opens its details first: check what it will add (skills, hooks, MCP servers), then choose whether it is for you, for everyone on this repository, or for you in this repository only.
/plugin install figma@claude-plugins-official - Type / and look for
/figma:figma-implement-motion, or simply ask for the task.
From your shell instead of a session:
claude plugin install figma@claude-plugins-officialThe plugin installs as a whole, so other skills come with it, including figma-3d-transforms, figma-code-connect, figma-code-workflows, figma-create-new-file, figma-design-to-code, figma-generate-design, figma-generate-diagram, figma-generate-library, figma-generative-plugins, figma-shaders, figma-spec, figma-swiftui, figma-use, figma-use-figjam, figma-use-motion, figma-use-slides.
Claude Code: copy the folder into your skills folder
Put the skill's folder in ~/.claude/skills/ to use it in every project on this computer, or in .claude/skills/ inside a repository to share it with everyone who works there (commit it).
git clone --depth 1 https://github.com/figma/mcp-server-guide.git
mkdir -p ~/.claude/skills
cp -R mcp-server-guide/skills/figma-implement-motion ~/.claude/skills/Claude Code notices new or changed skills in these folders during the session. If the skills folder did not exist when the session started, run /reload-skills once. Then type /figma-implement-motion or just describe the task.
On Windows, run the commands in Git Bash or WSL, or copy the folder into the same place with File Explorer.
Codex, Gemini CLI, Cursor and GitHub Copilot
These agents read the same SKILL.md folders. The one folder all four accept inside a project is .agents/skills/, so this copies the skill there:
git clone --depth 1 https://github.com/figma/mcp-server-guide.git
mkdir -p .agents/skills
cp -R mcp-server-guide/skills/figma-implement-motion .agents/skills/| Agent | Project folder | Your user folder | Notes |
|---|---|---|---|
| OpenAI Codex | .agents/skills/ | ~/.agents/skills/ | Type $ or run /skills to pick a skill; Codex also chooses one when your task matches. |
| Gemini CLI | .agents/skills/.gemini/skills/ | ~/.agents/skills/~/.gemini/skills/ | Or install from Git with gemini skills install <git URL> --path <folder> --consent. Google replaced Gemini CLI with Antigravity CLI for free-tier and Google One users on 18 June 2026; Antigravity uses .agents/skills/ in a project and ~/.gemini/config/skills/ for you. |
| Cursor | .agents/skills/.cursor/skills/ | ~/.agents/skills/~/.cursor/skills/ | Type / in Agent chat to pick a skill. Cursor also reads Claude Code's .claude/skills/ folders. |
| GitHub Copilot | .github/skills/.agents/skills/.claude/skills/ | ~/.copilot/skills/~/.agents/skills/ | Works in Copilot CLI, the cloud agent, and agent mode in VS Code, Visual Studio and JetBrains (IDE support depends on the version). Or run gh skill install OWNER/REPOSITORY SKILL (public preview, GitHub CLI 2.90.0 or later). |
Sources for these steps
Checked against each vendor's documentation on 2026-11-14:
Two tools, joined by node ID
get_design_context says what each layer looks like and where it sits; get_motion_context says which layers animate and how. The skill's core move is matching the two by node ID, with a fallback ID for layers inside reused components, so that each animation lands on the right element and two instances of one component can still move differently.
When the two disagree on timing, easing or values, the motion tool wins.
Keep the values, clean up the code
Timing, easing, keyframes and transform origins are copied exactly from Figma's snippets, because regenerating them loses custom curves and spring overshoot. The code around them is not copied blindly: when many layers share one animation with different delays, the skill builds it once as a reusable component or variants object instead of pasting the same block for each element.
Questions about figma-implement-motion
How is figma-implement-motion different from figma-use-motion?
They work on opposite sides. figma-implement-motion reads an animation from Figma and writes it as code in your app. figma-use-motion creates or edits the animation inside the Figma file, through use_figma. A typical flow uses figma-use-motion to animate a design, then figma-implement-motion to ship it.
Which animation libraries does it output?
Figma's get_motion_context returns motion.dev and CSS @keyframes snippets. The skill uses motion.dev for React and CSS for other web projects by default, but adapts to whatever your project already uses, such as Framer Motion, React Spring, GSAP or anime.js. SwiftUI is translated from the CSS snippet.
Does it handle reduced motion?
Yes, by default. Its rules say any motion it adds must soften or switch off under prefers-reduced-motion, usually by rendering the resting state or cutting the duration to almost nothing.
What doesn't export to code yet?
The skill's references list arc paths, generative effects, some path-trim timings, component variant transitions, animated masks and complex boolean or vector-network motion. For those it suggests a fallback such as video or Lottie, or asks you.
Is the figma-implement-motion skill free?
The skill files are free to install but not open source: there is no licence file and Figma's Developer Terms apply. It needs a Figma account and counts against Figma's read-tool rate limits; Figma Motion itself is an open beta.
More AI skills
Related skills
Figma Use Motion skill
Official · FigmaFigma's skill for animating layers inside a Figma file with AI: keyframes, animation styles, easing, text reveals and timeline length.Figma Design to Code skill
Official · FigmaFigma's skill for turning a Figma frame into code in your project, reusing your components and assets instead of pasting generated markup.Figma Generate Design skill
Official · FigmaFigma's skill for building or updating screens in a Figma file from your code, using your design system's components and variables.Thumbnail Design skill
Community · Frank HeijdenrijkBrief honest, mobile-readable video thumbnails and plan a native comparison test.Design and Templates skill
Community · Frank HeijdenrijkSpecify a reusable brand kit, template family and production workflow for recurring social graphics.Quote Cards and Text Graphics skill
Community · Frank HeijdenrijkChoose and attribute one strong line, then brief a readable typographic card without fabricating quotes.