How a video is built

Every video in these guides — and every video you'll invent yourself — is built the same way: as a list of beats.

Beats

A beat is one idea on screen. A line of text landing. A feature name over a background. A logo drawing itself on. When the idea changes, the beat changes. Three rules cover most of it:

• and
  One idea per beatIf describing a beat needs the word "and", it's two beats.
• Read oncetwice

  0 s2 s
  ~2 secondsA text beat lives about two seconds — long enough to read once, not twice.
• 510
  5 to 10 beatsA video is five to ten beats. The launch video is eight.

The skeleton

Every video that works has the same three acts:

The vocabulary8

When you describe a beat to your agent, plain words work — and some plain words map especially well to what Remocn can build:

• Shipit.
  "an animated headline"A line of text that enters with motion
• "lines that stack up"Claims appearing one after another
• "a living background"Slow, animated color behind everything
• "a hard cut" / "a scene change"How one beat hands over to the next
• $ npx shadcn add
  "a terminal that types"A command line typing itself out
• Save
  "a fake app screen"An interface with buttons, menus, and dialogs that act
• "a logo that draws itself on"
• 110+
  "a counter"A number counting up to a milestone

You never need to know what any of these are called internally. Your agent does.

From beats to prompt

Write your video as a numbered list of beats — one line each, your copy in quotes. That list is 80% of a prompt; add a format line and a style line and it's done:

Build a ~15-second, 1920×1080, 30fps video in this Remotion project,
using remocn components:

1. Hook — an animated headline: "<YOUR LINE>".
2. Body — three lines that stack up: <YOUR CLAIMS>.
3. Close — a terminal that types: `<YOUR CTA>`.

Style: dark background, one accent color <HEX>, calm pacing.