zero (@twoclipping) published a detailed motion-design workflow built around Claude Opus 5.5, browser-rendered frames, and FFmpeg. The striking part is not simply that an AI model wrote animation code. It is the production discipline around that code: reference analysis, beat timing, licensed assets, preview stills, and frame-by-frame checks. This guide reorganizes zero's long X article into a usable sequence. The original remains the place to watch all four clips and read the three complete demo prompts.
zero's workflow makes short launch films from a time-addressable HTML scene. Claude Code plans and writes the animation; Playwright captures frames at requested times; FFmpeg turns frames and sound into a video. The films depend on creative direction and quality control, not a one-click generator. The article's "$0" claim is best read as no required traditional editing software or paid stock footage, not a verified zero total cost.
Watch and Credit the Original Creator
Original article and demos: How I Make $10K Launch Videos for $0 with Opus 5.5 (Full Course), by zero (@twoclipping), posted 28 September 2026. It includes an opening sample, three product or UI demo clips, and their complete prompts. The price comparison and results are the creator's claims; they are not independently established here.
The X card above links to the article. X's standard external embed does not expose its individual videos as separate players, so use the original article to play the clips and access the full prompts. We have not copied or rehosted the creator's media.
The Six-Step Workflow
1. Turn a reference into a storyboard
zero begins with a motion reference rather than a blank prompt. The agent extracts regular frames and lays them out as contact sheets, then identifies scene beats, transitions, camera moves, typography, and color decisions. The aim is to understand how the reference communicates, then write a new structure for the user's own product. A reference should guide technique, not become a shot-for-shot copy of someone else's protected work.
2. Prove the rendering pipeline with two seconds
The creator has Claude Code set up FFmpeg, Playwright, and Chromium, then render a tiny test before attempting the full film. A single HTML file exposes a function such as seek(t) that can draw any requested moment. Because frames derive from time rather than accumulated timer state, the agent can inspect a particular frame, make a targeted change, and render it again. Playwright documents browser screenshot capture; FFmpeg handles media assembly. This is a code-and-browser workflow, not a claim that the model itself generates final video pixels.
3. Bring approved assets and map the music
zero uses a music track with a clear rhythmic change, real sound effects, product imagery, a logo, and a restrained font set. The agent analyzes the track's beat grid so visual events land deliberately rather than at arbitrary times. The article points to Mixkit music, Mixkit sound effects, Pexels footage and photos, and Google Fonts. Check the license for each selected file before publishing: Mixkit has asset-specific licenses, and Pexels limits uses involving identifiable people, brands, and unaltered resale.
4. Brief one format, not a generic 'make it cinematic' request
Each of zero's three long prompts has the same useful architecture: inputs to collect, art direction, a beat-by-beat story, technical build rules, known failure cases, and a checkpoint before the complete render. That order forces the project to become reviewable. The prompts and clips are published together in zero's article; the format summaries below help you choose one without reproducing the full source prompts.
5. Design transitions that carry the story
Across the examples, objects transform into the next scene: a button expands into a page, a circle reveals a product card, or one UI control changes state. Motion is tied to the music, the camera makes one readable move at a time, and sound effects mark interaction. This is zero's aesthetic preference, not a universal rule: a softer product or documentary story could call for cuts or a different visual language. The general principle is to give every transition a purpose.
6. Render, inspect, and revise
Before committing to the full export, the creator asks for a beat map and key stills. The final pass renders at 60fps, adds subframe blending for motion blur, balances audio, and checks fast transitions for single-frame pops or overlapping text. FFmpeg's tmix and loudnorm filters are part of the toolchain. The specific subframe count varies by sequence in the source prompts; more samples increase render work and do not automatically repair poor animation timing. A human still watches the complete export and gives concrete notes.
Which of the Three Demo Formats Fits?
Product request to result
The first demo is a roughly 15-second widescreen film for a fictional food-ordering assistant. A typed request becomes a send action, an agent's search becomes a visual motif, and the selected meal resolves into an order and end card. Its strength is a simple customer story: request, matching result, action. It needs product screenshots or licensed result images, one clear user input, and a logo. Watch the demo and read zero's first full prompt on X.
Photo product across devices and purchase
The second demo is a square product film, built as one continuous chain of photos, editing controls, phone and desktop interfaces, an order sequence, and a final physical print. The source brief is substantially more complex: several supplied images, a wall clip, interface states, glass-like layers, and careful timing through a longer track. It illustrates how a product's full journey can remain legible when each state grows from the previous one. Watch the second clip and consult its prompt on X.
One shape, many interface states
The third demo is a looping UI-motion reel. A single element changes through controls such as a button, loader, player, slider, toggle, tabs, chart, command palette, and toast. Here the product story is replaced by a study in continuity: the last frame must match the first, including cursor motion, so the loop does not jump. This is the smallest format to try when you have no licensed photography or real product footage. Watch the loop and read zero's third prompt on X.
What Actually Makes the Result Look Finished?
- A beat map before animation: decide when the viewer should understand each product benefit.
- Visible handoffs: use the same object to connect scenes when continuity helps the story.
- Deliberate constraints: choose a format, palette, type system, and motion language early.
- Real audio: licensed music and sound effects should be checked for timing and rights.
- Frame inspection: stills and fast-moment scans catch issues a broad prompt cannot.
- Director feedback: ask for a shorter hold, clearer label, quieter sound, or better reveal instead of simply asking the model to “make it premium.”
The Headline Says $0. What Does That Mean?
zero argues that this method can avoid After Effects, conventional video-editing software, and paid stock for the examples shown. That is useful, but it is not a production-cost audit. Claude access may be paid or usage-limited; rendering consumes computer time and electricity; finding or preparing assets takes time; and revision, accessibility, rights checks, and client approval remain labor. The article's comparison with studio-priced launch films is a creator claim, not evidence that every output has equivalent quality or value. For client work, log minutes, model usage, render time, licensed-asset checks, and revision rounds before you quote a price.
zero also closes with a distribution point: a polished film does not, by itself, put a product in front of buyers. The creator promotes an affiliate/creator network and reports campaign outcomes. Treat those numbers as self-reported marketing claims; the transferable lesson is to plan the audience, channel, and measurement alongside production.
A Sensible First Project
- Choose one real product action and a 10-15 second story. Write the audience, promise, and final frame in plain English.
- Use your own product UI, logo, and two or three approved assets. Record their sources and licenses.
- Sketch four stills: opening problem, product action, result, end card. Get a human to approve the story before coding.
- Run a two-second rendering test and inspect its first, middle, and final frames.
- Render a low-resolution preview, revise pacing and legibility, then export the final video with sound.
- Watch it on a phone without sound and on a desktop with sound. Publish only after brand, claims, rights, and accessibility are reviewed.
Turn the Workflow Into a Business Idea
This original prompt uses the article's production skills to explore buyers and a small test. It does not assume that a video agency is automatically the right business.
Find a buyer for a repeatable motion workflow
Three distinct offers, one seven-day validation.
Sources, Tools, and Creator Credit
- Creator and primary source: zero's full X article, with four playable clips, the complete production process, and the three original prompts. Follow @twoclipping for the creator's work. This article is an independent explanation, not a republication or endorsement.
- Rendering tools: Playwright screenshot guide and FFmpeg filter documentation.
- Assets and rights: Mixkit licenses, Pexels license, and Google Fonts. Read the relevant license for each asset and output channel.