Opus 5.5 can't output a video file. It writes the code that draws one, and a browser renders that code to MP4.
The setup most creators use: Claude Code runs Opus 5.5, and the open-source HyperFrames plugin turns its code into video. About 15 minutes the first time.
Official docs: Claude Code, HyperFrames quickstart
Opus 5.5 makes videos by writing and running code, so you need an agent that can create files and run commands. Claude Code on a paid Claude plan is the common setup.
HyperFrames is an open-source framework from HeyGen that turns HTML, CSS and animation code into a deterministic MP4. It ships skills that teach the agent the whole production loop.
claude plugin marketplace add heygen-com/hyperframes claude plugin install hyperframes@hyperframes
Start the prompt with /hyperframes and say what you want: length, aspect ratio, subject, style, audio. Give it your website or product folder so it can use real screenshots and colors.
/hyperframes make a 15-second launch video for https://your-product.com, 16:9, bold kinetic type, music on every cut
The agent builds an HTML composition you can scrub in the browser. Ask for changes in plain words: slower intro, bigger logo, swap the palette.
npx hyperframes preview
Rendering runs on your own machine with a headless browser and FFmpeg (Node.js 22+ required), so it costs no model usage. Export 16:9 for YouTube and 9:16 for Shorts, Reels and TikTok.
npx hyperframes render
Rewritten from the patterns behind the videos people are sharing. Replace the {{PLACEHOLDERS}} and paste into Claude Code.
Use it for: A first test, or when you want the model to pick the style.
Use /hyperframes to make a dynamic {{LENGTH}}-second motion graphics video about {{TOPIC}} that shows what an incredible motion designer you are, like a showreel. Go all out: pick the style, pacing, typography and sound yourself. 1920x1080.Tip: Run it at the highest effort level. Point it at your project folder and it will use real screens and colors instead of inventing them.
Use it for: Launch posts, Product Hunt, landing page hero videos.
Use /hyperframes to make a {{LENGTH}}-second launch video for {{PRODUCT}} ({{URL}}).
Audience: {{AUDIENCE}}. One-line promise: {{PROMISE}}.
Read the website first and use its real screenshots, logo and colors ({{BRAND_COLORS}}).
Structure: a hook in the first 1.5 seconds, the problem, three features with one scene each, then the call to action with the URL.
Style: large kinetic type, a new idea every 2 seconds, hard cuts on the beat.
Rules: no invented stats, customer names or prices. No timecodes, scrubbers or UI chrome on screen.
Audio: royalty-free or generated music, a sound on every cut.
Export 16:9 and 9:16.Tip: The "no invented stats" rule matters. Without it the model happily adds fake numbers.
Use it for: Teaching a concept, a feature or a process.
Make a {{LENGTH}}-second animated explainer of {{CONCEPT}} for {{AUDIENCE}}.
Write the script first as 4 to 6 scenes, each with one idea and one visual metaphor.
Use diagrams, labels and simple shapes, not stock-looking illustrations.
Keep on-screen text short enough to read in the time it is shown.
Add narration if a text-to-speech tool is available, otherwise captions.
Render to MP4 at 1920x1080.Tip: Ask for the script and storyboard before any code. Fixing a scene list is much cheaper than fixing a render.
Press play to watch each one from the creator's original post on X. The notes under each video are ours.
The short, open brief that started the trend: ask for a 15-second showreel and let the model pick style, pacing and sound.
Canvas · @ajith_io
The model is told to research a known SaaS and pull real screenshots and logos before animating, which is why it looks like a real launch.
SVG, GSAP · @moritzkremb
A structured prompt with inputs, rules and a music brief. A single shape becomes a button, a loader, a player and more, cut to a 120 BPM track.
SVG · @twoclipping
Asks for 8 to 12 real product states plus brand colors, then renders one HTML file with one draw(t) function in 1:1, 16:9 and 9:16.
Canvas · @verbove
Five fixed scenes: the problem, what you do, how it works in 3 steps, one proof point, your name. A reusable skeleton for any small business.
SVG, GSAP · @alex_prompter
A two-line prompt that asks for a new visual style on every level of the explanation. Good proof that constraints beat length.
Canvas · @emollick
A step-by-step recipe animation. Works for any process: onboarding flows, setup guides, how-it-works sections.
Canvas · @Ror_Fly
A doodle and paper-fold style set by the prompt, telling a long story in a short loop. Style words carry most of the look.
Canvas · @songkeys
Starts from an empty repo: the model pulls real weather data, compares years and animates the result with sound.
Canvas, Audio · @GroundControl
The prompt makes the model analyse an S3M music file first, then time every effect to it. The pattern behind most beat-synced videos.
Three.js, Shader, Audio · @gandamu_ml
A two-minute piece from a two-sentence prompt, with background music and sound design. Shows how far a short brief can go at high effort.
Shader, Canvas · @Michaelzsguo
Not a video but a playable 3D scene. Anything the model can build in a browser can be screen-recorded into a video.
Three.js, Shader · @MandelDuck
Different tools for different jobs. Opus 5.5 builds motion graphics from code; video models generate footage.
| Opus 5.5 (code-rendered) | Text-to-video models | |
|---|---|---|
| What it outputs | Code (HTML, SVG, Canvas, WebGL) rendered to MP4 | Video pixels directly |
| Editing one detail | Change one line: a word, a color, a timing | Regenerate the clip and hope it keeps the rest |
| Text on screen | Always spelled right, any font you load | Often garbled or inconsistent |
| Brand accuracy | Exact logo, colors and real screenshots | Approximate |
| Best for | Launch videos, explainers, data stories, UI demos, kinetic type | Realistic footage, people, nature, camera moves |
| Weak at | Photoreal people and live-action scenes | Precise layouts, legible text, exact timing |
The workflow above is free apart from your Claude plan. If you would rather not run it yourself: