Turn Reference Images into 3D Teardown Simulators
Build a 3D mechanical simulator from reference images, with parts you can separate and inspect. teardown uses Three.js to keep part motion and instrument readings in sync, with a guided tour that can be recorded as a video.
Works with Claude Code
Requirements
- Node.js >= 22.20.0
- Chromium
Overview
What you get
- A Three.js mechanical scene with interactive views, cutaways, exploded parts and instruments driven by the model’s state.
- A guided tour shared by the interactive page and frame-by-frame video capture, with Python scripts for procedural music and sound.
- Three bundled mechanisms: a V8 engine, Cessna 337 landing gear and Strandbeest, each with an interactive page and a film version.
Good fit
- Explaining mechanical structures and motion through parts that readers can inspect and operate.
- Producing an interactive mechanical demonstration and a short explanatory video from the same scene.
Tutorial
See how the parts work inside
A photograph shows a machine’s appearance. Explaining how power reaches each part takes more than an outside view. teardown guides AI through building a Three.js mechanical scene with exploded views, cutaways, instruments and working controls. The same scene can become a short video.
Watch the author’s Mellis HB-7 bee-shaped robot above. Look for:
- How the internal parts stay aligned as the body opens into layers.
- Which instruments and status labels change as the parts move.
- How the camera moves from the whole machine to a detail and back.
Start with the bundled Cessna 337 landing gear. Then use your own reference images to plan a simulator.
Choose a diagram skill
| Skill | Best suited to |
|---|---|
| teardown | Three.js mechanical simulators with parts you can separate; the interactive page and video share a model and tour. |
| Colorfigures | Colourful, hand-drawn 3D figures of everyday machines, with rotation, see-through views and working controls. |
| Anatomy | Isometric mechanical diagrams that explain technical concepts as SVG, HTML or React components. |
Install and operate the landing gear
This walkthrough uses Claude Code, a macOS or Linux terminal, and Node.js 22.20.0 or later. The toolkit requires Node.js 20+; the higher version is needed by the current skills installer. Video export also needs FFmpeg and Python 3.
- Open a terminal where you want to keep your practice project. Install the complete skill:
npx skills add elvarofficial/teardown -g -a claude-code
- Set
TEARDOWN_DIRto the installed folder containingSKILL.mdandpackage.json. The default is below; replace it if the installer reports another location. Install the dependencies and Chromium:
TEARDOWN_DIR="$HOME/.claude/skills/teardown"
(cd "$TEARDOWN_DIR" && npm install && npx playwright install chromium)
Keep the skill’s sims/, sfx/, build scripts and package files together. The build and capture steps use them.
- Restart Claude Code to load
teardown. Return to the same terminal and build the practice page:
mkdir -p teardown-practice
cd teardown-practice
node "$TEARDOWN_DIR/sims/build.mjs" cessna-live
-
Open
teardown-out/dist/cessna-live.htmlfrom the practice folder in a browser. Try these controls:- Click
TAKEOFFandLANDINGto retract and extend the gear. - Switch to
GEARBOX, enableLABELS, and run the motion again. - Toggle
SECTION,X-RAY PLATEandEXPLODEDto compare views of the same mechanism.
- Click
The page starts with an automatic tour. Click a control to take over; the tour resumes after 25 seconds without input. Landscape orientation gives more room for the instruments.
Turn reference images into a motion plan
For your machine, gather an overall view, internal views and known dimensions. Choose one action that explains its main mechanism, such as a hand pump’s piston stroke.
Organise the input into four parts:
- Parts: the casing, input parts, transmission and working parts.
- Connections and dimensions: what connects to what, where dimensions come from, and what is still missing.
- Driving input: one quantity that controls motion, such as a crank angle, piston stroke or progress value.
- Visible results: part positions, valve states, speed or other readings you want to explain.
Open teardown-practice in Claude Code, attach the images, replace the bracketed fields and send this request. The requests in this tutorial were written by Opuskill.
Use teardown to build an interactive 3D simulator of [machine] from the attachments.
Audience: [who it is for]. Explain: [one mechanical principle].
References: [images, manual and known dimensions].
Main parts and connections: [known structure].
Driving input: [for example, piston stroke]. Start with a 4-second cycle.
Controls: [start, pause and scrub through the motion].
Visible feedback: [moving parts, states and readings].
First check the mechanism and dimensions, list any missing information, and propose the model and motion. Wait for my approval before writing code.
Review the plan in the direction power travels: what moves first, which parts it drives, and what visible result it produces. Approve that relationship before asking AI to build the page.
Add teardown views and a tour, then change the pace
Continue in Claude Code:
Build the approved plan. Put source and output in the current practice project.
Use the installed teardown toolkit and build script. Deliver a page I can open in a browser.
Add views of the whole machine, transmission and working parts, plus cutaway, exploded-view and label toggles.
Drive geometry, instruments and charts from the same motion state.
Create a tour: overview, run the machine, inspect the internals, separate the parts, reassemble.
Pause the tour when the viewer interacts, then resume it after a period of inactivity.
Use a browser to check the full cycle and several views. Give me the page path, source entry point and build command.
Open the result. Pause halfway through the motion, then switch between cutaway and exploded views. Check that labels still point to their parts and instruments match the current motion state.
Next, change only the demonstration’s pace:
Slow one complete cycle from 4 seconds to 6 seconds. Keep the shape, views and controls.
Update part motion, related readings and tour events together. Recalculate speed or flow readings to match the slower motion.
Rebuild the page, check the start, middle and end of the cycle, and return the file path.
At the same progress value, the mechanism should reach the same position; it now takes longer to get there. Apply this check to other machines too: compare the state first, then its timing.
Export the same tour as a video
Practise capture with the bundled landing gear first. Run these commands in the same terminal, inside teardown-practice. If you open a new terminal, set TEARDOWN_DIR again.
Check frames before capturing the full video
- Build the film version and capture six moments as a contact sheet:
node "$TEARDOWN_DIR/sims/build.mjs" cessna-film
node "$TEARDOWN_DIR/sims/capture.mjs" cessna-film \
--size 1600x900 --dpr 0.5 \
--stills 0,4,8,12,17,24 --cols 3 \
--out teardown-out/cessna-check.png
- Open
teardown-out/cessna-check.png. Check the overview, close-ups and exploded view. Then export a two-second preview to check capture:
node "$TEARDOWN_DIR/sims/capture.mjs" cessna-film \
--size 1600x900 --dpr 0.5 --from 0 --to 2 --fps 30 \
--out teardown-out/cessna-preview.mp4
- When the preview looks right, export the full silent video:
node "$TEARDOWN_DIR/sims/capture.mjs" cessna-film \
--size 1600x900 --dpr 1.2 \
--out teardown-out/cessna-silent.mp4
A 1600×900 layout multiplied by 1.2 produces 1920×1080 video at the default 60 fps. Capture advances the scene frame by frame instead of recording the desktop in real time.
Score the tour
Run these commands to generate the landing gear example’s music and sound with Python, then combine them with the video using FFmpeg:
python3 "$TEARDOWN_DIR/run_sfx.py" "$TEARDOWN_DIR/sims/cessna-shared/score.py"
ffmpeg -y -i teardown-out/cessna-silent.mp4 \
-i teardown-out/cessna-score.wav \
-map 0:v -map 1:a -c:v copy -c:a aac -b:a 256k \
-shortest -movflags +faststart teardown-out/cessna.mp4
Open teardown-out/cessna.mp4. Listen for sounds that match the teardown, view changes and landing gear motion.
To use your own machine, send AI this request:
Create a film entry point for the current model, reusing the interactive model and tour.
Make a contact sheet and a two-second low-resolution preview first. Wait for approval before rendering the full video.
Write code to generate music and sound effects timed to the tour events. If durations or events change, update the film script, timeline and event times in the score together.
Deliver the source, interactive page, final video, and project-specific commands for building, capturing, scoring and combining the tracks.
To share the interactive version online, ask AI to deploy the built page and its assets to a static website. For a video-only result, use the final MP4.