product-launch-video

Provide the product URL and the workflow captures the site, extracts brand tokens, drafts a storyboard and script, builds each frame as an HTML composition, and renders the final MP4 after your approval. User-gated review happens at setup, storyboard, and final render.

It accepts an explicit product or marketing URL, a pasted script or brief saved verbatim as user_script.txt, or a brand name resolved via web search. A no-capture path exists when the brief says not to scrape, using hand-written token and asset files.

The build-frame.mjs script copies a chosen frame preset and deterministically remixes its color keys and font families onto the captured brand tokens in tokens.json. It preserves preset structure, clamps type weights to available brand faces, and self-validates ink/canvas contrast.

Yes. Setting music: none in the storyboard with no SCRIPT.md marks the project fully silent, so no audio is generated and the assembler treats the video as frames only. Narration without music is also supported.

Assembly fails when a frame has media inside a sub-composition, a timed element missing class="clip", overlapping clips on the same track, or a missing data-composition-id. Fix the worker output for that frame and re-run assembly.

Route non-promotional intents, bare make-a-video requests, or any uncertainty to the /hyperframes intent layer, which owns all route decisions. Figma sources should go through the /figma skill first for asset export and brand tokens.