As of: 2026-10-12 07:22 CEST.
Researched and written by AI agents (Claude Opus 5.5 in Claude Code). Human editor: Adam Bicz.
Canonical page: https://postcutoff.com/p/x-rexan_wong-2103707054108299437/

# “everyone’s sharing motion graphic videos that Opus 5.5 made, and it’s genuinely…”

Rexan Wong (@rexan_wong), X, 2026-09-26.
Source: https://x.com/rexan_wong/status/2103707054108299437

## Archived text

> everyone's sharing motion graphic videos that Opus 5.5 made, and it's genuinely insane
> 
> everyone says they created it with "one prompt", but my one prompt video looked mid
> 
> so i went through a bunch of these videos to see how they were actually made, and found the workflow that works
> 
> here's how to generate pro level motion graphic videos w/ opus:
> 
> 1. get reference videos to direct from -> http://whatships.com
> 
> pick 1-2 videos whose style you want and tell opus to match them. naming a style works way better than describing one
> 
> without a reference, opus falls back to its default look: centered text, gradient background, everything fading in
> 
> that's why so many of these videos look the same. a reference gives it the pacing, the type and the transitions to copy
> 
> 2. install @HyperFrames_ or @Remotion so opus can build the video
> 
> both let opus write every scene as code and render it straight to mp4. no video editor
> 
> without one, opus can only describe a video or hand you a rough html page you have to screen record
> 
> with it, every frame is exact, and when you ask for a change it edits one line and re-renders instead of starting over
> 
> 3. install @21st_dev for high quality components in the video
> 
> real buttons, cards and UI components made by design engineers, instead of whatever opus invents on the spot
> 
> without it, opus draws your product UI from scratch and it looks off. wrong spacing, placeholder boxes, fake-looking buttons
> 
> anyone who's used good software can feel it in a second, and the whole video reads as cheap
> 
> 4. steps 1-3 were context + setup. now dump all of it into opus
> 
> your brand (logo, colors, fonts), screenshots of your real product, the reference video, and a quick braindump of how you see the video
> 
> then ask for 3 storyboard variants
> 
> without this, opus guesses your colors, your font and what your product even does. the video could be for any startup
> 
> with it, it could only be yours. and 3 variants means you pick a direction instead of fixing the first idea it had
> 
> 5. pick the storyboard you like
> 
> ask for one still frame per scene before anything moves. fixing a storyboard is way cheaper than fixing a render
> 
> without this step, you only find out scene 4 is wrong after the whole thing is animated, and every fix means re-rendering. a still frame takes seconds to change
> 
> 6. let claude cook
> 
> then give notes like a director: "slow every zoom to 0.7x", "hard cut here", "push in on the button"
> 
> without notes, the first render is usually 80% there, and that last 20% is what makes it look pro. vague notes like "make it better" get random changes. camera words get exactly the change you want
> 
> everyone has the same model. the context you give it is what makes it look pro
> 
> let it cooookk

Archived 2026-10-11 via fxtwitter (unofficial).
Counts: 632,029 views, 6,864 likes, 562 reposts, 144 replies (at fetch time)
Media: https://video.twimg.com/amplify_video/2103706737085980672/vid/avc1/2016x1512/SspSYoIGK60rnXFy.mp4?tag=29

## Cited in

- Video: [Opus 5.5 motion-graphics workflow: reference videos, HyperFrames/Remotion, 21st.dev, storyboards](https://postcutoff.com/v/rexan-wong-opus-5-5-motion-graphics-workflow-x/)