Mr. Bean the fade-up and the model hands you a scale-in from 0.95.
Same habit. New costume.
That's what the ban list is for:
> run a generation
> read what replaced the thing you banned
> ban that too
> two or three rounds clear the defaults for a whole project
In this one the confetti cannon fires a burst every 2.4 seconds.
Red smoke rolls, the sun throws rays, pages and cards orbit the man and his bear.
How many rounds did your last prompt get? One?
The loop I run with Opus 5.5 is in the article 👇
"Smooth" has no duration.
"Snappy" has no curve.
"Elegant" has no distance.
Ask an AI for smooth motion and it fills the gaps with the motion it has seen most.
That's why every AI animation looks the same.
Numbers don't have a median.
Every camera move in this video:
1200 ms
cubic-bezier(0.4, 0, 0.2, 1)
then an 1800 ms hold on the target
Cards orbit the dealer and slip behind him, 31.8 seconds a lap.
What would "smooth" have given you here?
How to brief Opus 5.5 in numbers, step by step, in the article 👇
The fastest way to make an AI animation look AI-generated is to ask for "smooth, cinematic motion."
Sounds like a good prompt. Until you realize thousands of people are giving the model the exact same instruction.
You get the familiar result. Floating elements, gentle camera moves, fade-ins everywhere, and transitions that somehow always feel like 300ms.
Opus 5.5 can produce much more interesting motion, but you have to stop letting it make every creative decision.
Take the animation in this video.
The camera moves through a futuristic reactor, closes in on individual components, shifts perspective, and reveals details you couldn't see from the starting position.
Making those movements look intentional comes down to a few things:
>Remove the default fade, bounce, and slide effects before writing anything.
>Give each camera movement an exact duration and easing curve.
>Specify when the camera accelerates, slows down, and holds its position.
>Freeze the animation at key moments and compare the frames.
>Fix the timing values that feel wrong without rebuilding the scene.
One of the most useful tricks is reviewing frozen frames instead of watching the animation on repeat.
A transition can feel fine at full speed while hiding awkward spacing, bad composition, or a camera that settles too early.
And when something looks wrong, "make it smoother" usually isn't enough information to fix it.
Change the duration. Adjust the easing. Move the start time. Check again.
I wrote a full breakdown of this workflow using Opus 5.5, including how to build a motion brief, review the frames, and make precise corrections.
The article is quoted below 👇