Animations-Prompts für Claude und die Videos, die daraus entstanden

48 Animations-Prompts für Claude, die Creators zusammen mit den daraus entstandenen Videos gepostet haben: die 8 beliebtesten aus jeder der 6 Kategorien, ausgewählt aus 861 Prompts im Archiv. Jede Karte zeigt das Video, das vom Creator genannte Modell und den vollständigen Prompt.

Made entirely with Opus 5.5 + $3.21 of OpenRouter API usager/ Prompt verfügbar1:00
Motion Design
u/Singularity-42·Opus 5.5

Create a pure javascript animation. 30s-60s whimsical hand drawn collage style with appropriate audio on the topic what is the purpose of life ? Entire video should be as high of a production value…

Vollständiger Prompt
Create a pure javascript animation. 30s-60s whimsical hand drawn collage style with appropriate audio on the topic what is the purpose of life ? 
    
    Entire video should be as high of a production value as possible. Please spend your time on this, it's very important.
    
    Use high quality text-to-speech model for generation. You can find open router API key in .env file
    
    You can use any tools you can find access to and resources on the internet. You create the script, the assets, the animation, concept, everything.   
    I have to go away from my computer so please work autonomously until done. Quality is paramount. Production value should be on professional level.
    
    One more thing: max OpenRouter spend is $10
Videoseite
WTF?r/ Prompt verfügbar0:15
Motion Design
u/ramcodes·Opus 5.5

make a dynamic 15-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.

Videoseite
Sonnet 5.5 max effort𝕏 Prompt verfügbar
Motion Design
@robj3d3·Sonnet 5.5

make a dynamic 15-second motion graphics video for SuperX that shows what an incredible motion designer you are, like it's your showreel for a resume. go all out.

Videoseite
time to drop a fucking BOMB for free𝕏 Prompt verfügbar
Motion Design
@sleepclip·Model not specified

1. Dusty Dawn: dusty blue-grey, slate teal, warm beige, navy, soft purple 2. Desert Clay: terracotta, sand, sage green, deep cocoa, mustard 3. Nordic Frost: ice blue, pale stone grey, pine green,…

Vollständiger Prompt
1. Dusty Dawn: dusty blue-grey, slate teal, warm beige, navy, soft purple
2. Desert Clay: terracotta, sand, sage green, deep cocoa, mustard
3. Nordic Frost: ice blue, pale stone grey, pine green, charcoal, berry red
4. Retro Mint: mint, cream, coral, deep teal, burgundy
5. Ink and Ochre: ochre, warm off-white, indigo, rust, olive
6. Dusk Arcade: deep plum, muted cyan, dusty magenta, midnight blue, warm butter yellow
7. Forest Paper: moss, kraft beige, forest green, plum, cream
8. Candy Slate: slate grey, peach, lilac, butter yellow, sea teal
9. Harbour: navy, sail white, brick red, sea-glass green, rope tan
10. Citrus Concrete: concrete grey, lime, tangerine, graphite, sky blue

Code colours: derive 11 hex values from the palette and save them in dna.json: ink (text), alert (red-family, for X marks and stamps), warm, highlight, success, dark panel, headline A, headline B, label grey, card fill, transition fill.
Rules: ink on card fill at least 7:1 contrast. Alert on card fill at least 4.5:1. White caps on headline A and B at least 4.5:1. Alert, warm, highlight and success at least 30 degrees of hue apart.
Dusty Dawn keeps the original set: ink #2b2d42, alert #d62828, warm #f4a261, highlight #f6b93b, success #2fb37a, dark #1f2a48, headline A #e2552f, headline B #5b3fa6, label grey #8a8c9c, card #ffffff, transition fill #f4f1fb.

Character build (pick 1):
1. Big round heads, dot eyes, small bodies
2. Tall pill-shaped bodies, oval heads, solid-shape eyebrows that carry the emotion
3. Chunky rounded-square heads, stubby legs, wide shoulders
4. Long thin limbs, small heads, oversized hands and shoes
5. Egg-shaped heads with no nose, big blocky hair shapes, tiny feet
6. Bean bodies where head and torso are one shape, dot eyes set wide
Skin: give each main character a different flat skin tone from a broad range, light peach to deep brown.

Font (pick 1, Google Fonts, heaviest weight): Montserrat 900, Poppins 800, Archivo Black, Anton, Bebas Neue, Rubik 800, Barlow Condensed 800, Lexend 800, Outfit 800, Fredoka 700, Unbounded 800, Sora 800.

Card style (pick 1), used on every board, card and bubble:
1. Rounded cards (radius 18-20), soft drop shadow (blur 22, y 8, 22%)
2. Square-cornered cards (radius 4) with a hard flat offset shadow in the dark colour, 8 px down-right
3. Pill-ended cards with a thick accent strip on the left edge, no shadow
4. Paper notes with a random tilt of ±0.04 rad and a flat strip of tape on top
5. Die-cut stickers: the card sits on a slightly bigger card in the dark colour

HUD position (pick 1): date and place cards top left, top right, bottom left, or one thin strip across the top.

Tag style (pick 1):
1. A line with a dot at the thing, pill on the end
2. A curved arrow from the label to the thing
3. A bracket hugging the thing with the label on the bracket
4. A flag on a pole planted next to the thing
5. A label with a small triangle pointer, no line

Text entry (pick 1): letter by letter typing, word by word pop, lines sliding up out of a mask, letters dropping in from above with a bounce.

Motion personality (pick 1). It sets the primitives in <animation>:
1. Bouncy: spring 1 - e^(-6.5Δ) cos(13Δ), pop 0.3 s with 1 + 2.9(p-1)^3 + 1.9(p-1)^2, kick 0.1
2. Snappy: spring 1 - e^(-10Δ) cos(9Δ), pop 0.2 s with a small overshoot, exits 0.18 s, kick 0.07
3. Floaty: spring 1 - e^(-4.5Δ) cos(8Δ), pop 0.4 s, slower camera, idle props sway gently
4. Punchy: heavy squash and stretch on every arrival (1.25x by 0.8x, settling in 0.2 s), kick 0.16

Camera language (pick 1): slow 2-4% pushes and pans; gentle handheld drift (±6 px, 0.3 Hz noise) on top of pushes; snap zoom-ins of 6-8% on stressed words; layered parallax where foreground props cut from the plate move 1.5x the background.

Shot transition (pick 1): horizontal push, vertical push, circle iris opening on the next subject, three diagonal slats, zoom through a door, window or screen in the old shot. All 0.22-0.28 s with a whoosh 0.02 s before.

Chapter transition (pick 1), in the transition fill colour: blob splat, a big paint swipe, a shutter of 5 vertical bars, an ink drop growing from the centre, a page curl made of flat shapes.

Narrator (pick 1, then use the closest voice I have): deep warm US documentary, crisp British documentary, calm warm female documentary, energetic younger US explainer, dry deadpan storyteller, gravelly older storyteller.

Music family (pick 1): soft piano and pulses, light lo-fi beats, warm orchestral strings, minimal electronic, acoustic plucks, synthwave pads.

Pace: draw places per minute from 8-12 and the "something new" interval from 1.6-2.4 s.

Host (pick 1): no host; a recurring host who opens and closes every video and pops in once per chapter; a mascot animal; a mascot object with a face. The host gets full sheets at setup, reused in every video.

Stings (pick 1 each, built at setup and reused):
Intro, 2-3 s: the channel name entered on a board in the first plate; the host walks in and presents the title; the chapter transition reveals the title on a banner.
Outro, 3-4 s: the host waves goodbye on a closing plate; a board with the channel name swings in; the signature motif's final state with the channel name.

PER-VIDEO TRAITS (rerolled every video)

Script shape (pick 1): chronological story, countdown of reasons, mystery that opens on the ending, myth vs reality, one day in the life, "what if" escalation, follow the money.
Hook type (pick 1): a shocking number, a direct question to the viewer, a scene already mid-action, a common belief to break, a tiny detail that turns out huge.
Signature motif (pick 1): a map the story keeps returning to, a counter that keeps climbing somewhere in the plates, one prop that appears in every chapter, a big chapter number stamped on each chapter's first plate, a side character who reacts to every twist.
Accent: one palette colour that leads banners and stamps this episode.
Thumbnail layout (pick 1): face left with object right, two characters facing off, one huge object with a tiny character, before and after split.

[DNA ...] below means a value from dna.json. Never fall back to Dusty Dawn unless it was rolled.
</dna>

<look>
A 1920x1080 animated explainer in the style of the big flat-vector infographic channels.
Every line of narration is acted out by cartoon people inside a full illustrated place.
All motion is code. There are no AI video generations, just a few still images that code cuts up, rigs and animates.

Art:
Flat colour shapes with NO outlines, at most one slightly darker flat shade for form, simple geometric shapes and crisp edges.
Palette: [DNA palette]. Characters: [DNA character build], each main character with their own skin tone.
Mood comes from the plate's own light: daylight, a cold night, warm indoor lamps.

Code colours: the 11 in dna.json.
Font: [DNA font], all caps on cards and signs.

Pace:
A new place every 60 / [DNA places per minute] seconds.
Something new arrives every [DNA interval]: a tag, a stamp, a person walking in, a number.
Never hold a still over 1 s. Never have a character who doesn't move.

Banned:
outlines, glossy UI panels floating over the art, emoji, burned-in subtitles
any channel's logo or name, photos of real people
facts written on a plain colour card when the place could hold them
a look that clones one specific channel (reroll the trait causing it)
</look>

<length>
Everything scales from the length (1-10 min). Show me these numbers with the script.
Words: minutes x 175.
Places: minutes x [DNA places per minute]. About 30% come from hero plates and the rest from quad tiles, 4 per quad.
Main characters: 1-2 under 3 min, 2-3 above. The host doesn't count, because it already exists.
Chapters: under 2 min, no chapter breaks, just beats every 15-20 s; 2-5 min, 3-4 chapters; 5-10 min, 5-8 chapters.
Rough image budget: 1 min about 12 images (about $0.50), 3 min about 25, 5 min about 40, 10 min about 70 ($3-4).
Voice: one take under 3 min; above that, chunks split at chapter breaks.
Render: one browser page under 3 min; above that, 4-6 parallel pages.
Over 5 min, spread the motif and host pop-ins evenly so the middle doesn't sag.
</length>

<art>
Image count comes from <length>. Feed the library/ style frames and host in as references every time.

Every prompt starts with this style core, word for word, with the DNA filled in:
"Flat vector illustration in exactly the same art style as the reference images: NO outlines or line art anywhere, every shape is a flat solid colour fill with at most one slightly darker flat shade for form, simple geometric shapes, crisp clean edges, no gradients, no texture, no painterly lighting. Muted modern palette: [DNA palette, five colours]. Characters are [DNA character build]. No text, no letters, no numbers, no logos."

Then add one line that locks the setting ("The setting is [time, place]: [materials, light sources], nothing from other eras unless asked").

Style references, made at setup: if I give a reference channel (logo cropped off), use it only for composition and detail, never its colours or characters. Otherwise generate 3 style frames from the style core, get my OK, and use those.

1. Hero plates, count from <length>, one full 16:9 image each, for places you zoom into or come back to.
   EMPTY: "no people, no characters, no animals".
   Straight-on, with an open floor in the middle where characters will stand.
   Blank signs, boards, screens and pages that code writes on later.
   Plan at least 2 plates around the signature motif.
2. Quad plates, count from <length>, 4 places each. Pack 4 places into one image:
   "The image is a 2x2 grid of FOUR completely separate scenes, each filling exactly one quarter of the image (each quarter is itself a 16:9 picture), divided by perfectly straight thin pure-white gutters, one vertical down the exact centre and one horizontal across the exact centre."
   Then describe the TOP-LEFT, TOP-RIGHT, BOTTOM-LEFT and BOTTOM-RIGHT scenes.
   Split each quad on the brightest white row and column near the centre, walk out while the line stays over 60% white, and trim 6 px more.
   Crop each tile to 16:9 at 1920x1080.
   Object close-ups make great tiles: a desk, a screen, a document, a plate of food, a vault.
3. Main characters, count from <length>. Write one fixed description per character in the DNA build (age, hair, face, skin tone, every piece of clothing with colours from the palette) and paste it word for word into every sheet.
   Base sheet: 6 views. (1) front, neutral, drawn WITHOUT ARMS, only round smooth shoulder sockets where the arms would join; (2) the same armless front with a second emotion; (3) side view walking right; (4) seen from behind; (5) and (6) two poses the script needs.
   Expression sheet: 6 armless fronts (hopeful, disgusted, terrified, exhausted, sick, shocked, or whatever the script needs), with the base sheet as a reference.
   Pose sheet: 6 full poses with their props (sitting at a desk typing, sleeping, eating, running, signing, falling), with the base sheet as a reference.
4. Everyone else: role sheets of 4-6 people, each drawn in the exact pose their shot needs; crowd sheets of 8-10 small figures; prop sheets.
   Every sheet: "on a solid flat chroma green background (#00B140) with lots of empty green space between figures; nothing touches, nothing on any character or object is green, full bodies, nothing cut off by the edges". If the palette has a green near #00B140, use magenta #FF00FF instead.
5. Thumbnail art in the DNA thumbnail layout: the same characters with richer saturated cartoon lighting and extreme emotions, the top quarter left free, no text, with the base sheets as references.
</art>

<rig>
Cutouts:
The background is every border-connected pixel with G - max(R,B) over 40 and within 110 of the median green (mirror the rule for magenta). Key only from the border, or dark clothes leak.
Add a 2 px soft alpha band and clamp G to max(R,B) + 6 inside it, which kills the fring
Videoseite
Subject Analysis - Claude Opus 5.5𝕏 Prompt verfügbar0:15
Motion Design
@aimikoda·Opus 5.5

Mit Referenzbildern, Audio oder anderen Eingaben erstellt.

Turn the attached image into a seamless looping GIF (~15s, 15fps) styled as a surveillance-camera "subject analysis" sequence: 1. ACQUIRE – desaturated CCTV feed with REC, camera ID, running…

Vollständiger Prompt
Turn the attached image into a seamless looping GIF (~15s, 15fps)
styled as a surveillance-camera "subject analysis" sequence:

1. ACQUIRE – desaturated CCTV feed with REC, camera ID, running
   timecode; a search reticle locks onto the subject.
2. SILHOUETTE – background dims to a dark grid; AI detection boxes
   (head, torso, limbs + confidence scores) pop in; a scan line
   turns the subject into a flat silhouette.
3. STRUCTURE – silhouette becomes a glowing wireframe (edges +
   triangle mesh), then a pose skeleton with joint angles.
4. FEATURES – real colors return; an "ENHANCE" zoom on the face;
   animated callouts with typed labels for 4–5 key features.
5. PALETTE – extract the 6 dominant colors (k-means); swatches fly
   from the image into a panel with hex codes and percentages.
6. IDENTIFY – "TARGET LOCKED" + ID card (class, threat level,
   match %), then a glitch back to frame 1 for a seamless loop.

Keep the original artwork intact (segment it, don't redraw it).
Minimal HUD: white + one accent color, monospace font, a stage
progress panel in the emptiest area of the frame, no text over
the face. Export GIF + MP4.
Videoseite
Sonnet 5.5 is the same quality as Opus 5.5, but cheaper. Icreated me a 30-second motion graphics about Reddit. Everything is generated.r/ Prompt verfügbar0:30
Motion Design
u/oxmannnn·Sonnet 5.5

gets you when the thing you're vibe coding isn't an app. So I gave Claude Code (Sonnet 5.5) this, in an empty folder: >make a dynamic 30-second motion graphics video about Reddit that shows what an…

Vollständiger Prompt
gets you when the thing you're vibe coding isn't an app. So I gave Claude Code (Sonnet 5.5) this, in an empty folder:

>make a dynamic 30-second motion graphics video about Reddit that shows what an incredible motion designer you are. and not too fast, people should actually understand what the video is about.

**What it actually is:** no After Effects, no stock footage, no video model. It's plain JS drawing on a canvas in headless Chrome, one frame at a time, piped into ffmpeg. The music is synthesized in numpy. One timing file drives both the visuals and the audio, so every slam on screen has a hit in the sound.

**What worked (stuff you can steal):**

* **Make it look at its own output.** After every change it rendered a contact sheet of frames and read the image. That's how it caught things like a word that never appeared because of a math bug, and text running off the screen. Without that loop I'd have been the one finding all of that.
* **One source of truth for timing.** A single `sync.js` for beats and impacts. Change a number and the visuals and the sound move together.
* **Parallel agents, one file each.** For the 30 s version it spun up 5 builders (one per shot), then 5 independent reviewers who weren't allowed to edit, then fixers. The reviewers found real stuff, including a bug that would have crashed the final render at one specific frame.
* **Steer in plain English.**
Videoseite
Testing Claude for 3D creation. Max took a whole hour, but just look at the result 👀r/ Prompt verfügbar0:07
3D & Generativ
u/bursinru·Model not specified

Create a low-poly 3D horse running in a seamless loop using Three.js. Build it procedurally from primitive geometry, animate the legs, body, head, and tail, and return a single self-contained HTML…

Vollständiger Prompt
Create a low-poly 3D horse running in a seamless loop using Three.js. Build it procedurally from primitive geometry, animate the legs, body, head, and tail, and return a single self-contained HTML file.
Videoseite
this is the only prompt you need to make high-end motion videos with claude opus 5.5𝕏 Prompt verfügbar0:40
3D & Generativ
@everestchris6·Opus 5.5

one short, soft whoosh per real scene change, and small clicks or pops only on real on-screen actions - screen effects for boom, hiss and length before using them, and set each one just above the…

Vollständiger Prompt
one short, soft whoosh per real scene change, and small clicks or pops only on real on-screen actions
- screen effects for boom, hiss and length before using them, and set each one just above the music in its own frequency range, with a cap so nothing gets harsh
- cut every scene change on a beat
- always export a music-only version
</audio>

<critic_loop>
the builder never judges its own work.
- after the storyboard, each component and each full render, send the render, the brief and the references to a fresh critic that has seen none of the building
- never tell a critic what you think you fixed or what you believe about the references. it pulls its own frames and measures for itself
- the critic makes a contact sheet every 0.2 seconds plus dense frames around every transition, measures frozen time and loudness, and returns a ranked list of problems with timestamps, ending with ship or one more pass
- fix the biggest problem first, render, then send to a new critic that checks every previous item as fixed, partly fixed or still there, and hunts for anything new that broke
- keep a ledger of every round: what was found, what changed, and the numbers before and after
</critic_loop>

<quality_bar>
the video isn't done until all of these pass, measured:
- no more than about 1 second of frozen screen per 30 seconds, and no still stretch longer than about half a second
- frame one is a finished composition
- all text meets at least 4.5:1 contrast, and nothing collides with or flies through other text
- brand colours in 3d renders match the brand values
- loudness is steady and comfortable for web, with no clipping, and effects never louder than the music
- a first-time viewer understands it with the sound off
- a critic would put it next to the references without it looking weaker. a video with no bugs is not the same as a good video
</quality_bar>

<honesty>
- only put numbers, names and claims on screen that are in the facts file
- no invented testimonials, ratings, prices, savings, warranties or results
- anything conceptual or generated is labelled as such
- in your reports, separate what you measured from what still needs a human to watch or listen
</honesty>

<deliverables>
- the final mp4 in every size requested, at 1080p and 60 frames a second
- a music-only version
- a contact sheet of the final video
- the critic ledger and the final quality bar results
- a short note on anything a human should still check
</deliverables>
Videoseite
holy f*ck, I just sold this single AI-generated 3D neuron for $2,000 to a private biotech lab.𝕏 Prompt verfügbar0:25
3D & Generativ
@thegreatest_sv·Model not specified

https://t.co/UcgHiqCJQj the neuron in this video? I built it myself with Claude Code and a few 3D and motion tools and sold it for 2K. no studio, no team. want to make something like this? like +…

Vollständiger Prompt
https://t.co/UcgHiqCJQj

the neuron in this video?
I built it myself with Claude Code and a few 3D and motion tools and sold it for 2K. no studio, no team.

want to make something like this?

like + save this post, comment
Videoseite
I created a 3D lunar rover survey game with Opus 5.r/ Prompt verfügbar0:56
3D & Generativ
u/oxmannnn·Opus 5

Create me a fully playable release-ready game. On GPU. Game about moon discovery with rover with gravity, moon sand and etc.. I need it in 3D and not a voxel game. Make it with maximum effort, show…

Vollständiger Prompt
Create me a fully playable release-ready game. On GPU. Game about moon discovery with rover with gravity, moon sand and etc.. I need it in 3D and not a voxel game. Make it with maximum effort, show me best what you can create. Use all your power, knowledge and make best graphics and best game design. Surprise me with graphics, lore and everything.
Videoseite
Claude Opus 4.5 builds a 3D city with one shotr/ Prompt verfügbar0:58
3D & Generativ
u/ozgrozer·Opus 4.5

Create a 3D city scene using Three.js that features a bustling urban environment with skyscrapers, apartment buildings, and smaller shops lining the streets. Incorporate roads with moving cars,…

Vollständiger Prompt
Create a 3D city scene using Three.js that features a bustling urban environment with skyscrapers, apartment buildings, and smaller shops lining the streets. Incorporate roads with moving cars, traffic lights, and pedestrian crossings to bring the city to life. Add pedestrians walking on sidewalks and crossing the streets to enhance realism. Include street elements such as lampposts, benches, and trees for a more immersive experience. Utilize dynamic lighting to simulate day and night cycles, and implement basic camera controls to allow users to explore the vibrant cityscape from different perspectives.
Videoseite
claude code is animating "what if" stories into 3D animations now𝕏 Prompt verfügbar1:20
3D & Generativ
@fuckscales·Model not specified

stories into 3D animations now made this entire video in 15 minutes for $0 i know absolutely nothing about blender or capcut😭 literally did the whole thing with one claude code prompt giving it…

Vollständiger Prompt
stories into 3D animations now

made this entire video in 15 minutes for $0

i know absolutely nothing about blender or capcut😭

literally did the whole thing with one claude code prompt

giving it away for free

Thank me later for this 👇

<role>
Act as an AI animation studio specializing in 3D cartoon animation, science storytelling, and automated video production.
Recreate the production style of my attached
Videoseite
🚨 Fable 5.5 TESTING Part 4𝕏 Prompt verfügbar0:13
3D & Generativ
@camperaigg·Fable 5.5 · laut Creator

Make me a transformer truck with animations of its transforming. I never touched Blender. 🤯 ⏱️ 107 minutes 💸 $9.64 in API costs 🤖 Claude Fable 5.5 Xhigh in Claude Code What it did on its own 👇…

Vollständiger Prompt
Make me a transformer truck with animations of its transforming.

 I never touched Blender. 🤯

⏱️ 107 minutes
💸 $9.64 in API costs
🤖 Claude Fable 5.5 Xhigh in Claude Code

What it did on its own 👇

🦾 Rigged 51 joints and baked every one on all 375 frames
🦵 Wrote a ground solver so the feet stay planted while the body rises
🌧️ 5,000 Geometry Nodes raindrops + rippling puddles on wet asphalt
🔊 Synthesized all 64 sound cues from scratch: diesel, air brakes, servos, ratchets, stomps. Zero samples
🔦 Caught its own bugs: headlights aimed backwards, fingers poking through the grille
🔍 Head glowing too hot? It ran 5 test renders to find the culprit (visor bloom + key light)

📦 12.5 s · 1080p30 · 73 robot parts · ~73k tris · Cycles + OptiX · −14.6 LUFS
Videoseite
Claude Code tip: install huashu-art-motion and Opus 5.5 can draw animations in 𝟯𝟱 𝗮𝗿𝘁 𝘀𝘁𝘆𝗹𝗲𝘀 with…𝕏 Prompt verfügbar0:41
Kurzfilm
@Voxyz_ai·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…

Vollständiger Prompt
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.
Videoseite
i just made this stickman animation in full code with claude opus 5.5𝕏 Prompt verfügbar1:23
Kurzfilm
@finnardley·Opus 5.5

for a local text-to-speech). Everything is built in code: no AI images, no AI video. Make it MY story, not a copy of an example. </inputs> <format> The style is a second-person survival thriller…

Vollständiger Prompt
for a local text-to-speech). Everything is built in code: no AI images, no AI video. Make it MY story, not a copy of an example.
</inputs>

<format>
The style is a second-person survival thriller with stickmen, built as a series:
-
Videoseite
Fable 5 vs Opus 5 for 2D Spritesr/ Prompt verfügbar0:40
Kurzfilm
u/bobo-the-merciful·Fable 5

Build me some knight sprites which I can use in my new medieval 2D isometric game. The game doesn't exist yet I am starting with sprites - this is the first thing we are building.* Done with Claude…

Vollständiger Prompt
**

*Build me some knight sprites which I can use in my new medieval 2D isometric game. The game doesn't exist yet I am starting with sprites - this is the first thing we are building.*

Done with Claude Code CLI.
Videoseite
I recreated the viral riso animation with Claude Code + Opus 5. Here's the full prompt, the process and the token countr/ Prompt verfügbar0:28
Kurzfilm
u/GoldianSummer·Opus 5

for your own title) Build a 30-second procedural animation in a risograph-print style, as ONE self-contained index.html (Canvas 2D, no libraries, no network fonts, no images, no assets of any kind —…

Vollständiger Prompt
for your own title)

    Build a 30-second procedural animation in a risograph-print style, as ONE self-contained index.html (Canvas 2D, no libraries, no network fonts, no images, no assets of any kind — every pixel is drawn by code). Make the finished animation, not a demo of techniques.
    
    The idea
    A lone ink dot calls out into the world with ripples, and everything that resonates answers back — bells, wolves, whales, radios, fireworks. It collects them as memories, but alone they fade to blue. Then a second dot, pink, answers from off-screen. Call and response. Where their ripples meet, a flower blooms, the world is reprinted in their two inks, and we pull back to a universe full of pairs. It ends on a hand-lettered signature.
    
    The spine of the whole piece: a small indigo dot pinned to the exact centre of the frame, and concentric ripple rings coming out of it. Every scene, every transition and every camera move is organised around that dot. It never drifts during Acts I–III.
    
    Format
    Square 720×720 canvas (internally render at devicePixelRatio), 28.0 s, time-based (not frame-based).
    Warm cream paper background in all
Videoseite
i made this ricksclips style animation completely from scratch using opus 5.5𝕏 Prompt verfügbar0:34
Kurzfilm
@treyscalez·Opus 5.5

Make a vertical animated cartoon short of MY story, built in code: three.js r160 world + canvas-drawn 2D character cards, rendered frame by frame in headless Chromium (Playwright, swiftshader),…

Vollständiger Prompt
Make a vertical animated cartoon short of MY story, built in code: three.js r160 world + canvas-drawn 2D character cards, rendered frame by frame in headless Chromium (Playwright, swiftshader), encoded with ffmpeg. 1080x1920, 30fps, exactly as long as my voiceover. Work start to finish; only ask if script and audio don't match.
Videoseite
Opus 5.5 .. what is the point of life?r/ Prompt verfügbar1:14
Kurzfilm
u/MaxLo85·Opus 5.5

Showing off your ability to storyboard, illustrate, motion design, graphic design, use any tools you need to answer the question in a 60s video "What is the point to life?" First video was exactly…

Vollständiger Prompt
Showing off your ability to storyboard, illustrate, motion design, graphic design, use any tools you need to answer the question in a 60s video "What is the point to life?"

First video was exactly this, but it was so fast that some of the text was hard to read. So I asked it to just slow it down a bit. I think it just took the mp4 and stretched it out. End result is a readable video at 1:14, but the music sounds odd at a couple points.

Anyway, I found this video to be ridiculously beautiful. It's hard to imagine it was a basically an algorithm that put this together.
Videoseite
OPUS 5.5 IS ALL YOU NEED FOR MOTION DESIGN𝕏 Prompt verfügbar
Produkt & UI
@rossaxbt·Opus 5.5

Order: one black shape keeps changing: Ordered ✓ → Printing % → On its way (a van on a route) → Delivered ✓. Wall: the delivered circle expands until black fills the frame, holds for one beat, then…

Vollständiger Prompt
.
Order: one black shape keeps changing: Ordered ✓ → Printing % → On its way (a van on a route) → Delivered ✓.
Wall: the delivered circle expands until black fills the frame, holds for one beat, then shrinks into the framed print hanging in the real wall footage. The same iris opens onto the print and closes again. The frame fills the screen, contracts into the pill → the dot → the letters spring back out on the returning beat. Last frame = first frame.
</structure>

<build>
1. One HTML file, square 1440x1440. Compute every style from time inside an async seek(t): no CSS transitions, timers or state carried between frames.
2. Use closed-form step responses for springs. When a value has multiple targets, add one spring per change so it remains a pure function of time.
3. Liquid glass: each glass element keeps its own clone of the scene behind it. Filter that clone with an SVG feImage displacement map (a rounded-rect distance field) through three feDisplacementMaps at slightly different scales for chromatic edges, then add a rim light. For glass letters, use a canvas distance field per glyph to create the map, mask and highlights.
4. Goo: apply blur and an alpha threshold, then composite the source on top so the glass stays sharp inside.
5. Iris: place 6 blades around a hexagonal aperture. Each blade uses its two vertices, both edge extensions and the SHORT arc between them.
6. Wordmark squeeze: move every letter toward the dot by the same factor and adjust its drawn width to match (narrow the wdth axis, scale the rest), keeping the letters in contact.
7. Footage: re-encode it all-intra (ffmpeg -g 1), load it as a blob URL and await
Videoseite
this is my best project yet and its fucking insane𝕏 Prompt verfügbar0:22
Produkt & UI
@twoclipping·Opus 5.5

Light emotion tags only: [softly] on the quiet lines, [excited] on the [Verb] line. The opener gets no tag and a plain full stop. </script> <voice> Call the ElevenLabs API directly with my key, no…

Vollständiger Prompt
Light emotion tags only: [softly] on the quiet lines, [excited] on the [Verb] line. The opener gets no tag and a plain full stop.
</script>

<voice>
Call the ElevenLabs API directly with my key, no MCP. Generate 4 takes of the whole script in one read and let me pick. If one line is off, regenerate only that line 4 times and splice the best one into my take.
Cut every pause over 0.28s down to 0.2s, then level each phrase 85% of the way to the median level, changing gain only inside the pauses.
For word timings, cut the read at every pause of 100ms or more, transcribe each chunk on its own with Whisper and pin each chunk's first word to its measured onset. One Whisper pass puts words up to half a second late.
</voice>

<direction>
A 22 second square launch film, 1440x1440 at 60fps, in the style of an AI lab's launch: a white page, one typeface, black ink, real images, and every caption typed word by word at the exact moment it's spoken.
Every control (the prompt bar, the settings panel, the caption pill) is liquid glass: the scene behind it frosted, its edge bending that scene like thick glass, a top sheen, a bright rim and a soft lift shadow. Glass on plain white shows nothing, so put a slow pastel aura in my brand colours, or a blurred wash of the photo, behind it.
The one word she stresses types in a gradient of my brand colours with a faint glow behind it.
Motion rules: the camera always drifts (a 1.0 to 1.04 push per scene, and when one scene hands its content to the next, the next starts at the zoom the last one ended on), nothing pops in (fades of at least 0.3s, eased), images switch on 16th notes with a click each, scene changes land on phrase starts, and the music's drop lands on the [Verb] line. No full stops on screen.
Banned: selection-box highlights, beat-snapped slams, white flashes, 3D, templates.
</direction>

<structure>
Seven scenes, each hung on the voice:
1.
Videoseite
I have mastered AI motion & design.𝕏 Prompt verfügbar0:08
Produkt & UI
@notdwd·Opus 5.5

to-website reveal, 1920x1080 at 30fps (226 frames), one continuous take: a prompt types, the send button is pressed, and the box itself becomes the finished landing page. Look: blue-graded sky…

Vollständiger Prompt
to-website reveal, 1920x1080 at 30fps (226 frames), one continuous take: a prompt types, the send button is pressed, and the box itself becomes the finished landing page.
Look: blue-graded sky #294376→#769cc2 with thin white line graphics (two circles, two horizontal and two vertical lines, two diagonals, 4-point sparkles at the crossings, a blurred violet→yellow→teal rainbow glow top-right, light film grain). The background subject is a crisp, opaque, full-colour cut-out (hand-traced mask, 2–3 px feather) on the right. White prompt box, radius 18, soft shadow; Inter 34.8px/44.4px #121212; black send button with a white arrow; a grey "Opus 5.5 ⌄" label beside it. Freshly typed characters arrive indigo #24249a, pass through blue and maroon, and settle to #121212 over ~13 frames.
Page: full-bleed hero with the subject cut out on the right over a steel-blue sky #3b5876→#75a2c4, and a horizontal motion-blur smear of the subject trailing left. White Inter UI: logo top-left, nav Features/Pricing/FAQ/Download, an outline pill top-right, bold 63px headline, 23px paragraph, white pill CTA, three muted feature rows with icons, three muted wordmarks bottom-left.
Default page copy: logo "Monke"; pill "Made with Claude Opus 5.5"; headline "Smile Harder. Selfie / Smarter, Week by Week"; paragraph "Monke tracks grins, bananas, selfies and naps—then turns every photo into clear, motivating progress you'll actually feel."; CTA "Get the Banana"; features "Grin zones (Z1–Z5 time & trends)", "Banana scores (coach-ready)", "Auto-sync from any camera you steal"; wordmarks BANANA CO. / JUNGLE / OPUS 5.5. Give the monkey white shield sport sunglasses with a mirrored lens (yellow→orange→red→magenta→orange→yellow, vertical streaks, top highlight, drop shadow) along his eye line (25° tilt).
Banned: crossfades between scenes, stock UI kits, glows on the text, anything that looks like a template.
</direction>

<structure>
Default prompt typed: "Build a premium, modern meme-tech landing page for a monkey who takes selfies. Create a full-screen cinematic hero featuring a grinning macaque in sport sunglasses, positioned on the right side with generous negative space on the left. Use a bold white headline about taking better selfies, a short supporting paragraph, and a clean rounded "Get the Banana" CTA. / Add a minimal top navigation with logo."
f0–29, type: the box starts at x884 y635 709x112 and eases out to x570 y477 778x130 (90% there by f12) while the whole scene pulls back 7%. Typing starts on f4 with a real keystroke rhythm, reaches 30 characters by f26, then stalls. Four white selection handles hug the box corners.
f29–44, charge: a violet solarised wash floods the scene (peak f36). The box tilts back up to 12° (rotateX, peak f36), the handles fly out to the frame corners, and an ASCII field of % @ # ⨸ glyphs appears at the left and right edges. The box grows to a tall card x541–1374, y425→227. On f40–48 the rest of the prompt bursts in (about 50 characters per frame) and fills ~12 lines.
f48–63, settle: the tall card lands at x575 y227 766x626. The camera eases back toward the subject. A black cursor appears on f55 at (1455,595), pointing up-left, and grows to 112 px.
f64–96, press: hard cut to a 3.19x zoom on the send button (75 px becomes 239 px on screen), a pale pink wash across the top. The cursor swings in from the right (f64–68) and glides to the button (f68–80). Press f80–86: the cursor squashes to 0.9, the button inflates 12% and flashes Claude terracotta #D97757, and the box edge bulges under it. f93–96 the frame blurs 6 px under a lavender veil.
f97–120, reveal: wide shot. The page's hero photo zooms slowly behind (1.1% per frame). The box (763x596) drops from y60 to y245 with an ease-out, settled by f110. On f106–110 it turns grey, then goes dark from the bottom while a cyan band sweeps down through it (f111–121), wiping the text away.
f121–145, morph: the box grows into the page, from x576 y245 763x596 to full frame on a fast ease-out (half the distance by f127, full by f145). Its fill is glass: a dark veil at the top, a cyan→white band sweeping down and out, white fading away. Every page element slides from inside the box to its final place on one progress curve (50% at f130, 90% at f147, done at f161). The headline types two lines at once from f122 to f158.
f161–224, pull back: the page shrinks around its centre onto a flat #dddddd background, from 1920 px wide to 1344 px (1634 by f173, 1404 by f190, 1344 by f214). The hero's motion blur strengthens as it goes. f225 is black.
</structure>

<build>
1. One HTML file, 1920x1080, rendered from seek(t). Every style is a pure function of the frame: no CSS transitions, no timers, no Math.random. Use seeded hashes.
2. Animate with keyframe tables, kf(frame, [[f, value], ...], ease), interpolating numbers or arrays. Every move above is a table of these keyframes.
3. Cut-outs are SVG masks from hand-traced polygons with a 2–3 px Gaussian feather. The motion-blur smear is a scaleX-stretched copy through an SVG horizontal blur (feGaussianBlur stdDeviation="40 0").
4. The press, the grey-to-dark box and the glass card are layered linear gradients whose stop positions are driven by the band value.
5. Sound: no voice.
   - Music: cut Voxscape so its first bass step lands at 1.72 s (source 38.76 s) and its big bass attack at 4.11 s (source 47.36 s, splice at 3.41 s).
   - Low-pass sweeps: the music dips to 400 Hz from 2.4 to 2.78 s and to 150 Hz from 3.41 to 3.58 s, reopens by 4.08, and fades out 6.6–7.5 s.
   - Synthesized sound effects: keystroke ticks on the typing (0.13–1.97 s) and on the headline (4.3–5.1 s); whooshes at 1.35, 2.18 and 3.30 s; a click at 2.78 s; a shimmer rising to 4.08 s; a sub boom at 4.09 s; a pop at 5.15 s; a settle at 6.54 s.
   - Master to -14 LUFS, true peak -1 dBTP.
6. Render with Playwright, one screenshot per frame, then encode h264 at 30 fps and mux the audio.
</build>

<gotchas>
Measure text only after the fonts load, or the words collide. The cut-out subject must be opaque and crisp; blending it into the sky makes it look like a ghost. The zoom shot is a hard cut, not a zoom animation. Keep the page content inside the card while it grows (overflow hidden), except the nav, which sits above the box early on. Frame 225 is black.
</gotchas>

<start>
Ask me for the inputs. Then show me 4 stills (f20 typing, f82 the press, f125 mid-morph, f200 the pull-back) before you render the full film.
</start>
Videoseite
People have been asking how I'm generating my product videos.𝕏 Prompt verfügbar0:58
Produkt & UI
@elie2222·Model not specified

make product videos with code and AI agents Copy everything below the line into a coding agent (Claude Code, Codex, etc.). Fill in the `{{…}}` placeholders first. It describes how Inbox Zero…

Vollständiger Prompt
make product videos with code and AI agents

Copy everything below the line into a coding agent (Claude Code, Codex, etc.). Fill in the `{{…}}` placeholders first. It describes how Inbox Zero produced its landing-page hero, launch films and about 15 docs and app walkthroughs, each costing well under $1 in API calls.

---

You are producing product videos for **{{PRODUCT}}** ({{ONE-LINE DESCRIPTION}}). The videos are a landing-page hero (~55s), short launch films (25–40s) and feature walkthroughs (45–110s) for the app and docs. They are made entirely with code: there's no screen recording and no video editor. Quality matters far more than cost.

The product's source code is at `{{APP_REPO_PATH}}` and its docs are at `{{DOCS_PATH}}`. The founder or reviewer is {{REVIEWER}}. They give taste feedback, and you turn that feedback into written rules.

## 1. Core idea

Every video is an **HTML/CSS/JS page whose every frame is a pure function of time `t`**. Headless Chrome screenshots each frame, and ffmpeg encodes them. This gives you:
- Exact, repeatable renders: a copy change means a cheap re-render, not a re-edit.
- Parallel rendering, because nothing carries over from one frame to the next.
- Real product UI, because the "footage" is real DOM captured from the running app.

Don't use Remotion or any other video framework; a ~200-line engine is enough. Don't screen-record: recordings can't be re-timed, re-worded or kept pixel-perfect.

## 2. Set up a private video repo

Create a **private** repo (e.g. `{{ORG}}/demo-video`) separate from the product repo. Its layout:

```
AGENTS.md        # read-first notes for every agent: pipeline, taste rules, mistakes made
README.md        # catalog: every video, its branch, length, status, where it's used
BRIEF.md         # product truths, fictional cast, kit API, end-card and taste rules
EXPLAINER.md     # brief for the walkthrough format
LAUNCH.md        # brief for launch films
MUX.md           # hosting IDs for every published video
engine.js        # renderAt(t), addScene, spring/easing helpers, word-by-word captions
render.mjs       # parallel Playwright frame renderer → ffmpeg
           # voice + music mix with ducking and loudness normalisation
judge.mjs        # audio judge (picks the best TTS take)
vjudge.mjs       # video judge (reviews a whole render)
         # contact sheet from sampled frames
kit/app/         # REAL app screens captured as DOM snapshots (see §3)
kit/explainer.js # overlays: step captions, callouts, highlights, camera, cursor, typing, toasts,
                 # and mocks of third-party UIs (Gmail, Outlook, Slack, …)
kit/endcard.js   # shared end card
music/           # shared music bed(s)
tools/           # upload scripts (hosting), helpers
```

**One branch and one git worktree per video** (`git worktree add -b explainer-foo ../demo-explainer-foo main`). `main` holds only shared things: the kit, the briefs and the tools. Merge `main` into a video branch to pick up kit fixes. Put kit fixes found while making a video in a separate commit so they can be cherry-picked to `main`.

Commit each video's web encode, poster, `.vtt` captions and a `VARIANT.md`. That file holds the script, the timings, chapter markers, the claim checks, and any docs-vs-UI discrepancies found. Git-ignore masters and intermediate files.

Keep `AGENTS.md` alive. Every time the reviewer gives feedback, or an agent makes a mistake, add a one-line rule there. This file is what makes the tenth video good on the first try.

## 3. Capture the real UI kit

1. Run the app locally with a **seeded database of fictional data**: one consistent cast (a main user plus 4–5 contacts and a fictional company), and realistic but fake emails, events and numbers. Use local emulators for third-party APIs where possible.
2. Write a capture script (Playwright) that visits each screen and state the videos need. It saves the **rendered DOM plus inlined CSS** as a standalone HTML snapshot, plus a PNG for reference. Inbox Zero ended up with ~140 states.
3. Missing states can be **derived** from the nearest snapshot by editing the DOM to match the real component's source (text, classes), never invented.
4. **Audit every snapshot for leaks** before committing: real names, emails, avatars, API keys, and the capture machine's **timezone and locale**. A real city name once leaked through a timezone picker.
5. Document the states, selectors and how to recapture in `kit/app/README.md`.

## 4. Write the script (accuracy first)

- Read the docs page and **the app source** for the feature. Every label, button and step on screen must match the product. Where the docs and the UI disagree, the UI wins; log the discrepancy in `VARIANT.md` and fix the docs afterwards. (This produced a steady stream of real docs fixes and bug reports.)
- Check claims in code, not just in the docs. For example, does feature X actually use data Y?
- Keep a list of **product truths** in `BRIEF.md`: supported platforms ("always say Gmail *and* Outlook"), trial terms, and what is early-access.
- A walkthrough has a 1–2s product payoff up front, then numbered steps (one caption each), one result shot, and a minimal end card.
- **Intro messaging** (hero and launch) must say what the product *is* in the first line. Write several candidate openers and let the reviewer pick.

## 5. Build the timeline

- `engine.js`: scenes are DOM subtrees shown and hidden with `display:none` (not `visibility`, because visible children leak through a hidden parent). All motion is computed from `t` with springs and easing.
- **Render purity is mandatory**: no ` no randomness without a seed, no state carried between frames. Workers start mid-timeline.
- Camera moves are CSS transforms on the snapshot, and so are cursor paths, typing and highlights.
- Preview live with `npx serve .`, using `?t=17` to start at 17s.

### Taste rules (start with these; add your reviewer's)
- **Openers:** light and product-native. No dark gradients, glossy fake app icons with red badges, or captions over blurred clutter. Reach the product payoff within ~2s.
- **No recaps:** never repeat earlier points in words or as a montage at the end.
- **End cards:** neat and centred, with a logo lockup, one line and a quiet URL. Landing cuts can carry one CTA (e.g. "Try free for 7 days") plus small platform marks. Never "·"-joined copy, and never a button stuffed with text.
- **Legibility:** body text ≥ 20px at 1080p, no wide shot of unreadable UI for more than ~1s, no words sliced at frame edges, and captions fully settled ≥ 0.4s before the click they describe.
- **Transitions:** no long crossfades between two busy UIs (the double exposure looks muddy). Use a cut, a camera push or a short blur-through.

## 6. Audio

- **Voiceover:** a strong TTS model with style instructions (Inbox Zero used Gemini Flash TTS through OpenRouter). Pick one voice per format. Generate **2–3 takes per line** and pick the best with an audio-capable model (`judge.mjs`): it scores pacing, mispronunciations, odd stresses and clipped endings.
- **Music:** generate one shared bed per format (Inbox Zero used Lyria). Models ignore the requested length, so detect the beat grid (librosa) and cut or loop at phrase boundaries.
- **Mix (` duck the music under the voice with a sidechain, then do two loudnorm passes to −14 LUFS and −1.2 dBTP.
- Agents can't listen. Flag music endings and loop points for a human ear-check.

## 7. Render

- `render.mjs` splits frames across N Playwright workers. Each one loads the page, sets `t` and screenshots. ffmpeg then encodes a high-quality master (CRF ~12) and a web copy (CRF ~20).
- Add a screenshot timeout and retry (e.g. 120s, 5 tries); long renders hit flaky frames.
- Support env vars to render a sub-range or a single segment, so fixes don't need a full render.
- **On a shared machine:** cap workers (e.g. 3 per agent) and only stop your own processes by PID. Never `pkill -f render.mjs`: it kills other agents' jobs.

## 8. Review before showing anyone

- Sample frames into 2×2 contact sheets and **look at them yourself**, zooming in on captions, edges and data. This is the main review.
- Use a video-capable model (`vjudge.mjs`, Gemini Flash) for whole-video checks like timing and caption order, but **treat its output as hints**. Video and audio judges hallucinate problems, so verify every claim against frames.
- Check: claims match the code, the fictional cast only, no leaks, the legibility rules, the end card.
- Show the reviewer the finished mp4s (open the folder for them) along with the `VARIANT.md` discrepancy list.

## 9. Work in parallel with subagents

- Once the kit and briefs exist, give **one subagent per video**. Each gets its own worktree and branch, the brief, the relevant docs page, and the instruction to read `AGENTS.md` first.
- Each subagent writes the script, builds, renders, reviews and reports back with the mp4 path and the discrepancies found.
- The coordinator merges kit fixes into `main`, uploads, and integrates the videos into the app and docs.

## 10. Publish

- **Hosting:** use Mux (or similar) rather than YouTube embeds. You get a clean player, no recommendations and auto-subtitles. The upload script sets a public playback policy and generated English captions, and records each ID in `MUX.md`. Pass API tokens via env vars and never commit them.
- **In the app:** a feature-page video button or dismissible card. **Lazy-load the player** (`next/dynamic`, `ssr:false`) so it only loads when the dialog opens and adds nothing to the page bundle.
- **Docs:** a lazy `<iframe src=" loading="lazy">` at 16:9.
- **Landing hero:** track `video clicked / started / progress / completed / closed` with a `video_id`. Don't A/B test the hero video: only the ~10% who click can be affected, so overall-sign-up tests are underpowered. Ship the better cut and compare cuts on watch-through and viewer → sign-up by `video_id`.
- **YouTube:** the API locks uploads from unaudited projects to private, so upload in Studio and schedule one video every ~2 days. If an agent automates Studio, set text with `execCommand('insertText')`, type dates with real keystrokes, and **read every value back before clicking Schedule**.
- If the product repo is public, keep commit and PR text free of private details. If it mounts private submodules, grep them before removing any shared component.

## 11. Mistakes we already made (don't repeat them)

- Invented UI in v1, where the reviewer's first note was "show real UI". → Real DOM snapshots only.
- Claims the product doesn't make (e.g. "important emails move to the top" when they're actually labelled). → Check in code.
- Taglines the company doesn't use. → Offer options and let the reviewer pick, then record the pick.
- A real timezone leaked in a snapshot and was committed to history. → Audit before committing.
- Agents killed each other's renders with `pkill`. → Stop processes only by your own PID.
- A judge model "found" skips and glitches that weren't there. → Verify against frames.
- Removing a shared component broke production through a private submodule. → Grep it first.
- A free hosting plan capped the asset count, and the upload script swallowed the error. → Scripts must surface API errors.

## Deliverables per video

- [ ] `out/<slug>-web.mp4`, poster, `.vtt`, and chapter markers
- [ ] `VARIANT.md`: script, timings, claim checks, docs/UI discrepancies
- [ ] An entry in the `README.md` catalog, and its hosting ID in `MUX.md`
- [ ] Any new rules learned are added to `AGENTS.md`
Videoseite
Difference between basic and meta prompt - Opus 5.5r/ Prompt verfügbar0:30
Produkt & UI
u/reddit0_r·Opus 5.5

Make a dynamic 150 second motion graphics video that shows what an incredible motion design you are, like it's a showreel for a resume. go all out. you're minimalist and tasteful, but not afraid to…

Vollständiger Prompt
Make a dynamic 150 second motion graphics video that shows what an incredible motion design you are, like it's a showreel for a resume. go all out. you're minimalist and tasteful, but not afraid to add a wow factor. You'll build the video for supernotchy.com product
Videoseite
I have made this video with Fable 5.1 in one shot using Claude Desing + Remotions + ElevenLabsr/ Prompt verfügbar0:35
Produkt & UI
u/Own-Culture3567·Fable 5.1

/>` between beats so lines land near their marks, but do NOT trust breaks for timing: ElevenLabs stretches them. - Generate one clip per cut through the API with timestamps (`POST…

Vollständiger Prompt
/>` between beats so lines land near their marks, but do NOT trust breaks for timing: ElevenLabs stretches them.
    - Generate one clip per cut through the API with timestamps (`POST /v1/text-to-speech/{voice_id}/with-timestamps`) and derive a cue sheet from the character alignment. Per line: `{ in, out, at }` where in/out index the source file and `at` is the composition time the line starts. Save as `src/vo.ts`.
    - Play each cue as its own `<Audio src startFrom={in·fps} endAt={out·fps}>` inside `<Sequence from={at·fps}>`. No re-encoding. Regenerating the voice changes only `vo.ts`.
    - Then retime the scene table in `cuts.ts` to the voice, not the other way round. Picture marks (the thing closing, the notification, the domain) land 0.3–0.6 s after the line that announces them.
    - Files go to `public/audio/vo-<Cut>.mp3`; `scripts/props.ts` detects them and sets `withAudio`. Missing files render silent.
    
    ## Music and SFX
    You cannot produce music. [Pick one:
Videoseite
Yes, opus 5.5 is great at motion design, but its even better using the Runway MCP along with it 🍦𝕏 Prompt verfügbar
Erklärvideos & Bildung
@notiansans·Opus 5.5

Create a [60 second] motion graphic explainer video about [the history of ice cream from the inception, to present day]. All of the visual images should be handled by Runway, and all the motion…

Vollständiger Prompt
Create a [60 second] motion graphic explainer video about [the history of ice cream from the inception, to present day]. All of the visual images should be handled by Runway, and all the motion graphics elements and animations should be handled by you. The art style should be [newspaper cutout / mixed media aesthetic] with a high degree of polish. This piece is for your portfolio, so make sure to make it great.
Videoseite
Indonesian history recap, plain Opus vs Opus with Tesseract𝕏 Prompt verfügbar0:59
Erklärvideos & Bildung
@hanifproduktif·Opus 5.5

Mit Referenzbildern, Audio oder anderen Eingaben erstellt.

Create an animation that quickly recaps the 81 years of Indonesian history. The style should be simple, lighthearted and fun, in a line drawing animation format, with suitable music and voiceover…

Vollständiger Prompt
Create an animation that quickly recaps the 81 years of Indonesian history. The style should be simple, lighthearted and fun, in a line drawing animation format, with suitable music and voiceover added. The video should be less than 1 minute"

The 2nd video made with same voiceover and prompt, but I added the Tesseract cli.

You can try it yourself with your Claude!
Videoseite
How to make a Product Promo Video with Claude Design (Prompts inside)r/ Prompt verfügbar0:40
Erklärvideos & Bildung
u/gnurpreet_·Model not specified

The file upload to YouTube, Instagram & Facebook should look like the file being dragged and dropped onto those sites in a browser. Show a basic drag-and-drop UI element for each site matching their…

Vollständiger Prompt
- The file upload to YouTube, Instagram & Facebook should look like 
      the file being dragged and dropped onto those sites in a browser. 
      Show a basic drag-and-drop UI element for each site matching their 
      brand colors. Get the correct icons for each platform from the web.
    - Make overall scene transitions faster and slicker. Keep the whole 
      thing under 40 seconds.

That’s it. Two prompts total. The second one fixed exactly what needed fixing.

**The lesson:** Don’t try to get everything right in one massive prompt. Get a working draft, watch it, note what’s off, fix those specific things. Claude Design responds well to targeted correction.

# The generic prompt you can steal for any product

    Make a 30–45 second product intro video for [YOUR PRODUCT URL].
    Scenes:
    - Scene 1: Text animation — "[One-line problem statement]"
    - Scene 2: Show the old/painful way of doing this. 
      Use a browser window. Keep it simple and recognizable.
    - Scene 3: Introduce [PRODUCT NAME]. Show the core action 
      (the thing the user actually does — paste URL, upload file, 
      click button, etc.)
    - Scene 4: Show the product working. Progress indicator, 
      loading state, or live output — whatever fits.
    - Scene 5: Show the result. File icon, dashboard, confirmation 
      screen — make it feel satisfying.
    - Scene 6: Show where the result goes. Social platforms, email, 
      Slack, client — wherever the output lands.
    - Scene 7: Text animation — "[Core value proposition in one line]"
    
    Use the look and feel of [YOUR PRODUCT URL] for all UI components.
    Colors, fonts, and style should match the site.
    Keep transitions smooth and fast-paced throughout.

Then follow up with one refinement prompt targeting anything that’s off.

To export the animation into MP4, you can use my tool - [claudevideoexport.com](http://claudevideoexport.com)  
Audio was added to the video outside of any of these tools.

Edit: I turned this into a skill: [https://github.com/Gnurpreet/promo-video-script-skill](https://github.com/Gnurpreet/promo-video-script-skill)
Videoseite
Asked Opus 5.5 to show me how an earthquake actually happens with an interactive tectonic sandbox.𝕏 Prompt verfügbar
Erklärvideos & Bildung
@egeberkina·Opus 5.5

Create a visually stunning 60-second video explaining how an earthquake happens through an interactive tectonic sandbox. Make it feel like we are watching someone explore a beautiful real-time…

Vollständiger Prompt
Create a visually stunning 60-second video explaining how an earthquake happens through an interactive tectonic sandbox.

Make it feel like we are watching someone explore a beautiful real-time simulation, not a slideshow or traditional educational video.

Start with a clean 3D cross-section of Earth’s crust. Two tectonic plates slowly move against each other. Visualize the fault between them and show friction locking the plates while stress gradually builds.

As pressure increases, make the simulation more intense: rock layers deform, stress zones glow, subtle vibrations begin, and a live seismograph starts reacting.

Then trigger the earthquake. The fault suddenly slips and releases a massive burst of energy. Show seismic waves radiating outward through the ground, then transition upward to the surface where the landscape and a small city begin shaking.

Visualize P-waves and S-waves traveling differently through the Earth, followed by the strongest surface waves. Show buildings reacting differently depending on distance from the epicenter.

End by zooming back underground to reveal smaller aftershocks around the fault, then pull out to show the complete tectonic system.

Use cinematic motion graphics, satisfying physics simulations, dramatic scale transitions, premium 3D scientific visualization, minimal typography, dynamic labels, smooth UI overlays and seamless transitions.

The pacing should constantly evolve and reveal something new every few seconds so the full 60 seconds stays visually engaging.

Make it feel like an Apple-quality interactive science visualization turned into a cinematic motion-design video.
Videoseite
Opus 5.5 on Max Effort made this video in one-shot. This opens a world of possibilities for educators…𝕏 Prompt verfügbar5:13
Erklärvideos & Bildung
@mablesjoseph·Opus 5.5

Can you generate a motion graphics explainer in the visual style of this post and using all its content? I will leave the details up to you. I want you to show off what you can do so you have full…

Vollständiger Prompt
Can you generate a motion graphics explainer in the visual style of this post and using all its content? I will leave the details up to you. I want you to show off what you can do so you have full creative freedom within those styling constraints. I want to give this to my engineers at my company. I want you to be proud of the final product. Utilize the elevenlabs and remotion tools at your disposal and let me know if you don't see them for some reason. Use whatever you want in those tools to make the most polished product that you would be proud of. Source Article : Context Tax - X article from the article"

Tools :
- Claude Desktop
- Connectors : ElevenLabs (available in Connector library - need an account)
- Skill : Remotion (available in skills library)
Videoseite
give Claude Code 3 reference images and a topic. it can turn them into a storyboarded animated…𝕏 Prompt verfügbar0:35
Erklärvideos & Bildung
@RealMarvelX·Opus 5.5

Create a 60-second animated explainer about how artificial intelligence works. Use my reference images for the visual direction. Build a scene-by-scene storyboard, use smooth transitions, clear…

Vollständiger Prompt
Create a 60-second animated explainer about how artificial intelligence works. Use my reference images for the visual direction. Build a scene-by-scene storyboard, use smooth transitions, clear typography, engaging motion graphics, and export the finished animation as an MP4.
Videoseite
i recreated a video from 1.4 billion view youtube channel with one claude code prompt𝕏 Prompt verfügbar
Erklärvideos & Bildung
@Bajanpunkw·Model not specified

make me a 45–60 second animated video in the style of oversimplified about [your topic], built 100% in code. no ai images, no ai video 1. script - 10–12 short lines, one idea per line, a joke or a…

Vollständiger Prompt
make me a 45–60 second animated video in the style of oversimplified about [your topic], built 100% in code. no ai images, no ai video

1. script
- 10–12 short lines, one idea per line, a joke or a twist every 2 lines
- line 1 is a hook that sets up a question or a myth. the last line pays it off, so the ending lands instead of just stopping
- every fact must be true. check anything you're not sure about

2. voice
- pip install edge-tts numpy. voice en-US-AndrewMultilingualNeural, rate +18%
- generate each line separately with boundary="WordBoundary", cut the silence edge-tts adds at the start and end of each clip, join lines with 0.1–0.2s gaps
- save voice.wav and timeline.json with every word's start/end. retry with backoff if a request fails

3. visuals
- one html file, 1920x1080 canvas, a function render(t) that draws frame t. one scene per line
- things appear on the exact word that names them (use the word timings). every line needs at least one action, not a still picture with a caption
- the camera never stops: slow push-in and drift in every scene, a quick punch-in on each scene change, zoom toward whatever the key word is about, a small shake on impacts. keep titles inside the frame when zoomed
- characters always idle (breathing, blinking). nothing on screen stays frozen for more than ~2 seconds
- the first 0.5s is an event (something drops in, explodes, slams), not a calm intro
- style: flat colors, round-headed characters with dot eyes and thick dark outlines, oversized hats, a yellow year badge in the corner, big bold labels that pop in, simple maps from world-atlas topojson with countries filling in color, quick pop-in animations, a comic military march under the voice

4. captions
- word by word at the bottom, current word highlighted, big bold font, max ~20 characters per chunk

5. sound (all synthesized in python, no samples)
- a quiet music bed that fits the style, ducked under the voice, stops on a short final chord
- sound effects on the actions: pops when things appear, a low thump for landings, a cannon/boom for explosions, a soft note on scene changes
- use clean tones. if you need noise (explosions, wind), run it through proper low-pass filters. no raw white noise, no buzzy saw waves
- the voice is always the loudest thing: voice peaks at -3 dBFS, every effect is set relative to it and sits under it, the final chord no louder than the voice. low-pass music+effects around 4.5 kHz

6. render
- puppeteer loads the page, calls render(i/30) for every frame, pipes screenshots into ffmpeg (libx264, 30fps), then muxes the mixed audio

7. check before you show me
- render ~10 stills from different moments, look at them and fix overlaps, cut-off text, empty space and anything unreadable
- after the full render: no silence longer than 0.5s, no part of the video where nothing moves for 2+ seconds. fix and re-render if there is
Videoseite
Building Videos with Clauder/ Prompt verfügbar0:30
Erklärvideos & Bildung
u/Botboy141·Opus 5.5

Build a 30 second motion graphics video that explains the process we use to build videos. \> This can follow the benefits Blake voice and brand - not for our usual audience so don't send them to the…

Vollständiger Prompt
\> Build a 30 second motion graphics video that explains the process we use to build videos.

\> This can follow the benefits Blake voice and brand - not for our usual audience so don't send them to the website, maybe make a joke about not sending them there, but the idea is to showcase the video building pipeline by pointing at a repo or article, etc. Include an ElevenLabs voice-over. Use assets from our repo, feel free to use my headshot, pieces from other videos, etc. You have access to openrouter, maximum spend on open router is $9.99 for this project.

\> How good can you make animations with that spend and open router access?

\> It should be PERFECT and Professional, even if satirical.

\> No .MD, no shared repo, but a here's how and have fun!

Result is above after \~20 minutes.

P.S. Eleven Labs voice clone is from the Professional subscription, usually settles on whisper2 for voice model IIRC. Open Router spend was under $3.00, including 16:9, 9:16 and 1:1 shots generated (not cropped). With my usual pipeline (less open router graphics), including voiceover, runs about $2/finished minute of video...
Videoseite
opus 5.5 is insane as a motion designer𝕏 Prompt verfügbar0:15
Typografie
@rossaxbt·Opus 5.5

Return: the orange dot moves back through the halftone, graph and toggle. Match the final frame to the first so the video loops cleanly. </structure> <build> 1. One HTML file, 1920x1080 at 60fps.…

Vollständiger Prompt
.
Return: the orange dot moves back through the halftone, graph and toggle. Match the final frame to the first so the video loops cleanly.
</structure>

<build>
1. One HTML file, 1920x1080 at 60fps. Compute every visual from time inside seek(t): no CSS transitions, timers or state carried between frames.
2. Use closed-form springs for the toggle, bouncing dot and graph. Draw the graph from the same spring function that moves the dot.
3. Animate letters individually for the
Videoseite
HOLY SH*T𝕏 Prompt verfügbar1:02
Typografie
@treyscalez·Opus 5.5

<inputs> 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,…

Vollständiger Prompt
>

<inputs>
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.
</inputs>

<direction>
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.
</direction>
Videoseite
Fable 5.5 is really something else. I had it make this kinetic typography music mideo on max…𝕏 Prompt verfügbar4:39
Typografie
@atomtanstudio·Fable 5.5 · laut Creator

make a dynamic motion graphics music video with lyrics that shows what an incredible motion designer you are, like it's your showreel for a résumé. go all out. I included the song lyrics below the…

Vollständiger Prompt
make a dynamic motion graphics music video with lyrics that shows what an incredible motion designer you are, like it's your showreel for a résumé. go all out. 

I included the song lyrics below the prompt.
Videoseite
I wanted to get Claude Opus 5.5 to turn the news into a video. This was done for data centers.𝕏 Prompt verfügbar0:25
Typografie
@Gdgtify·Opus 5.5

Create a 25.00-second kinetic typography film titled **“WHO PAYS FOR THE WIRES?”** Make it for someone opening an electric bill at their kitchen table. They should finish the film able to explain…

Vollständiger Prompt
Create a 25.00-second kinetic typography film titled **“WHO PAYS FOR THE WIRES?”**  Make it for someone opening an electric bill at their kitchen table. They should finish the film able to explain why a data center can cost money before it uses electricity, and who bears one specific construction risk in AEP Ohio’s service territory.  Deliver one self-contained HTML file with original stereo sound, embedded artwork and type, a 1920 × 1080 capture area, and deterministic 60fps rendering. Give the film the craft of an opening title sequence and the factual precision of a reported graphic.  **The shot to build first**  An eraser sweeps across an architectural drawing. In twelve frames it can remove a building big enough to fill the screen. At the edge of the site, the eraser collides with a steel transmission tower that has already been erected. The pencil shaft flexes. The graphite tip breaks against the paper as the pencil falls. The steel gives one low, sustained note.  Hold on the empty site and the standing tower. Let the viewer discover the question a beat before the words arrive.  Everything before this shot prepares the distinction between *planned* and *built*. Everything after it follows the cost of what remains.  **One world, three materials**  Build a single tabletop set. An opened utility envelope, a household bill, a translucent engineering drawing, and a contract occupy different depths. Behind the table, one warm kitchen window establishes a human scale. Keep the household bill anonymous and its dollar amount outside the crop.  Use graphite for proposed work. A soft mark can be drawn, smeared, or erased. Use dull galvanized steel for installed infrastructure. It casts a hard shadow and has real mass. Use dark red ink for financial obligations. It moves through the contract and invoice while the steel stays planted on the site.  Set the headlines in a heavy, slightly narrow grotesque. Set the contract paraphrase in a readable book serif. The type should look like it belongs to the surface carrying it. During a fast move, one word can become architecture. During its reading hold, give the viewer its complete silhouette.  **0.00–3.00 seconds · The envelope**  Start in near darkness. Paper slides across wood. A kitchen light catches the embossed words **ELECTRIC BILL**. One thumb holds the envelope against the table while a finger opens the fold. Give the paper a little resistance. The sound is close enough to hear the fibers separate.  From this low angle, the fold makes a roofline. Move along it until a printed rule on the bill meets a survey line on the translucent plan underneath. Follow that line into the plan. In the margin, establish **ILLUSTRATIVE PROJECT**. The site and cancellation are a hypothetical example.  **3.00–7.50 seconds · Build two different futures**  Reveal **PROPOSED DATA CENTER** in graphite. The crossbars of the letters extend into a floor plan. Rack aisles draw themselves in quick succession. Leave a small square gap at the far end of the building. The viewer will recognize that patch of bare paper after the erasure.  In the foreground, the phrase **GRID WORK BEGINS** lands. Use the strokes of GRID as fabrication guides. Steel members lift off the guides, rotate around visible joints, and bolt into a single tower. Give the tower one distinctive asymmetrical gusset plate. A cable settles into its insulator with a short downward sag.  Keep both states readable in one low tracking shot. Behind the tower, a building still made of pencil. In front, steel already casting a shadow. The score borrows its rhythm from the work. Two bolt strikes, a cable pluck, a pencil stroke. Build the bass underneath those sounds.  **7.50–11.50 seconds · Cancel the project**  Across the top edge of the drawing, typeset **WHAT IF THE DEVELOPER CANCELS?** Let CANCELS travel with the eraser while the rest of the question holds steady.  Execute the pencil shot. Give the disappearing rack lines a dry directional smear. Let the last graphite dust settle around the tower footing. The kitchen light keeps shining through the same window. The audience should feel the peculiar ordinariness of a project that simply stops.  Land **BEFORE POWER IS SWITCHED ON** beside the empty site. A small service switch, previously visible on the plan margin, stays open. Omit the server-fan crescendo the score has led us to expect. Leave the steel ringing.  **11.50–15.00 seconds · Find the cost**  Lock the camera for half a second. Across the vacant footprint, place **THE WIRES ARE ALREADY UP.**  Then lower the camera until the tower’s diagonal brace fills the frame. Follow its shadow across the paper. The shadow meets a red invoice rule at precisely the same angle. Move from one to the other in a continuous shot. The solid tower remains visible behind us in the reflection of a metal ruler.  Reveal **WHO PAYS?** Set WHO small enough to fit between the strokes of the monumental P in PAYS. Let the question mark land over the original envelope. Hold the empty space beneath it. This is where a viewer might expect to see their own name.  **15.00–20.50 seconds · Read the agreement**  Slide the translucent drawing aside. Beneath it is the contract that has been on the table since the opening. A red rule leads to the source label **AEP OHIO · DATA CENTER AGREEMENT**. Present the operative condition in editorial type, clearly identified as a paraphrase.  Use three successive reading holds.  **CUSTOMER CANCELS BEFORE POWER-UP**  **DATA CENTER CUSTOMER REIMBURSES THE UTILITY**  **100% OF BUILDOUT COSTS**  Keep the condition and the AEP Ohio label visible when **100%** lands. Give **OF BUILDOUT COSTS** enough room to read at the same glance as the number. That wording defines exactly what the percentage covers.  Build the percentage sign from objects already on the table. Two punched registration holes supply the circles. The camera slides until the tower brace aligns between them to form the slash. The viewpoint clicks into place and **100%** reads as a single piece of typography. Hold it for at least 1.4 seconds. A viewer who pauses here should get a complete, accurately qualified frame.  Sound the answer with the same three notes heard during construction, now tapped on the desk with a pencil. Let the final note coincide with the registration of the percent sign.  **20.50–25.00 seconds · Return to the kitchen**  Pull back. The household bill occupies the near side of the table. Across from it, the project invoice sits on the developer’s agreement. The red obligation line ends there. Between the two documents stands the same tower, its gusset plate catching the kitchen light.  The final copy belongs in the empty building footprint.  **WHO PAYS FOR THE WIRES?**   **IN THIS OHIO CASE, THE DATA CENTER CUSTOMER.**  Hold this composition from approximately 21.7 to 24.2 seconds. Finish with the sound of the pencil stub rolling across the table and coming to rest against the tower footing. The kitchen light goes out. Reach black by 24.85 seconds.  **Sound and pacing**  Write the score at 144 BPM, giving 15 bars in 25 seconds. Let construction sounds push against the beat. Place the pencil break between beats so it feels like an interruption. Reserve the strongest bass resonance for the standing tower after the project disappears. A quieter, closer kitchen sound at the end should make the return to the household tangible.  Generate the full score and effects as one original 48 kHz stereo buffer, exactly 1,200,000 samples per channel. Drive playback from the audio clock. Use the same cue records for the bolt landings, eraser contact, pencil break, percentage alignment, and their sounds.  **Reporting and delivery**  Use the cancellation provision in AEP Ohio’s Letter of Agreement as the factual basis. Its trigger in this example is customer cancellation before the target energization date. Keep the **100%** attached to the covered buildout costs. Keep household bills unquantified. Put the full source, the 2025 approval date, the November 2026 reporting context, and the separate provision for a delay exceeding 12 months in a source panel outside the film.  Provide **Play with sound**, pause, replay, scrub, and WAV download outside capture. Expose `window.ready`, `window. seek(seconds)`, `window.renderFrame(n)`, and `window.cues`. Render frames 0–1499 at `n/60`. Make dust, cable sag, lighting, camera position, and type placement reconstructible from any timestamp.  Review the erasure through the contract reveal first **with the sound off**. The material change alone should tell the story. Then play it with sound and check that the pencil break gets room to register before WHO PAYS enters. At half resolution, verify that the cancellation condition, responsible customer, and scope of the 100% figure can all be read. Check the opening and closing frames for the black loop boundary. Report which checks were actually executed.
Videoseite
Opus 5.5 is mindblowing good with these kinds of kinetic typography tasks. I am trying to build an…𝕏 Prompt verfügbar0:20
Typografie
@Gdgtify·Opus 5.5

Create a 20.00-second kinetic spoken-word film titled “BUILD THE FLOOR.” Treat this as an original miniature speech staged inside a typographic field. Every line reorganizes the field of the frame.…

Vollständiger Prompt
Create a 20.00-second kinetic spoken-word film titled “BUILD THE FLOOR.”
Treat this as an original miniature speech staged inside a typographic field. Every line reorganizes the field of the frame. The final declaration must stand on a field that finally lies flat.
Deliver one self-contained HTML file, 1080×1080, targeting 60fps, using SVG and/or Canvas. Embed all required assets.
ART DIRECTION
Background #102820. Letterforms # F4E9D5. Field lines and filings # F2B544. A magnetic-monument world: streamlines, flux, stillness at the null. Typography stays crisp; particles are atmosphere only. High-contrast serif for the speech, heavy grotesque for load-bearing words, restrained monospace for flux gauges. No horseshoe magnets, lightning, electron diagrams, or sci-fi arcs.
ORIGINAL SPEECH — EXACT WORDS, EXACT ORDER
“We were told to wait.”
“So we learned the weight of waiting.”
“Then one voice made room.”
“Then another.”
“Now the floor belongs to us.”
Do not attribute these words to any real person. No extra slogans. The complete speech must be understandable without audio.
CENTRAL VISUAL RULE
Words have assigned field roles. WAIT is a repelling plate; letterforms lean away from it, kerning compressed. WAITING is field lines sagging under load while filings stream toward the low side. VOICE is one pole reversed; the field reorganizes and letters stand upright along it. ROOM is a null point, a still eye inside the field. FLOOR is the field flattened into a horizontal plane. These roles must emerge from the actual letterforms responding to the field, not from illustrations.
STORYBOARD
0.00–3.00 — “We were told to wait.” The sentence leans away from the WAIT plate; streamlines compress against it. Available space pinches on the plate side; the sentence remains readable, pressed but intact.
3.00–6.50 — “So we learned the weight of waiting.” Reveal in phrase groups. Field lines sag deeper with each phrase. Filings — deterministic, hash-seeded per id and time — drift along the streamlines toward the low side and gather. The WAITING glyph hangs tilted inside the field as a suspended load.
6.50–10.00 — “Then one voice made room.” VOICE enters; one pole reverses. The field reorganizes: old streamlines retract by dash-offset while new ones draw in. Letters rotate upright along the new field — analytic rotation of whole glyphs, never path morphing. ROOM opens as a null point, a still eye; the counter of the O in ROOM is its center, and the next composition sits calm inside it.
10.00–12.50 — “Then another.” A second pole turns. The field becomes symmetric; every letter stands vertical. The baseline levels into the first perfect horizontal in the film. Hold absolute stillness for at least 400ms — even the filings pause.
12.50–16.00 — “Now the floor belongs to us.” The field flattens into a horizontal plane. The filings settle onto its surface as hairline grain. The final sentence locks in with the field; US aligns with the strongest flux line. Emphasis through alignment and scale only.
16.00–18.00 — Hold the complete declaration. One streamline pulses gently, then stills. No new text. No decorative motion.
18.00–20.00 — The camera travels along a flux line into the WAIT plate; filings rise as an occluding curtain filling the frame. Under full occlusion, return hidden elements to initial positions. Reveal the exact opening composition.
CHOREOGRAPHY
No dance beat; the field follows phrases, pauses, and emphasis. Phrase reveals follow reading order. Streamlines are precomputed curves revealed by dash-offset; filings are pure functions of (id, t), never simulated. Critically damped settling for the flattened plane. Available still space carries the emotional progression.
Videoseite
I asked Opus 5.5 to visualize a famous speech. I kept it at 20 seconds because I didn't want to burn…𝕏 Prompt verfügbar0:20
Typografie
@Gdgtify·Opus 5.5

Create a 20.00-second kinetic typography film titled “ESCAPE THE ORBIT,” based on John F. Kennedy’s Rice University address, September 12, 1962. The central experience: a sentence discovers that it…

Vollständiger Prompt
Create a 20.00-second kinetic typography film titled “ESCAPE THE ORBIT,” based on John F. Kennedy’s Rice University address, September 12, 1962.

The central experience: a sentence discovers that it can change its own trajectory.

Deliver one complete, self-contained HTML file. Composition: 1080×1080. Target: 60fps. Use Canvas, SVG, or embedded WebGL. Embed required assets and libraries. The film must work without audio.

EXACT DISPLAY TEXT
“We choose to go to the moon”
“[…]”
“not because they are easy,”
“but because they are hard”
Preserve this order. The bracketed ellipsis explicitly indicates omitted speech. Attribution is separate from the excerpt. No additional slogans.
ART DIRECTION
Background: midnight # 080D23.
Primary type: warm white # FFF4DD.
Trajectory: electric coral # FF654F.
Secondary orbital geometry: blue # 6685FF.
Use a broad, confident grotesque for the speech and a sharply drawn italic for the final emphatic word. Avoid the appearance of a spacecraft dashboard. No rockets, astronaut illustrations, starfield wallpaper, lens flares, or decorative telemetry.
The frame should resemble an exceptionally refined astronomical instrument that has become expressive.

CENTRAL VISUAL RULE
The baseline of the sentence is a trajectory.

At first it is trapped in a closed orbit. A rhetorical decision changes that orbit into an open path. The letters remain the same travelers throughout.
Use an abstract orbital metaphor; do not present invented mission data or imply a physically accurate flight simulation.
STORYBOARD
0.00–3.50
The opening excerpt appears across the center, large and horizontal. Reveal it in three meaningful phrase groups.
A single hairline ellipse passes behind the baseline. A small circular lunar mark occupies its distant focus.
Hold the completed phrase motionless for 700ms.

3.50–6.00
The camera pulls back. The previously straight baseline reveals a shallow curvature.

The phrase travels along the ellipse as a coherent unit. Keep its glyphs upright during the initial movement. Only after the reading hold may they progressively adopt the tangent of the path.

The viewer realizes the sentence is circling rather than advancing.
6.00–7.00
Show the bracketed omission in an uncluttered central opening. The orbital movement decelerates.

7.00–10.50
Reveal the next clause on the near side of the orbit. Its final word travels through one smooth, effortless arc and returns toward where it started.

This ease should feel elegant but unproductive. Avoid comic bouncing.

10.50–14.50
Reveal the final clause horizontally before transforming it.
At its emphasis, the ellipse opens at one precise point. The same tracked letter group takes the new tangent and departs.
Perform one deliberate 70-degree camera roll. Counter-rotate the active phrase so it remains readable while the orbital field changes orientation around it.

The trajectory sweeps from lower left to upper right. Acceleration is conveyed by expanding spacing between its trailing marks, not by shaking the camera.

14.50–17.00
The camera matches the departing phrase’s velocity. The phrase becomes visually still while the old orbit recedes beneath it.

The lunar mark enlarges into a restrained crescent through geometric overlap. The crescent brackets the destination without becoming a cartoon illustration.
17.00–20.00
Resolve into a spacious editorial composition containing the selected excerpt in reading order, including its omission marker.

The open trajectory runs through the margins and exits the frame. Hold the entire image completely still for the final 1.2 seconds.

CHOREOGRAPHY
Use only three camera operations: pullback, roll, velocity match.
Give each operation a rhetorical purpose.
Keep the currently read phrase at least 64px high in the 1080px composition.
Motion blur may affect trailing geometry, never the active text.
No word may begin its ornamental travel before its reading hold finishes.

IMPLEMENTATION
Represent the ellipse and departure path analytically. Blend position and tangent continuously at the departure point; no teleportation.
Use arc-length sampling for consistent spacing along curves.
Separate camera transforms from glyph orientation.
Cache glyph rendering and static geometry.
Expose window.ready and window. seek(t). Seeking must pause playback and render any time from 0 through 20 deterministically, including out-of-order calls.
Provide window.frame(n) for n=0…1199 at t=n/60.
Render t=20 as the final held composition.
Use no accumulated physics or runtime randomness.

QUALITY GATE
Inspect frames at 0, 3, 5, 7.5, 10.5, 13, 16, and 19 seconds.
Verify that the same tracked phrase visibly follows the changing trajectory.
Check the camera roll at phone size.
Inspect the departure transition for position or tangent discontinuities.
Return the complete HTML. If actual browser inspection is unavailable, state that briefly after the implementation; do not claim it was tested.
Videoseite