Make launch and product animations with Claude in code, and budget for follow-ups

A creator's lab notebook shows Claude Opus 5.5 producing three studio-style animations in code, and how many follow-ups and hours each one really took.

Get the prompt

Explain it simply

Instead of drawing an animation, the AI writes computer code that produces the pictures and the sound. Because it is code, you can fix it precisely by pointing at a specific frame. Each piece still took a couple of hours and many rounds of changes.

What was done

Florence published three animations made with Claude Opus 5.5: a liquid-chrome title loop, a 3D product shot of wireless earbuds made from a vague prompt and from a directed one, and a 3D mascot.

Opus writes three.js, shader and Web Audio code instead of drawing pixels, so picture and sound can be checked frame by frame and fixed with notes that use exact numbers.

How it went

Each piece took real iteration. The chrome loop took about 2 hours, 10 picture follow-ups and 12 transition checks, plus about 45 minutes and 5 follow-ups for sound.

  • The vague earbuds prompt came back with most of the clichés the directed prompt banned; the directed version took 15 follow-ups and about 90 minutes, plus 90 minutes and 12 follow-ups for sound.
  • The mascot took about 2 hours plus 70 minutes of sound; all 71 frame checks passed after 6 failures were fixed.
  • Claude can't hear: early mixes landed hits late and put energy where phone speakers play nothing.
  • A creator's own experiments, not client work.

Prompt

PromptWritten by our editors from the source
Make a 6-second seamless loop, 1080x1080 at 60 fps, as a single HTML file using three.js [pin the version].

Goal: [one sentence on what the viewer should feel or understand].
Timeline: 0–1.0s [action]; 1.0–2.5s [action]; 2.5–6.0s [action].
Use easing [cubic-bezier(0.22, 1, 0.36, 1)], a 60 ms stagger, and anticipation before every big move.
Ban: dark space backgrounds, glowing rings, bloom, floating particles and made-up taglines.

After building, render frames 0, 30, 60 and onward, check every transition against these timings, and list what's off by frame number before fixing it.

Our structured version; the article’s exact prompts are in the source.

Setup notes

  1. Write the timeline in seconds and the bans up front; vague prompts come back full of clichés.
  2. Give follow-ups by frame number, not by feel.
  3. Add sound last, with one prompt keyed to frame numbers, and check it on a phone speaker.
  4. Budget 5 to 15 follow-ups per piece.

Business fit

Who this helps, and how:

  • CreatorsCreators can make signature intros and loops without After Effects.
  • Shopify & ecommerceStores can produce product loops for launches and ads from a prompt and a reference.
  • StartupsStartups can make launch videos in-house and iterate by frame instead of by agency round.

Related

Similar tools

Other tools for this job, and how they differ. Chosen by our editors, never paid for.

  • Claude Code

    Anthropic's coding tool: it works on the animation files and runs commands from your terminal instead of a chat.

  • HeyGen

    Makes presenter videos with an AI avatar from a script, rather than animations you direct in code.

  • Opus Clip

    Cuts long videos you already have into captioned shorts; it needs a source video to work from.

Evidence grade B means: The person who did the work describes the setup and results in detail. How we grade. Spotted a mistake? Suggest a correction.