How it works

The workflow from brief to render, and what runs underneath it.

A launch folder

A product repo keeps its videos in launch/. launch/CLAUDE.md tells Claude how to work there, including anything your team writes down about how it makes videos. Each video is a folder:

Path	What it holds
`launch.config.ts`	Marks the folder and points at the product, so videos can import its components.
`videos/<id>/video.tsx`	The video: its shots, timing and copy.
`videos/<id>/brief.md`	The claim, the features and where each one can be seen.
`videos/<id>/captures/`	Scripts that record the running product, and their manifests.
`videos/<id>/audio/`	The music track and its beats, sound effects, a voice-over.
`videos/<id>/media/`	Images and clips you bring for the video: a logo sting, a photo, a screen recording.
`videos/<id>/reference/`	Your screenshots of what to show. Claude reads them; they do not appear in the video.
`videos/<id>/licences.json`	Where each external file comes from, and its licence.
`videos/<id>/comments.json`	Review notes left on the storyboard.
`videos/<id>/out/`	Stills, boards and renders. Not committed.

The workflow

Each step is agreed with you before the next one starts. What you hand over at the start (a sentence, screenshots, a track, a recipe your team wrote down) decides how much Claude asks; the steps stay the same. Recipes has ways to start.

Discover. Claude reads the product and runs it, then asks what only you know: what sets it apart and who it is for. The result is brief.md.
Script. One person doing one real task, each feature the next thing that happens in it.
Music. Intentface Launch does not make music, but it cuts the video to a track, so the track comes before the sketch. Use music you already have, or generate one (Suno, ElevenLabs Music and the like) from the brief Claude writes from the script. Drop it in audio/, and pnpm launch beats finds the beats, sections and quiet breaths that the shots are timed to.
Sketch. Claude captures the product and builds every shot flat and cheap, on the track's beats. pnpm launch board makes a storyboard and an animatic, and lists under each shot any text held too briefly to read; you leave notes per shot in the studio.
Build. Shots are finished one at a time: the product's own motion, UI state changes, 3D and motion blur where planned. Claude checks each one in stills and contact sheets.
Check and render. pnpm launch check measures every piece of text on screen for reading time, size and contrast, and flags layers that cut their own content and end frames that differ from the approved logo. Then pnpm launch render makes the mp4.

Underneath

Frames, not playback. Time comes only from useFrame(). The renderer seeks each frame and screenshots it, so nothing depends on how fast a machine is.
Captures. A capture script drives the running product in a browser one exact frame at a time. A snapshot saves the page's DOM and CSS, so close-ups stay sharp at any zoom.
Rendering. Work is split into one-second chunks that browser workers take from a queue. Frames with motion blur render several subframes and average them. A stopped render resumes with --resume.
Skills. The method lives in skills that Claude loads: product-launch-video, creative-direction, kinetic-typography, ui-motion, micro-animations, logo-animation, motion-review, music-brief, sound-design and social-formats.