✓ Checked
Teardown: A Claude Code Skill That Builds 3D Machine Simulators
A viral X article shows teardown, a free Claude Code skill that builds a machine as a 3D simulator in one offline HTML page and records it to video. We checked the repository: MIT, three working examples, what setup really needs and which claims hold up.
On October 30, 2026 Elvar (@elvar_official) published an X Article, "How I Turn Any Machine Into a 3D Simulator You Can Take Apart". It promotes teardown, a free skill for Claude Code that builds a working 3D model of a machine as one web page: the machine runs in the middle, live gauges sit around it, every subsystem has a button that opens it up, and the page records itself to video. The article walks through nine steps, from picking a machine to putting the page online.
The prompt blocks of the article did not come through in the text we could read, so we checked the claims against the teardown repository instead: its README, SKILL.md (the instructions Claude reads), package.json, LICENSE and the example code. The short answer: the workflow is real and reproducible, the license is MIT, and most of the article's advice is written into the skill itself. The repository is also very new, and setup needs more than the article's list of requirements suggests.
The original article by @elvar_official on X (October 30, 2026)
What teardown is
teardown is a folder Claude Code reads as a skill, plus a small JavaScript and Python kit. It is installed with the open skills command line tool: npx skills add elvarofficial/teardown -g -a claude-code, then npm install && npx playwright install chromium once inside the installed folder. You need Node.js 20 or newer; ffmpeg only for the video and Python 3 only for the sound.
Its package.json pins five dependencies: three.js 0.186.1 for the 3D scene, Playwright 1.58.2 to drive Chromium when recording, esbuild 0.28.1 to bundle each machine into one HTML file, and two font packages. A built page opens from the disk without a network connection and weighs about 800 KB, as SKILL.md puts it.
kin.js, gear.js, jansen.js: real dimensions, one input (crank angle, stroke or wind), every pose and readout computed from itengine.js, beast.js: geometry built from code, posed by that one inputconsole.js: a fixed 1600 x 900 overlay of charts, toggles and callouts redrawn from each framestage.js: lights, shadows and post effectsfilm.js: a script of camera moves; live.js: the same machine with buttons, which plays the tour when nobody touches itscore.py: a procedural score on the film's timelineThree machines ship as examples, each in a shared folder, a live page and a recorded film:
| Example | What drives it | Detail from the code |
|---|---|---|
| V8 engine | Crank angle | Firing order 1-8-4-3-6-5-7-2, glass liners, a chamber pressure model for the indicator chart |
| Cessna 337 main landing gear | Stroke | A 201 mm rack turns a 32-tooth pinion (module 4 mm) through 180° |
| Theo Jansen's Strandbeest | Wind | 20 legs on one crankshaft; every joint solved from Jansen's 11 link lengths |
The nine steps, checked against the skill
The article's steps follow the rules in SKILL.md closely, so you get most of the method even without the author's prompts.
| Step in the article | What the skill itself says |
|---|---|
| 1. Install | The same two commands as the README |
| 2. Pick a machine and a reference | Rule 1: start from a photo, a manual cutaway or a clip, never from imagination; invented machines come out generic |
| 3. Build the machine | Rules 2 and 3: real dimensions, one source for every number, one input that poses everything |
| 4. Build the console | Panels and charts read the same state as the 3D parts |
| 5. Give it the look | A light studio with one accent; give near-white parts an ink outline; a 3/4 camera for linkages |
| 6. Check it like a critic | A review loop on sheets of still frames, with a checklist; fix collisions by changing a number, not the camera |
| 7. Make it a page you drive | Test on an integrated GPU, use quality tiers, compile shaders before the first frame |
| 8. Turn it into a video | Render frame by frame to a 60 fps MP4, score it to −14 LUFS, join both with ffmpeg |
| 9. Put it online | Keep the page under 1 MB so X and Slack can read its share card |
What the post gets right
- Free and MIT. The LICENSE is MIT and names two copyright holders, elvarofficial and whaleyxbt, which matches the article's credit to whaleyxbt's claude-motion. The README says the runtime, frame capture, sound engine and review rules come from there.
- Three machines inside. The V8, the Cessna landing gear and the Strandbeest are all in the repository.
- The gear numbers check out. A 32-tooth gear at a 4 mm module has a 128 mm pitch diameter, and by our calculation half its circumference is 201.06 mm, which matches the 201 mm rack stroke.
- The Strandbeest is the real linkage.
jansen.jscarries the link lengths Jansen arrived at in 1990 and solves each joint by intersecting circles. - Reference first. The article's lesson (a pangolin, an armadillo and a scorpion drawn from nothing came out as toys) is also rule 1 of the skill.
- The demo site is live. visual-learning.app says it is made by @elvar_official and now lists seven simulators, one more than the article's six, plus a gallery of other machines.
What it leaves out
- Setup downloads a browser. The article's "What You Need" names Node.js, ffmpeg and Python, but setup also runs
npx playwright install chromium, which fetches a Chromium build that the recorder uses to render frames. - A brand-new project. The repository was created on October 30, 2026, the day of the article, and has two commits by one contributor. It is a skill and a set of examples, not a maintained library.
- "Any machine" means any machine you can measure. Without a reference and real dimensions the skill itself expects generic results.
- Model use is on your Claude plan. The author built everything with Opus 5.5 in Claude Code, which on AgentGid's data comes with Pro at $17/month billed annually or $20 monthly; the Free plan does not include Claude Code. Several builds and review passes per machine use a lot of it.
- claude-motion is a different license story. teardown does not depend on Remotion, but claude-motion, the toolkit it was built from, ships a Remotion project and Remotion skills. If you install claude-motion too, note that Remotion's license is free for individuals and companies with up to 3 employees, and larger companies need a paid license, according to our data.
- The view counts are the author's. The X view numbers quoted in the article are as reported; we did not check them.
The sounds are clean: the 12 recorded samples are CC0 from Freesound, each source page listed in sfx/samples/SOURCES.md, and everything else in the score is synthesised in Python.
Stars
The repository had 2,202 stars and 341 forks when GitHub's API was read on November 6, 2026. It got 490 new stars on October 31, its busiest day.
AgentGid data
Claude Code is #1 of all tracked agents by Gid Score (84.6), with 12,690,433 weekly package downloads as of 2026-11-05; Gid Score measures adoption and attention, not quality. The tools under teardown have their own pages: three.js, Playwright, the skills CLI and FFmpeg.
Other skills for code-made video are in our guides to Claude Code skills for video and animation and videos made in code with Opus 5.5.
How to try it
- Install the skill and run the setup command once; check that
ffmpegis on your PATH if you want video. - Build one example first (
node sims/build.mjs v8-live) and open the HTML file to see what a finished machine looks like. - Pick a machine with one moving input and published dimensions, find one reference picture, and ask Claude Code in plain words for a simulator of it.
- Let it run the review loop on still sheets until a pass finds nothing, then test the page on a laptop's built-in graphics.
- Record and score only once the live page is right; keep heavy models outside the page if you plan to share the link.
The verdict
- A real, reproducible workflow. The skill, the examples and the build and recording scripts are all in an MIT repository, and the article's advice is mostly the skill's own rules.
- Best for machines you can measure. Engines, gears and linkages with known dimensions are where it shines; invented creatures need a reference to look like anything.
- Young code. Two commits and one contributor so far: copy what you need rather than depend on it.
- Mind the toolchain. Node.js, a Playwright Chromium download, ffmpeg and Python, plus plenty of Claude usage per machine.
Facts come from the teardown repository (README, SKILL.md, package.json, LICENSE, jansen.js and the samples list), claude-motion's GitHub page and visual-learning.app; star counts from GitHub's API on November 6, 2026. The gear check is by our calculation, and the article's view counts are as reported. We did not run teardown.
Agents mentioned in this guide
| # | Agent | Gid Score | Downloads 7d | 7d | 30d | Stars | Latest release | ||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 |
Claude CodeAnthropic |
87 | 17.5M | up 23.5% | down 0.7% | 156K+134/day | 2.1.3262d ago | ||||
Live table, updated daily (figures as of Nov 18, 2026); numbers in the text above are as of the dates given there. "#" is the rank among products of the same kind by Gid Score, our 0-100 composite of adoption, community, attention and momentum (how it is calculated); a dash means no public data.