01
How Claude creates videos
Claude does not generate video pixels. In Claude Code, it writes the code, assets, and commands that video frameworks such as HyperFrames or Remotion render into MP4 files.
That means Claude can:
- Plan scenes and timing
- Write animations in code
- Add captions and text
- Use your brand colors and fonts
- Render and re-render on request
- Make many versions from one template
You direct. Claude builds. The framework renders.
02
Set up first
- A paid Claude plan with Claude Code
- Node.js and FFmpeg installed
- A video framework, such as HyperFrames or Remotion
- The framework’s official skill or plugin installed
- An assets folder with files you have rights to use
For complex videos, use Opus 5.5 at high effort: /model opus, then /effort high.
03
The video brief
1 · Brief
Help me write a video brief. Ask me one question at a time about the goal, audience, platform, aspect ratio, duration, key message, tone, brand colors and fonts, assets, voiceover, music, and call to action. Then write the brief to brief.md.
04
The plan and storyboard
2 · Plan
Read brief.md. Before writing any code, propose the scene list, timing, visual style, transitions, and file structure. List any assets or decisions you still need from me. Wait for my approval.
3 · Storyboard
Turn the approved plan into a storyboard table: scene number, start and end time, on-screen text, visuals, motion, voiceover line, and sound. Flag any line that is too long to read in its time slot.
05
Brand rules
4 · Brand rules
Add our video brand rules to CLAUDE.md: colors as exact hex values, fonts and weights, logo files and minimum sizes, caption style, safe zones for each platform, preferred transitions, and things to never use.
06
The first draft
5 · Build
Build the video from the approved storyboard using the brand rules in CLAUDE.md. Use only files from the assets folder. Keep each scene in its own file. Start the preview and tell me how to open it.
07
Captions and text
6 · Captions
Add captions from the voiceover script with word-level timing. Keep them inside the safe zone, at most two lines, high contrast, and in our caption style. Make sure captions are on screen from the first frame to the last.
7 · Kinetic text
Create a 15-second kinetic typography video for the line “[line]”. Animate each word in on the beat, with one strong emphasis word in our accent color. 9:16, 30 fps.
08
Special video types
8 · Product demo
Create a 45-second product demo from these screenshots in assets/screens. Show each screen in a device frame, zoom into the key feature, add a short caption per step, and end with the call to action “[CTA]”.
9 · Data video
Turn data/[file].csv into a 30-second animated chart video. Animate the bars or lines growing, label the key numbers, and highlight the biggest change. Check every number against the file.
09
Final review and render
10 · Review and render
Review the whole video before rendering: spelling, timing, captions in safe zones, contrast, audio levels, and every fact against the brief. List problems and fix them with my approval. Then render the final MP4 at [resolution] and [fps] to exports/.
10
Make prompts work better
- Approve the plan before any code is written
- Change one thing at a time
- Use exact times: “scene 3 starts at 0:07”
- Describe motion with timing: “ease out over 0.4 seconds”
- Keep a CLAUDE.md with your rules
- Commit to Git after each good version
11
Before you publish
- Watch the full video at normal speed
- Check rights to every asset, font, and track
- Disclose AI voices where required
- Check every fact and number
- Test on a phone
The golden rule
Do not ask Claude to “make a video.” Give it a brief, approve a storyboard, and build scene by scene.
- Brief
- Plan
- Storyboard
- Brand
- Build
- Captions
- Review
- Render
Start with prompt 1 today. A clear brief makes every next prompt work better.