kinetograph-migrate — Claude Code skill: what it does, how to install
kinetograph-migrate is a Claude Code skill that moves Remotion projects to Kinetograph for browserless video rendering. Triggers when code imports remotion or uses remotion render scripts.
Apache-2.0 ★ 542 updated 2026-11-17
npx skills add 0xS4N4TG/kinetograph --skill kinetograph-migrate -a claude-codeWhat kinetograph-migrate does
The skill adapts Remotion projects for Kinetograph without relying on Chrome, Puppeteer, or Playwright. Core remotion and 24 @remotion/* packages map to the runtime directly, keeping video component code intact.
The workflow inspects the entry point calling registerRoot, runs kinetograph doctor to spot unsupported properties, and generates frame sheets via kinetograph strip. Tooling packages like @remotion/player, @remotion/renderer, @remotion/lambda, and Three.js integrations are unsupported by design and must be replaced. Network access is disabled during rendering; fetch only reads local project files, requiring external assets inside public/.
All rendering runs as a pure function of frame numbers. Unregistered system fonts like Arial render as invisible text without warnings, which requires explicit font files via @remotion/google-fonts or @font-face. The build finishes with kinetograph render using the --strict flag to halt on missing elements.
What it helps with
- move an existing Remotion video project to Kinetograph
- detect unsupported elements and styles with kinetograph doctor
- replace timers and network calls with pure frame math and local assets
- export a contact sheet of frames using kinetograph strip
Example prompts for the agent
- Migrate this Remotion project to Kinetograph and run doctor on src/index.ts
- Check which Remotion packages in this repository are unsupported by Kinetograph
- Render a contact sheet for composition Main using kinetograph strip
How to install kinetograph-migrate
1Skills CLI (Vercel)
npx skills add 0xS4N4TG/kinetograph --skill kinetograph-migrate -a claude-code2Manually: put the files in place
~/.claude/skills/kinetograph-migrate/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/kinetograph-migrate/
1Skills CLI (Vercel)
npx skills add 0xS4N4TG/kinetograph --skill kinetograph-migrate -a codex2Manually: put the files in place
.agents/skills/kinetograph-migrate/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add 0xS4N4TG/kinetograph --skill kinetograph-migrate -a cursor2Manually: put the files in place
.cursor/skills/kinetograph-migrate/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install 0xS4N4TG/kinetograph packages/cli/skills/kinetograph-migrate2Manually: put the files in place
.github/skills/kinetograph-migrate/SKILL.md1Skills CLI (Vercel)
npx skills add 0xS4N4TG/kinetograph --skill kinetograph-migrate -a gemini-cli2Platform CLI
gemini skills install https://github.com/0xS4N4TG/kinetograph --path packages/cli/skills/kinetograph-migrateManually: put the files in place
.devin/skills/kinetograph-migrate/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.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 kinetograph-migrate
How to install kinetograph-migrate in Claude Code?
Run npx skills add 0xS4N4TG/kinetograph --skill kinetograph-migrate -a claude-code. The file will be placed in ~/.claude/skills/kinetograph-migrate/SKILL.md.
What does kinetograph-migrate do?
It guides the migration of Remotion compositions to Kinetograph's browser-free rendering pipeline, replacing tooling scripts and validating frames.
What is required for kinetograph-migrate to work?
It requires the kinetograph dev dependency, moving remote assets to public/, and registering fonts explicitly because system fonts fail silently without a browser.
Source text
SKILL.md · Apache-2.0
---
name: kinetograph-migrate
description: Move an existing Remotion project onto Kinetograph so it renders without a browser. Use when the user has a Remotion project (remotion or @remotion/* imports, `remotion render` scripts, @remotion/three, @remotion/player) and wants it to run, preview or render with Kinetograph, or asks what in a Remotion project will not work there.
metadata:
version: "0.4.0-rc.1"
---
# Migrate a Remotion project to Kinetograph
Most of a Remotion project runs unchanged. `remotion` and 24 `@remotion/*` packages are mapped onto Kinetograph's core
by the CLI, so the video code does not change. What changes is the tooling around it, and a few packages that have no
equivalent. There is no browser anywhere in the render path. Never add one: no Chrome, Puppeteer, Playwright or iframe
as a stopgap, for any reason.
Run commands as `npx kinetograph <command>`. Add `--json` to get one JSON object. For the other commands and the
project API, use the `kinetograph` skill.
Keep the project's own folder layout; do not move files. Only what the commands generate goes under `out/`, which is their default.
## The loop
1. **Find the entry and the compositions.** Read `package.json` (scripts, dependencies) and any `remotion.config.ts`
too: `doctor` only sees files the entry imports, so a player page, a render script or a config file never shows up in
its report. Search the project for `@remotion/(player|renderer|bundler|lambda|cloudrun|cli|three)`, `from 'three'` and
`IFrame`, and treat each hit as a finding. The entry is the file that calls `registerRoot` (often `src/index.ts`;
`package.json` scripts or `remotion.config.ts` name it). Run `kinetograph compositions <entry>`. If it fails with
`... is not supported by Kinetograph yet`, that import is the first finding. (The message says to run `doctor`, but
`doctor` stops on the same import until you fix it.)
2. **Doctor.** `kinetograph doctor <entry>` (add `--comp <id>` for one composition). It reports every element,
property and reason the engine cannot draw, with frame ranges. An import that cannot be bundled stops the command
before any report, with the package named; fix that first and run `doctor` again. Keep the report; work from it.
3. **Fix each finding.** Pick by kind:
- `@remotion/three` or `three` imports: read `references/three.md`.
- `@remotion/player`, `@remotion/renderer`, `@remotion/bundler`, `@remotion/lambda`, `@remotion/cloudrun`, `@remotion/cli`,
`remotion.config.ts`, `npm run` scripts, webpack overrides: read `references/tooling.md`.
- `IFrame`, `@remotion/webcodecs`, `@remotion/media-parser` sample callbacks, `@remotion/rive`, `@remotion/skia`,
Canvas, WebGL or CSS issues in the report: read `references/unsupported.md`.
- Anything else: the property or element is named in the report. Change it to one the engine draws, or leave it
out. Do not guess; run `doctor` again.
4. **Lint.** `kinetograph lint <entry>` and `kinetograph check <entry>` (type errors). Fix every error. Errors that say
"no declaration file" for `react` mean `@types/react` is not installed: add it as a dev dependency at the project's
React version and tell the user. That is not a migration problem and does not block `render`.
5. **Look.** `kinetograph strip <entry> -n 12` (it writes `out/sheets/<id>-strip.png` under the project folder), then open the PNG. Use `still <entry> <frame>` for one
frame. Compare with what the project was meant to show (a Remotion render, a screenshot, the user's description; if
you have none, check against the code and say that you could not compare). `doctor` and `lint` can both be clean
while text is missing, so check that every title and caption is on screen (see Fonts).
6. **Render.** `kinetograph render <entry> --comp <id> --strict` (it writes `out/renders/<id>.mp4`) (`--range 0..30` first for a quick
test; `a..b` stops at b-1, `a..=b` includes b). `--strict` fails on the first frame
with anything unsupported, so no video leaves with something missing.
If `--strict` still fails after the fixes, a left-over is real. Either approximate it (say how) or remove it, then say
so in step 7. Do not hide it by dropping `--strict` for the final render.
7. **Report to the user.** List what was ported as is, what was replaced (and with what), what was left out or
approximated, and the commands to run the project now. Say plainly when the result differs from Remotion's.
## Rules
- A `remotion` import needs no edit. Do not rewrite `remotion` or `@remotion/*` imports to `@kinetographdev/core`.
- Never remove a feature silently. Every omission or approximation goes in the report from step 7.
- **Fonts.** Text in a font that is not registered may be drawn as nothing, with no warning from `doctor`. A
`fontFamily` that names only system fonts (`Helvetica, Arial, sans-serif`) is the usual cause. Register a font file
the user is allowed to use: `@remotion/google-fonts/<Family>` (`loadFont()`), `registerFont({ family, path:
staticFile('F.ttf') })` from `@kinetographdev/core`, or `@font-face { src: url(...) }` in an imported `.css` file. Do not
copy system fonts into the project.
- Rendering is a pure function of the frame. Replace `Date.now()`, `Math.random()` and timers with frame maths and
`random(seed)`.
- There is no network. `fetch` reads project files only. Copy remote assets into `public/` and use `staticFile`.
- Do not add dependencies for the render path, except `kinetograph` itself as a dev dependency (it brings
`@kinetographdev/core`, which the 3D elements import from). If it is not on npm yet, ask the user where to install it
from. Packages for the studio or tests are fine.
## Coverage in one line
Core `remotion` and these `@remotion/*` packages are mapped: transitions, motion-blur, noise, paths, shapes,
layout-utils, animation-utils, captions, google-fonts, fonts, lottie, gif, media-utils, media, light-leaks, starburst,
sfx, zod-types, timeline-utils, media-parser, webcodecs, canvas, rive, skia. Not ported on purpose: three, player,
renderer, bundler, cli, lambda, cloudrun, tailwind, tailwind-v4 (Tailwind itself works). The full table is on the docs
site at `/docs/guides/migrate/`. GSAP (core, the free plugins, Flip) works too: seek a paused timeline to
`frame / fps` in a layout effect, or let a `gsap.to` in a `useEffect` play by itself (`/docs/compat/#gsap`).
Needs no rewrite: `<Img src>` of an `.svg` file (text inside it is left out), named and functional CSS colours
(`white`, `rgb()`, `oklch()`), `<TransitionSeries>` and `<Series>` children in a Fragment, `<canvas>` and `<Canvas>`,
`-webkit-text-stroke`, and symbols or emoji missing from a font (bundled fallback; CJK needs a font you load). Libraries
(Recharts, d3, rough.js, Chart.js, anime.js, Motion, Paper.js) run as they are when they draw from the frame; see
`/docs/plugins/library-adapters/`. Mermaid draws with its default HTML labels (`<foreignObject>`); load the label font first.
© 0xS4N4TG · Apache-2.0 · 0xS4N4TG/kinetograph