Motion design · Claude Opus 5.5 · Remotion · MCP
Aura Lab is a motion design toolkit for Claude and Remotion. A director skill plans every scene before Claude writes code. Live components let you set text, data and colours in the browser. Then Claude brings them into your project as the original code, identical to what you saw.
The problem
Since Opus 5.5, anyone can get an animated video out of Claude. But three things get in the way of using it for real work: the videos all look alike, getting them right takes hours of steering, and every time you ask for a component again, it comes back a little different.
Centered text on a gradient, everything fading in, a logo at the end. Your launch video looks like everyone else’s.
Aura Lab: a director skill writes the plan first: message, visual metaphor, mood, palette, camera and beats for every scene.
You end up giving frame-by-frame notes and re-rendering for hours.
Aura Lab: finishing layers are mandatory, a script blocks the work until they’re there, and a critic reviews the frames before you see them.
Paste a description and Claude rebuilds the component from scratch: spacing, timing and easing drift from what you saw, and it can trip over the scenes you already built.
Aura Lab: Claude receives the original component code with your settings, in its own folder. Same frames as the preview, and nothing else in your project changes.
01 · The director skill
The cure for “every AI video looks the same”. A Claude Code skill for Remotion that works like a motion designer: it plans from a short brief, builds with a kit of ready effects, checks its own work and fixes it before you see it. It works with or without our components.
The brief for the video above
“A 5–10 second video about the problem everyone has: AI videos that all look the same.”
The direction plan the skill wrote
Checks and critique, for real. The script checked layers and timing for each scene. On the first frame sheets the critic found the eyebrow flying through the camera, the light overlapping the title and the underline covering the small text. The skill fixed all three before the render.
Message, metaphor, mood, palette, camera, then every scene split into anticipation, entrance, response and breath.
Level 1 to 3. Each level makes finishing layers mandatory: depth in the background, secondary motion, accents, a moving camera, type by word or letter.
3D parallax camera, faded perspective lines, glows, dust, grain, masked text, lines that draw themselves, plus a recipe book for Three.js, paths, morphing and Lottie.
A script blocks the work if layers are missing or timings don’t add up. Then a critic agent reads 5 frames per scene, scores them, and the skill fixes them, at most 2 rounds.
02 · Live components
Charts, titles, maps, timelines, cards and backgrounds, each playing live in the gallery. Open one, change texts, data, colours, position and the parts you want to show. What you see is exactly what lands in your video.
Every component is split into parts (text, number, data, shape, line). Each part shows only its own options and can be hidden without moving the rest.
Percentages never pass 100%, donut slices share the ring, every number stays in the component’s range.
Your settings travel with the component. With Claude connected to Aura Lab, it gets the original code. Without it, the copy-prompt block lists only what you changed.
A simplified version of the editor, running right here. The real one, with the actual Remotion components, is one click away.
Q3 report
Revenue by channel
In the library today
03 · Connect Claude Early access
Connect Claude to Aura Lab with our MCP server and a personal key from your account. When you ask for a component, Claude doesn’t guess or rewrite it: it receives the same Remotion code that runs in the gallery, with your settings, and fits it into your video.
Pick a component, set text, data, colours and parts. Save it.
Your account gives you one command with a personal key for the Aura Lab MCP server. Paste it in your terminal.
“Add my donut to scene 4.” Claude gets the original files plus your settings, writes them in src/auralab/ and drops the component into the scene.
# one command, copied from your account claude mcp add --transport http auralab https://yourauralab.cc/api/mcp \ --header "Authorization: Bearer <your key>" # then, in Claude Code > add my donut to scene 4 src/auralab/ the original component files, your scenes untouched
Everything goes in src/auralab/. None of your files is overwritten or renamed.
Styles live inside each component, so your other scenes look exactly as before.
Components have no background of their own: they sit on top of your scene.
Ordinary React and Remotion files, identical to the ones the gallery runs. Claude checks your Remotion version before adding anything.
One registry, more ways in: the MCP server for Claude, and next a command for any editor or AI (npx auralab add donut). Same components, same code.
How it works
Customize a component in the gallery, or describe the video in two lines.
use motion-regia: a 15-second intro for my fitness app, energetic
In your Remotion project, Claude writes the direction plan, brings in the Aura Lab components through MCP and runs the checks and the critic.
regia.md direction plan src/auralab/ original components src/scene/ one file per scene
Remotion renders every frame from code, so the same input gives the same video, every time.
npx remotion render Video out.mp4
Claude never “watches” a video. When it needs to see one, the skill renders frame sheets (still images) and Claude reads those.
Built with Claude
Pricing
€0
€10 / month, VAT included
Payments are handled by Dodo Payments as merchant of record. Checkout is in test mode until the public launch: no card is charged today.
Where we are
FAQ
Yes. It doesn’t output a video file: it writes code that draws every frame, and a renderer such as Remotion turns those frames into an MP4. The skill makes that code look directed instead of generic.
A connection between Claude and the Aura Lab library. Once it’s added to Claude Code with your personal key, Claude can search the 26 components, fetch the original code with your settings, and add components or a whole video to your Remotion project. Searching is free, installing needs Pro. It’s in early access.
No. Aura Lab components go in their own folder (src/auralab/), carry no global styles and have a transparent background. Claude adds them as a normal Remotion component in the scene you choose; your other scenes and files stay as they are.
Claude is the easiest way, through MCP. The components are plain Remotion/React code, so a command for any editor is coming next.
No. You need Claude Code, Node.js and a Remotion project; Claude writes and edits the code. Knowing a little React helps if you want to tweak things by hand.
A short brief: what the video is about, how long, and the mood. Brand colours, fonts or a script are welcome but optional. The level (1 to 3) defaults to 3.
No. When the skill needs to look at a render, it prepares frame sheets, still images of a few frames per scene, and Claude reads those.
Remotion is free for individuals and teams of up to 3 people. Larger companies need a Remotion company license.
Yes, from your account, at any time. Pro stays on until the end of the month you paid for.
Four live components are open to everyone, no account needed.
Try the live components