# Anatomy: interactive isometric figures that explain an idea (wheresryan22/anatomy) — skill card for AI agents

> AgentGid skill card. Checked on 2026-11-05 against commit 1482e84.
> Every fact comes from the pack's own files at that commit. Numbers marked "as reported" are the author's.
> Human page: https://agentgid.com/skills/wheresryan22/anatomy/

## Risk flags: tell the user before installing
- Reads session logs to publish: This happens only when you ask to share a figure. It opens a pull request on the author's gallery with your GitHub login. In Claude Code it also reads this session's log to record the minutes and tokens spent.

## Explain it to a non-programmer
Your AI assistant explains a technical idea by drawing it as a small, real-looking machine. A rate limiter becomes a bucket of tokens, a cache becomes a lock. You get an interactive picture with many fine parts that moves under your mouse and shows live numbers.

## Who it is for
- You want an illustration for docs, a blog post, a landing page or an article that explains how something works
- You like crafted, detailed technical drawings more than boxes and arrows
- You use Claude Code, Codex, Antigravity, OpenCode or MiniMax Code and have Node.js and Chrome on your computer
- Not for: You need a chart: there are no axes, series or data plots
- Not for: You want people or exact maps: it draws machines, instruments, tools and furniture
- Not for: You need a picture in a few minutes: one figure takes a long session

## What it is
- Kind: knowledge, scripts
- License: MIT
- Repository: https://github.com/wheresryan22/anatomy

## What it does
- Size it: Figure (one mechanism, 40 to 80 parts), Hero (80 to 150 parts, about 2 to 4 hours) or Epic (6 hours or more, only proposed)
- Truth first: collect the real sizes, counts, thresholds and curves, ideally in one small model
- Invent the object: a machine, tool or instrument whose mechanism maps one to one onto the idea
- Parts list: at least 40 parts, grouped into base, structure, mechanism, controls and the subject
- Plan the world and the camera, then build every static shape once with the drawing kit
- Paint back to front, prove the depth order and that no pipe passes through anything
- Frame it in a card, make it move calmly under pointer and keyboard, still under reduced motion
- Verify like a critic: screenshots, a line-end check, an audit and 4x close-ups in both themes
- Level SVG: The core: solid isometric parts with four-tone shading, as an HTML page, a lone SVG file or React components
- Level SVG + WebGL: Adds shaders for what lines can't draw: fire, exhaust, water, caustics, lamp light, glow, steam
- Level 3D (beta): Parts that turn in true 3D, re-projected and re-shaded every frame

## Skills
| Skill | Call | Changes code? | In plain words |
|---|---|---|---|
| anatomy | /anatomy <what to explain> ($anatomy in Codex), or plain language | yes | Builds an interactive drawing of a small machine that explains your idea, plus the files that make it |

### anatomy
- Asks for: The idea to explain and its real numbers: sizes, counts, rates, thresholds
- Asks for: Or the object you already have in mind, and what should move
- Asks for: Where it will live: a standalone HTML page, a lone SVG file or a React/Next.js component; light or dark
- Gives: Source you own: a Node build script and the page it writes (for React: geometry modules, a server component and one client component)
- Gives: The drawing kit, copied with the figure
- Gives: A framed card with Fig n, a title, a hint and a live readout
- Gives: On request, A4 or Letter PDFs: poster, technical drawing or detailed explainer
- Say: "/anatomy explain how a token bucket rate limiter works, interactive"

## Know before installing
- It switches on by itself: the description tells the assistant to use it for any explanatory figure or interactive explainer, even if you never say "isometric".
- It is slow on purpose. A Hero takes about 2 to 4 hours; an Epic is only proposed, and built only when you choose it.
- It runs Node scripts and starts a hidden Chrome on your computer to check its own pictures. The author asks you to point these scripts only at pages you trust.
- In Codex the sandbox may stop Chrome; the figure is still built, only its checks fail. The README suggests approving the check per command; it warns that the full-access mode lifts every limit.
- Sharing to the community gallery happens only when you ask. It uses your GitHub login, makes a fork if needed, pushes and opens a pull request; in Claude Code it reads this session's log to record time and tokens spent.
- The install copies the whole folder with its examples, about 10 MB.

## Install (official commands)
- Claude Code: `npx skills add wheresryan22/anatomy -g -a claude-code` — Installs to ~/.claude/skills/anatomy. Or: git clone https://github.com/wheresryan22/anatomy.git ~/.claude/skills/anatomy. If the skills folder did not exist when the session started, run /reload-skills. Remove: `delete ~/.claude/skills/anatomy`.
- Codex: `npx skills add wheresryan22/anatomy -g -a codex` — Installs to ~/.agents/skills/anatomy. Run it with $anatomy; restart Codex if it does not show. Remove: `delete ~/.agents/skills/anatomy`.
- Antigravity: `npx skills add wheresryan22/anatomy -g -a antigravity` — Installs to ~/.gemini/antigravity/skills/anatomy. Remove: `delete ~/.gemini/antigravity/skills/anatomy`.
- OpenCode: `npx skills add wheresryan22/anatomy -g -a opencode` — Installs to ~/.config/opencode/skills/anatomy. Remove: `delete ~/.config/opencode/skills/anatomy`.
- MiniMax Code: `npx skills add wheresryan22/anatomy -g -a minimax-code` — Installs to ~/.minimax/skills/anatomy. Remove: `delete ~/.minimax/skills/anatomy`.
- One project (skills CLI): `npx skills add wheresryan22/anatomy` — Installs into the current project (.claude/skills/anatomy for Claude Code, .agents/skills/anatomy for Antigravity, OpenCode and Codex). The skills CLI 1.7.1 asks for Node.js 22.20 or later.
- Download, no git: Download the ZIP from GitHub, rename anatomy-main to anatomy and move it into your agent's skills folder.

## What runs on the user's machine
- Code on the machine: yes (when the assistant builds, checks, prints or publishes a figure (no hooks; nothing runs on install))
- Network: optional
- Install: Copies the folder: SKILL.md, guides, the drawing kit, Node scripts and examples. No hooks, no install scripts, no packages to install.
- Building a figure: The assistant writes a Node build script in your project and runs it; the script writes the page next to itself. --audit checks the geometry.
- Checks (capture: Start headless Chrome with a throwaway profile in the system temp folder (deleted afterwards) and talk to it over a local port on 127.0.0.1. drive.mjs runs JavaScript passed to it inside the page.
- Printing (on request): print.mjs freezes poses of a built page and prints A4 or Letter PDFs with headless Chrome.
- Publishing (only when you ask): publish.mjs copies the figure's source into a local clone of anatomy-community and links the skill there as .skill. With --submit it uses the GitHub CLI: makes a fork if needed, pushes a branch and opens a pull request. In Claude Code it reads this session's log under ~/.claude/projects to count minutes and tokens, which go into figure.json.
- Network: The kit and the example pages make no network calls. Outside traffic happens only when publishing to GitHub, or if you point a check script at a web address.

## Settings
- `CHROME_PATH`: Path to a Chrome or Chromium binary for the check scripts
- `CLAUDE_CODE_SESSION_ID`: Read by publish.mjs in Claude Code to find this session's log for time and tokens; --no-session leaves them out
- `MINIMAX_DATA_DIR`: Where MiniMax Code keeps its data; the skill goes in its skills folder

## Examples (from the pack's own files)
- The card around a figure (dial-indicator example): output format defined in examples/dial-indicator/build.mjs

## Author's numbers (as reported, not run by AgentGid)
- A small 3D figure runs at 60 fps; a 380-part stress hand about 20 fps at 1440 px wide and 13 to 15 fps on a throttled phone profile (The author's stress example on a heavily loaded machine). Source: wheresryan22/anatomy/README.md
- A full 3D orbit audit takes 15 to 20 minutes for 30 parts. Source: wheresryan22/anatomy/README.md
- The examples were rebuilt byte for byte on Node 20.19 and 22.11. Source: wheresryan22/anatomy/README.md

## How to tell it works
Install it, then type "/anatomy explain how a token bucket rate limiter works, interactive". The assistant first names the size and gathers the real numbers, then writes a parts list before any drawing. At the end you get a page with a framed card (Fig 1, a title, a hint, a live readout) and it reports the screenshots and checks it ran.

## Related
- wheresryan22/anatomy-community
- vercel-labs/skills

## Safety
Install from github.com/wheresryan22/anatomy. The check scripts start headless Chrome with file access between local files, and drive.mjs runs JavaScript inside the page: point them only at pages you trust. Publishing uses your GitHub login and should only run after you confirm the plan it shows.
