One Reference Image, 260 Pistons: Opus 5.5 Turns Mechanical Teardown into three.js

A demo on X turned a single reference image into a complete three.js mechanical teardown. The shell, gears, and hoses are all written in code, and the entire 3D workflow is packed into a Claude skill.

The aircraft in the video is called Mellis HB-7. The parameters on the left include a wingbeat frequency of 7.5 Hz, power at 84%, battery voltage at 3.78 V, and temperature at 34°C. The exterior is defined by the reference image, and the parts are not a fake teardown made with textures. Hidden beneath the large gear are 260 tiny pistons, hoses, screws, and cables. Every 2 to 3 seconds, a component detaches; when a leg is pulled out, the servo rod flips to the DETACHED state.

The easiest way this kind of demo fools the eye is by watching only the final animation. What actually took time was, before producing the video, comparing the rendered result side by side with the reference image for 3 rounds. Generating 3D from a single image is not rare; what is rare is packing the validation process into the skill too. Most demos stop at looking similar; engineering has to answer reproducibility.

In the comments, there was a more specific reminder: add a validation step in the skill that automatically compares the rendered result with the original image, pin the three.js version, and set an upper limit on mesh count; otherwise the scene easily becomes heavy. Another reminder was that the repost missed the author @elvar_official.

The number 260 is catchy. What is more valuable is that it reveals a direction: the barrier to generating mechanical animations is falling, but the dirty work of making results reproducibly stable still has to be written into the workflow by someone.