Step 1 · Requirements
What you need
Claude Code can install most of these for you. You don't have to type the setup commands yourself.
- ✓A PC or MacWe used a Mac (Apple Silicon). The skill's author used Windows. We haven't tested Windows ourselves.
- ✓Claude Code + a Claude plan (or API access)The skill is free, Claude Code isn't. We used a Pro plan (see the numbers below).
- ✓Free tools: Node.js, Python 3, ffmpegClaude Code can install them. We had Node 20, Python 3 and ffmpeg 7.
- ✓Remotion +
@remotion/threeFree for individuals (check Remotion's license if you're a company). Claude sets it up: our install took 33 s. - ✓Space on a big driveKeep the project and its temp files on a drive with room. Ours ended at 6.7 GB, all on an external SSD.
- ✓A voice-overYour own recording, or an AI voice. We used ElevenLabs.
Steps 2 to 6 · Copy, paste, check
The prompts, step by step
Paste each one into Claude Code, inside your project folder. Fill in the < > parts first. Claude does the hard parts; your job is to read what it shows you and say go.
-
02
Install the skill from GitHub
The skill is a folder of instructions and templates. It has to live in
~/.claude/skills/cartoon-3d-short/.Install the Claude Code skill from https://github.com/mromidev/claude-animated-shorts into ~/.claude/skills/cartoon-3d-short/
3D props: the skill's template loads free Kenney 3D models that are not in the repo. We didn't download them: Claude built every prop in code (the jeep, the tram, the shop, the globe, the palm trees). The two Kenney kits are only about 14 MB if you'd rather use them.
-
03
The master prompt
This is where the topic, story, visual style and duration go. Claude researches the facts and writes the script, then waits for your OK.
Use the cartoon-3d-short skill to make one vertical animated short. Topic: <what it's about, e.g. how the jeepney started> Story: <one TRUE story with a cause and effect you can SEE, in 1-2 sentences> Visual style: the skill's default (flat 2D cartoon characters in a colourful 3D world). Setting: <place + year>. Characters: <who appears>. Duration: about 60 seconds, 9:16 vertical. Language: <English or Taglish>. Narration: one steady storyteller voice. Before anything else: 1. Research the facts. List each one with its source at the top of SCRIPT.md. Don't state anything you can't source, and mark anything uncertain. 2. Write the script with the skill's beat formula and show it to me. Wait for my OK. Rules: - Work in this folder: <a folder on a drive with lots of free space>. Keep every temp and render file there too (set TEMP, TMP and TMPDIR to a folder inside it). - If a 3D model file isn't available, build the prop in code. Don't download anything without asking me. - Ask me before any paid API call and before deleting files. - Save after every step. Keep a log of what you ran, how long it took, and every error and fix.
Our run: Claude wrote a script with a source for every fact. Zeke then rewrote it in his own words, and we used his. The script is yours to change.
-
04
The voice-over
Two options:
Record your ownSave it asvoice.wav. Free.Use an AI voiceElevenLabs or similar. Make 2 takes of the whole script and pick by ear.Then give it to Claude Code so it can sync the animation to your narration:
Here's my voice-over: <path to voice.wav>. Make the word timings (words.json) and fix any wrong words by hand against SCRIPT.md. Sync the animation to the narration.
Our run: 2 ElevenLabs takes = 1,296 credits. We didn't like the first voice for a story, so we re-voiced with a storyteller voice from the ElevenLabs library (another 1,296 credits). Claude re-timed the whole video to the new take by matching the words. The word timings came from a free speech-to-text model on the Mac (mlx-whisper).
-
05
Generate the video
Claude builds the shots, the world and the characters, renders test stills and checks them. The skill also makes its own sound effects and background music, so you don't have to make every sound yourself.
Build the shots, the world and the characters, render test stills, and check them with the skill's verifier. Then make the sound effects and music and mix them under my voice.
Our run: the skill's verifier is an Opus agent that scores the stills against the skill's look. We ran it once (one round alone used about 117k tokens) and fixed what it flagged, e.g. sunset shots that looked like night.
-
06
Preview and export
Look at every shot before the final render. Ask for changes in plain words ("the tram looks like a building", "the ending is too dark").
Show me test stills of every shot. After I approve, render the final 2K video and mux it with the sound mix. Then check every frame for black, white or frozen frames.
Our run: the final is 89 s at 1440 × 2560. The frame check caught a wall blocking one shot; Claude fixed it and re-rendered only that shot.
Real talk · our run, 2026-11-17
What it cost us
Every number here is from our own run on a Mac with a Claude Pro plan. Your numbers will be different.
| Total time | About 5 hours, start to final video, including waiting for our own answers and one stall when our session restarted. |
|---|---|
| Final render | 2,670 frames at 1440 × 2560: 65.5 min the first time, under 4 min on a later run with the same settings. Other heavy jobs on the Mac slow it down a lot. The skill's author reports about 10 min on his PC. |
| Test stills | 1 to 6 s each after a ~40 s load. |
| Disk | 6.7 GB project folder (1.7 GB Node packages, 3.7 GB speech-to-text tool and model, 735 MB render temp). The author reports 60 to 110 GB of temp files after many rounds with the 3D model kits, so watch your free space. |
| Claude plan | Pro plan: about 5 % of the weekly limit for the whole run, and ~20 % of one 5-hour window while building the sample. |
| Voice | 2,592 ElevenLabs credits (2 voices × 2 takes). Recording your own voice costs nothing. |
Length: our narration ran 88 s, longer than the skill's 55–70 s target. That's fine; it just means more frames to render.
If you're on a Mac
Problems we hit, and the fixes
The skill was made on Windows. On our Mac these came up. You don't have to fix them yourself: paste the error into Claude Code and ask it to fix it. That's what we did.
- Temp files filled the internal drive. The skill sets
TEMP/TMP(Windows names); macOS usesTMPDIR. Fix: setTMPDIRtoo. - The stills script points at Windows Chrome (
C:/Program Files/...). Fix: let Remotion use its own browser. - "Waiting for root component to load" timeout. The first load took ~2.5 min. Fix: a longer timeout.
- Blank stills (only the sky colour) with newer library versions. Fix: draw each frame once more after the post-processing is ready.
- The final render failed:
--scale 1.3333gives 2559.94 px, and Remotion now wants whole pixels. Fix:--scale 1.3333333333333333.
Honest notes
- The skill is free, but Claude Code isn't. A long run uses a good chunk of a Pro plan's limits.
- Monetization: these videos may qualify on Facebook or YouTube, depending on each platform's rules and your eligibility. We make no earnings claims.
- Make the story, characters and voice your own. The skill's
references/folder holds another creator's frames for style study only: don't upload or copy them. - Credit the skill's author, mromidev, when you share your video.