Same Claude Opus 5.5. Same product. The only difference is the first domino
Most people open Claude Code, type "make a cool 20-second video for my app" and then wonder why the timing feels random and every small fix breaks half the clip
Claude isn't bad at animation, it's just guessing, because nobody told it when anything is supposed to happen
What fixed it for me was writing a short brief before any code gets written, so every moment of the video is decided upfront, the same way you line up dominoes before you push the first one:
> Structure: how many scenes there are and what happens in each, for example the interface comes in, one click happens, the result holds on screen, then the logo
> Key moments: when the button appears, when the click lands, and from what point the result has to be readable
> Constraints: style and colors, spring() for entrances, no CSS animations, every value driven by useCurrentFrame()
> What stays locked: everything Claude must leave alone when you ask for changes later
> And before watching any motion, ask for three stills (the opening, the click, the final frame), because layout problems show up there instantly
Revisions work the same way. Instead of "make it smoother", you tell Claude where the problem is, what exactly is wrong, what to change and what has to stay the same, and it fixes that one thing instead of quietly rebuilding the whole video
One action per video, one clear brief and a couple of targeted revisions, and by your second or third video the difference is obvious
The full workflow and the example brief in article ⤵️