reanimate is a Claude Code skill that clones an animation from a site, video or gif, then measures the copy against the original frame by frame
reanimate (NiazMorshed2007/reanimate) is a free Claude Code skill that records an animation from a site, video, gif or Lottie file, rebuilds it in your project, then films the copy the same way and compares timing, easing and pixels, for up to five rounds.
reanimate (GitHub: NiazMorshed2007/reanimate) is a free, MIT-licensed skill for Claude Code that copies an animation and then checks its own work. It films the reference (a live page, a screen recording, a video file, a gif or a Lottie file) in a headless browser, writes a timing spec, rebuilds the motion in your project's stack, films the copy the same way and compares the two frame by frame. The loop repeats until the numbers pass or five rounds are used up, and anything still off is reported with its numbers. Created on October 29, 2026, the repository had 1,699 stars and 146 forks as of November 16, 2026.
Quick facts
- What it is: an Agent Skills folder (SKILL.md, reference notes, TypeScript scripts). Only skills/reanimate/ is installed; site/ is the showcase website.
- Inputs: a live URL, a screen recording, mp4/mov/webm, a gif or a Lottie file. Rive files and Figma, Framer or After Effects prototypes go through the video path.
- Output: code in the animation stack your project already uses (CSS, Framer Motion, GSAP, three.js).
- Platforms: macOS or Linux with Bun 1.1 or later; Windows untested. Tested only with Claude Code.
- Price and licence: free, MIT, no API keys. No releases have been published; the last commit was on October 31, 2026.
How to install
The README gives one install command, through the skills CLI. It notes that adding -a claude-code skips the question about which agents to set up:
npx skills add NiazMorshed2007/reanimate -gThen you describe the target, the source and the destination in Claude Code, for example /reanimate the hero entrance on https://example.com, into components/Hero.tsx. A single widget or a time range of a video (0:03 to 0:05 of a .mov file) also works.
First setup: what it installs
The first run calls setup.sh. It stops if Bun is missing, runs bun install if Playwright or the ffmpeg binary is absent (playwright pinned at 1.64.1, plus ffmpeg-static, pixelmatch and pngjs), and downloads Playwright's Chromium if none launches: about 250 MB together, per the README.
Each job keeps its evidence (captures, spec, compare reports and sheets for every round) in .reanimate/<name>/ inside your project; the skill suggests adding it to .gitignore. The clone also needs a page the skill can film at the reference viewport: a dev-server route or a standalone HTML file.
How the proof step works
Reference and clone must be filmed with the same viewport, crop, trigger, duration and frame rate; compare.ts warns when the two capture settings differ.
compare.ts aligns the clone to the reference on the first ten frames, then reports mean mismatch (the share of differing pixels per frame, via pixelmatch, with red diff images), the timing error in seconds between the two motion windows (first, last and peak frame of change), which the docs call the main motion metric, and an activity curve whose shape exposes a different easing. easing.ts fits tracked positions to named easings and detects springs; sheet.ts puts reference, clone and diff side by side.
The pass bar depends on the level you ask for. The default, motion-faithful, needs start, end and duration within 0.08 seconds, the same easing family, stagger gaps within 0.04 seconds, travel within 10 percent and nothing moving in one that is still in the other; copy, colours and fonts may differ. "Match it exactly" (pixel-faithful) adds a mean pixel mismatch of 2 percent or less, no frame above 5 percent, rest frames at 0.5 percent or less, and the same fonts, colours, sizes and assets. A mixed level ("clone X and add Y") verifies the cloned part at one of those levels and keeps your additions separate.
For canvas and WebGL, --gl traces WebGL, WebGPU and canvas 2D calls (shaders, uniforms, the three.js scene) and --clock virtual steps the page frame by frame with a seeded Math.random, so captures come out identical; gl.ts compare checks each animated value as a channel. Rendering defaults to SwiftShader for identical pixels on every machine; --gpu hardware uses the real GPU.
Each round fixes the biggest difference and films again, usually 2 to 5 rounds. A row still failing after five goes into the report with its numbers and reason; the instructions forbid quietly loosening thresholds.
What stands out
- A measurable loop rather than one pass: every spec row becomes a check, and a "?" means the frames have not been read yet.
- Declared CSS and Web Animations API timings are read from the page before anything is estimated from pixels.
- It reuses your project's animation library instead of adding one.
- Triggers include scroll, hover, hover-out, pointer paths, drag with fling, click and loops.
- Self-reported results: the README's examples table has 14 rows from nine sites, mostly built in 30 to 90 minutes, from 417 of 417 frames identical to under 0.6 percent of pixels differing.
How it was built with Claude
All 20 commits on main are by the maintainer, Niaz Morshed, and 18 carry a Co-Authored-By trailer for Claude Opus 5.5. One commit fixes the kind of slip the tool exists to catch: compare.ts looked for frames.json in the wrong folder and treated every capture as 25 fps, misreporting timing. The example clones were each made by a separate agent running the skill. The repository tree has no CLAUDE.md.
Try it with your AI. To try reanimate on an animation you own or have permission to copy, fill in the brackets and give this prompt to Claude Code:
I want to use the reanimate skill (github.com/NiazMorshed2007/reanimate) to rebuild [the
animation, e.g. the hero entrance] from [URL or path to my screen recording] into
[destination file]. Fidelity: [motion-faithful (default), pixel-faithful, or mixed plus
my additions]. I confirm I may use this reference: [yes/no]. If no, stop.
First check and report:
1. My OS is macOS or Linux (Windows is untested; if Windows, stop and tell me).
2. bun --version shows 1.1 or later. If Bun is missing, stop; do not install it.
3. If /reanimate is not available, show me the README install command, npx skills add
NiazMorshed2007/reanimate -g (with -a claude-code to skip the agent question), and
wait for my confirmation. The first run downloads Playwright's Chromium and a static
ffmpeg, about 250 MB.
4. If the reference is not my own site, do not use --gl until I confirm: open issue #8
says a hostile page can write files outside the capture folder in --gl captures.
Then run /reanimate:
- Evidence stays in .reanimate/[name]/. Show me the .gitignore line (.reanimate/) before
adding it.
- Capturing and writing the spec may proceed. Before changing any file outside
.reanimate/, show me the plan and wait.
- Use the animation library my project already has. Ask before adding any dependency. Do
not delete files. Do not capture pages behind a login or ask for credentials.
- End with the last compare round as a table (timing error, mean mismatch, easing,
pass/fail) and any row still failing, with numbers and reason.Known limits
- Copyright and licensing. The README says it clones whatever you point it at and that fonts, images and code from another site still belong to their owners, so make sure you may use what you copy. Its examples recreate parts of nine sites as a study, with a not-affiliated disclaimer.
- Security of --gl captures. Open issue #8 (November 10) reports that gl.ts names shader, buffer, texture and canvas files from ids in the captured page's GPU trace, so a page could write files outside the capture folder via ../ paths; it was reproduced at commit 3f7a55a and a patch proposed, unmerged as of November 16. Our caution, not the project's: treat --gl captures of untrusted sites as risky.
- Pages behind a login, YouTube and Loom cannot be recorded directly, and Vimeo cannot be downloaded; use a screen recording or a browser tool that can record. Iframes and cross-origin stylesheets are not inspected.
- Springs are fitted, not read from source; worker clocks run in real time; --gpu hardware on Linux is untested.
- Windows fixes sit in open pull requests #1, #4 and #6. Issue #5, titled "Ask, Support more than 1 minutes?", has no further detail.
Related on claudefox
- PhoneBox turns an old Android phone into a desk panel and control deck for Windows, Linux and macOS
- huashu-motion lets Claude Code or Codex make a product launch film with music that you edit by clicking a frame
- TV Detox gives an old Android TV a 30 MB ad-free home screen and a Claude Code cleanup you can undo
- teardown: a Claude Code skill that builds take-apart 3D machine simulators as one offline HTML page
Problems and feedback
Issues and pull requests are on the GitHub repository, with 7 open as of November 16, 2026. The repository has no SECURITY.md or contributing guide; the security report in issue #8 was filed as a public issue.
FAQ
Does reanimate need an API key? No. The README says no API keys are needed; the first run installs a static ffmpeg and Playwright's Chromium.
What happens if something still does not match after five rounds? The skill stops and reports that row with its numbers and the reason, such as a missing font or a shader you may not copy, instead of lowering the threshold.
Does it work on Windows or with other agents? The README says it needs macOS or Linux and that Windows is untested; other agents that read SKILL.md can install it, but only Claude Code has been tested.
Source: GitHub: NiazMorshed2007/reanimate, reanimate repository file tree, reanimate README, reanimate SKILL.md, reanimate verification reference, reanimate implementation reference, reanimate capture reference, reanimate WebGL reference, reanimate compare.ts, reanimate setup.sh, reanimate script dependencies (package.json), reanimate commit history, reanimate issue #8: trace ids can write files outside the capture folder, reanimate pull request #4: make the scripts run on Windows, reanimate issues and pull requests, reanimate pull request #6: wait for a painted frame before the sheet screenshot
This story first appeared in the claudefox daily briefing for November 16, 2026.