'One prompt' motion graphics is mostly a myth. Here's what the good ones actually did
Nikandr Surkov went through about a hundred of the most-shared Opus 5.5 motion videos and the replies under them. The 'one prompt' turned out to be a brief, references, a spec and several rounds of notes.
Nikandr Surkov's six-minute video (and the longer X article behind it) is the most useful corrective we've seen to the 'Claude one-shot this' wave. He reviewed about a hundred viral Opus 5.5 motion pieces and read the replies. His examples: a Claude Code engineer at Anthropic pointing out that the 'one prompt' is often 10,000 characters plus skills, examples and API keys; the viral 'Claude Pop' music video coming from a brief of more than 9,000 characters, a folder of references and around 12 hours of Claude working; and one creator's 45-second hand-painted short taking 163 model calls, about $34 and almost seven hours. Those figures are as he reports them.
Pick where to build. Claude Motion (which he says Anthropic launched on October 8) builds explainers as code inside Claude, but it's a Team/Enterprise beta. Claude Design is on every plan and suits animated prototypes and single scenes. Claude Code with a renderer, Remotion or HyperFrames, is what most of these creators use, because a change is one edit and a re-render instead of starting over.
Start from a reference, not an adjective. Without one, he says, Opus falls back to its default look: centred text, a gradient background, everything fading in. Claude reads images, not video, so turn the reference into frames first (his article uses ffmpeg at 4 frames per second) and have Opus write down what it sees before it builds anything. Then give it your real logo, fonts, colours and screenshots, or it will invent a generic interface.
Write a spec, not a vibe. That means size, frame rate, length, an ordered shot list, and a beat grid: at 120 BPM and 30 fps, something should land every 15 frames. It also means a banned list: no cream background, no gradient, not everything centred, not fade-in as the only entrance. Every animated value should come from the frame number, with no CSS transitions or timers, so each frame renders the same way every time and fixing one shot doesn't break the next.
Storyboard in stills before anything moves. Ask for three storyboard options, pick one, then get one still per scene, because fixing a still takes seconds and fixing a render takes a re-render. After each pass, have Opus render frames at every cut and check them itself. If there's music, have it measure the real beats in the track. Give notes the way an editor would, with a timestamp and a concrete instruction ('hard cut here', 'push in on the button'), because 'make it better' just gets you random changes.
On the business side, he cites one founder who says he sells 15-second promos for $400, and founders who priced freelancers at $500 to $1,500 for 30 seconds. Those are figures he quotes, not market data we've checked. He also flags licences: Remotion is free for individuals and companies of up to three people, and HyperFrames is open source. His conclusion, and ours: what you sell is taste, real assets and rounds of review. The prompt is the least valuable part.