Prompt library
Almost every viral Opus 5.5 video follows one of six prompt patterns. Each one below is our own fill-in-the-blank rewrite: replace the {{PLACEHOLDERS}}, paste it into Claude Code with the HyperFrames plugin, and render.
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.
Use it for: App store previews, feature announcements, social clips.
Build a {{LENGTH}}-second vertical video (1080x1920) that walks through {{APP}}.
First ask me for 6 to 10 screens or UI states and the real data shown in each.
Move between states with morphs (a button becomes a loader, a card expands into a detail view) rather than slide transitions.
Use the brand colors {{COLORS}} and the font {{FONT}}.
End on the app icon and "{{CTA}}".Tip: Real data in each state is what makes it look like a product and not a template.
Use it for: Music videos, promos, anything cut to a track.
Here is a music track: {{AUDIO_FILE}}.
Analyse it first: tempo, beats, the drop and any quiet breakdown.
Make a {{STYLE}} motion graphics video where every cut and hit lands on a beat, calmer in the breakdown and at full energy on the drop.
Use only code-drawn visuals (Canvas, SVG or WebGL), no stock footage.
Render to MP4 with the audio included.Tip: The model cannot hear, but it can measure the waveform. Asking it to analyse the audio first is what makes the sync land.
Use it for: Reports, newsletters, social posts built on a number.
Get {{DATASET}} (or use the data below) and turn it into a {{LENGTH}}-second animated data story.
Pick the one finding that matters and build toward it: set the scene, show the trend, reveal the number.
Use a chart race, an animated line or a map, whichever fits the data.
Label every axis and value, cite the source on the last frame. 1920x1080, 60 fps.
{{DATA}}Tip: Give it the source URL as well as the numbers so the citation on the last frame is real.
Prompt pack
The free patterns above cover the basics. The pack goes further: 50 prompts across launch videos, explainers, app walkthroughs, music videos, data stories and logo stings, each with fill-in variables and notes, plus an index of 100+ public Opus 5.5 videos linked to the original posts. Saves you digging through dozens of threads and repos.
Opus 5.5 Video Prompt Pack
$9.9one-time
Every prompt pattern that works, rewritten as fill-in-the-blank templates.