I Gave Claude Code One Line, Ten Times: Tesla Coil, Water Pump, Escapement (Anatomy Skill)

Author: Prompt Engineer 48 · Watch on YouTube

Video authored by the channel shown, not by IANIA; all rights belong to the creator. Transcript and summary generated automatically; the original-language content is preserved.

Original language: English

Original video: I Gave Claude Code One Line, Ten Times: Tesla Coil, Water Pump, Escapement (Anatomy Skill) · Channel: Prompt Engineer 48 · 06:42 · Watch on YouTube

Topics: AI agents, Claude Code, Software engineering with AI, Open source and software ecosystems

Summary

The video tests the open-source Anatomy skill, which lets Claude Code turn a one-line description into an interactive machine illustration. The presenter explains its figure types, installation, and safety checks, then demonstrates five builds using the default model and five more using Opus with the skill’s checks enabled. The examples include a Bunsen burner, a connection pool, a hydraulic ram pump, an escapement, and a Tesla coil, with reported build times and audit results. The presenter cautions that these are first drafts, none of the ten ran the full geometry audit, and they should not be published without further verification.

Key points

Anatomy is an open-source skill that turns a described idea or machine into an interactive illustration made from small parts.
It supports plain SVG, SVG with WebGL effects, and a beta 3D mode.
The presenter installed it with one command and reports that the security assessment found no API keys or npm dependencies.
The Bunsen burner took about four minutes to build, but had roughly 25 parts rather than the skill’s 40–80 target and did not run the audit.
Four default-model examples—a token bucket, connection pool, CDN edge cache, and espresso machine—took between 2 minutes 41 seconds and 6 minutes 33 seconds.
Five Opus builds with checks enabled took 8 to 17 minutes each; the presenter reports line checks with zero loose ends for the cash lock and Tesla coil.
The hydraulic ram pump used WebGL water, while the escapement’s model was checked in Node before drawing.
None of the ten builds ran the full geometry audit, so the presenter describes them as first drafts rather than publish-ready work.
The presenter recommends naming the idea, providing real numbers, specifying what should move, and stating the intended output format and theme.

Chapters

Start	Chapter	Summary
00:00	Introducing Anatomy and its figure types	The presenter introduces ten machine builds and explains Anatomy’s purpose, supported figure types, and installation.
01:32	Safety checks and the first build	After describing the security assessment and headless setup, the presenter tests a Bunsen burner and notes what the first draft omitted.
03:04	Four builds with the default model	The presenter shows a token bucket, connection pool, CDN edge cache, and espresso machine, including their behavior and build times.
04:07	Five Opus builds with checks	The cash lock, load balancer, hydraulic ram pump, escapement, and Tesla coil demonstrate the more detailed results and reported checks.
06:11	Limitations and prompting advice	The presenter stresses that the builds lack full geometry audits, shares prompting recommendations, and wraps up the demonstration.

Quotes

you describe an idea or a machine, and Claude invents a physical object whose working is the concept. — 00:30

So, this is a first working pass. — 02:34

Opus took 8 to 17 minutes each against under seven for the default model. — 05:40

Mine are good first drafts. — 06:11

none of my 10 ran the full geometry audit, so I would not publish them as they are. — 06:11

Concepts and entities

Anatomy, Shrine22/Anatomy, Claude Code, Opus, WebGL, Ryan, Raptor engine

Full transcript (original language)

00:00 All right. In this video, we will see 10 machines, and every one of them was built by Claude Code from a single line on my own PC. A Tesla coil with a plasma arc, a hydraulic ram pump with real water, a pendulum escapement, a load balancer, a cash lock, an espresso machine, and more. They all come from one open-source skill called Anatomy. Let’s go ahead and see how it works. So, this is the repo where Shrine22/Anatomy. If you look here, it’s MIT license, about 3,000 stars, 230 forks, and the

00:30 first release 1.0 only went out on the 10th of October. So, this is very new. What it does is you describe an idea or a machine, and Claude invents a physical object whose working is the concept. A cash key that skips work becomes a pin tumbler lock, then it builds that object out of dozens of small shaded parts inside an interactive card with a live readout. There are three kinds of figure. The first is plain SVG, solid isometric parts. The second is SVG plus WebGL for what lines can draw, fire,

01:00 exhaust, water, and the shader sits inside the drawing in the same camera. And the third is 3D, which the readme marks as beta, where a dial or a hand actually turns in three dimensions. And mind you, it says it draws machines and instruments. It is not a chart library. Now, for installing, it’s one command, NPX skills add Code. I’m doing the project install, so it goes into .claude-skills anatomy inside this folder only. And you can see the security assessment it

01:32 prints here. Gen says safe, socket says zero alerts, Snyk says low risk, no API keys, and nothing to npm install. It uses only Node’s built-in modules. Now, the way I’m running it, instead of typing into the chat, I’m calling Claude Code headless Claude -p with /anatomy in the prompt, and I’m only allowing it to read, write, edit, and run Node. The first prompt is straight from the project’s evals, a Bunsen burner on a lab bench opening the air collar turns the lazy yellow flame into a roaring

02:03 blue cone. WebGL for the flame light theme. One thing before it draws anything, the skill makes Claude size the job first and say so. A figure is 40 to 80 parts and about 30 to 90 minutes. A hero is 80 to 150 parts, 2 to 4 hours, and an epic is 6 hours or more. And the skill says, do not start it, give the estimate and propose a hero instead. I asked for a figure, the smallest. And you can see the result. This is a single HTML file, about 128 kilobytes, with the

02:34 collar closed air 0%. The flame is a lazy yellow teardrop. Move across the figure and at air 100% it turns into a narrow blue cone and the readout at the bottom changes with it. The whole thing took about 4 minutes on my machine, which is a lot less than the half an hour the skill estimates for a figure. Now, to be honest, Claude itself told me what it skipped. It built roughly 25 parts. The skill’s own target is 40 to 80. It did not run the audit and without WebGL there is no flame at all. So, this is a first working pass. So, I tried

03:04 four more at the same time, each in its own folder with the same skill, a token bucket rate limiter, a database connection pool, a CDN edge cache, and a heat exchanger espresso machine. The token bucket is a column of coins with a capacity of eight and a feeder that refills it. Each request pushes a coin out and when the column is empty, the request is rejected. That took 2 minutes 47 seconds. The connection pool is a block of 10 base. When all 10 are busy, new requests wait in the queue in arrival order. 2 minutes 41 seconds. And

03:36 mind you, this is the dark theme and it is quite dim on screen. The CDN edge cache has a dial where one turn is the 60-second TTL. A fresh crate on the shelf is a hit and an expired one sends the request on to the origin. 2 minutes 46 seconds, and dark theme again, so again dim. And the espresso machine, water goes from the tank through a pump into a coil in the boiler and up to the group head. The pump needle goes from three bar pre-infusion to nine bar. 6 minutes 33 seconds, the longest of these

04:07 four. Now, all of those used the default model, so then I ran five more, and this time I told Claude Code to use Opus with one extra instruction, run the skills own checks and fix what they find. Let’s see what that changed. First, a cash key as a pin tumbler lock. Five pin stacks stand for the five fields of the key. When every pin meets the shear line, the plug turns and nothing is redrawn. If one pin is off, it turns red, the plug jams, and the screen redraws. 8 minutes and the line check came back with zero loose ends out of 262.

04:38 Second, a round-robin load balancer. A shuttle on a rail carries each request to the next server whose top pin is raised. A checker pings every server, and after two miss checks, the pin drops, the lamp goes red, and the other three take one and three. I’m pulling plugs with the number keys. 8 minutes. Third, a hydraulic ram pump. The WebGL water is drawn in the same camera as the drawing, so it passes in front of and behind the parts. The valve slams, a slug goes up through the check valve, and the readout shows beats per minute and liters per minute, which change as I

05:09 move the valve stroke. 13 and 1/2 minutes. Fourth, an anchor escapement. A weight turns a 32-tooth wheel, and the pendulum rocks the anchor so the wheel moves one tooth per swing. Claude checked the model in node before drawing anything. 6 seconds of swinging gave exactly six ticks. I’m changing the bob height with the arrow keys. 17 and 1/2 minutes, the longest. Fifth, a Tesla coil. The spark’s reach follows the 1.7 times root P rule, so when the gap is shorter than the reach, a violet WebGL arc strikes the ball, and when it’s

05:40 longer, you only get streamers. I’m sliding the rod and raising the power. 11 and 1/2 minutes, zero floating line, ends out of 927. So, Opus took 8 to 17 minutes each against under seven for the default model. The cost Claude code reported was between about two and five dollars per run on my account, and you can see what it bought. Real water, a plasma arc, a 32 wheel, and all five passed the line check. Now, compare with the project’s own examples. The Raptor engine ships with an audit that proves no pipe passes

06:11 through anything in every frame. Mine are good first drafts. There’s our hours of verification. So, the honest part, it is slow on purpose. The 3D mode is beta, and it needs node 20.10 and Chrome for its checks. And none of my 10 ran the full geometry audit, so I would not publish them as they are. If you want better results, the readme gives three habits. Name the idea, not the drawing, and give the real numbers like 10 connections or 60 seconds, or name the object and say what should move, and say where it will

06:42 live. A standalone HTML page, a lone SVG, or a React component, light or dark. That is how the connection pool and the Syrian prompts were written. So, in this video we have seen how to install Anatomy with one command, and how one line becomes a machine you can poke at 10 times over. If you’re interested, you can go ahead and try this out on your own system as well, and let me know how it goes. Credit to Ryan for building Anatomy, and the promo clip is his. I’ll see you in another one. Check out the next video.