Teardown turns any machine into a 3D model you can take apart

A project at elvarofficial/teardown lets a coding agent build an interactive 3D page. A reader can take a machine apart on it to see how the parts work. The repository is two days old. It is MIT-licensed and has reached 705 GitHub stars and 113 forks. Trendshift's daily list ranks it 17th.

The repository calls itself "a Claude Code skill that turns any machine into a 3D simulator you can take apart". The user asks a question in plain English. The agent builds the answer as a single offline HTML file. Three worked examples come with it: a V8 engine, a Cessna aircraft, and a Strandbeest walking frame.

What the output is

The README describes one HTML file per machine. The machine runs in the middle of the page. Panels around it read the real numbers the parts are producing. A button opens the part doing the work. When nobody touches the page it tours itself.

A user types a sentence like "Build me a simulator of a 4-stroke motorcycle engine I can take apart". Another example from the README is "How does a mechanical watch keep time? Show me as a simulator". The agent builds the page. The HTML file needs no server. three.js and the fonts are inlined into it.

The repository also includes a second step. It records a tour of the page as a 60 frames per second video. Sound is generated in Python on the film's timeline. The maintainer masters it to negative 14 LUFS. Node 20 is the baseline for the toolchain. ffmpeg is needed for video and Python 3 for sound.

What it is built on

The project credits whaleyxbt/claude-motion. That is a motion design toolkit for coding agents released two weeks earlier. Teardown takes its runtime, frame capture, sound engine and review rules from there, under an MIT licence.

Teardown adds a specialised skill on top. It carries the three example machines. It sets the layout where panels read live numbers off the central model. The self-tour is its own addition.

Both projects share the same review loop. The agent cannot watch a 3D scene. It renders a contact sheet of still frames. It checks for parts that clip through each other. It checks for a safe area that reads on a phone. It fixes what it finds before declaring the piece done.

What it does not say

The README does not claim the output matches a hand-made CAD simulator. It does not claim engineering teaching quality. It names the frame rate, the resolution and the file shape. The accuracy question is left to the reader.

The maintainer notes that recorded samples are CC0 from Freesound. They are prepared through a related repository. The sources file is listed in the project.

A product team describing a mechanical product can use this. A short-form teacher explaining an engine can use it. So can a maker writing docs. A single-prompt first draft shows whether the idea reads. That is cheaper than paying somebody to build the explainer by hand. The output is one HTML file. The user opens it, emails it, or embeds it.

Source

elvarofficial/teardown on GitHub.