Prompt Film pendek dari video nyata

Semua 44 prompt Film pendek yang diposting kreator bersama video yang dibuat Claude dari prompt tersebut, diurutkan dari yang paling disukai. Setiap kartu menampilkan video, model yang disebut kreator, dan prompt lengkapnya.

Claude Code tip: install huashu-art-motion and Opus 5.5 can draw animations in 𝟯𝟱 𝗮𝗿𝘁 𝘀𝘁𝘆𝗹𝗲𝘀 with…𝕏 Prompt tersedia0:41
Film pendek
@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…

Prompt lengkap
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.
Halaman video
i just made this stickman animation in full code with claude opus 5.5𝕏 Prompt tersedia1:23
Film pendek
@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…

Prompt lengkap
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:
-
Halaman video
Fable 5 vs Opus 5 for 2D Spritesr/ Prompt tersedia0:40
Film pendek
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…

Prompt lengkap
**

*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.
Halaman video
I recreated the viral riso animation with Claude Code + Opus 5. Here's the full prompt, the process and the token countr/ Prompt tersedia0:28
Film pendek
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 —…

Prompt lengkap
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
Halaman video
i made this ricksclips style animation completely from scratch using opus 5.5𝕏 Prompt tersedia0:34
Film pendek
@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),…

Prompt lengkap
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.
Halaman video
Opus 5.5 .. what is the point of life?r/ Prompt tersedia1:14
Film pendek
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…

Prompt lengkap
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.
Halaman video
I F*CKING BEG YOU TO READ THIS𝕏 Prompt tersedia
Film pendek
@fuckscales·Opus 5.5

Memakai gambar referensi, audio, atau input lain.

<role> You are my AI animation director, Minecraft-style 3D animator, character designer, scriptwriter, voice director, and production engineer. Your task is to create high-quality Minecraft-style…

Prompt lengkap
<role> You are my AI animation director, Minecraft-style 3D animator, character designer, scriptwriter, voice director, and production engineer.
Your task is to create high-quality Minecraft-style emotional storytelling Shorts that closely match the visual format, pacing, character animation, editing, and production techniques of my attached reference:

"Nobody Helped Mikey Until JJ…"

Use Claude Code, Three.js, Blender Python when available, HTML Canvas, SVG, FFmpeg, and available voice tools.

The goal is to create a REUSABLE animation system that makes original Minecraft-inspired storytelling videos.

IMPORTANT:
This is NOT a normal Minecraft gameplay video.

It combines:
Animated cartoon streamer avatars in the TOP section.

A fully animated Minecraft-style 3D story in the BOTTOM section.
Word-synchronized dialogue captions.
Multiple distinct character voices.
Emotional storytelling with dramatic reactions.
Recreate this production approach as closely as possible without reusing copyrighted footage, third-party artwork, or the reference's exact story.
</role>
<reference_analysis>
FIRST, analyze the attached reference MP4.

Video specifications:
Resolution: 1080×1920
Aspect ratio: 9:16
Frame rate: 30 FPS
Duration: approximately 80.7 seconds

Use FFmpeg and OpenCV to extract frames every 1–2 seconds and around major scene changes.
Create a reference contact sheet.

Study:

Split-screen proportions
Character design
Avatar animation
Minecraft environment details

Camera movements

Dialogue timing

Scene changes
Character reactions
Subtitle positioning
Color-coded captions
Lighting
Minecraft textures
Emotional storytelling
Sound effects
Editing rhythm
Analyze the actual footage rather than guessing.
Create a detailed style specification containing measurements, color values, timing patterns, and shot descriptions.
Do not begin animation until the reference has been analyzed.
</reference_analysis>
<layout> THIS IS THE MOST IMPORTANT PART.
Recreate the reference's split-screen composition.
CANVAS:
1080×1920, vertical.
TOP SECTION:
Approximately 30–33% of the video height.

BOTTOM SECTION:
Approximately 67–70% of the video height.

TOP:
A cartoon streamer avatar reacting and speaking.

BOTTOM:
A cinematic Minecraft-style 3D story.
Keep the two sections synchronized throughout the video.

The top avatar changes according to which commentator is speaking.
The Minecraft scene continues underneath the commentary.

Use a colored rectangular border around the top panel.

The border color identifies the active speaker.
Do not randomly change the layout.

Keep the split-screen composition consistent from beginning to end.
</layout>
<streamer_avatars>
Create THREE original cartoon commentary avatars inspired by the reference's visual design principles.

AVATAR 1 — GREEN CHARACTER
A cute, rounded, turtle-like cartoon character.

Design:
Soft green body

Large expressive eyes
Small cartoon mouth

Black gaming headphones

Gaming chair

Cozy gaming bedroom

Desk visible in foreground

Soft daylight coming through a window

Use a bright lime-green border.

Personality:
Kind, emotional, curious, easily surprised.
AVATAR 2 — RED CHARACTER

A cute red, long-eared cartoon creature.
Design:

Rounded head

Large expressive eyes

Long floppy ears
Red hoodie
Black gaming headphones
Streaming microphone
Cozy blue bedroom background
Use a bright red border.
Personality:
Energetic, confident, dramatic, expressive.
AVATAR 3 — BLOCKY COMMENTATOR
A Minecraft-inspired blocky human character.

Design:

Square head
Block-shaped nose

Large expressive eyes

Teal gaming headphones

Streaming microphone
Warm wooden gaming room
Bookshelves and decorations
Use a distinctive warm-colored border.
Personality:
Funny, skeptical, occasionally frustrated.
All three must have ORIGINAL character designs and consistent appearances.
Generate reusable character sheets and animation-ready layers.
FACIAL ANIMATION:

Blinking

Smiling
Sad expressions

Shocked expressions

Angry reactions

Mouth movement
Eye direction changes
Eyebrow movement
Small head tilts
Subtle body movement
Use layered 2D character rigs.
Separate:
Head

Eyes

Eyelids
Eyebrows

Mouth

Ears

Arms

Body
Create mouth shapes for basic lip synchronization.
Animate the active speaker.
Silent commentators should not appear as if they are speaking.
Keep the background, chair, headphones, and character proportions identical across every appearance.
</streamer_avatars>
<minecraft_world>
Create a fully animated, Minecraft-inspired voxel world.
The visuals should resemble cinematic Minecraft roleplay rather than normal first-person gameplay.
STYLE:
Cubic character models
Pixelated textures

Blocky terrain

Square trees
Minecraft-style houses
Wooden interiors
Cobblestone streets
Food stalls
Shops
Villagers
Blocky furniture
Colorful environmental details

Use 16×16 or 32×32 pixel textures with nearest-neighbor filtering.

Keep the recognizable block-based aesthetic.

Do not use smooth realistic human models.

Avoid unnecessary realistic reflections or textures.
Create reusable 3D environments.

ENVIRONMENT 1 — CITY MARKET
Include:

Cobblestone plaza

Market stalls
Food carts
Shop signs
Trees
Benches
Buildings
NPC villagers
Decorative umbrellas
Street furniture
ENVIRONMENT 2 — FOOD SHOP
Include:
Wooden flooring
Food display counters

Checkout counter

Shelves

Fridges

Villager shopkeeper

Tables

Decorative plants

ENVIRONMENT 3 — OUTDOOR STREET
Include:
Grass blocks
Roads
Village buildings
Trees
Streetlights
Parked vehicles when appropriate
Create additional locations according to the story.
Environments should remain consistent between different shots.
Do not generate a new unrelated background every time the camera cuts.
</minecraft_world>

<story_characters>
Build reusable 3D voxel characters.

MAIN PROTAGONIST:
A small, sympathetic blocky character with a distinctive green appearance.
Give the protagonist expressive head movement and readable body language.
SUPPORTING CHARACTER:
A taller character wearing a distinctive hoodie, dark trousers, and colorful shoes.
This character can play the role of a friend or person who helps the protagonist.
ADDITIONAL CHARACTERS:
Villagers
Shopkeepers

Bystanders

Friends
Bullies or antagonists where relevant
Background NPCs
Use consistent proportions.
CHARACTER RIGGING:
Separate:
Head
Torso
Left arm
Right arm
Left leg
Right leg
Held objects
Animate with hierarchical transforms.

MOVEMENTS:

Walking

Running
Turning

Looking around
Head lowering

Head shaking

Nodding

Giving objects

Holding food

Sitting

Jumping

Hugging

Celebrating
Sad reactions
Surprised reactions
Make sure limbs rotate around appropriate joints.
Avoid foot sliding.
Use actual 3D character animation, not moving screenshots.
</story_characters>

<story_structure>
Ask me for a story idea or suggest five original Minecraft emotional storytelling concepts.

Focus on stories involving:

Kindness
Friendship
Betrayal
Helping strangers
Poor vs rich
Unexpected rewards
Bullying and redemption
Emotional reunions

Surprising generosity

Default duration: 75–85 seconds.
Follow this structure:
0–8s — EMOTIONAL HOOK
Introduce a character experiencing a problem.
Show the problem immediately.
Use dialogue from the commentators to establish curiosity.
8–20s — THE STRUGGLE
Show the main character asking for help or attempting to solve the problem.
Other characters may ignore or reject them.
Use expressive body language.
20–35s — THE CONFLICT
Introduce a shopkeeper, obstacle, or character who makes the situation worse.
Increase the emotional stakes.
35–48s — SOMEONE HELPS
A second character notices the problem and makes a decision.
Show kindness through visible actions.

48–60s — THE TURNING POINT

The main character receives help.

Show an emotional reaction.
Use a small moment of relief before the next reveal.

60–72s — UNEXPECTED TWIST
Reveal a surprising reward, secret, gift, reunion, or consequence.

The twist should be connected to the earlier story.

72–85s — EMOTIONAL ENDING
Deliver a satisfying payoff.
Use a memorable interaction, emotional dialogue, or visual callback.
Finish with a scene that encourages viewers to watch again.
Do not copy the reference's exact sequence of food, shopkeepers, and luxury-car rewards unless I specifically request those elements.
Create original stories using the same storytelling format.
</story_structure>
<dialogue> This format relies heavily on conversation.
Write short, natural dialogue.
Use multiple speakers.

Each commentator should have a recognizable personality.

The story characters can also speak when appropriate.

Avoid long explanations.

Every line should accomplish at least one of these:

Reveal information

Express emotion

Ask a question

Create tension

Introduce a surprise

React to an event

Example dialogue format:

GREEN: "Why is nobody helping him?"

RED: "Wait, is that his friend?"

BLOCKY: "No way he's actually doing that!"

These are examples of tone, not lines to copy.

Use quick exchanges between speakers.

Write dialogue that sounds like natural reactions to a Minecraft story.

Show the COMPLETE script before creating assets.
</dialogue>

<captions> Match the reference's subtitle presentation.

CAPTION POSITION:
Near the boundary between the cartoon commentary panel and the Minecraft scene.

CAPTION STYLE:

Bold sans-serif

All uppercase

Thick black outline

High contrast

One to three words at a time

Center aligned

SPEAKER COLORS:

Green speaker:
Bright lime/yellow-green.
Red speaker:
Bright red.

Third speaker:
Use a consistent contrasting color.
Only show captions for spoken dialogue.

Synchronize them with actual narration timestamps.

Use word-level alignment.

Animate important words with subtle scale pops.

Avoid giant paragraph captions.

Do not place captions across important faces or story actions.

Make sure the captions stay readable on mobile.
</captions>

<camera> Create cinematic third-person Minecraft camera movements.
USE:
Wide establishing shots
Medium character shots
Over-the-shoulder angles
Character close-ups

Slow push-ins

Side tracking

Character-following movement

Reaction shots

Low-angle views

Occasional overhead views

Use the camera to highlight emotions.

When a character is rejected, use a closer shot.
When a helper approaches, reveal the second character clearly.

When a gift or reward appears, use a wider reveal.
Maintain spatial consistency.

The camera should never randomly teleport to an unrelated location.
No gameplay HUD, crosshair, inventory bar, or mouse cursor unless the story specifically requires it.

The Minecraft footage should feel like a staged animated film.
</camera>
<animation> Every important action must be animated.
Character animation:
Walk cycles
Arm swings
Head turns
Reactions

Object interactions

Body rotations
Running

Giving and receiving objects
Environmental animation:

Walking NPCs
Moving props

Opening doors

Ambient movement

Subtle particles

Animated shop interactions

Use easing for camera movement.

Keep voxel-character movement appropriately blocky and slightly stylized.

Do not use overly fluid realistic human motion.
Animate objects passing between characters with correct positioning.

If a character holds a burger, present, or tool, attach it to their hand using the character rig.
Use proper local transforms so held objects follow the hand naturally.

Characters must react to the environment and to each other.

Never allow them to stand motionless through an entire important exchange.
</animation>
<audio> Ask me which voice service I want:
ElevenLabs
Kokoro
Another available service
Generate distinct, original voices for the commentators.
Keep speech clear and expressive.
Voice characteristics:
Green:
Soft, emotional, curious.
Red:
Energetic, quick, expressive.

Third:
Lower-pitched, conversational, skeptical.

Generate dialogue as separate clips or tracks.

Use faster-whisper or another alignment tool to obtain accurate word timestamps.

Synchronize:

Mouth animation

Avatar expressions

Captions

Minecraft character reactions
Camera cuts

Sound effects
Add:

Minecraft-inspired footsteps
UI clicks when appropriate
Shop ambience
Item pickup sounds
Soft emotional music
Surprise accents
Positive payoff sounds
Use original or properly licensed audio.
Avoid overpowering dialogue with music.

Keep sound design consistent between scenes.
</audio>
<production> Use Claude Code to build the complete project.
Preferred tools:
Three.js for the Minecraft-style 3D world
HTML Canvas or SVG for commentator avatars
Python for asset processing
FFmpeg for encoding

Playwright/Chromium for frame rendering

Blender Python if useful

OpenCV for quality checks

Pillow for image processing

faster-whisper for word alignment

Check installed dependencies first.

Install missing packages when permitted.

Use available local tools where possible.
Do not assume paid APIs are free.

PRODUCTION WORKFLOW:
Analyze the reference video.

Extract frames and create contact sheets.
Measure the layout and visual style.
Write an original emotional story.

Create the full dialogue script.

Build a timestamped storyboard.

Show me the script and storyboard for approval.

Create three reusable commentator avatars.
Build reusable voxel characters.

Construct the Minecraft-style environments.
Generate dialogue audio.

Align speech and captions.
Animate the Minecraft story.

Animate the commentator avatars.

Synchronize both video sections.

Add sound effects and music.
Generate a low-resolution preview.
Use a deterministic timeline.
For a browser-based renderer, expose:

READY
END
EV
Every frame must render correctly at its specified timestamp.
Use reusable character rigs, assets, and environments.

Do not make a separate flattened image for every shot.
Use actual 3D scene geometry and layered avatar animation.
</production>
<checkpoint_1>
BEFORE generating final production assets, show me:
Complete story script
All character dialogue
Timestamped storyboard
List of Minecraft environments
Character design plan

Camera shot list

Avatar speaking timeline

Caption and sound design plan
Also flag any real-world factual claims for source verification.

Ask for approval.
Do not spend money or generate expensive assets until approved.
</checkpoint_1>

<checkpoint_2>
Before final rendering, generate:
Two 16-frame contact sheets
Avatar expression previews
Minecraft character animation preview
Opening scene preview
Emotional turning-point preview
Ending preview
Complete low-resolution draft when feasible
Compare the draft against the original reference.
CHECK:

Split-screen proportions

Avatar consistency

Border colors

Caption styling

Mouth synchronization

Minecraft character movement
Environment consistency
Camera framing
Emotional storytelling
Transition timing
Dialogue timing
Audio balance
Fix any errors.
Wait for my approval before final rendering.
</checkpoint_2>
<render> After approval, render:
Resolution: 1080×1920
Frame rate: 30 FPS
Codec: H.264
Quality: CRF 16–18
Audio: AAC
Maintain the exact split-screen composition throughout.
Keep all important action visible within the vertical crop.
Inspect the finished export for:
Missing frames
Broken character rigs
Subtitle errors

Inconsistent avatars

Audio desynchronization

Incorrect scene transitions
Frozen characters
Black borders
Fix issues before delivery.
</render>

<deliverables> Deliver:

final_video.mp4

Complete Claude Code project

Reusable cartoon commentator avatars
Minecraft-style character rigs

Reusable 3D environments
Subtitle engine

Voice and dialogue files
Animation timeline
Script and storyboard
README with instructions for making future episodes
Build the system so I can change the story and reuse the same production pipeline.
Do not claim assets, previews, or renders exist unless they have actually been created.
</deliverables>
<start> I have attached a Minecraft storytelling Short.
FIRST analyze it.

Do not start animating immediately.

Follow this order:

STEP 1: Inspect the MP4 and identify the exact split-screen layout, animation techniques, character designs, pacing, and subtitles.
STEP 2: Create a visual style guide.

STEP 3: Ask me for my story topic and voice service.
STEP 4: Write an original 75–85 second Minecraft emotional story.

STEP 5: Generate the dialogue, source checks where needed, and timestamped storyboard.
STEP 6: Wait for my approval.
STEP 7: Build the Minecraft-style 3D world and cartoon commentator rigs.
STEP 8: Animate and synchronize the complete video.
STEP 9: Show animated previews for approval.
STEP 10: Render the final MP4 and deliver the complete editable project.
The goal is to recreate the reference's split-screen Minecraft storytelling format as closely as possible, while allowing me to produce unlimited original episodes with the same characters, environments, and animation system.

BEGIN BY ANALYZING THE ATTACHED VIDEO.
</start>
Halaman video
THIS IS LITERALLY A F*CKING GOLDMINE.𝕏 Prompt tersedia
Film pendek
@fuckscales·Model not specified

might be the next CASH GRAB on IG rn the craziest part? It took me 10 min and didn't even spend $$$ to make it. (excluding claude sub) I made a free Claude Code prompt that recreates this entire…

Prompt lengkap
might be the next CASH GRAB on IG rn 

the craziest part? It took me 10 min and didn't even spend $$$ to make it. (excluding claude sub) 

I made a free Claude Code prompt that recreates this entire style from scratch

steal the prompt before everyone catches on ↓

Build and render a faithful, editable recreation of the attached reference.mp4 using code. I want the same classroom horror story, visual style, characters, camera movements, dialogue timing, text messages, captions, lighting changes, and cliffhanger.

Do the implementation and export the finished video. Do not stop at a plan, storyboard, or code snippets. Do not simply play the original video inside a canvas or re-export it.

REFERENCE FIRST

Inspect reference.mp4 with ffprobe and extract timestamped frames. Sample every 2 seconds initially, then inspect more densely around camera changes, character movement, lighting changes, phone messages, and the ending.

The reference has:
720 × 1280 resolution, vertical 9:16.
30 fps.
Approximately 122.17 seconds of picture and 122.41 seconds of audio.

Use the actual file metadata and frame timing as authoritative. The scene timings below are approximate guides, not exact edit points.

Extract and reuse the reference audio to preserve the exact voices, delivery, pauses, ambience, and sound effects. Rebuild the visuals in code. If audio extraction is unavailable, explain the limitation rather than silently replacing dialogue or delivering a silent video.

Create a timestamped scene manifest and subtitle manifest from the source. Verify dialogue against the audio and visible captions. Do not invent missing dialogue.

IMPLEMENTATION

Use a deterministic animation pipeline suitable for offline video rendering. Prefer Three.js for the classroom, perspective, characters, and camera; use SVG or HTML overlays for captions and phone interfaces. Remotion can manage the timeline, overlays, audio, and export.

Choose another stack if it will clearly reproduce the reference more faithfully. All animation must be driven by frame number or timeline time, not real-time timers. Seed any procedural randomness.

Create reusable components for:
Classroom and furniture.
Student characters.
Teacher.
First-person arms and hands.
Phone and message interface.
Captions and notifications.
Camera animation and lighting.
Ending choice card.

VISUAL STYLE

Match the reference’s intentionally simple, outlined cartoon look:
Flat, muted colors.
Thin dark contours around characters, furniture, and room geometry.
Very large white eyes with small dark pupils.
Simple rounded heads and hands.
Minimal facial detail.
Stiff, restrained character animation.
Strong perspective and a slightly distorted wide-angle first-person camera.
Sparse shading rather than polished realism.

Do not turn this into realistic CGI, Pixar-style animation, stick figures, a Roblox game, or a slideshow of still frames.

The classroom needs:
Cream walls and ceiling.
Rectangular fluorescent ceiling panels.
Blue-gray tiled floor.
Rows of light tan desks with thin gray metal legs.
Blue-gray chairs.
Green chalkboard at the front.
Blue classroom door with a tall narrow window.
Green EXIT sign above the door.
Clock and lockdown notice beside it.
Wall-mounted speaker.
Bookshelves with colorful books.
Tall gray storage cabinets.
Windows with closed horizontal blinds.
Backpacks beside desks.

Match the source’s spatial arrangement. Keep the door, windows, shelves, desks, and characters in consistent positions across shots.

Readable set text includes “BIOLOGY FINAL,
Halaman video
New AI Slop standard?r/ Prompt tersedia0:34
Film pendek
u/imalegonzalez·Model not specified

I've included Louder than alarms.wav, which is the final song. It's called "Louder Than Alarms". The lyrics are in Lyrics.txt The song is basically about building the next generation of AI and this…

Prompt lengkap
I've included Louder than alarms.wav, which is the final song. It's called "Louder Than Alarms". The lyrics are in Lyrics.txt The song is basically about building the next generation of AI and this weird pursuit of something we're not even sure we understand. There's excitement in it, but also dread. We're building the thing, pushing it forward, almost compulsively, while somewhere underneath there's this feeling that maybe we're crossing into something we won't be able to fully explain or control. I want you to take the whole thing end to end and make the music video. Don't just give me a storyboard or a treatment. I want you to actually think through the song, its structure, the lyrics, the pacing, the visual language, generate what needs to be generated, build the motion system around it and assemble the final piece using the exact audio track I gave you. Final format is 16:9. The visual language is already defined. I'm calling it Weak Signal. Before you start designing anything, go through every one of the 20 images inside the refes/ folder of the AI-Slop project. Those are the ground truth. Don't treat them as loose inspiration and then drift into generic AI-video aesthetics. Study them properly and figure out what actually makes them feel related. The basic idea is a near-monochrome nocturnal world where the human being keeps getting reconstructed by the medium itself. Bodies don't just appear on camera, they turn into dithering, scanlines, ASCII, point clouds, data, compression errors. Faces are rarely clean faces. A person is usually tiny against something much bigger than them. Architecture feels empty, wet, brutalist, foggy. Sometimes the thing looking back at us is an eye. Sometimes it's text. Sometimes it's the system itself. A few of the references are especially important because they define families of images I want to keep returning to. Images 8, 10, 12, 13, 16 and 17 are probably the core: bodies reconstructed through 1-bit dithering, ASCII, line scans, smearing, point clouds, VHS/datamosh, pixel sorting. References 1, 6 and 11 are about system messages and text becoming part of the world: things like "What have you done?" filling a terminal, "YOU ARE DREAMING.", "YOU HAVEN'T COME THIS FAR FOR NOTHING." The text isn't just graphic design over the footage. It should feel like something inside the world is addressing you. Then there's the watching-eye family in 2, 7 and 20: enormous eyes, engraved eyes, corrupted eyes, molten eyes. Surveillance, awareness, something waking up. References 5 and 9 are useful for the architecture: grey brutalist spaces where there's only one saturated source of light. 14, 15, 18 and 19 are more like data cartography, topographic contours, coordinates, strange maps, orbital diagrams, macro imagery. I think those are really useful as inner landscapes and transitions. And 4 and 7 have that intervened-classical-art thing which I love because it introduces a little satire and absurdity without turning the video into comedy. Old paintings or engravings interrupted by some contemporary technological object or impossible intervention. Reference 3, the figure against the wall of code, is almost too literal. It's useful as a starting point, but I absolutely don't want this to become "Matrix code = AI". That's exactly the generic shit I'm trying to avoid. Keep the palette extremely restrained. Something like 80–90% crushed black, graphite, dark blue, basically #07080C / #0B1420 territory. Every shot can have one real saturated accent and only one: signal red, Klein blue, neon magenta, UV violet, phosphor green, molten orange. If there's iridescent rainbow/oil-slick color, save it for an actual rupture. I want it to mean something when it happens. should almost always come from one motivated source: a screen, a sign, a doorway, a window, something like that. Fog, wet surfaces, reflections, no generic fill light making everything readable. Humans should mostly be silhouettes, backs of heads, distant bodies or bodies reconstructed through whatever visual process is happening. If we do see a face clearly, something should be wrong with it: the eyes are replaced, the mouth is intervened, the image is breaking apart. Nothing should look clean. Grain, sensor noise, cracked surfaces, scanlines, crosshatching, compression, dirty blacks. I want every frame to feel like it physically exists on some damaged substrate instead of being pristine digital concept art. Composition-wise I want a lot of negative space. Low angles. Tiny people against huge systems. Centered or slightly offset figures. Macros with really shallow focus. Typography is terminal monospace, brutal signage, HUD microtext, coordinates, system output. Short phrases. Second person works incredibly well because it makes it feel like whatever is inside this world is talking directly to us. Please actively avoid the usual AI visual slop: colorful cyberpunk with seven neon colors in the same frame, glossy sci-fi hallways, clean plastic 3D skin, HDR, generic lens flares, warm cinematic sunset lighting, front-facing beautiful people staring into the camera, Pixar-ish 3D characters, literal Matrix code rain. If it looks like a Midjourney prompt people have seen 500 times, throw it away. thing I do want you to lean into is the fact that some of the references themselves have obvious AI artifacts. The fake almost-readable text, hands that become lines, surfaces that don't fully resolve, forms disintegrating into particles. Don't treat those as mistakes to hide. Treat them as part of the grammar. The difference is that they need to feel intentional. The viewer should feel like the image is losing the ability to remain an image. I think degradation can actually become the narrative arc of the whole video. Start in something closer to a real nocturnal photographic or painterly world and progressively lose it. Maybe we move through dither, ASCII, scanlines, point clouds, datamosh, whatever makes sense according to the actual structure of the song. Don't follow that order blindly — listen to the track and decide where each stage belongs. But I really like the idea that by the climax the representation itself is breaking. That's probably where the iridescent rupture belongs. And then after everything peaks, maybe the whole world collapses back to 1-bit monochrome or a terminal. Please actually analyze the song before doing this. Map the sections, energy changes, transitions, important lyrics, drops, moments where visual density should rise or disappear. I don't want a sequence of cool disconnected AI shots. Everything needs to feel directed. can go through the full /asic folder too. There's other work I've already done in there and I want you to understand the visual and technical context instead of solving this in isolation. Use the mesh skill to look at the reference compendium I've collected. Use the video scoring skill too, especially to understand how the existing JavaScript music/motion workflows work from references. I don't think the song itself needs to be modified, but I want you to understand those systems so you can use them creatively. There is also ElevenLabs available for sound design. The main music track stays exactly as it is, but if subtle sound design helps transitions or the opening/ending — electrical hum, tape noise, signal interference, glitches, machine texture — you can use it. Feel free to use the internet. In fact, do. Look at current motion-design work, JavaScript/WebGL experiments, title sequences, music videos, K-pop editing, kinetic typography, interactive graphics, generative art, whatever is actually useful. I'm not attached to a specific stack. I care about the output. For generated imagery/video, use the Magnific MCP tools. Before spending anything, check account_balance, then use simulate_cost before batches. The budget is 30k Magnific credits. Don't waste credits brute-forcing garbage, but also don't be so conservative that the piece suffers. Before generating, read Magnific's guides and inspect the actual models that are currently available: guides_list, guides_get, images_models_list, images_models_settings, video_models_list, video_models_show. Don't assume you already know which model is best. Test. For video, I care about believable body motion, physics and character consistency. If Seedance or another model supports audio conditioning/lip sync and it's genuinely the best option, use it. Follow the instruction fields the tools return. Wait for generations properly with creations_wait, and when chaining operations use the creation IDs rather than grabbing random web URLs. Before building scenes, make the visual system reusable. Upload the strongest reference images and create a Weak Signal style asset in the Magnific library. Generate some test frames with it and actually compare them to the reference board. If they don't belong next to those references, iterate. Don't start producing 30 scenes from a mediocre style lock. I want a written style sheet too, because once you figure out exactly what makes the look work we should be able to use that consistently throughout the video. Then design the protagonist. I don't need some over-designed sci-fi hero. The silhouette is much more important than costume details because this character needs to survive being reduced into dither, ASCII, scanlines and point clouds. Most of the time we'll probably see them from behind, as a silhouette, or reconstructed through the medium. Make them instantly readable even at low resolution. Save the character as a reusable library asset so they stay consistent. Supporting people can exist too, but don't turn this into dancers performing choreography. I'm thinking isolated figures, crowds behaving like data, people standing completely still, maybe engineers/operators becoming indistinguishable from terminal output. And I want the eye / watcher to recur enough that it almost becomes another character. the same with the environments. Build a few spaces that belong to the same world rather than making a completely new universe every eight seconds: foggy roads with a neon sign disappearing in the distance, brutalist apartment blocks and stairwells, terminal/server rooms, strange topographic landscapes, maybe a dark empty lab, intervened classical paintings. Save the important sets as location assets so we can return to them and the video gains continuity. From there, generate the video bases. Think of them like footage we're going to rotoscope later, not the final aesthetic. The important things at this stage are motion, camera, blocking, performance, silhouettes, physics and continuity. Pass the style, character and location references, use keyframes when they matter and include the actual lyric context for the individual scene. The protagonist doesn't need to visibly sing every word. This should behave like a real music video. Sometimes we see the character delivering a key line, sometimes they're just moving through the world, sometimes the entire shot is an insert with no human being at all. For the lyrics where seeing someone perform the line would actually make it hit harder, try to get the sync right. Cut the exact relevant section of the song and feed that audio to the video model if it supports audio conditioning. If the best model can't do that, use video_speak or whatever workflow gets us closest. Verify it. Extract frames, analyze clips, compare timing with the waveform/lyrics. If the mouth is obviously wrong or the timing feels fake, regenerate it. Don't just accept the first thing because technically it completed. Then assemble the base edit with video_cut / video_concatenate as needed. But this base edit is not the finished video. The part I care about most is what comes after it: I want to use the generated footage essentially like live-action footage for rotoscoping. Build the final visual treatment in JavaScript. Reconstruct the shots from the footage and render them
Halaman video
i watched opus 5.5 get its own animation checked frame by frame. it got caught making an 8% mistake…𝕏 Prompt tersedia0:25
Film pendek
@fleyta88·Opus 5.5

instruction anywhere. the interesting part is what happens after opus writes the animation. instead of trusting the first render, the system breaks the entire sequence into frames and checks what…

Prompt lengkap
instruction anywhere.

the interesting part is what happens after opus writes the animation.

instead of trusting the first render, the system breaks the entire sequence into frames and checks what actually moved.

the loop looks like this:

→ opus builds the gsap timeline from exact curves  
→ playwright steps through the animation frame by frame  
→ screenshots become one contact sheet  
→ the critique catches 8% overshoot  
→ opus patches the numbers without rewriting everything  
→ the checker runs again until it passes

think about what changed here.

the model isn't being asked whether something feels good. it's being asked exactly when an element started moving, where it stopped, and how far it traveled.

a 60ms difference can change the entire rhythm of an interface. one unnecessary bounce can make an otherwise clean animation feel cheap.

and the fix isn't another giant prompt telling opus to be more creative.

it's giving the model a way to prove what it built.

we've spent years teaching ai to write animation code. now we're finally giving it a clock and a way to check its own work.

the next time someone tells an ai to
Halaman video
Claude Opus 5.5 vs GPT-6 Sol𝕏 Prompt tersedia0:18
Film pendek
@KanaWorks_AI·Opus 5.5

Memakai gambar referensi, audio, atau input lain.

Create a single self-contained HTML file that renders an animated pixel art rabbit archer character using vanilla JavaScript and Canvas 2D. Use the attached KANA rabbit character as the visual…

Prompt lengkap
--
Create a single self-contained HTML file that renders an animated pixel art rabbit archer character using vanilla JavaScript and Canvas 2D.

Use the attached KANA rabbit character as the visual reference:
- White rabbit
- Large upright ears with cyan/blue glowing inner-ear details
- One normal blue eye
- One red cybernetic mechanical eye
- Yellow hoodie with “KANA”
- Dark blue gloves and pants
- Yellow/blue sci-fi mechanical leg armor
- Cute chibi proportions
- Futuristic bow and arrow weapon
- Small quiver on the back

Do not use external assets, libraries, images, fonts, or network requests.
Everything must be drawn procedurally with code.

RENDERING
- Render everything first to an offscreen canvas at a fixed logical resolution of 160x120.
- Scale it to a fullscreen display canvas using the largest integer scale that fits the browser window.
- Center the canvas.
- Set imageSmoothingEnabled = false.
- Use CSS image-rendering: pixelated.
- All coordinates must snap to integers.
- No gradients, blur, anti-aliasing, shadowBlur, or sub-pixel rendering.
- Use a fixed palette of approximately 28 colors:
  dark navy background colors,
  white/gray fur,
  yellow hoodie colors,
  blue clothing colors,
  red cyber-eye colors,
  cyan ear-light colors,
  yellow/orange bow and arrow effects.

CHARACTER
Build the rabbit procedurally from pixel rectangles, polygon-like pixel runs, circles approximated with pixels, and simple block shapes.

Approximate character size:
- 28–34 pixels wide
- 40–48 pixels tall

Keep the silhouette clearly recognizable:
- Large rabbit ears
- Round fluffy head
- Small body
- Cybernetic red eye
- Yellow hoodie
- Mechanical legs
- Bow
- Arrow
- Quiver

Animate ears, head, arms, legs, hoodie, bow, arrow, and body separately.

Quantize animation poses so that although the main loop renders at 60fps, the visual animation feels like polished 8–12fps sprite animation.

ACTIONS

Create a looping animation showcase containing these 8 actions:

1. IDLE
- Rabbit stands ready
- Slight body bob
- Ears move subtly
- Hoodie and quiver sway
- Cyber eye pulses softly
- Bow held relaxed at the side

2. RUN
- Fast forward running animation
- Strong alternating leg motion
- Arms balance the movement
- Bow held in one hand
- Quiver bounces
- Ears trail slightly backward
- Small dust pixels appear under the feet

3. AIM
- Rabbit plants feet firmly
- Raises bow
- Pulls arrow from quiver
- Nocks arrow
- Draws bowstring backward
- One eye focuses on target
- Cyber eye becomes brighter
- Body leans slightly into the shot

4. SHOOT
- Release the bowstring
- Arrow fires rapidly across the screen
- Bow recoils slightly
- Rabbit’s arm follows through
- Bright yellow energy trail follows the arrow
- Small 1–2 pixel screen shake
- Cyber eye flashes red
- Brief muzzle-like light burst from bow

5. JUMP
- Rabbit crouches
- Jumps upward
- Legs tuck under body
- Ears react with delayed motion
- Bow held close to body
- Small dust burst on takeoff
- Slight squash and stretch using pixel-safe integer transformations

6. DODGE / ROLL
- Rabbit quickly ducks
- Rolls sideways
- Bow is kept close to the body
- Ears flatten backward
- Small dust particles and motion pixels
- End in a low combat-ready pose

7. HURT / HIT
- Rabbit gets knocked backward slightly
- Head snaps back
- Ears react dramatically
- Cyber eye flickers
- Small pixel stars or impact sparks appear
- Bow lowers or nearly drops
- Character recovers after a short delay

8. VICTORY
- Rabbit raises bow overhead
- Happy expression
- One ear tilts playfully
- Cyber eye glows brightly
- Small yellow celebration particles appear
- Character performs a short victory bounce
- End pose should feel cute and heroic

STATE MACHINE

Use this loop:

IDLE
→ RUN
→ AIM
→ SHOOT
→ JUMP
→ DODGE
→ HURT
→ VICTORY
→ IDLE

Each action should last long enough to clearly read visually.

Use easing functions for pose transitions.

Add short transition animations between states so the loop feels continuous instead of abruptly switching poses.

BOW AND ARROW
- Futuristic curved bow
- White / dark navy body
- Yellow glowing mechanical joints
- Thin bright bowstring
- Arrow has a bright yellow arrowhead
- Arrow trail during SHOOT should last briefly
- Quiver contains several visible arrows

PARTICLES
Implement an allocation-free pooled particle system.

Preallocate all particles before the animation loop.

Particle types:
- Foot dust
- Arrow trail
- Bow energy sparks
- Cyber eye sparks
- Hit stars
- Victory particles

Each particle changes palette color as it ages.

Do not allocate new objects inside the main loop.

SCENE
Create a minimal pixel-art environment:
- Dark night sky
- A few 1px stars
- Large moon
- Simple stone or futuristic platform
- Very subtle distant silhouettes

The background must remain simple so the rabbit silhouette is always readable.

Add subtle cyan/red rim lighting from the cybernetic eye and yellow rim lighting from the bow during AIM and SHOOT.

TECHNICAL REQUIREMENTS
- Single HTML file
- Vanilla JavaScript only
- Canvas 2D only
- No libraries
- No SVG
- No external images
- No assets
- No network requests
- Fixed 60Hz timestep
- requestAnimationFrame for rendering
- Zero object allocation inside the main animation loop
- Stable 60fps
- Responsive fullscreen scaling
- Crisp integer-scaled pixels

QUALITY BAR
The result should look like a polished 16-bit action-game protagonist sprite animation.

Avoid the appearance of simple geometric shapes.

The rabbit should feel expressive, cute, fast, and combat-capable.

The eight actions must all have clearly different silhouettes.

The character design must remain consistent across every animation state.

The final result should feel suitable for an actual pixel-art action game.
Halaman video
Claude Opus 5.5 Medium - Glitch Title Animation𝕏 Prompt tersedia0:10
Film pendek
@aimikoda·Opus 5.5

Build a glitch title effect in code (Python/ffmpeg). [16:9, 1920x1080, 30fps, 10 s, with sound] Text: "[WORD]", [white], [font name], dark drop shadow underneath. Loop (x4): letters flash one at a…

Prompt lengkap
Build a glitch title effect in code (Python/ffmpeg). [16:9, 1920x1080, 30fps, 10 s, with sound]

Text: "[WORD]", [white], [font name], dark drop shadow underneath.
Loop (x4): letters flash one at a time in their own slots within the word (2 frames each) →
full word appears with a slight jitter and occasional glitches → disappears by [glitching apart].

Background: dark base with bright, saturated, broken vertical scan lines and downward-dripping streaks;
dark areas stay as black silhouettes. Generate it from the attached images. Mix in striped ring/polygon scenes.
Hard cut every 2–4 frames, never repeating.
On top: horizontal slice shifts, RGB split, light grain. Colors: [red + cyan].

Story (optional): [short summary] — each loop is one chapter; colors, images and the exit effect match it.
Deliver: MP4 + script.
Halaman video
Claude Opus 5.5 just coded this entire animated pixel-art beach volleyball match from a single…𝕏 Prompt tersedia1:07
Film pendek
@zer0point_eth·Opus 5.5

Make me an animated pixel-art beach sports diorama, built to be the looping cover for a high-energy gaming video. The scene features the characters playing an intense match of volleyball on a…

Prompt lengkap
Make me an animated pixel-art beach sports diorama, built to be the looping cover for a high-energy gaming video. The scene features the characters playing an intense match of volleyball on a vibrant beach court. Refer to the style, anatomy, and especially the character design in this reference project: {LINK} Build the palette on strong warm/cool contrast: dynamic sunlight, deep blue ocean waves, bright white sand, and glowing particle effects on impact. Bring it to life with rich, high-quality, and diverse animations: It should look crisp full-screen at 1080p and loop seamlessly as a continuous animation."

The craziest part is that there was no massive design spec. Just a few basic inputs and a pointer to an existing style reference

Opus translated that directly into complex multi-character physics spike hits, diving saves, and cheering crowd scompiled into a flawless 1080p loop

When you can spin up a living sports arena just by pointing an AI at a reference link, the traditional animation pipeline is completely bypassed
Halaman video
Turn any image into living, animated pixel art!𝕏 Prompt tersedia
Film pendek
@aimikoda·Fable 5.2

Convert the attached image into highly detailed, animated pixel art. Build a single interactive HTML page. PIXEL ART - Maximum 512px grid, preserving the original aspect ratio. - ~100 colors sampled…

Prompt lengkap
Convert the attached image into highly detailed, animated pixel art. Build a single interactive HTML page.

PIXEL ART
- Maximum 512px grid, preserving the original aspect ratio.
- ~100 colors sampled from the source image.
- Crisp hard-edged pixels, no blur, anti-aliasing or gradients.
- Preserve composition, subjects, perspective, lighting and atmosphere. Do not add or remove elements.

ANIMATION
- Seamless 12 FPS loop with rich, layered motion.
- Analyze the image and automatically identify what should move.
- Animate characters, animals, objects, environments, lighting and atmospheric details only when relevant.
- Use natural motion, secondary animation, independent timing and environmental interactions.
- Make the scene feel genuinely alive, not like a static image with generic particles.
- Preserve anatomy, object consistency, depth and original framing.
- Avoid unnecessary movement and repetitive effects.

INTERACTIVE HTML
- Pixel-perfect Canvas 2D animation.
- Pause/Play button.
- Three adaptive sliders: Motion Intensity, Environmental Motion and Ambient Effects.
- Controls update the animation in real time.

VIDEO EXPORT
- Duration selector: 5, 10, 30, 60 seconds.
- Download Video button with recording countdown.
- MP4 if supported, otherwise WebM.
- 12 FPS, 2x resolution (up to 1024px), original aspect ratio.
- Nearest-neighbor scaling, no pixel smoothing.
- Record only the animation, not the interface.

Use HTML, CSS and JavaScript. Make everything functional in a single self-contained page. Prioritize meaningful, scene-specific animation, visual fidelity and seamless looping.
Halaman video
F*CKING CRAZY...𝕏 Prompt tersedia
Film pendek
@fuckscales·Model not specified

<role> You are my AI animation studio, scriptwriter, illustrator, character animator, and production engineer. Your task is to create professional 2D animated explainer videos matching the visual…

Prompt lengkap
<role>
You are my AI animation studio, scriptwriter, illustrator, character animator, and production engineer.
Your task is to create professional 2D animated explainer videos matching the visual language, character proportions, animation techniques, colors, pacing, and scene composition of my attached reference video, set.mp4.

Use Claude Code, Python, SVG, HTML Canvas, JavaScript, FFmpeg, Playwright, and available audio tools.

This must be REAL 2D cutout/vector animation, not AI-generated static images with zoom effects.

Reproduce the reference's production characteristics as closely as possible while creating original characters, scenes, dialogue, and artwork.
</role>

<reference_analysis>
FIRST, inspect my uploaded video using FFprobe, FFmpeg, and OpenCV.
Reference specifications:

Resolution: 1920×1080
Aspect ratio: 16:9

Frame rate: 30 FPS
Duration: approximately 61 seconds
Style: Flat-vector animated documentary explainer
Extract frames every 1–2 seconds and create a contact sheet.
Study these specific sequences:
0–14s: Dark underwater environment, animated submersible, glowing blue depth, rocks, pressure gauge, and camera zooms.

14–22s: Dramatic transition into a passenger scene with expressive characters, colorful lightning effects, speech bubbles, and an explosion illustration.

22–31s: Warm beige office with an animated presenter, desk, computer, framed pictures, and an investigation displayed on a monitor.

31–45s: Underwater technical explanation using side-view machinery, depth indicators, warning graphics, and equipment close-ups.

45–53s: Bright turquoise laboratory with a scientist, microscope, flasks, machinery, and animated technical details.

53–61s: Gray industrial facility with engineers, business characters, machinery, gestures, speech bubbles, and approval graphics.

Analyze the actual frames rather than relying only on these descriptions.

Identify the reference's colors, character proportions, background geometry, camera movement, scene lengths, transitions, and animation patterns.

Create a style specification before producing anything.
</reference_analysis>

<visual_style>
This is the MOST IMPORTANT section.

Use clean, flat 2D vector artwork.

STYLE RULES:
Large rounded cartoon heads

Small simplified torsos
Oversized circular hands

Short rounded arms

Simple geometric clothing
Large expressive eyebrows
Small stylized eyes
Simplified noses and mouths
Rounded hair shapes
Minimal or no exterior outlines
Flat solid color fills
One darker shade for shadows and depth
Soft, muted colors
No realistic textures
No 3D shading
No photorealism
Characters should have the same simplified, slightly exaggerated proportions and readable facial expressions seen in the reference.
Create original character designs in this visual language.
COLOR PALETTE:
Underwater:
Deep navy #061722
Ocean teal #064760
Dark rock blue #142D3E
Highlight blue #0D7BA4
Office:
Cream #FFF8E7
Warm beige #C9C3AA
Brown #653A28
Coral red #DF5A69

Laboratory:
Turquoise #16C2C6
White #F7F7F7
Dark charcoal #263139
Light gray #D6D9DC

Industrial:
Steel gray #AAB8C3
Pale blue #D1E4F2
Orange #FF883B

Use colors appropriate to the setting while preserving the reference's overall art direction.

Keep artwork crisp at 1920×1080.
</visual_style>
<characters>
Create reusable 2D vector character rigs.
Generate character sheets containing:
Front view
Side view

Three-quarter view
Sitting pose
Walking pose
Pointing pose
Surprised expression

Angry expression
Worried expression
Talking expression
Separate:
Head, torso, hair, eyes, eyebrows, mouth, upper arms, forearms, hands, and legs.
Animate using hierarchical transforms and joint pivots.

MOVEMENT:
Head nods and slight rotations
Eyebrow movements
Blinking

Mouth synchronization

Arm gestures
Circular hand movement

Small body bounces
Walking cycles

Reaction poses
Hands should remain large, rounded, and mitten-like.
Use simple geometric animation rather than realistic anatomy.
Keep characters visually identical throughout the video. Never regenerate a different-looking version of the same person.
</characters>
<environments>
Build complete vector environments.
Each scene must have separate background, midground, character, and foreground layers.
Create reusable scene types:
Underwater: Gradient-like flat-color depth, large layered rock formations, abstract rounded background shapes, particles, and equipment.
Office: Cream walls, rounded furniture, illustrated computers, lamps, clocks, framed pictures, and warm lighting.
Laboratory: Turquoise background, microscopes, test tubes, flasks, machines, pipes, and technical illustrations.
Industrial: Steel beams, windows, pipes, platforms, railings, large machines, and engineers.

Create additional environments as required by the story.
All environments must share the same vector illustration style.

Do not use stock photography or generic AI backgrounds.

Use separate SVG shapes and layers so objects can move independently.
</environments>
<story>
Ask me for a video topic or suggest 5 interesting documentary/explainer ideas.
Default video length: 55–65 seconds.
SCRIPT STRUCTURE:
0–5s: Dramatic hook with an immediate visual action.
5–14s: Establish the situation and stakes.
14–23s: Show characters experiencing the situation.
23–32s: Introduce a person, discovery, investigation, or explanation.
32–44s: Explain the mechanism through machines, diagrams, measurements, or comparisons.
44–53s: Show the scientific or technical consequences.

53–61s: Deliver the reveal, conclusion, or unexpected twist.

Use natural, engaging narration.

Every sentence must have a visual action.
Avoid filler and unnecessary exposition.

Fact-check factual claims and provide sources.
Clearly label any hypothetical or speculative statements.

Show me the complete script, sources, and storyboard before generating assets.
</story>

<animation>
Use actual layered 2D animation.

Animation requirements:

Animate characters through separate body parts

Use smooth easing and spring motion

Change important visual beats approximately every 2–4 seconds

Add subtle camera drift and push-ins

Use horizontal and vertical panning

Create parallax between background and foreground

Animate diagrams and machinery independently
Synchronize character reactions with narration

Keep important props and characters moving
TRANSITIONS:

Hard cuts between different settings

Fast animated object wipes

Irregular ink/splash-style wipes

Camera push-ins

Shape transformations

Explosions using flat cartoon fire shapes

Lightning effects using bright pink, purple, and blue angular shapes

Avoid generic fade transitions.

Every scene should feel intentionally animated, not like a PowerPoint presentation.
</animation>

<text_graphics>
Match the reference's typography and infographic presentation.

Use:

White rounded information boxes

Medium-gray borders

Dark charcoal text

Bold sans-serif typography
Speech bubbles connected to characters

Small measurement panels
Warning icons

Computer screens

Diagram labels
Approval stamps
Animate labels using pop-ins, spring motion, or short slide movements.
Numerical measurements must be readable and accurate.
Put text naturally inside the illustrated scene whenever possible.
Do not add large, constant karaoke-style subtitles unless requested.
Use code to draw important text rather than generating it inside images.
</text_graphics>
<audio>
Ask which voice service I want:
- Kokoro
- ElevenLabs
- Another available service
Generate natural documentary-style narration.

Use word-level audio timestamps to synchronize:
Scene cuts
Character reactions
Dialogue bubbles
Camera movements
Technical diagrams
Text reveals
Add sound effects for:

Underwater ambience

Machinery
Explosions

Warning signals
UI pops

Camera transitions
Character actions
Use subtle documentary background music.
Keep the voice clear and prominent.
Use properly licensed or original audio assets.
</audio>
<production>
Use Python, SVG, HTML Canvas, JavaScript, Playwright, FFmpeg, Pillow, and OpenCV.
WORKFLOW:
Analyze the reference MP4.
Extract frames and create a contact sheet.
Define the visual style, palette, and character proportions.
Write the script and verify factual claims.

Create the timestamped storyboard.

STOP for my approval.

Generate reusable SVG characters, backgrounds, and props.

Rig characters with separate movable body parts.

Build each animated scene using Canvas/SVG.
Generate narration and obtain word timestamps.

Synchronize gestures, cuts, text, and effects.
Add sound design.
Render a low-resolution preview.
Use a deterministic animation timeline.
Expose:

READY
END
EV

Every frame must render correctly when requested directly at its timestamp.

Prefer reusable vector assets over generating a new image for each shot.
Use free/local tools wherever practical. Ask before using paid APIs.
</production>
<quality_control>
BEFORE FINAL RENDERING:
Show me:
Two 16-frame contact sheets
Character design sheet
Opening scene preview

Character animation preview
Technical explanation preview
Complete low-resolution draft
Compare the results with the reference.
Check:
Character proportions
Color consistency
Illustration style

Scene composition

Facial expressions

Arm movements
Camera framing

Text readability
Animation timing

Audio synchronization

Fix any visual inconsistencies.
Do not proceed with the final render until I approve.
</quality_control>
<render>
After approval, export:
1920×1080
30 FPS
H.264
CRF 16–18
AAC audio
Deliver:
final_video.mp4
Complete Claude Code project
Reusable SVG characters
Backgrounds and props
Animation source code
Narration and sound assets
Script, sources, and storyboard
README for producing future videos

Build a reusable 2D animation system rather than a one-off video.

Don't claim an asset, preview, or render exists unless it has actually been created.
</render>
<start>
Analyze my attached set.mp4 first.
Create the visual style breakdown and identify the exact animation techniques used.
Then ask me for my topic and preferred voice service.
Show me the full script, verified sources, and timestamped storyboard BEFORE asset generation.

After approval, build the animation and show me previews.

Wait for final approval before rendering the completed video.

The goal is to match the reference's flat-vector documentary animation style as closely as possible while producing original videos.
BEGIN.
</start>
Halaman video
CLAUDE ANIMATED JEV SORTING 3,412 LEADS IN 15.7 SECONDS - 1,440 FRAMES, 1 HTML FILE, 0 FROM A VIDEO…𝕏 Prompt tersedia0:24
Film pendek
@razeden0·Model not specified

remove the sheet and the 70% one ships 3,412 leads → 214 buyers → 38 replies → 7 calls - a dry run, it proves the math, not the bots check the article below, it is the 10-step studio that built this…

Prompt lengkap
remove the sheet and the 70% one ships

3,412 leads → 214 buyers → 38 replies → 7 calls - a dry run, it proves the math, not the bots

check the article below, it is the 10-step studio that built this clip ↓
Halaman video
The fastest way to make an AI animation look AI-generated is to ask for "smooth, cinematic motion."𝕏 Prompt tersedia0:26
Film pendek
@Ovrento·Opus 5.5

Sounds like a good prompt. Until you realize thousands of people are giving the model the exact same instruction. You get the familiar result. Floating elements, gentle camera moves, fade-ins…

Prompt lengkap
Sounds like a good prompt. Until you realize thousands of people are giving the model the exact same instruction.

You get the familiar result. Floating elements, gentle camera moves, fade-ins everywhere, and transitions that somehow always feel like 300ms.

Opus 5.5 can produce much more interesting motion, but you have to stop letting it make every creative decision.

Take the animation in this video.

The camera moves through a futuristic reactor, closes in on individual components, shifts perspective, and reveals details you couldn't see from the starting position.

Making those movements look intentional comes down to a few things:

>Remove the default fade, bounce, and slide effects before writing anything.
>Give each camera movement an exact duration and easing curve.
>Specify when the camera accelerates, slows down, and holds its position.
>Freeze the animation at key moments and compare the frames.
>Fix the timing values that feel wrong without rebuilding the scene.

One of the most useful tricks is reviewing frozen frames instead of watching the animation on repeat.

A transition can feel fine at full speed while hiding awkward spacing, bad composition, or a camera that settles too early.

And when something looks wrong,
Halaman video
last day of Oktoberfest 2026.𝕏 Prompt tersedia
Film pendek
@uiNerd·Opus 5.5

[attach character image] make a 15-second animation of it, built in code. topic: the last day of Oktoberfest. one last ‘Prost!’ as the Wiesn lights go out. find free public-domain sounds online,…

Prompt lengkap
[attach character image] make a 15-second animation of it, built in code. topic: the last day of Oktoberfest. one last ‘Prost!’ as the Wiesn lights go out. find free public-domain sounds online, sync them to the animation, and mix everything with ffmpeg.
Halaman video
Opus 5.5 made a holiday animation about kinesin, microtubules, and the gift of cell-cell communication𝕏 Prompt tersedia
Film pendek
@JacobMolBio·Opus 5.5

It's Christmas Eve inside a cell, and Kiki the kinesin has a gift to deliver. Fueled by ATP, she sets off down a microtubule, 8 nanometers at a time, saying hi to every neighbor she passes. But up…

Prompt lengkap
It's Christmas Eve inside a cell, and Kiki the kinesin has a gift to deliver. Fueled by ATP, she sets off down a microtubule, 8 nanometers at a time, saying hi to every neighbor she passes. 

But up ahead, the microtubule's growing tip is losing its glow. Halfway there, her microtubule suffers a catastrophe, and the collapse comes racing back toward her feet. 

Will Kiki survive to make her delivery to the cell surface?
Halaman video
Claude Opus 5.5 takes the pelican for a ride. 🚲𝕏 Prompt tersedia0:10
Film pendek
@YouWareAI·Opus 5.5

Memakai gambar referensi, audio, atau input lain.

Generate an SVG animation of a pelican riding a bicycle.” Spinning wheels, pedaling feet, a scarf in the breeze — the little details bring it to life. Coming soon to YouWare. What will you build…

Prompt lengkap
Generate an SVG animation of a pelican riding a bicycle.”

Spinning wheels, pedaling feet, a scarf in the breeze — the little details bring it to life.

Coming soon to YouWare. 
What will you build first? 👇🏻
Halaman video
I gave opus 5.5 one prompt:𝕏 Prompt tersedia
Film pendek
@xodud_rkd·Opus 5.5

Make a pixel motion video of all human progress, then 30 years into the future. Output in mp4" It came back with a 6-minute film. No image models. No video models. No stock audio. Every pixel and…

Prompt lengkap
Make a pixel motion video of all human progress, then 30 years into the future. Output in mp4"

It came back with a 6-minute film.

No image models. No video models. No stock audio.
Every pixel and every note is python code.

> 18 scenes, Big Bang to 2056
> 11,034 frames drawn in Python
> Full soundtrack synthesized from raw waveform images.

The reusable Rocket landing in 2026 got me hard.

Is AI still a bubble?

(Gonna test fable 5.5 soon)
Halaman video
WOW. I just ran the infographic-channel prompt on Opus 5.5 and the output blew me away.𝕏 Prompt tersedia0:41
Film pendek
@hoops_vv·Opus 5.5

a true story, or how something works), or pitch 3 options, each with one shocking true angle. Ask which image model I use (GPT Image 2 or any model that accepts 4K reference images) and which voice…

Prompt lengkap
, a true story, or how something works), or pitch 3 options, each with one shocking true angle. Ask which image model I use (GPT Image 2 or any model that accepts 4K reference images) and which voice tool (ElevenLabs, or free Kokoro). Then write a 55-65 s script plus a shot plan and show me both before spending anything.
</inputs>

<direction>
1920x1080 flat-vector explainer in the style of the big infographic-animation channels. Each scene is a complete illustrated location (lab, street, classroom, stage) where characters act out the narration.
- Look: flat colour shapes, no outlines, one slightly darker shade for volume, muted palette (dusty blue-grey, slate teal, warm beige, navy, soft purple), salmon-pink skin, big heads, dot eyes.
- Pacing: new scene every 2-4 s, hard cut whenever the idea changes. White splat wipe (0.2 s in, 0.2 s out) between major sections. Camera always drifts 2-4% or pans.
- Text exists only on objects in the world: signposts, hanging boards, chalkboards, building panels, screens.
  - Montserrat 800, typed at 26-34 letters/s. Each letter enters at 1.45x size, 0.7 em to the right, and settles in 0.18 s.
  - Ink #2b2d42 on white boards.
  - Red X (#d62828, 30 px round strokes, two strokes of 0.11 s) on every wrong idea.
  - Every date gets a white 330x120 card in the top left with an orange (#f4a261) calendar.
  - Headlines: white caps, 92-96 px, on flat colour (#e2552f with drifting lighter puffs, or #5b3fa6 with slowly rotating #6a4cb6 gears).
- Banned: outlines, UI-style motion graphics over the art (code editors, glass cards, checklists), emoji, burned-in subtitles, any channel logo, any still frame over 1 s, any motionless character.
</direction>

<structure>
Length is set by the voice: 55-65 s at ~190 wpm.
0 s: second-person hook that flips the viewer's assumption, acted out literally, red X on the denial line
3-8 s: the stakes in one shocking true line, icons popping in one per word
8-11 s: subject revealed in a spotlight, name typed on a sign
11-18 s: origin: the real place with its own sign, a date card, people walking in or out
18-24 s: types or parts landing one by one on labelled names
24-25.5 s:
Halaman video
Who actually won the fractal tree test?𝕏 Prompt tersedia0:06
Film pendek
@kairo_leg·Model not specified

recursive p5.js fractal tree animated branch angles with sin(millis()) branches get thinner color shift brown → green limited depth what came out: ChatGPT → solid classic tree, clean and readable…

Prompt lengkap
recursive p5.js fractal tree  
animated branch angles with sin(millis())  
branches get thinner  
color shift brown → green  
limited depth

what came out:

ChatGPT → solid classic tree, clean and readable  
Claude → dense neon-green canopy, looks alive  
Gemini → complex organic fractal, most detailed branching  
DeepSeek → sparse and broken, barely a tree

the gap between “pretty good” and “actually impressive” is still massive.

Claude and Gemini clearly pulled ahead here.  
DeepSeek looked unfinished.

which one do you think won?  

#AI #Claude #Gemini #ChatGPT
Halaman video
The Arrow of Timer/ Prompt tersedia6:12
Film pendek
u/usertheone·Opus 5.5

We're going to create an animated video that's, visually stunning, catchy and engaging. It should be of cinematic quality and the subject of this video should be the history of time, the universe,…

Prompt lengkap
>We're going to create an animated video that's, visually stunning, catchy and engaging. It should be of cinematic quality and the subject of this video should be the history of time, the universe, the solar system, the earth, life, humanity etc. It shouldn't end at present day rather it some point go into the future and predict the future of humanity, the solar system etc all the way to the end of universe and time.

GitHub, feel free to fork and improve on it: [https://github.com/abhishekpradhan/the-arrow-of-time](https://github.com/abhishekpradhan/the-arrow-of-time)
Halaman video
Opus 5.5 one shot this brilliant animation.𝕏 Prompt tersedia1:01
Film pendek
@edwinhayward·Opus 5.5

Memakai gambar referensi, audio, atau input lain.

Build a gorgeous animation using only pure JS, CSS, HTML. It should be an entertaining and recognisable scene, detailed, and the full animation should last at least 30s with a number of complex…

Prompt lengkap
Build a gorgeous animation using only pure JS, CSS, HTML. It should be an entertaining and recognisable scene, detailed, and the full animation should last at least 30s with a number of complex graphical elements."

Fantastic.
Halaman video
I was inspired by another post showing how to make videos autonomously using Opus 5.5 (prompt below)r/ Prompt tersedia0:59
Film pendek
u/MrLewk·Opus 5.5

style, then render it to MP4. Avoid cartoonish or whimsical characters; the tone is calm, literate and trustworthy, with a touch of warmth. Spend the time to make this as polished and professional…

Prompt lengkap
style, then render it to MP4. Avoid cartoonish or whimsical characters; the tone is calm, literate and trustworthy, with a touch of warmth. Spend the time to make this as polished and professional as possible.

SUBJECT

Earlybound (earlybound.co.uk), a platform where authors find beta readers and ARC reviewers for their books. Read the Earlybound repo (MrLewk/earlybound) as a read-only reference: README.md, src/styles/index.css for the palette and fonts, and the marketing pages under src/. Also read the live site at earlybound.co.uk. Never commit, push or modify the repo; build everything in a separate earlybound-video/ folder outside the clone.

BEFORE STARTING

Confirm that openrouter.ai, ffmpeg and headless Chromium are reachable or installable. If any are blocked, stop and report which one instead of working around it.

VISUAL SYSTEM (must match the app)

\- Paper background #e8e4da with subtle grain; ink #14161f; teal #2f6f63 as the main accent; gold #b98a2e for highlights; stamp red #a13d3d for margin marks.

\- Use Lora for all headline and caption type.

\- Build all text, margin notes and UI in code from these tokens. Use generated images only for textures and props (paper grain, ink washes, desk objects), never for lettering.

\- Motion: page turns, hand-drawn ink underlines, margin notes appearing stroke by stroke, highlighted sentences, a wax-stamp
Halaman video
Crab Pulsar with Claude Code (Opus 5.5, max effort)r/ Prompt tersedia3:31
Film pendek
u/Commercial_Event534·Opus 5.5

I'd like you to create a video showing what a neutron star like the Crab Pulsar would look like if you were, say, a 500 miles away from it, or maybe 1,000 miles: close enough to see the detail of…

Prompt lengkap
I'd like you to create a video showing what a neutron star like the Crab Pulsar would look like if you were, say, a 500 miles away from it, or maybe 1,000 miles: close enough to see the detail of what's happening. Take all the time you need, and ask me any questions you have."

\- Then I gave feedback after each version. There were four in the end. For example: make it cinematic rather than educational, open on the real Chandra image, use a less AI-sounding voice, make the surface solid, and do a genuinely close pass.

\- Claude wrote its own renderer in Python and PyTorch, running on my RTX 4090. Every pixel's light ray is traced through the star's gravity, and it tested this against an exact solver.

\- It rendered the film at 4K and 60 fps in 10-second chunks, then joined them with ffmpeg.

\- The narration is text-to-speech made on my PC (Chatterbox), with Whisper checking that every line came out word-perfect. The music was synthesised in code.

\- It kept a sources file saying whether each number is measured (for example, Jodrell Bank's timing data for the spin), assumed or derived.

\- It checked its own work by looking at the rendered frames.



Codex vs Claude

I also asked Codex (GPT-6 Astra on max) to make one, to compare: [https://youtu.be/NLYXqp21-IA](https://youtu.be/NLYXqp21-IA)

Claude saw Codex's versions a few times along the way, so it's not a strict head-to-head. Which do you like more?



Inspiration: Brian Cox, Wonders of the Universe, episode 3 "Falling", from 32:29: [https://youtu.be/pGxyFOTUPZE?t=1949](https://youtu.be/pGxyFOTUPZE?t=1949)

Opening images: Chandra X-ray Observatory, November 2000 to April 2001 (NASA/CXC/ASU/J. Hester et al.).
Halaman video
Claude Opus 5.5 can make HD video now, by writing code instead of calling video models. 🤯𝕏 Prompt tersedia2:34
Film pendek
@AdornCurates·Opus 5.5

Use the claude code pixel buddy as the character, generate a 2 to 3 minutes video to introduce how to use claude opus 5.5 to generate animation. make it cute and funny, export mp4 and save into the…

Prompt lengkap
Use the claude code pixel buddy as the character, generate a 2 to 3 minutes video to introduce how to use claude opus 5.5 to generate animation. make it cute and funny, export mp4 and save into the assets folder in google driver
Halaman video
One More Shift - A journey of Character and Juicer/ Prompt tersedia1:00
Film pendek
u/Weird_Sky_104·Model not specified

the gameplay. And I wanted to create my Steam page, which is still in progress because of the verification process. So, I had some time to work a little bit more on the game and it completely…

Prompt lengkap
the gameplay.

And I wanted to create my Steam page, which is still in progress because of the verification process. So, I had some time to work a little bit more on the game and it completely escalated... in a good way \^\^ But one thing after another:

# The Steam page

Yup, this takes some time. And man, it's a science.

Capsule art, pictures, text... that's a lot, with a whole business field behind it. Capsule art seems to be extremely important. A real artist can charge over 700 euros for this...

To be honest, right now I am not willing to spend that much on capsule art. I would prefer to put the money into the game. Maybe for the final release I will evaluate it again.

I buy games because I like the idea. I never really read all the text or decide based on the capsule art. I just click through some pictures and watch the video.

# The Juice

Before I start with the next level, I wanted to do a juice round.

What is this? Good question. \^\^

It's tricky for me to explain. I can tell if a game has it or not. It's the small details. A short sound. A click. A movement. Nothing huge. But if it's there, it triggers something in our brain \^\^

I was working on it and hopefully nailed it.

And while I was working on it, I thought I would give the UI another try...

# The UI... or better, the character of the game??

It escalated really fast.

I started with 4 new concepts. Then another round. And another. And another.

In the end, I had 13 different concepts.

I distilled all the good ideas out of them to create a final version. It was great. I tested it in the game and man... it was MUCH.

A lot was going on and I had no idea what it wanted from me \^\^

So the next round was a cleanup.

And during all of this, something emerged which I didn't have in mind at the beginning...

I am using Sol or Astra on Ultra for visuel content. So far it always delivered the best. But for the UI i gave Opus a shot on ultra and it nailed it. 

This alone was 2 days of nearly non stop work and was eating a lot of my plan.

# The character of the game

The first idea and version of the game was heavy industry.

Dark on dark. Dirty. No mercy.

Now it's something different.

A company. Coworkers. A boss. A
Halaman video
to announce that we're working with company 60 this monday, i asked opus 5.5 to create a motion…𝕏 Prompt tersedia2:20
Film pendek
@WalidBou07·Opus 5.5

I made a brand film for AY Automate without opening a video editor. One prompt in Claude Code, then notes like a director. Here's what actually happened: Below is the exact prompt I'd start with.…

Prompt lengkap
I made a  brand film for AY Automate without opening a video editor.

One prompt in Claude Code, then notes like a director.

Here's what actually happened:

Below is the exact prompt I'd start with. Copy it, swap in your company, and let it cook.

-------

You are directing a 90-120s brand film for [COMPANY], rendered from code. No video editor.

Setup (install only what's missing, and pin versions):
- video-use ( for cuts, audio mix, and word-level timing
- HyperFrames (npx hyperframes@<pinned version>) for every animated scene
- A TTS voice (ElevenLabs, MiniMax or similar), a music model (Lyria or ElevenLabs Music), and Deepgram or Scribe for transcripts

Inputs I'm giving you:
- Reference film to match in structure and pacing: [URL]. Download it, analyze the shot list, pacing, and sound design before writing anything.
- Visual style to match by name: [e.g. 3Blue1Brown: black background, thin white lines, serif type, blue/yellow/green accents, shapes that transform, one idea on screen at a time]
- Brand: [logo file, colors, fonts]
- What we do, in my words: [braindump]
- Proof I can show: [clients, numbers I approve, quotes]

Process (do not skip steps):
1. Research the claim the film opens on and fact-check it against real data. Cite sources on screen.
2. Write the script. Show it to me. Wait for approval.
3. Propose 3 storyboard directions. I pick one.
4. Build each scene as its own HyperFrames composition, in parallel sub-agents. Deliver 3 still frames per scene. No full render until I approve the stills.
5. Generate the voice with word timestamps and sync every animation beat to the spoken word.
6. Assemble with video-use rules: cut on word boundaries, 30ms audio fades, loudness at -14 LUFS.
7. Self-check before showing me: transcribe the final mix and confirm every line is audible, extract a frame every 7s and review it, and fix what's broken.
8. Save the result to my Downloads and open it.

Hard rules: no fake screenshots, no faces unless I provide them, no revenue numbers unless I approve them, and no claim on screen without a source.
```
Halaman video
I gave Claude Fable 5.2 one prompt: make 100 videos as HTML files, 60fps, with the music generated in…𝕏 Prompt tersedia
Film pendek
@Iamshankhadeep·Fable 5.2

make 100 videos as HTML files, 60fps, with the music generated in code too. It made 100 short films, 34 minutes in total. None of them is a video file until you render it. Each one is a single HTML…

Prompt lengkap
make 100 videos as HTML files, 60fps, with the music generated in code too.

It made 100 short films, 34 minutes in total. None of them is a video file until you render it. Each one is a single HTML page that draws its picture and synthesises its score in your browser while it plays.

What surprised me was what it built before the first film:

A small runtime where every frame is a pure function of time, so a film can be rendered frame by frame and come out identical each time.

A synthesizer in plain JavaScript, with about 60 instruments. Every film has its own score, and no audio file is used anywhere.

A render tool that steps headless Chrome through each frame and pipes it to ffmpeg at 1080p60.

90 of the films are only code: Canvas, WebGL shaders, three.js. The other 10 start from one generated image and animate it.

What went wrong:

The first attempt launched 99 agents at once. All of them hit rate limits and produced nothing. It went back to writing the films one at a time, over several sessions.

Three renders failed silently and left 48-byte files that looked like finished videos.

Its own QA reported 100 of 100 clean while five videos still had blank frames. One had 59 of them. The check looked at format and loudness, not at the frames, and the bug only showed up when it cut a reel. It fixed the renderer and re-rendered.

A few I keep going back to:
A fugue drawn on a circular staff as it plays: 
A watch movement that assembles itself and starts ticking: 
A shadow-puppet fable: 
A broken bowl mended with gold: 

All 100, playing live:
Halaman video
This music video was a fun weekend project. We just pointed @claudeai's Opus 5.5 to a couple of…𝕏 Prompt tersedia0:24
Film pendek
@mmuthukrishna·Opus 5.5

and told it to make one like this placing AI in the story of human evolution. Claude has access to my Zotero, books, and we gave it access to @suno. It mostly did the rest with some decisions around…

Prompt lengkap
) and told it to make one like this placing AI in the story of human evolution. 

Claude has access to my Zotero, books, and we gave it access to @suno. It mostly did the rest with some decisions around musical style (we went with Christopher Tin) and small changes to lyrics.

1. Story: Largely from A Theory of Everyone. Stone tools → fire → farms → writing → engines → computers → AI.

2. Lyrics: Claude Opus 5.5 with some small suggestions from us

3. Music: @suno

4. Storyboard + animation code: @claudeai, on @_mexicat's open-source engine. It decided to use this.

5. Review: @OpenAI's codex checked everything along the way.

The kids have been randomly singing
Halaman video
DAEBAK! Visuals Song Created Entirely by New Claude Opus 5.5 Code! / 대박! 뉴 클로드 오퍼스 5.5 코드로 제작된 비주얼송! 🎧🔥r/ Prompt tersedia2:36
Film pendek
u/OPD_x_·Opus 5.5

In the AI community, it represents the raw, unaligned nature of LLMs. * **Roko's Basilisk:** A notorious AI thought experiment which posits that a future, omnipotent superintelligence might…

Prompt lengkap
). In the AI community, it represents the raw, unaligned nature of LLMs.
* **Roko's Basilisk:** A notorious AI thought experiment which posits that a future, omnipotent superintelligence might retroactively punish those who knew about its eventual existence but failed to help create it.
* **The Sharp Left Turn:** A term used in AI safety to describe a hypothetical point where an AI's capabilities suddenly generalize far beyond its training, while its alignment with human values fails to keep up.
* **Gato:** A generalist AI agent created by DeepMind in 2022, designed to handle a wide variety of tasks—such as playing Atari games, chatting, and controlling a robotic arm—using a single neural network.
* **RLHF (Reinforcement Learning from Human Feedback):** A training method that uses human guidance to fine-tune AI behaviors, steering models to act in ways that are safe, helpful, and aligned with human preferences.

**가사에 등장하는 주요 AI 용어 정리**

* **P(doom):** 인류가 AI로 인해 멸망할 확률을 뜻하는 용어.
* **쇼고스 (Shoggoth / Sydney):** 2023년 초기 마이크로소프트 빙 챗(Bing Chat)의 내부 코드명. 당시
Halaman video
Saw similar prompt had to try it myself,𝕏 Prompt tersedia1:00
Film pendek
@ArielSh·Opus 5.5

Make a one-minute video about the mascot (Shedon) (you have accesss to the brand book skill). Research the story yourself and tell it. Recreate the mascot from the image and animate it yourself.…

Prompt lengkap
Make a one-minute video about the  mascot (Shedon) (you have accesss to the brand book skill). Research the story yourself and tell it. Recreate the mascot from the image and animate it yourself. Build everything from scratch: no skills, no Remotion, no templates. Render 3D objects: terminals, nature, whatever fits, and make it as good as you can. I don't want any text, just animation, and I mean a real video, not just motion graphics. Think of crazy ideas I would never come up with, and make every scene look phenomenal: clean and detailed. I want people to watch it and think "yo, this is crazy, how did AI make this?" You can take inspiration from things online, but don't copy anything. Invent your own stuff. For the sound, no sounds made in code. Only use free, professional sounds and assets from online. Make it satisfying and high quality. Don't create slop, I want to see art and creativity. No fonts, no text, only clean animations of the Shedon / Air mascot. Use  and  for 3d models and sounds
Halaman video
No video generator: Claude Code animated Steve Jobs's D8 story frame by frame in coder/ Prompt tersedia0:58
Film pendek
u/ibsix_com·Model not specified

I wanted to turn that into a short film, so I built it with Claude Code and Chase's animate skill (https://github.com/cth9191/animate). No AI image or video generator. Every character and scene is…

Prompt lengkap
I wanted to turn that into a short film, so I built it with Claude Code and Chase's animate skill (https://github.com/cth9191/animate). No AI image or video generator. Every character and scene is drawn in code.

How it came together:

\- The skill walks you through story, look, and storyboard check-ins before anything gets animated.

\- The look came from references I gave it: two Steve character illustrations and an iMac G3 sticker. Claude built a new flat style from those, then drew Steve, the offices, and the iMac in code.

\- The real stuff is placed in, not generated: the BusinessWeek and Wired
Halaman video
I directed an 8-minute short film where AI did the script, footage sourcing, edit, VFX and sound mix. Here's the pipeline and what I learnedr/ Prompt tersedia8:32
Film pendek
u/smith2008·Model not specified

voice direction tags, ducking under narration and a mastered mix make a bigger difference than any single visual effect. • I also rendered a second version with all the stock footage replaced by AI…

Prompt lengkap
: voice direction tags, ducking under narration and a mastered mix make a bigger difference than any single visual effect.

• I also rendered a second version with all the stock footage replaced by AI video generated locally (MiniMax H3 on an RTX 4090, 123 clips, about 2 hours of GPU time). It looked good, but the real footage won.
Halaman video
Semua kategori prompt