Opus 5.5 Video Prompts Without the Generic Look: Six Parts and Three Test Runs

Opus 5.5 builds a video out of code, so anything your prompt doesn't decide, the model decides for you with a default. Give it frontend work without design direction and Opus 5.5 falls back on a few default styles; tell it in general terms to "avoid a generic AI look" and it mostly trades one default for another. Distinctive results come from prompts that settle the choices you care about (format, content, structure, look, motion) and call out the defaults you don't want by name. Once the first render is back, put whatever default it used on that list and run the prompt again.

Most of the prompts floating around leave nearly all of those choices undecided. The bulk of the Opus 5.5 video prompts people post are short. In the group of roughly 100 words or under, the median is 26 words, and over a quarter are just one sentence. Under 2% of them mention color at all.

What Happens Between Your Prompt and the MP4

In the usual setup, Opus 5.5 writes one self-contained HTML file with Canvas, SVG, GSAP or Three.js. A headless browser renders that file frame by frame, and the frames get encoded into an MP4. That means your prompt has a say over anything code can decide: on-screen words, colors, layout, typography, motion and timing. It has no way to film a scene or record a voice, so those requests need other tools.

Anthropic spells out the defaults Opus 5.5 leans on for frontend work, including cream backgrounds and pill-shaped buttons. In video, the default you'll recognize first is centered text on a gradient with everything fading in.

The amount you need to write changes with where you run it:

• In Claude or Claude Code, the prompt has to include the render rules too: one HTML file, each frame drawn as a pure function of time through a seek(t) function, and no timers or CSS animations, which lets a renderer capture any frame in any order.
• On opus6.video, those rules are handled for you. The tool gives Opus the motion-designer role, has it write a storyboard before any code, enforces the rendering contract, and builds in baseline craft like varied rhythm, a clear type hierarchy and a firm ending. Format and length are buttons, the look comes from a preset or up to three brand colors, and you can add up to four named effects. The brief takes up to 2,000 characters, and the videos are silent. Your brief only has to handle content and design.

Six Parts Every Opus 5.5 Video Prompt Needs

Format: How Long, What Shape, Where It Plays

Format covers the duration, the aspect ratio, and how people will watch: on a phone with sound off, as a five-second intro, or as a loop on a landing page. It goes first. Skip the length and Opus chooses one: a one-line prompt about the history of AI came back at close to three minutes.

A 15-second 16:9 launch video for a product page, readable with the sound off.

Content: Exact Wording, Names, and Numbers

All we gave it was "Make a launch video for my plant care app," and Opus called our test app "Verdant" and finished on a "Download free" card dated spring 2026. Whatever the viewer reads (product name, headline, features, figures) gets made up if you leave it out. A one-line launch prompt for a real product priced it in dollars when the product uses pounds and redrew the app from imagination.

Type the copy out in quotation marks, exactly as it should show up. For an explainer, either provide the dates and numbers or verify each one Opus produces before you publish.

Headline: "Your plants, finally on schedule." Features: snap a photo to identify any plant; a watering reminder for every pot; a care log that shows what worked.

The Opus 5.5 prompt people reuse most is the showreel one-liner. Posts that copied it as-is have a median of 3 likes; posts that worked their own product, topic or music into the same sentence have a median of 34. Our earlier post on 13 Claude Opus 5.5 video examples collects all 13 finished videos together with their full prompts, that showreel included.

Structure: The Beats and How It Ends

Structure sets the number of beats, what each one does, and how the video wraps up. Give the last frame a purpose and a length of time on screen, because a video that cuts off mid-motion feels unfinished.

Open on a drooping houseplant in the first second, reveal the Fernly name, one beat per feature, then end on a card with the headline and fernly.app, held for the last 2 seconds.

Look: Reference, Colors, and Type

The look comes down to three choices, and shared prompts seldom get to the last two.

• A named reference. "Swiss botanical poster" gave our test video flat, poster-like shapes. In the story animations from our earlier post, "Sand animation", "origami" and "Grand Budapest Hotel" each called up a complete visual world in two or three words.
• Specific colors. List hex values, each with a role, and add "No other hue" when nothing else should show up, as the identity bumper in our earlier post did. All three hex values in our test came out exactly as written.
• A named typeface. Anthropic's design guidance calls out Inter, Roboto and Arial as overused defaults. Choose a face with some personality and assign it a job: one for headlines, one for small labels. Our brief named Archivo Black and Archivo, and those are what rendered.

Look: a Swiss botanical poster. Background #10352A, accents #8FD694 and #F2B134, all type in white. Archivo Black for headlines, Archivo for small labels. Big type on a strict left-aligned grid.

Motion: Speed and Transitions

"Punchy" leaves the speed and the transitions up to Opus. Put the tempo in beats or seconds and every change lands on a count, as it does in the UI video from our earlier post that used "120 BPM, 7 bars, something happens on every beat". A transition rule takes away the fade-in default, as the photo-print launch in that post did with "Every scene is made out of the previous one: nothing fades, blurs or cuts". Add one spot where things hold still, so the pacing has contrast. A transition you describe in detail is one Opus builds: in our test, the leaf-into-F-into-phone transition from the brief showed up on screen.

Motion: 120 BPM, something changes on every beat. Each scene grows out of the previous one. Fast cuts, with one held beat on the headline.

The Defaults You Don't Want

Spell out the exact patterns to leave out. A broad "no AI slop" lands you on a different default; a list of named patterns gets rid of them. These make a good first list:

• centered text on a gradient
• everything fading in
• an ending that is only a logo
• cream or off-white backgrounds
• italic accent words
• numbered 01/02/03 labels
• small uppercase labels above every headline
• pill-shaped buttons
• a glow on a dark background

Only about one in twelve of the short prompts people share includes a "no" or "avoid" instruction of any kind.

Combined, the six parts make a short block you can fill in:

Format: [length], [aspect ratio], watched [where and how].
Content: [product or topic]. Headline: "[exact words]". [Features, facts, numbers].
Structure: [opening beat], [middle beats], end on [final frame], held for [seconds].
Look: [named reference]. Background [#hex], accents [#hex] and [#hex]. [Typeface] for headlines, [typeface] for labels.
Motion: [tempo]. [Transition rule]. Hold on [moment].
Avoid: [default], [default], [default].

Same Brief, Three Versions on opus6.video

We made the same launch video three times on opus6.video for Fernly, a plant-care app we invented for the test. Each run was set to 16:9, 15 seconds, the "From my prompt" look, and no template or effects, so the brief was the only difference. Every generation took about 75 seconds.

Version 1: Just the Topic

Make a launch video for my plant care app.

Version 1: Opus made up the name, the release date and the features.

The scenes switched back and forth between a dark green radial gradient and a cream background, the headlines were serif, and the features came from Opus. The end card picked up a pill-shaped button.

Version 2: Adding Content and Structure

For this one, the brief named the app, gave the headline and three features, and walked through the video beat by beat, ending on an end card that holds. It came to 82 words.

Version 2: the words are all correct, and the look is Opus's defaults.

Every word, feature and beat came out as written, right down to the end card held for the final two seconds. The look came directly off the default list: a cream background, numbered "01 / 02 / 03" labels, a pill-shaped button and Inter for body text.

Version 3: Adding Look, Motion and an Avoid List

This brief kept all of version 2 and added three lines, 192 words in total.

Look: a Swiss botanical poster. Background #10352A (deep fern green), accents #8FD694 (leaf green) and #F2B134 (pollen yellow), all type in white. One typeface: Archivo Black for headlines, Archivo for small labels. Big type on a strict left-aligned grid.
Motion: 120 BPM, something changes on every beat. Each scene grows out of the previous one: the drooping leaf straightens into the F of Fernly, and the F's stem becomes the phone outline. Fast cuts, with one held beat on the headline.
Avoid: centered text on a gradient, everything fading in, cream or off-white backgrounds, italic accent words, numbered 01/02/03 labels, neon glow, and an ending that is only a logo.

Version 3: colors, typeface, grid and transitions all follow the brief.

The three colors, the typeface and the grid are all there as written, and the transitions did what the brief asked: the drooping leaf straightened into the stem of a giant "F", and the F folded into the phone outline. There was no cream background, no centered gradient text and no numbered labels. Two new problems turned up instead. Opus held on to a small label above every headline and replaced the banned numbers with uppercase words ("DAY 9 · NO WATER", "ANY PLANT, ONE PHOTO"), along with dash page indicators in the corner. The layout also slipped twice: at 3.4 seconds the wordmark ran past the right edge, and on the end card the plant overlapped the headline.

| Version | Added to the brief | What changed | What was still wrong | | --- | --- | --- | --- | | 1 | The topic | A finished launch video | Invented name, date and features; gradient and cream end card | | 2 | Name, headline, features, structure | Every word and beat correct | Cream background, 01/02/03 labels, pill button | | 3 | Look, motion, avoid list | Colors, type, grid and transitions as written | Labels swapped to uppercase words; two layout slips |

Templates for Four Everyday Video Types

Fill in the brackets, leave the structure alone, and when the result misses, change one part at a time.

Product Launch

Gather first: what the product is called, its headline, three short features, the URL, and two or three brand colors.

A 30-second launch video for [Product], [what it does in one line].
Headline: "[headline]". Features: [feature 1]; [feature 2]; [feature 3].
Structure: a hook in the first second, the product name, one beat per feature with a simple product-screen illustration, then an end card with the headline and [url], held for the last 3 seconds.
Look: [named reference]. Background [#hex], accents [#hex] and [#hex]. [Typeface] for headlines, [typeface] for labels.
Motion: [tempo]. Each scene grows out of the previous one. One held beat on the headline.
Avoid: centered text on a gradient, everything fading in, cream backgrounds, numbered 01/02/03 labels, pill-shaped buttons.

Settings: 16:9, 15 or 30 seconds. Want more energy? Change Motion first. Want a different mood? Change the named reference. Examples #2 to #4 in our earlier post are finished launch videos shown with their prompts. opus6.video's Product launch template starts from this structure.

App Walkthrough

Gather first: the three or four actions you want to show and a description of each screen, with the sidebar items, list names and button labels. Opus draws the interface from what you describe, so the more precise the screen text, the closer it looks to your actual product.

A 30-second walkthrough of [App], [what it does].
Show these actions in order: [action 1], [action 2], [action 3]. A cursor performs each one with a real click or drag.
Screens: [screen 1: sidebar items, header, list contents]; [screen 2: ...].
End on "[closing line]" over the final screen, held for 3 seconds.
Look: [your app's real colors as #hex], [your app's typeface]. Keep the interface flat and exact, no glassy reflections.
Motion: zoom in on each click, hold for one beat after every state change.
Avoid: invented features, placeholder text, a logo-only ending.

Settings: 16:9, 30 seconds. For something more ambitious, have one shape morph through every state, the way the single-shape UI example in our earlier post does.

Vertical Social Ad

Gather first: one claim, one number or contrast that backs it up, and the call to action.

A 15-second vertical ad for [Product]. It must read with the sound off.
Hook in the first second: "[hook line]". Then "[claim]", then "[proof]", then "[call to action]".
One idea per screen, big type, at least half the screen height for the main line.
Look: [named reference]. Background [#hex], text [#hex], one accent [#hex]. [Typeface].
Motion: a hard cut every 2 seconds, one held beat on the proof.
Avoid: centered text on a gradient, everything fading in, small captions.

Settings: 9:16, 15 seconds. The fintech ad from our earlier post builds its entire pitch on one contrast: "Money still moves like it's 1973."

Explainer

Gather first: the steps in order, plus every fact, date and number you want on screen.

A 30-second explainer: [topic] in [number] steps.
Steps: 1. [step]. 2. [step]. 3. [step]. Use only these facts: [facts and numbers].
Structure: a title card, one step per scene with a diagram that builds up, a progress tracker showing which step we're on, then a one-line summary held for 3 seconds.
Look: [named reference, e.g. a technical manual or a chalkboard]. Background [#hex], diagram lines [#hex]. [Typeface].
Motion: each diagram draws itself in, then holds for one beat before the next step.
Avoid: invented numbers, centered text on a gradient, everything fading in.

Settings: 16:9, 30 seconds. A step tracker like the one in the Negroni recipe from our earlier post helps viewers keep their place. On opus6.video, anything over 30 seconds has to be broken into parts.

Revising an Opus 5.5 Video Prompt, Step by Step

Check the Storyboard First

opus6.video shows Opus's storyboard while the code is still being written. The version 2 storyboard started with "Warm cream background, a terracotta pot centre-left" before there was a single frame. If the storyboard is off, stop and fix the brief before the code exists.

Tackle One Kind of Problem at a Time

Give a timestamp. "At 3.4 seconds" or "from 13.5 seconds" points Opus to the exact spot, and a round that deals with one kind of problem leaves the rest of the video as it was.

Say What's Wrong and What You Want Instead

Let Opus work out the fix. A note that prescribes a fix gets that fix, whether or not it actually solves the problem. Our first edit to version 3 named both layout problems and the result we wanted:

Two layout problems. At 3.4s the Fernly wordmark runs off the right edge of the frame. From 13.5s the potted plant on the end card overlaps the end of "schedule.". I want the whole wordmark inside the frame with clear margin, and the plant fully clear of the headline so the end card reads cleanly. Keep everything else as it is.

One message took care of both layout problems and left the rest of the video alone.

Put Each New Default on the Avoid List

Look at which default the result used in place of the ones you listed, and add it to the list. Our second edit added the new default from version 3:

Add two more things to the avoid list: small uppercase labels above the headlines ("DAY 9 · NO WATER", "ANY PLANT, ONE PHOTO" and the rest), and the dash page indicators in the bottom-left corner. Remove both. Keep everything else as it is.

The labels and the indicators are gone, and nothing else moved.

Each edit took less than a minute.

If the Preview Never Loads, Say So

The code Opus writes sometimes fails to run. One of our three generations got stuck on "Loading preview…" because the script declared the same variable twice. A single chat message describing the error and asking for nothing else to change fixed it in about 40 seconds.

Stop Once the Video Works

Some things no prompt can solve: real footage, a recorded voiceover, a licensed song, or a running time beyond the tool's limit. opus6.video videos run up to 30 seconds and come out without sound, and opus6.video only loads fonts from Google Fonts and public CDNs, so a private brand font file won't load. For footage, audio or long edits, work in Claude Code with a renderer such as Remotion, which can place your own video and audio files in a composition using its <Video> and <Audio> components.

Common Questions

How Long Does an Opus 5.5 Video Prompt Need to Be?

It needs enough room for all six parts. Our version 3 brief got there in 192 words, while the short prompts people share have a median of 26. On opus6.video the brief holds up to 2,000 characters, and format and length are picked with buttons.