teardown (elvarofficial/teardown)Partly tested🌏 World

@elvar_official packed his Claude Opus workflow for turning one reference image into a take-apart 3D machine simulator into the teardown skill, with all 9 prompts public

Elvar (@elvar_official) turned "any machine with moving parts → an interactive 3D simulator" into a Claude Code skill, teardown (MIT): give Opus one reference image, insist every part is three.js code driven by one math model that also feeds the gauges; cut parts open, press subsystem buttons, auto-tour when idle, and record a 60 fps film with a procedural score. The repo ships three machines (V8, Cessna landing gear, Strandbeest). Install with `npx skills add elvarofficial/teardown -g -a claude-code`, then npm install + Playwright Chromium in the skill folder. His X Article publishes all 9 prompts; demos live at visual-learning.app. On Linux we cloned commit e7e668c, installed deps, and bundled cessna-live.html (~799 KB with three.js inlined); we did not open Claude to invent a new machine or record video.

Visit site teardown (elvarofficial/teardown) ↗
Pricing
Freemium
Region
Global
Where it's from
Overseas
Added
Oct 31, 2026
Tested on
Oct 31, 2026
Version we used
elvarofficial/teardown commit e7e668c (2026-10-30); SKILL.md name teardown; sample machines v8 / cessna / strandbeest
Categories
VideoDesignCoding
Original author
Elvar @elvar_official ↗
Our test
Partly tested
Cost / time
Skill and sample machines are MIT and free; running Claude Code / Opus needs your own Anthropic plan; demo pages open offline with no credit spend.
Source
X @elvar_official ↗X Article @elvar_official ↗GitHub elvarofficial/teardown ↗Playground visual-learning.app ↗

The task

Explain how engines, landing gear, linkages and similar mechanisms move with an interactive 3D teardown and live gauges—not just a static cutaway or a screen recording.

Steps

  1. Install: `npx skills add elvarofficial/teardown -g -a claude-code`, then once in the install folder run `npm install && npx playwright install chromium` (Node 20+; video also needs ffmpeg and Python 3).
  2. Open a shipped machine first: `node sims/build.mjs v8-live` (or cessna-live / strandbeest-live), open `teardown-out/dist/*.html`, orbit, and press subsystem buttons.
  3. Pick a machine with one moving input and real dimensions, plus one reference (manual cutaway, photo, or clip). Without a reference the author says results come out as generic toys.
  4. In Claude Code run `/teardown` or ask in plain words; paste the article's main prompt skeleton: pure-function model first (one input → every pose and readout), then geometry, then console and auto tour.
  5. Follow the article for the console (live charts, cutaways, camera buttons), look rules (pale studio, one accent), review loop (stills per beat for collisions), integrated-GPU quality tiers, then optional film + score.
  6. Keep the published HTML under ~1 MB (externalize heavy models), deploy e.g. to Vercel; compare against visual-learning.app demos.

Prompt

/teardown Using the attached cutaway, build an interactive 3D simulator of the Cessna 337 main landing gear. Write the model as pure functions of stroke 0→1 first: a 201 mm rack turns a 32-tooth pinion at module 4 mm through exactly 180°; show the hand check before drawing parts. Every panel and label reads that one model—nothing keyframed by hand. Pale studio, one accent color; show me a contact sheet of stills at every tour beat before any video.

What the author says

@elvar_official: packed the whole 3D workflow into one Claude skill; gave Opus 5.5 one reference picture and required every part in code, matching the render to the picture for 3 rounds before motion; ~260 tiny pistons/hoses/screws/wires under the big gears; something comes apart every 2–3 seconds, pull a leg and its servo bar flips to DETACHED. Built 7 in 2 days; 3 ship in the skill (V8, Cessna gear, Strandbeest); a V8-style sim pulled ~3.79M views on X. Skill, playground and all 9 prompts are public; built on whaleyxbt/claude-motion.

Our test

On Linux we cloned elvarofficial/teardown commit e7e668c (2026-10-30), ran npm install, then `node sims/build.mjs cessna-live`. We did not install Playwright for capture, did not run run_sfx.py, and did not drive Claude Code end-to-end on a new machine.

What we found when we tried it:cessna-live.html wrote to teardown-out/dist/ at 818256 bytes (~799 KB), with canvas and three.js-related code and title cessna-live—matching the author's "~800 KB offline page" claim. The repo has v8 / cessna / strandbeest shared+live+film trees plus kin.js / gear.js / jansen.js math modules.

How to get in

The post and X Article are in English (login may be required); GitHub and visual-learning.app are public. Using Claude Code in regions without native Anthropic access needs your own compatible endpoint.

Who it suits

People making educational demos, product teardowns, or mechanism explainers; anyone already on Claude Code who will iterate against a real reference.

Pitfalls

  • In our test we could bundle offline HTML, but we did not have Claude invent a new machine from scratch or run capture/film—so "7 in 2 days" and "3 visual-match rounds" are the author's claims.
  • The author stresses that without a reference (pangolin, armadillo, scorpion, etc.) you get generic toys; you need real numbers plus one picture.
  • Film capture needs Playwright Chromium + ffmpeg; on integrated GPUs you must enable quality tiers or you may drop to ~15 fps.
  • Share cards are size-sensitive: a 15.9 MB rabbit page hid the X link card until models were externalized (~967 KB).
  • Built on whaleyxbt/claude-motion; you still need npm install in the skill folder—copying SKILL.md alone is not enough.

More in this category