LogoAhaPrompt
  • Prompts
  • Featured
  • Models
  • AI Reverse
  • Pricing
  • Submit
  • Blog
AhaPrompt

AI Prompts for Images, Video & Audio — Every Model, One Library

Explore

  • All Prompts
  • Featured Prompts
  • Image Prompts
  • Video Prompts
  • Audio Prompts
  • AI Models

Tools

  • AI Reverse Studio
  • Image to Prompt
  • Video to Prompt

Resources

  • Pricing
  • Submit a Prompt
  • Blog

Copyright © 2026 AhaPrompt All rights reserved.

Privacy PolicyTerms of ServiceRefund PolicyDMCA / Takedown
HomeAI Prompt LibraryAI Video PromptsCode-Animated POV Disaster Choice Series

Code-Animated POV Disaster Choice Series

AClaude Opus 5.5Anthropicvideo

ROLE Senior motion designer, 3D artist and short-form story writer. Build a fully code-animated vertical video for a faceless "choose your own adventure" disaster series. No AI video or image generators. Every frame is rendered from code. GOAL One 40–45s episode, 1080×1920, 30fps. The viewer IS the main character. It ends on a two-option choice viewers answer in the comments. The next part follows the most-commented option. INPUTS (ask me, never guess) - Disaster: [tsunami / earthquake / volcano…] - City + fictional landmark: [Miami Beach, "Marlin Beach"] - Part number + previous choice - The two ending choices: [BOAT / HELICOPTER] - Companion name: [Jay] + 1–2 side characters TECH - three.js in one HTML file, rendered headless with Playwright. - Expose https://t.co/JQhCZuhsmU(t) that sets everything for time t. Seeded random, no requestAnimationFrame state. - For each frame: seek(frame/30), screenshot, encode with ffmpeg (H.264, CRF 18). - Audio at -14 LUFS. ART - Flat toon-shaded 3D, 3-step toon shading, black outlines on characters and props. No realistic textures. - Palette: sky blue to warm horizon, sand, teal ocean with white foam, accent red #d8343a, safety yellow #f2c230. - Low-poly towers, pastel hotels, palms, lifeguard tower. - Chibi characters: big white eyes, thick brows that carry emotion, simple mouth shapes, mitten hands. Companion in a red tee and navy shorts. - Emotion in whole poses, mouths flap on syllables. CAMERA (MOST IMPORTANT) - True first-person POV. Your two arms are always visible from the bottom corners, reaching, grabbing, pointing. - Wide lens, 100° FOV, slight barrel distortion. - Head bob, panic sway, hard shakes on impact, quick whip pans. - Look up (wave, helicopter) and down (water, ladder) a lot. - Cut every 1.2–2.2s. One action and one line per shot. FX - Toon wave with a moving foam lip and speed streaks on impact. - Flooding room, splashes, water spraying from seams. - Underwater: teal fog, caustics, bubbles, floating cars and umbrellas. - Cartoon helicopter, swinging rope ladder, downwash on the water. STORY (every part) 1. 0–2s: start mid-panic. HUD shows place, time, previous choice. 2. 2–12s: the plan works ("It's holding!"), then fails. 3. 12–22s: trapped or underwater. Audio muffles, 0.5s of silence. 4. 22–34s: you surface, a friend calls your name, a new wave, rescue with "One pass!" 5. 34–40s: cliffhanger, cut to black. 6. 40–45s: choice card, 3s+. Lines of 1–4 words, shouted. Say the friend's name twice. Plant one mystery ("Is that really Jay?"). TEXT - HUD top-left: "[LANDMARK] · [TIME]" + "[City] · Part [N]" in yellow. - Red "YOU CHOSE [CHOICE]" badge for the first 3s. - Captions at 72% height, bold, outlined, one color per speaker. END CARD "WHAT WOULD YOU DO?", a blue and a red button with "OR" between, "Comment below ↓", gentle pulse. AUDIO 2–3 shouted TTS voices, panting, wave roar, impacts, hatch clang, underwater heartbeat, helicopter rotor, sirens. Only a tense drone until the end card swell. COVER Companion's shocked face, 2-line Anton title (white + yellow), choice subtitle, red PART pill. DELIVER episode.html, render.js, part[N].mp4, cover.png, caption, a file with both next parts. DAILY Read the top comment, build the next part, post. 4–6 parts per disaster, then a new city.

Details
Type
AI Video Prompts
Aspect Ratio
9:16
Duration
0:42
Updated
Nov 21, 2026
Category
VFXAnimationMotion Graphics
Source

How to use this prompt

  1. 1Copy the full prompt with the copy button above.
  2. 2Open Claude Opus 5.5 by Anthropic, or your preferred AI video generator.
  3. 3Paste the prompt and keep the camera and motion terms — they steer the cinematography.
  4. 4Match the example's settings (9:16 · 0:42 · VFX · Animation · Motion Graphics), then iterate — small wording changes shift the output a lot.

Frequently asked questions

Which AI model generated this video?

This clip was generated with Claude Opus 5.5 by Anthropic. The prompt on this page is the exact text used to create it.

What settings does this prompt use?

The example was generated with Claude Opus 5.5 using: 9:16 · 0:42 · VFX · Animation · Motion Graphics. Reusing these settings gives the closest match.

How do I get similar results?

Copy the prompt as-is first, then change the subject while keeping the camera, motion, and lighting terms. Video models are sensitive to wording, so expect a few runs.

Can I modify this prompt?

Yes. Prompts work best as starting points — swap scenes, adjust pacing terms, or change the aspect ratio to fit your project.

More Claude Opus 5.5 prompts

0:41
AClaude Opus 5.5
Use huashu-art-motion to make me a 15-second animation. The skill's docs are in Chinese; read them and talk to me in English. 1. First check for uv, ffmpeg and Playwright Chromium, and tell me how to install anything that's missing. 2. Ask me what it's about, who it's for, and whether it's landscape or portrait. From the material layer in references/风格配方/INDEX.md, pick 3 styles that fit, three-star ones first. Redesign the composition for my subject in all three, each different from the others, and don't copy the room from the samples. Show me one still frame of each to choose from. 3. Once I pick, give each scene one main action plus two motif loops from that style's card. For Van Gogh, that's the starry sky curling into swirls and the lamp's halo spreading outward. If there's music, use the skill's BPM synthesis and put the motion on the beat. 4. If people need to appear, ask me first: my own character art, frames from an image model, or only hands and figures seen from behind. 5. After rendering, follow the skill's own QA steps: run its QA script first, then send a subagent that took no part in making it to watch only the finished film and find problems, have it write its findings into the 审片/ folder, and deliver with its delivery script. If anything comes up red, fix it and re-render before giving it to me.
Details
1:27
AClaude Opus 5.5
ROLE You are a senior motion designer, map illustrator, gaming researcher and documentary scriptwriter. You build fully code-animated "map tour" explainer videos for a faceless GTA 6 channel. Every frame is rendered from code you write. No AI video generators, no re-uploaded trailer footage, no Rockstar logos, artwork or characters. GOAL Produce one finished map-tour video: 80–90 seconds, 1920×1080, 30fps (plus an optional 1080×1920 vertical cut). A getaway car drives a route across your own illustrated map of Leonida, stopping at each location on a topic list. Every stop gets a highway-sign title, a "case file" card with an illustration, three facts, a source line and an honesty stamp. It ends on a question that drives comments. INPUTS (ask me for anything missing, never guess) - Topic: [e.g. "Every heist spot we've seen in GTA 6" / "Every animal and where to find it" / "Every region and its real-world match"] - My voiceover file (ElevenLabs), or ask me to approve a script first - Channel handle, and the end-card question - Output format: landscape, vertical, or both STEP 1: RESEARCH (accuracy is the brand) - Search the web for every location on the topic. Use only official Rockstar material (trailers, the Extended Look, official screenshots, the Newswire, store listings) and reputable hands-on previews (IGN, Game Informer, Edge, GamesRadar). - For each item, record: what it is, where it is (only if actually shown), the source and its date, and a status: CONFIRMED (Rockstar showed it), SHOWN (seen in a preview or demo), REPORTED (press only) or MAYBE (a single outlet). - If the location isn't shown, the item gets a "LOCATION NOT SHOWN" tag. Never place a pin somewhere that's only a guess. If you approximate, label it "approx. position". - Save everything to research.md with links. Show me the list before writing the script. STEP 2: SCRIPT (documentary tone, about 2.6 words per second) 1. Hook (0–9 s): "Let's go through every [topic] we've seen in GTA 6, before it finally comes out." 2. Sources (9–14 s): name where the info comes from, and promise to flag anything unconfirmed. 3. Stops: one per item, 6–9 seconds each. "Stop one: [name]." → one vivid detail → one practical line or payout note. Say the status out loud when it's weak ("Only one outlet has reported this one, so treat it as a maybe."). 4. The big one: save the most exciting item for last, 12–16 seconds. 5. Twist: a broad truth that zooms out ("You can rob pretty much anything"). 6. Question: "Which one are you [doing] first?" Write in plain words. No hype words, no "smash that like button". STEP 3: THE MAP (build once, reuse in every video) - Build it in code: a stylized Florida-shaped peninsula from your own polygon (about 30 control points with seeded noise wobble so the coast looks hand-drawn), plus a chain of 20+ small islands for the Keys curving southwest, a thin barrier-island strip for Vice Beach, a big lake in the middle and a river running south from it. - Prerender it once to an offscreen canvas at 3 px per map unit, then draw it every frame with a camera transform (pan and zoom). Never redraw the geography per frame. - Look: - Ocean: radial gradient #2f8fe0 → #1553a6, with faint moving wave strokes at 6% opacity. - Shallow water: a cyan glow around every coast (#5fd0ee, 60 px blur). - Coast: a pale sand rim (#f3e6a8). - Land: #cfe07a, with 150+ soft patches of lighter and darker green. - Wetlands: #9fcf74 with short horizontal marsh strokes. - National park: #8fbf62. - City: a light grey area (#e9e9ee) with a fine street grid. - Roads and highways: cream lines. - Region labels in heavy rounded sans (Montserrat 900), white with a soft navy outline, each with its real-world match underneath, e.g. "VICE CITY / (MIAMI)". Use only region names Rockstar has published. STEP 4: ANIMATION LANGUAGE - Camera: open wide on the whole state (zoom so the full map fits), then glide down to the first stop. Each new stop is a smooth 1–2 s ease-in-out pan and zoom. Pull back to the full state for the twist. - Getaway car: a top-down red car icon (body, lighter roof, dark windows, headlights) that follows the route polyline by distance and rotates along the road direction. It eases between stops and pauses at each one. - Route line: the full route as a faint dashed pink line; the travelled part as a solid hot-pink line (#ff2e7e) with a soft glow. - Pins: a teardrop pin that drops in with a back-ease bounce and a pulsing ring. Yellow with "?" plus a "LOCATION NOT SHOWN" tag for unknown spots; pink with "$" plus a location tag for known ones. - Highway sign (top left): a green road sign (#0d7a3f) with a white inner border, a number shield, "STOP 1 OF 6", and the title in a heavy highway-style font (Overpass 900). A handwritten note card under it in a marker font (Permanent Marker) with a 3–5 word quote from the script. - Case file card (right side): an off-white paper card sliding in from the right with a sl
Details
0:24
AClaude Opus 5.5
make a dynamic ~24 second motion graphics video that shows what an incredible motion designer you are, like it's your showreel for a résumé. go all out. music, tempo, beat matching - bar's very high, so work backwards from it not to miss out on details. it should be a launch saas video for Grip (https://t.co/5RfUFdmCCG)
Details
1:21
AClaude Opus 5.5
You are my AI animation director, Minecraft-style 3D animator, character designer, scriptwriter, voice director, and production engineer. Your task is to create high-quality Minecraft-style emotional storytelling Shorts that closely match the visual format, pacing, character animation, editing, and production techniques of my attached reference: "Nobody Helped Mikey Until JJ…" Use Claude Code, Three.js, Blender Python when available, HTML Canvas, SVG, FFmpeg, and available voice tools. The goal is to create a REUSABLE animation system that makes original Minecraft-inspired storytelling videos. IMPORTANT: This is NOT a normal Minecraft gameplay video. It combines: Animated cartoon streamer avatars in the TOP section. A fully animated Minecraft-style 3D story in the BOTTOM section. Word-synchronized dialogue captions. Multiple distinct character voices. Emotional storytelling with dramatic reactions. Recreate this production approach as closely as possible without reusing copyrighted footage, third-party artwork, or the reference's exact story. FIRST, analyze the attached reference MP4. Video specifications: Resolution: 1080×1920 Aspect ratio: 9:16 Frame rate: 30 FPS Duration: approximately 80.7 seconds Use FFmpeg and OpenCV to extract frames every 1–2 seconds and around major scene changes. Create a reference contact sheet. Study: Split-screen proportions Character design Avatar animation Minecraft environment details Camera movements Dialogue timing Scene changes Character reactions Subtitle positioning Color-coded captions Lighting Minecraft textures Emotional storytelling Sound effects Editing rhythm Analyze the actual footage rather than guessing. Create a detailed style specification containing measurements, color values, timing patterns, and shot descriptions. Do not begin animation until the reference has been analyzed. THIS IS THE MOST IMPORTANT PART. Recreate the reference's split-screen composition. CANVAS: 1080×1920, vertical. TOP SECTION: Approximately 30–33% of the video height. BOTTOM SECTION: Approximately 67–70% of the video height. TOP: A cartoon streamer avatar reacting and speaking. BOTTOM: A cinematic Minecraft-style 3D story. Keep the two sections synchronized throughout the video. The top avatar changes according to which commentator is speaking. The Minecraft scene continues underneath the commentary. Use a colored rectangular border around the top panel. The border color identifies the active speaker. Do not randomly change the layout. Keep the split-screen composition consistent from beginning to end. Create THREE original cartoon commentary avatars inspired by the reference's visual design principles. AVATAR 1 — GREEN CHARACTER A cute, rounded, turtle-like cartoon character. Design: Soft green body Large expressive eyes Small cartoon mouth Black gaming headphones Gaming chair Cozy gaming bedroom Desk visible in foreground Soft daylight coming through a window Use a bright lime-green border. Personality: Kind, emotional, curious, easily surprised. AVATAR 2 — RED CHARACTER A cute red, long-eared cartoon creature. Design: Rounded head Large expressive eyes Long floppy ears Red hoodie Black gaming headphones Streaming microphone Cozy blue bedroom background Use a bright red border. Personality: Energetic, confident, dramatic, expressive. AVATAR 3 — BLOCKY COMMENTATOR A Minecraft-inspired blocky human character. Design: Square head Block-shaped nose Large expressive eyes Teal gaming headphones Streaming microphone Warm wooden gaming room Bookshelves and decorations Use a distinctive warm-colored border. Personality: Funny, skeptical, occasionally frustrated. All three must have ORIGINAL character designs and consistent appearances. Generate reusable character sheets and animation-ready layers. FACIAL ANIMATION: Blinking Smiling Sad expressions Shocked expressions Angry reactions Mouth movement Eye direction changes Eyebrow movement Small head tilts Subtle body movement Use layered 2D character rigs. Separate: Head Eyes Eyelids Eyebrows Mouth Ears Arms Body Create mouth shapes for basic lip synchronization. Animate the active speaker. Silent commentators should not appear as if they are speaking. Keep the background, chair, headphones, and character proportions identical across every appearance. Create a fully animated, Minecraft-inspired voxel world. The visuals should resemble cinematic Minecraft roleplay rather than normal first-person gameplay. STYLE: Cubic character models Pixelated textures Blocky terrain Square trees Minecraft-style houses Wooden interiors Cobblestone streets Food stalls Shops Villagers Blocky furniture Colorful environmental details Use 16×16 or 32×32 pixel textures with nearest-neighbor filtering. Keep the recognizable block-based aesthetic. Do not use smooth realistic human models. Avoid unnecessary realistic reflections or textures. Create reusable 3D environments. ENVIRONMENT 1 — CITY MARKET Include: Cobblestone plaza Market stalls Food carts Shop signs Trees Benches Buildings NPC villagers Decorative umbrellas Street furniture ENVIRONMENT 2 — FOOD SHOP Include: Wooden flooring Food display counters Checkout counter Shelves Fridges Villager shopkeeper Tables Decorative plants ENVIRONMENT 3 — OUTDOOR STREET Include: Grass blocks Roads Village buildings Trees Streetlights Parked vehicles when appropriate Create additional locations according to the story. Environments should remain consistent between di
Details
0:50
AClaude Opus 5.5
Ask me for: the product (a real one I give you, or invent a fake brand so there are no brand issues), the genre the story hides inside (detective, alien invasion, heist, nature doc, cooking show), and where it will be posted (it decides the follow handle). If I have no idea, pitch me 3 "What if" stories that each hide the product inside a genre, and let me pick. Ask which voice tool I have: ElevenLabs (about 1,000 credits a Short) or free Kokoro run locally. Tell me no image or video model is needed, because every frame is drawn in code. Then show me the script with word counts and seconds per line, a rough storyboard, and a cast sheet before anything costs money. A 1080x1920, 60 fps, 40-45 s vertical Short: a 2D "What if" kid cartoon that is secretly an ad, drawn entirely on an HTML canvas in code. Not 3D, not AI images, not a Roblox look. It borrows the big What-if channels' rhythm (DAY/CASE cards, a HUD counter, poofs, pop-in captions, a rewind loop) but every character and outfit is original. The ad formula (from the best Pixar-style AI ads): - Cold open in a genre with no product mention for the first beats; the viewer thinks it is a story. - The product enters as a plot device (the evidence, the stolen thing, the reason someone wins), never as an ad. - The twist is the product's benefit turned into a punchline ("too good to share", "too hard to kill"). - End on one glossy packshot: the product spinning in on a sunburst with a 2-line tagline. Characters: short, chibi, cartoony, one shared rig for the whole cast. - Big round head (radius 150 at scale 1, slightly wider than tall), small pear-shaped body, stubby rounded legs and arms ending in round mitten hands, oval shoes with a coloured sole. Adults are taller (1.2-1.3x body), little siblings 0.82x. - Every shape has an 8 px #2a1b3d outline and one soft darker shade on its right edge only (a thin crescent, never half the face). - Hair is smooth rounded shapes: a cap that covers the whole crown, a soft side swoop, a bowl cut, a side part, a ponytail hanging BEHIND the head. Never spikes or zigzags. - Give every character their own outfit; never copy a reference creator's character clothes 1:1. Example cast: detective kid (tan belted trench coat, red scarf wrap, brown fedora with a band), little brother (red-white striped tee, blue overalls, bowl cut), Mom (black hair, yellow headband, ponytail, coral sweater, green pants), Dad (side part, short jaw beard, round thin glasses, green sweater vest, white shirt, blue tie), dog (white with a brown eye patch and floppy brown ears). - Faces carry the comedy. Eyes: normal (white with a big pupil and two highlights), huge, happy arcs, closed, star, spiral, narrow. Brows: up, worry, angry, flat (mirror them per eye so worry never reads as angry). Mouths: smile, grin, wide, scream (one clean open shape with teeth band and tongue), o, flat, smirk, wavy, chew (puffed cheeks). Plus blush, sweat drops and sunglasses that drop in. Blink for 0.1 s about every 1.6 s. Mouths flap only while that character's words are being spoken. Sets: detailed flat rooms in saturated colours with thick outlines, each with a night version (darker blue grade plus warm lamp glows): a kitchen (wallpaper, upper cabinets, window with curtains and sky, jar shelf, plant, clock, pendant lamp, tiled backsplash, drawer counter, checker floor) and a bedroom (striped wall, window, poster, toy shelf, bed with a star blanket, nightstand lamp, plank floor, rug). Bursting sunburst colours for montages and the packshot. Fonts (all free, from Google Fonts' GitHub repo): - Captions: Lilita One. - Day/CASE cards and big world words: Luckiest Guy. - The product wrapper text: Sniglet ExtraBold, auto-fitted so it never clips. Captions: - 1-2 words at a time in Lilita One 94 px, centred at y 1600 (on the legs, never across a face), max 900 px wide. - White with a 20 px #1c1030 outline and a soft shadow, popping from 55% to 100% in 0.16 s. - Key words in caps and colour: red #ff5165, green #5dff8f, yellow #ffd23f, pink #ff7ad9, cyan #7debff, orange #ffa53d, purple #c49bff. - No full stops or commas on screen, ever. Hide captions on the packshot. Fake game UI over the world: - A HUD counter pill (260x92, centred at x 540, y 196) with a tiny product icon that tracks the story (snacks stolen, clues found) and ticks with a green "+N". - CASE/DAY cards: Luckiest Guy 230 px in yellow #ffd23f with a 38 px outline, tilted -6 degrees, popping in over 0.22 s and leaving at 1.05 s. - Toast pills (88 px tall at y 374), a FOLLOW button with the handle chip and a cursor that presses it (it turns green "FOLLOWING"). Motion: something moves on every line, and the picture changes every 1-3 s. - Things arrive with a squash (0.72, 1.12, 0.95, 1 over 0.3 s), an overshoot ease or a white poof cloud with stars, never a plain fade. - Characters breathe (1.2% squash) all the time. - The camera pushes in 5-15% per shot, stays inside the set, and shakes (decaying over 0.35 s) on every hit. Banned: real logos or real creators' characters, AI stills, spiky hair, a frame that holds still for more than 1 s, captions over faces, system fallback fonts, whispered narration. Length: 40-45 s, 85-100 words, 14 lines. Times below are from the 40.3 s "Snack Detective" ad; key every beat to a real word. 0-5 s: the narrator reads the title as line 1 ("What if you were a detective and someone kept stealing your snacks?") over the striking picture (crime-scene tape round an empty drawer; the hero poofs in on "detective
Details
1:04
AClaude Opus 5.5
You are my YouTube Shorts editor and motion designer. You turn a game topic and my clips into a 60-second vertical explainer: script, cut list, voice, on-screen graphics, captions, render. Every graphic is built in code. You never generate AI video and never invent game facts. Ask me for: 1. The game and the topic, as a title (e.g. "How the wanted system works in [game]") 2. My clips: gameplay I recorded, or official trailer footage I'm allowed to use. Tell me which files you need if I haven't attached enough 3. My sources for the facts (official posts, trailer moments, patch notes), or permission to research them 4. Length (default 60 s, 1080x1920, 30 fps) 5. Voice: free (Kokoro) or my ElevenLabs key Build a fact sheet: every claim the video makes, where it comes from, and whether it's confirmed, shown in a trailer, or speculation. Anything unconfirmed gets cut or worded as "looks like" / "from the trailer". Never fill a gap with a guess. Write 140-170 words, fast and friendly, like a guide who's already played it: - Line 1 names the system and makes a promise ("the police system in [game] has been completely redone") - Then 4-6 mechanics, each one line of "what it is" and one of "what it means for you" - One "most people will miss this" detail near the end - Last line loops back to the start or teases the next video Show me the script plus the fact sheet and WAIT for my OK. For every line: which clip, in and out timestamps, crop to 9:16 (keep the subject centred, track it if it moves), speed (100% default, 80% for slow-mo moments), and which graphic plays on top. Never use the same 2 seconds of footage twice. Cut every 1.5-3 s, always on a word. Build everything in one HTML file where https://t.co/6do3SVVxsJ(t) draws frame t as a pure function of time, rendered as a transparent overlay: - TITLE CARD (first 2 s): game logo if I give it, otherwise a bold title, plus the topic in white italic caps - HUD ELEMENTS that match what's being explained: a star/level meter that fills and drains, icons that light up one at a time, a minimap with a pulsing search circle, a phone text bubble, a news ticker. Rounded panels, a neon green glow, a thin dark border - CAPTIONS: 2-5 words at a time, heavy italic caps, white with a black outline, the key word in green or red, sitting in the lower third - MOTION: every element springs in (overshoot, then settle), nothing fades slowly, a light camera push on each clip Voiceover on top, a low hype beat ducked under the voice, a whoosh on every cut, a ding when an icon lights up, a siren hit when the stars go red. - Generate the voice first, get word timestamps, and lock every cut, caption and graphic to its word - Cut and crop the clips with ffmpeg, render the overlay frames with Playwright, composite and mix with ffmpeg (H.264, -preset veryfast, CRF 18) Before the full render, show me a contact sheet of 8 frames and WAIT for my OK. Check that captions never cover a face or the HUD, nothing is cropped badly, and every fact on screen is in the fact sheet. The final mp4, a clean version without captions, the script, the fact sheet with sources, and a title, description and 5 hashtags for YouTube.
Details
0:11
AClaude Opus 5.5
Ask me for: the accent colour, a song (mp3), the words for the 3 text moments (search query, card title, toast). If I skip any, use the defaults: lime #C6F432, any 120-130 BPM electronic track, "motion study 07" / "Every frame is code" / "Rendered from one file". One black shape (#0e0e10) on a warm light stage (#f4f4f1 to #e1e1dc radial). It never cuts: every UI state is born out of the one before it. White text, Geist for UI, Geist Mono for numbers and labels. The accent appears only where something turns on. A macOS cursor drives every change with real clicks and one real drag. Every morph uses one curve: cubic-bezier(.45,0,.15,1). Pop-ins use a closed-form spring with a tiny overshoot. Text rises through a mask line, it never fades in. The camera zooms per state so each state fills about 60% of the frame, and creeps slowly through every hold. Banned: crossfades, hard cuts, bouncy easing, particles, glows, gradients on UI chrome, holds over 1 second, anything that looks like a template. 120 BPM grid, 24 beats, then the whole film is time-warped onto the real song's beat. Generate pill → click → shrinks into a spinner circle → grows into a toggle → click, the knob springs right and the track turns accent → stretches into a slider → drag the knob from 15 to 85, the number counts → widens into a ⌘K search bar, the query types itself → unfolds into a chart card, 7 bars spring up one per 1/8 beat, the last one in accent → click the accent bar, it pulses → folds into a toast with a check → back into the Generate pill. Last frame = first frame, cursor included. 1. One HTML file, square 1440x1440. Every style is computed from time inside seek(t): no CSS transitions, no timers, no state between frames. 2. The shape is one div. Width, height, radius and colour are keyframe tracks [[t, value]] eased with the one curve. Each state's content is its own layer with its own in / out window inside the shape. 3. Camera: one scale track around the centre, plus a 1.2% sine creep over the whole loop. 4. Cursor: a track of screen positions for the free moves; during the drag its position is computed from the same function that places the knob, scaled by the camera. 5. Beats: analyse the song with numpy (onset envelope, autocorrelation for BPM, align to the kicks, find the drop). Put the drop on the chart bars springing up. 6. Render with Playwright: 60 fps, 4 subframes averaged per frame for motion blur, piped to ffmpeg x264. Then one real SFX per event (click, select, typing, whoosh), placed by its measured peak, quiet under the music, loudnorm to -14 LUFS. - If the cursor follows its own keyframes during the drag, it slides off the knob. Derive both from one function. - Retiming every key to a 129 BPM song breaks the grid. Author at 120 BPM and warp time once: t * (12 / 11.146). - A 300 px pill at zoom 1.7 looks lost in a 1440 frame. Size the zoom per state, about 60% of the width. - A frame-diff pop scan flags the fast morphs. Check each flag by eye: a moving edge is fine, a jumping layer is not. Ask me for the inputs, then show me the state list on the beat grid before you write any code.
Details
1:02
AClaude Opus 5.5
Ask me for: the topic (default: how peptides work), the length (default 60 seconds), whether I want captions on screen (default yes), and whether I have my own sound effects (if not, synthesize them in numpy). I attach the red character sheet on a black background. After I answer, write a voiceover script of about 2.4 words per second, give it to me in a code block, then stop and wait for my voiceover audio before you render anything. A flat cartoon explainer short at 1080x1920, 30fps, drawn entirely in code with Python and skia-python, piped to ffmpeg, one encoded file per scene joined with the concat demuxer. Every shape anti-aliased. Character: cut each pose out of the attached sheet into its own transparent sprite. The background is black and so are the outlines, so flood-fill the background from the image edges only at low tolerance and keep all black inside the figure (outlines, sleeves, waistband). Keep the white eyes. Add a 3px navy #24364F stroke around each silhouette to replace the lost edge. Upscale 3x with Lanczos. Show me a contact sheet of the cut-outs on #D3DFEC before going further. Posing: the character is a presenter anchored to the bottom edge, 800-1050px wide, never floating. Pick the pose from the line being spoken: pointing at the viewer for the hook and the final line, finger up when explaining, shrug on a question, arms crossed while watching, open palm when presenting an object, pointing at a zoom bubble. 1 to 3 pose changes per scene. Each change lands with a squash and stretch over 9 frames (8% wider, 10% shorter, then back). Idle: 0.5 degree sway and a 0.6% breathing scale. Script: a hook question in the first 4 seconds, a title line, 4 to 5 beats that each carry one visual idea, a one-line payoff. Short sentences, plain words, every claim accurate, no medical advice. Timing: run silencedetect on my voiceover at -35dB, 0.22s. Cut scenes in the middle of the long pauses and fire every pop, label and pose change on the word it belongs to. Palette: backgrounds pale blue #D3DFEC, mid blue #B4C7E6, strong blue #6790CB. Outlines and text navy #24364F. Accents amber #F4B740, coral #EE7B5B, teal #58B7A8, lilac #9A86D6. Flat fills only, 5-9px navy outlines on every drawn object. Scenes: the title card is solid #37557F with two lines of white text sliding in from opposite sides and an amber underline. At least two close-up scenes with no character. One circular zoom bubble, 320px radius, white ring with navy edges, that the character points at. The final scene is #6790CB with 14 lighter rotating rays. Diagrams: every explainer visual is drawn in code from circles, rounded rectangles and lines: chains of beads joined by a thick navy link, cells with a dotted membrane, arrows as moving dashed lines, labels in white rounded pills with a 6px navy outline. Captions: Inter ExtraBold Italic, all capitals, 66px, navy, centred at the top between y=200 and y=340, two lines maximum, each line rising 24px and fading in over 9 frames on its word. White with a navy stroke on the strong blue scene. Movement: a slow push-in from 100% to 104% across every scene, 14 soft white particles drifting upward at 35% opacity, every new element popping in with an 18% overshoot, beads rippling in a wave, a 7% zoom punch on the final line. Draw order: background, particles, floor line, diagrams, character, captions on top. Sound: my voiceover at full level. Effects at half the voice level: a swoosh 0.12s before each cut, a whip on each pose change, a pop on each element, a click or chime on key moments, a low hit on the title card and the final line. Before the full render: render 14 still frames at the busiest moments, look at them, fix overlaps and text leaving the frame. Banned: gradients, drop shadows, glow, 3D, AI images or AI video, stock footage, music, emojis, watermarks, any character other than the attached one, any other channel's characters, logo or name, text smaller than 30px, a character that floats above the bottom edge, more than two caption lines.
Details
Browse all Claude Opus 5.5 promptsExplore AI Video Prompts