Skip to content
MOTION CHEAT CODE Back to the pack
  1. Home
  2. Guides
  3. How to write a video prompt

Guide

How to write a video prompt

Five parts, in this order: FORMAT, SCENES, STYLE, SOUND, RENDER. Each one answers a question Claude Code would otherwise have to guess.

Guides Use cases Sound library Glossary Compare FAQ

Updated 4 October 2026

On this page

  1. The five parts
  2. A complete example
  3. Write SCENES in seconds
  4. STYLE, SOUND and RENDER
  5. Six common mistakes
  6. Short prompts, once a template exists

A video prompt for Claude Code works best in five parts: FORMAT (canvas, frame rate and length), SCENES (what happens when, in seconds), STYLE (colors, fonts, sizes and the safe area), SOUND (which sound at which second, how loud) and RENDER (check, look at snapshots, fix, render, report). Each part removes a guess, and guesses are where generic-looking videos come from.

This is the structure behind the "5-button combo" in Motion Cheat Code, explained here so you can write your own.

The five parts

Part The question it answers Weak Strong
FORMAT What is the canvas? "a vertical video" "1080x1920, 30 fps, 6.0 s, project folder promo/"
SCENES What happens when? "the title animates in nicely" "0.30 s: STOP slams in at y 640, scale 1.4 to 1 in 0.3 s (expo.out)"
STYLE What does it look like? "modern and bold" "background #0A0A0B, text #FFFFFF, accent #FFE600, bold condensed font from a local file, 150 px caps, text inside x 60 to 940, y 250 to 1440"
SOUND What is heard, and when? "add some cool sounds" "sfx/hit.wav at 0.30 s, volume 0.6; music bed at 0.2, fade out over the last 0.8 s"
RENDER How does it finish? "render it" "run check until it passes, snapshot 0.6, 2.0 and 4.0 s, fix what looks off, render to renders/hook.mp4"

A complete example

A seven-second tip reel, written in full:

Make this with HyperFrames. The brief is complete: build it straight away, no interview.

FORMAT
- 1080x1920, 30 fps, 7.0 s. Project: tip-steps/ (npx hyperframes init tip-steps --non-interactive --resolution portrait).

SCENES
- 0.0 to 0.4 s: plain light background.
- 0.4 s: title "3 STEPS TO A CLEAN DESK" rises 40 px into place at y 420 (0.5 s, power3.out).
- 1.4 s: step 1 "Clear everything" slides in from the left at y 760 (0.35 s, power3.out).
- 2.2 s: step 2 "Keep three things" slides in at y 900 the same way.
- 3.0 s: step 3 "Reset every evening" slides in at y 1040.
- 3.5 to 5.8 s: hold. A yellow highlighter swipes behind "every evening" at 3.8 s (0.3 s).
- 5.8 s: everything fades out in 0.2 s. Hold the empty frame to the end.
- Variables: the title and the three steps, with these texts as defaults.

STYLE
- Background #F4F1E8, text #0A0A0B, highlight #FFE600.
- Headline font from a local file, 96 px; steps 56 px. All text inside x 60 to 940, y 250 to 1440.

SOUND
- sfx/swish.wav on each step at 1.4, 2.2 and 3.0 s, volume 0.3.
- sfx/pop.wav at 0.4 s, volume 0.4.

RENDER
- Run npx hyperframes check and fix every error. Snapshot 1.0, 3.2 and 5.0 s and look at them.
- Render to renders/tip-steps.mp4. Report the path, the length and what you fixed.

Write SCENES in seconds

The SCENES part is where most prompts are weak. Give every beat a time, a position and a movement with an ease and a duration. These timing rules keep motion readable on a phone:

  • Entrances take 0.25 to 0.6 s with an ease-out; exits are faster, 0.15 to 0.3 s.
  • No more than three things start at the same moment. Stagger the rest by 0.04 to 0.12 s.
  • Reading time: about 0.3 s per word, and at least 1.2 s per screen.
  • No dead air: nothing should sit still for more than about 0.6 s, except the final hold.
  • Hold the last frame 0.8 to 1.2 s so the loop or the cut feels clean.

If you are not sure of a value, describe it in words ("a quick, bouncy pop") and let Claude Code pick numbers; then adjust the result.

STYLE, SOUND and RENDER

STYLE works best with exact values: hex colors, font files, sizes in pixels and the safe box for the format (see Reels safe zones). Fonts should come from local files, not a web link, so the render does not depend on a download.

SOUND names the file, the second and the volume. Hits go where the motion lands; whooshes start a little before. See adding sound effects on the beat.

RENDER is the line people skip, and the one that makes results reliable. Asking Claude Code to run the checks, look at its own snapshots and fix what is off means problems get caught before you see the video.

Six common mistakes

  1. No times. "Animate the title" lets Claude Code guess when and how fast.
  2. Text in the danger zone. The bottom 480 px, the right 140 px and the top 250 px get covered by the app.
  3. Everything at once. More than three things moving at the same moment reads as noise.
  4. No time to read. Viewers cannot pause a hook. Give each line its reading time.
  5. Sound on everything. One sound per real event; about two per second at most.
  6. Made-up proof. Invented numbers, prices or reviews. Put your real ones in the prompt.

Short prompts, once a template exists

The long form is for building something new. Once a design is a template with variables, a one-line prompt is enough: "Use t09. Count to 12,480 and label it NEW MEMBERS. Render." The structure is still there; the template supplies the parts you did not write.

Every build prompt in Motion Cheat Code uses these five parts, and the free starter kit includes three of them to copy and change.

Questions

Do I have to use these exact labels?

No. The labels just make sure nothing is missing. What matters is that the prompt states the canvas, the timed beats, the look, the sounds and how to finish. Using the same labels every time makes your prompts easy to reuse and compare.

How long should a video prompt be?

Long enough to remove the guesses. For a 6 to 10 second reel that is typically one line per beat in SCENES and one or two lines for each of the other parts. Short prompts work too, once a template exists to fill in.

What if Claude Code asks questions instead of building?

Add one opening line: "The brief is complete: build it straight away, no interview." Without it, an agent may reasonably ask about details first.

Keep reading

  • Make a Reel from a text promptTurn a text prompt into an MP4 Reel with Claude Code and HyperFrames, step by step, with what to install, a prompt that works and how to fix the render.
  • Kinetic typographyKinetic typography is text that moves to carry meaning and rhythm. Definition, common techniques in short video, timing rules that keep it readable, examples.
  • GSAP timelineA GSAP timeline is a sequence of animations placed at exact times. What it is, why video renderers need it paused and seekable, and the rules for exact frames.
  • Free starter kit3 prompts, 5 sound effects, 1 template and 3 UI Motion animations to make your first reel. No signup.

Motion Cheat Code

Type a prompt. Get a reel.

The all-in-one Claude Code video pack: 250 prompts, 60 templates, 400 sound effects, 30 music tracks and 60 overlays, plus studios for captions, carousels and covers. $49 one-time, free updates, 14-day money-back guarantee.

See what's insideFree starter kit

You need a paid Claude plan that includes Claude Code (Pro or higher), bought separately from Anthropic, and a Mac, a Windows computer or just your phone (phone setup). Not included in the pack.

Motion Cheat Code Free starter kit UI Motion Guides Sound library Glossary FAQ Help Terms Refunds Privacy Imprint

Motion Cheat Code is an independent product by NorthByte. Not affiliated with or endorsed by Anthropic or HeyGen. Claude and Claude Code are trademarks of Anthropic, PBC. HyperFrames is open-source software by HeyGen (Apache-2.0).

© 2026 NorthByte