Guide
Making a film
From a request to a delivered film: three storyboards, stills, a draft, the masters, review rounds, other formats, delivery and cleanup.
Asking
You ask in words, in any language, and nothing renders on its own. Each request below is one message: the skill fills whatever it does not say with a default, asks what it cannot guess, and waits for you three times, at the storyboards, at the contact sheet and at the delivery.
| Ask | You get |
|---|---|
| Make a 15-second promo loop of https://acme.app: premium, dark, no music. | Three storyboards on three formats, one recommended, then a wait for your pick. |
| A 60-second film of Acme from its repo, one chapter per feature, 16:9 for YouTube. | A film on a timeline, chapter marks in the mp4, the chapter list for the description. |
| A 9:16 teaser of acme.app for social, 10 s, kinetic type on the site’s own headline. | A vertical loop made of the site’s own words. |
A 6-second GIF loop for the README: the terminal typing acme init, 960 px wide. | A terminal film, encoded as a GIF. |
| Like last time’s promo, but on the grid look with the brand’s orange as the only colour. | The product’s kit reused, the look changed. |
Behind a request, Claude asks for the website or repository to base the film on (the brand, strings and screens come from its source), the duration, the format, the output, the accent, the look, the sound and where it goes. A promo is made in two versions by default, 16:9 and 9:16, each composed for its own frame; Claude asks only when you name a single aspect. The same questions are the Studio’s ten steps.
Three storyboards
Before any code, Claude shows three storyboards as tables on the music’s beat grid (time, beat, what happens), each on a different format: three storyboards are three formats, not three pacings of one idea. It recommends one, and you pick or tweak it: Storyboard B, with A’s ending. For a product that already has a film kit, the style is settled and a release film gets one storyboard.
Stills and the contact sheet
Next, one still per scene, the settled moment plus one mid-morph where a morph carries the scene, as a captioned contact sheet. Claude looks at every frame first (cramped, off-grid, illegible at that zoom, an empty hold, a ripple off the cursor’s tip) and runs clickcheck.mjs, which fails a click the viewer would not see. Then it shows you the sheet with a line per scene, and the looks sheet too while the look is still open, and waits for a go. Show me the looks sheet on the first real frame puts every preset on one sheet, to choose by eye.
A draft
A fast draft of the whole film first. PREVIEW=1 renders it at a sixteenth of the work, about 16 times faster.
The masters
On your go, the film renders, one render at a time, cool by default. The output’s extension picks the format: .mp4 (H.264, or HEVC), .mov (ProRes 422 HQ), .webm or .gif, in every aspect asked for, with a cover per aspect and, for a long film, chapter marks. Afterwards the file is read back (size, frames, length, sound) and a file that does not match fails the render instead of passing for a finished film. A loop is checked too: loopcheck compares the first frame with the last, and its PSNR must be infinite.
Review rounds
- The headline lands on the click, not before, and a slower camera in the second scene.
- Render 12–20 s at full quality, I want to see that transition. One range (
FROM,TO). - Put a metronome under it, so I can hear whether the cuts land.
AUDIO=click. - Put this track under it.
AUDIO=track.mp3, brought to −14 LUFS (AUDIO_LUFSchanges it,AUDIO_NORM=0keeps the track as it is). - Cut it on the track’s beat. See Sound.
- Crisper motion, like a film camera.
SHUTTER=180(orPROMO_META.shutter): the sixteen subframes cover half of each frame instead of all of it.
Other formats of the same film
- Also as .webm for the site, and a 960 px GIF. With
KEEP=1on the master, an encode in seconds rather than a new render. - A ProRes copy for Final Cut. A
.mov, ProRes 422 HQ. - A lighter mp4 under 8 MB for the newsletter. Re-encoded from the master, not rendered smaller.
Delivery and cleanup
While a film is made, everything lives in ~/Downloads/<name>-work/: the source in src/, stills, sheets, drafts, the renders. A second folder holds only what gets used.
| Folder | Holds | Lifetime |
|---|---|---|
~/Downloads/<name>-work/ | the source in src/ (page, engine, fonts, tools, node_modules), stills, sheets, looks, drafts, the renders | until the film is out |
<name>/, where your instructions keep finished media (else in ~/Downloads; with a brand library, <Brand>/video/<name>/) | each format and aspect of the film, a cover per aspect, a chapter list for a long film | yours, to use |
- Deliver it.
deliver.mjsclones the finished files into the second folder and nothing else. It never overwrites, refuses a draft, probes every video (size, fps, frames, colour tags) and writes the chapter list a YouTube description wants. When/Applications/ImageOptim.appis installed, each cover goes through it, compared with the original by SSIM. - The film is out: throw the work folder away.
deliver.mjs trashdoes a dry run first, listing anything that exists nowhere else; then, on your OK, the work folder goes to the Trash. It refuses until every source file in it is in the product’s kit (committed and on a remote branch) and every render was delivered. - Commit the kit to the repo, then clean up. The source goes into the product’s
scripts/film/, pushed, and only then the work folder.