RIP Blender? This crab has 206 parts, and Opus 5.5 wrote every one in code.
Watch the shell. At 0:06 it splits into 21 plates, and you can see:
> 672 rivets and bolts, every one placed by code
> a hydraulic ram on each knee with 67 mm of stroke
> 2 gears in each claw, 12 teeth driving 36
> eyes with a 10-blade iris
Nothing is a 3D model.
All of it is code, and the video records itself.
What should I build next? A spider, an engine, a crane?
Prompt, save it ↓
RIP Blender? This crab has 206 parts, and Opus 5.5 wrote every one in code.
Watch the shell. At 0:06 it splits into 21 plates, and you can see:
> 672 rivets and bolts, every one placed by code
> a hydraulic ram on each knee with 67 mm of stroke
> 2 gears in each claw, 12 teeth driving 36
> eyes with a 10-blade iris
Nothing is a 3D model.
All of it is code, and the video records itself.
What should I build next? A spider, an engine, a crane?
Prompt, save it ↓
most "AI built this" videos are just animation. here every gauge is computed
opus 5.5 wrote every part of this robot arm as code, then served a volleyball with it
how it's built:
> 147 parts, each one made by a function. nothing is drawn by hand
> the motion is math before anything gets drawn: 3 joints, one swing, the ball leaves at 59 km/h
> every gauge reads that same math, so the torque bars, the ball speed and the arc chart never disagree
> one click and the arm blows apart on a turntable, then snaps back together
paste this into claude ↓
"Build a robot arm that serves a volleyball, in one HTML file:
1. Every part is its own function. Write the parts list first.
2. Write the swing as math first: joint angles over time, then the ball launch from the real hand speed.
3. Add live gauges for torque, ball speed and the arc. They must read the same math as the arm.
4. Add an exploded view on a turntable that snaps back together.
Show me the plan first. No code until I say go."
swap the arm for any machine. same prompt
save it for the weekend