My X feed has been full of Opus 5.5 motion graphics this week.

And almost every post says the same thing:

“Made this with one prompt.”

So I started going through the good ones to figure out what they were actually doing.

And turns out, the model isn't the whole trick.

The best results usually have a workflow behind them:

a reference video, a proper storyboard, HyperFrames or Remotion, real UI components, and a few rounds of very specific direction.

Once you understand that, Opus 5.5 gets kinda ridiculous.

Because Claude isn't even generating these videos like Veo or Kling.

It's writing them.

I’m gonna tell you how you can create that too

I am Alex. Welcome to ShortCu8 by Innov8.

Lets Dive Deep🐰🐰.

Go to whatships.com and pick one or two motion-graphic videos you like.

Give those to Opus and tell it to follow that visual direction.

This matters because if you only say:

“Make me a clean Apple-style product video.”

Opus has to guess what that means.

And its default guess is often the same thing everyone gets:

centered text, gradient background, fade in, fade out.

A reference gives it the pacing, typography, camera movement and transitions to work from.

Install HyperFrames or Remotion.

This is what turns:

“make this animation”

into an actual MP4.

Opus writes every scene as code.

The renderer turns that code into exact frames.

And when something is wrong, Claude can edit the code and render again.

You don't have to rebuild the whole video.

If you're making a product video, install 21st.dev too.

Otherwise Claude may invent every button, card and dashboard element itself.

And you can normally feel it.

Spacing looks slightly wrong.

Buttons look fake.

The UI looks like a mockup instead of your actual product.

21st gives Claude proper components to work with.

Before generating anything, dump in:

your logo, brand colours, fonts, real product screenshots, reference videos and a rough explanation of how you imagine the video.

Then ask:

Give me 3 storyboard options.

Don't animate the first idea Claude has.

Pick the direction you actually like.

Once you choose a storyboard, ask for one still frame from every scene.

Check those before animation starts.

If scene 4 looks bad, fixing one image takes seconds.

Finding that problem after the whole scene has been animated is annoying.

This is basically your cheap review stage.

The first render probably won't be perfect.

Don't say:

“Make it better.”

Say:

“Slow this zoom to 0.7x.”

“Hard cut here.”

“Hold this frame another second.”

“Push into the button.”

“Don't touch scene 1. Redo scene 2.”

Those instructions are much easier for Claude to execute.

And this is probably the biggest thing people miss when they see the viral “one prompt” posts.

The model is the same for everyone.

The quality comes from the reference + context + storyboard + corrections you give it.

Now go and let Claude cook 👨‍🍳

We read every reply - just reply to this email and let us know how we can improve !

#AD1

Your teams are moving fast, burning tokens, and shipping more than ever.

But more output doesn’t mean more impact.

Jira Product Discovery brings your ideas, customer insights, and business context together so product teams can weigh the evidence, make the tradeoffs, and decide what’s actually worth building. Then connect those decisions directly to delivery in Jira, so everyone knows what you’re building and why.

Jira Product Discovery. For better product decisions in the AI era.

Get Started for Free

#AD2

Parallel, Turbopuffer, and Wordsmith run their entire GTM motion on Attio, with agents that chase every buying signal, build pipeline, and move deals forward, 24/7. Try Attio now.