Building a Remotion animation factory with Claude Code

Bonsai 🌳 @bonsaixbtOriginally posted 2026.10.26

Open original on X

Claude Opus 5.5 can run a tiny animation factory for you, and almost nobody sets it up Every time you prompt "make a cool 20-second video", Claude has to guess the timing, the pacing and what's allowed to change, so you get something close-ish and every revision breaks half of it But once you treat video as code, where every frame is just a function of time, you can set Claude Code up once as a small production line and then simply feed it orders Here's what that line looks like: > The rulebook: a CLAUDE. md with house rules Claude reads every time, so time only comes from useCurrentFrame(), motion from spring() and interpolate(), scenes live in <Sequence>, and CSS animations, Date. now and setTimeout are banned > The order form: a brief template with one action, one before and one after, 15–25 seconds at 30 fps, the key moments, and a list of what must never change > The machine: one Remotion composition with props, so the product name, colors, copy and screenshot swap in while the motion stays exactly the same > The QC desk: before anything moves, Claude renders 3 stills (the opening, the action and the final frame), so layout and readability bugs get caught early > The repair shop: revisions only come in as "where, what's wrong, what to change, what stays", so one fix never rewrites the whole video > Shipping: one render command per order, and the same props in always give you the same video out The official Remotion skills (npx skills add remotion-dev/skills) work like the factory's training manual, teaching Claude the patterns that don't fall apart the moment you start editing Set it up once, and every new launch, feature or update becomes an order you hand to the line instead of another lottery ticket The full method behind every station is in my guide, save this and read it 👇🏽

This post quotes another post: x.com/bonsaixbt/status/2113660680096170320