Video Storyboard

Do this BEFORE a single frame is animated. A demo video lives or dies on its plan: the wrong order, a missing hook, or a 40-second runtime kills it no matter how clean the motion is. You are the craft layer that decides what scenes exist, in what order, for how long, and what each one says - then hands a concrete scene plan to the mechanics pack (remotion-setup, remotion-compose, remotion-render) to actually build.

Fire eagerly on planning intent: "storyboard my demo," "plan the video," "what scenes do I need," "map out the launch video," "break this feature into scenes." If the user jumps straight to "animate this," still run the beat sheet first - a storyboard takes two minutes and saves a re-render.

Work one example throughout: a 30-second launch video for an AI code-review tool called Sentinel that flags risky diffs before merge.

Operating procedure

Run these in order. Do not write copy before the beats are fixed, and do not set durations before the beats exist - pacing is a function of structure, not the other way around.

Step 1 - Lock the one-line objective and the platform

Before beats, pin two things:

1. The single takeaway. One sentence the viewer must remember: "Sentinel catches the bug your reviewer missed." If you cannot say it in one line, the video has no spine. Everything downstream serves this line.
2. Platform and aspect ratio. Landscape 16:9 (1920×1080) for a site hero or YouTube; vertical 9:16 (1080×1920) for social/Shorts; square 1:1 for feed. This sets the canvas remotion-compose will author and caps the runtime - social wants 15-30s, a hero loop 20-40s, a feature walkthrough up to 60s.