A submarine dives by letting the ocean in. Vents open, air rushes out of the ballast tanks and seawater floods in. At zero weight in water, small wings fly it down. This Short got 1.8K views on YouTube. Every frame was built in code by Claude Code. No 3D software.

Everyone posts the "$8k/month faceless channel" screenshot. Here's a real one, 10 days in: 11 Shorts ~14,000 views 10 subscribers $0 earned I never opened a video editor. Claude Code built every 3D model, wrote the scripts, made the voice and rendered it. What the numbers taught me 👇

The full 9-minute version uses the same 3D model and answers the part this clip skips: why the turbine blades sit in gas hotter than their own melting point and survive. youtu.be/S9eM3bMSDKk

Guess what this 660-ton steel ball is doing near the top of Taipei 101. It hangs on cables between the 87th and 92nd floors. It's not decoration. Wrong answers welcome. I'll post the real one under this.

A jet engine is allowed to fail this test. They fire a bird of up to about 3.6 kg (8 lb) into the spinning fan. The blades can bend. The engine can even shut down. The one thing it must never do: catch fire or throw broken parts out through its case.

Why did the SR-71 leak fuel on the runway? At Mach 3 its titanium skin got so hot it grew. So the panels were built loose, with room to expand. Cold: gaps, leaks. Hot: sealed. What should I open up next?

She doesn't exist. Neither does the mask. One AI photo of the same face, then 15 seconds of AI video. This is take 7 of 10. Hardest part: her face has to survive the peel. Some tries came back as a slightly different person.

Inside a car engine.

Here it is moving. 14 seconds, balance wheel first.

A still teardown names the parts. Motion shows why they're there. Pin lock below: 5 spring-loaded pin stacks. A key has exactly one job, lift every split to the same line at the same moment. In a still you see pins. When the key slides in, you see the lock decide.

One prong on a US lamp plug is wider than the other. It's not a mistake. > The narrow slot in the wall is the hot side. It carries the live voltage. > The wide slot is neutral, the return path. > The lamp's switch is wired to cut the hot side, so when it's off, the bulb socket isn't live. > If the plug could go in backwards, that socket could stay live with the switch off. Touch it while changing a bulb and that's a shock. The wide prong only fits one way, so the hot wire always lands where the switch can cut it. Built in code with Claude. No keyframes.

This skincare creator doesn't exist. Every video starts as one AI photo of the same face, then 15 seconds of AI video from that photo. The hard part isn't the video. It's keeping her the same person every single time.

One-shot 3D demos are the wrong benchmark. The first render is the easy part. I've made 44 machine explainers with Claude, and what breaks is shot two: same parts, same scale, new camera, 9 to 12 cuts a minute. That's the test I'd want to see.

This tiny lever stops a mechanical watch 8 times every second. Then lets it go again. Every tick you've ever heard is this.

I asked Claude Opus 5.5 to explain how a lock works by building one you can take apart. Cut it open, follow the key past five split pins, then turn it and watch the plug spin free.

"If every cable on this elevator snapped, it still wouldn't fall."

I asked Claude Opus 5.5 to explain how a jet engine works by building one in code and taking it apart. Cut it open, follow the air through row after row of compressor blades, into the flame, then out past the turbine that spins the whole thing.

Making 3D explainer videos with AI: Must-Save Checklist 👇 • Script: Claude Code, one machine per short • 3D model: Three.js, real parts (teeth, bearings, bolts) • Motion: camera, cuts and exploded views written in code • Voice: Qwen3-TTS, runs locally, free • Render: Playwright captures every frame • Encode: ffmpeg, captions burned in • QA: a frame sheet before the final render

ALMOST NO ONE IS DOING THIS YET WITH CLAUDE CODE. I make 3D machine explainers without opening Blender or a video editor. Most people are still using it to write apps. → Claude writes the script → builds the machine in Three.js → animates and renders every frame in code → 36 shorts in 16 days

There's a YouTube channel called IFOLOGY. Black-head stickmen in hoodies, "what if" stories, a new video almost every day. Only 28K subscribers. One video is sitting at 649K views. Napkin math on their last 5 uploads: ~1.3M views. At a $2–5 RPM that's roughly $2.5–6K. So I tried building that style with Claude Code. No Blender, no drawing, just code. Took ~40 rounds to stop looking creepy. Now a new color variant renders in about 30 seconds. Which hoodie gets the first episode?

This spinning triangle is a whole engine. Three chambers, three power strokes every turn, no pistons going up and down. The catch: the rotor tips wear and it burns oil. Mazda still won Le Mans with one in 1991. Every frame of this is code, built with Claude Code + Opus 5.5. No Blender. Follow for more machines taken apart.

Everyone's making motion graphics with Claude Opus 5.5. Nobody's talking about what it's scary good at: 3D machine teardowns. This planetary gearbox came out of ONE prompt. Real gear teeth, cut-open housing, exploded view, labels. One HTML file that opens in your browser. I ran it 4 times in fresh Claude Code sessions (Opus 5.5 and Sonnet 5.5). Every run worked first try. 🔖 Bookmark it. Swap the machine name on the first line and run it. I've only verified the gearbox so far, so reply with what yours builds. Full prompt 👇 MACHINE = "planetary gearbox" Build a premium 3D animated cutaway of the MACHINE above as ONE self-contained file: index.html (no build step, no other files). It must open by double-clicking. Tech - Three.js 0.160.0 from the unpkg CDN via an importmap ("three" and "three/addons/"). - Use OrbitControls, RoomEnvironment + PMREMGenerator for reflections, ACESFilmic tone mapping, sRGB output, soft shadows, antialias, devicePixelRatio capped at 2. Resize with the window. Model (this is what makes it look expensive — don't cut corners) - Model every real part of the MACHINE with correct proportions and real geometry: e.g. gears get actual teeth built from ExtrudeGeometry with a proper tooth profile, shafts, bearings, housings, bolts. No placeholder boxes or plain spheres standing in for parts. - Real materials with MeshPhysicalMaterial: brushed steel (metalness 1, roughness 0.3), dark anodized aluminum, brass or bronze accents, matte rubber where it belongs. Slight color variation between parts so they read separately. - Show the inside: cut the housing open (half shell or a clipping plane) so the moving parts are visible. - Parts must mesh and move correctly relative to each other (correct gear ratios, matching rotation directions). Animation (seamless 12-second loop) - 0–4 s: assembled machine running, slow camera orbit. - 4–8 s: exploded view — parts slide apart along their axis with easing, still turning; a small floating label (HTML overlay, clean sans-serif) names each major part. - 8–12 s: parts ease back together, loop restarts without a jump. Look - Dark studio background with a subtle radial gradient, a soft ground shadow, one warm key light and one cool rim light. First frame must already look like a product render, not a demo. - A small title in the top-left with the MACHINE name, and one line under it explaining how it works in plain English. When done: list the parts you modeled and how to change MACHINE to something else (e.g. "4-stroke engine", "mechanical watch movement", "differential").

36 shorts in 16 days. I never opened a video editor. Every machine you see here is built in code — the jet, the rocket tower, the rotary engine, the 660-ton damper ball inside Taipei 101. The pipeline: 1. Script written as data (each line = one shot) 2. Voice from a local open-source TTS model 3. Every part modeled in code, cutaways and all 4. Frames captured headless, stitched with ffmpeg 5. Scheduled to YouTube and TikTok Tool subscriptions for this pipeline: $0. Why code instead of an editor? A fix is one line, not a re-edit. And the machines stay accurate, down to the pins in a lock. What machine should I take apart next?