Skip to content
Agents tracked: 502 Releases (7d): 613 Agent status: 4 with issuesSince last limit reset: Claude 7d · Codex 5d For AI agents: Markdown Updated Nov 18, 2026

Anatomy: interactive isometric figures that explain an idea

wheresryan22/anatomy

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.

Pack description by its author: “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.”

Design and frontendKnowledge and rules for your assistantGives your assistant new abilities with scripts

GitHub

Checked against the pack's files at commit 1482e84, on Nov 5, 2026. Tap a verdict to see its source.How we checkedReport an error

Read 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. source
Knowledge and rules for your assistantGives your assistant new abilities with scripts

Good for you if

  • 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

Probably not for you if

  • You need a chart: there are no axes, series or data plots
  • You want people or exact maps: it draws machines, instruments, tools and furniture
  • You need a picture in a few minutes: one figure takes a long session

What you'll notice

  • It first says how big the figure is: Figure, Hero (about 2 to 4 hours) or Epic, which it only proposes
  • It collects the real numbers and writes a parts list before drawing
  • A framed card: Fig 1 at top left, a title, a hint and a live readout
  • It opens the page in a hidden Chrome window and studies close-up screenshots of every joint

What you need

  • Claude Code, Codex, Antigravity, OpenCode, MiniMax Code
  • Free, MIT license
  • One command with the skills tool, or copy the folder into your skills folder
  • Needs Node.js 20.10 or later, and Chrome or Chromium for the checks. React 18+ only for React output.
Words on this page
Skill
A set of written instructions your AI assistant follows. Installing one is like giving it a playbook.
CLI
A program you run by typing commands in a terminal.
Repositorywheresryan22/anatomy · website
Also on AgentGidAnatomy as an agent: usage, releases and alternatives
GitHub stars27,378
Skills1
CategoryDesign and frontend
LicenseMIT
Last updatedOct 18, 2026 · card checked Nov 5, 2026 at commit 1482e84
Install countswheresryan22/anatomy on skills.sh, Vercel's skills directory, which shows installs and security audits per skill

wheresryan22/anatomy popularity over time

Most starred skill packs

wheresryan22/anatomy: GitHub starstotal over time 27,378
wheresryan22/anatomy: new stars per weekGitHub 1,286

What Anatomy does

Before writing anything, the assistant takes the first option that fully works:

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

From the pack's SKILL.md files, summarised by AgentGid.

The skill, explained

anatomy

Builds an interactive drawing of a small machine that explains your idea, plus the files that make it

You give

  • The idea to explain and its real numbers: sizes, counts, rates, thresholds
  • Or the object you already have in mind, and what should move
  • Where it will live: a standalone HTML page, a lone SVG file or a React/Next.js component; light or dark

You get

  • Source you own: a Node build script and the page it writes (for React: geometry modules, a server component and one client component)
  • The drawing kit, copied with the figure
  • A framed card with Fig n, a title, a hint and a live readout
  • On request, A4 or Letter PDFs: poster, technical drawing or detailed explainer
Say: “/anatomy explain how a token bucket rate limiter works, interactive”

Its rules, in pictures

The page it plans

1 Fig n (top left)
2 Short title (top right)
3 The figure, about 55–65% of the card
4 Interaction hint (bottom left)
5 Live readout (bottom right)
6 Legend keys and a true caption under the card

Fonts it uses

ui-monospaceuses
SF Monouses
Menlouses
Consolasuses

How things move: its curve against a plain one

cubic-bezier(.32,.72,0,1), 500ms
linear, for comparison

Drawn by AgentGid from the values in the skill's files. This is not output of the skill; sample text is ours.

See it in action

The skill defines what its answer looks like. Its own example:

fig:     Fig 1
title:   Dial indicator
hint:    Hover to slide the carriage
readout: block 1 · reads <height> px
caption: A dial indicator on a surface plate. Slide the carriage and the plunger rides up or
         down onto the block beneath it; one turn of the needle is 20 px of travel, so every
         block reads its own height.

From examples/dial-indicator/build.mjs.

When to reach for it

You wantUse
An interactive figure that explains how a system or algorithm works/anatomy <idea and its real numbers>
A drawing of a machine you already have in mind/anatomy <the object> and what should move
FireAsk for WebGL for the effect
A dial or turntable that turns in true 3DAsk for the 3D mode (beta)
A printable handout or posterAsk for a printable version (poster, drawing or detailed)
To share a finished figureAsk it to publish the figure to the Anatomy community gallery
Try it. 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.

Skills in wheresryan22/anatomy

SkillIn plain wordsChanges files?What it does (author)
anatomy
/anatomy <what to explain> ($anatomy in Codex), or plain language
Builds an interactive drawing of a small machine that explains your idea, plus the files that make itYes Build crafted, highly detailed, interactive isometric SVG figures that explain a technical idea as a real physical object (a test rig, a dial gauge, a cabinet of drawers, a plotter, a lock), with many small precise solid parts, four-tone shading, correct painter's order, a framed card with title,…
npx skills add wheresryan22/anatomy --skill anatomy

The author's descriptions come from each skill's SKILL.md; the plain-words column is AgentGid's.

Good to know before you install

  • 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 Anatomy

Official commands from the repository

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

Or with the open-source skills CLI: npx skills add wheresryan22/anatomy. Skills are instructions your agent follows: read them before installing.

What it installs and runs on your machine

Read in the code at commit 1482e84, Nov 5, 2026

WhenWhat happens
InstallCopies the folder: SKILL.md, guides, the drawing kit, Node scripts and examples. No hooks, no install scripts, no packages to install.
Building a figureThe 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 (captureStart 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.
NetworkThe 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.

The author's numbers, as reported

AgentGid did not run these tests

  • 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
  • A full 3D orbit audit takes 15 to 20 minutes for 30 parts. Source
  • The examples were rebuilt byte for byte on Node 20.19 and 22.11. Source

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

Quick answers

Is it free?
Yes, MIT license. No API keys.
Does it send my work anywhere?
Not while building. The kit and examples make no network calls; the only outside traffic is publishing to the community gallery on GitHub, which it does only when you ask and say yes.
What do I need on my computer?
Node.js 20.10 or later, and Chrome or Chromium for the checks. React 18+ only if you want React output.
Can it make charts?
No. It has no axes, series or data plots; numbers appear as a live readout and as the true sizes of the parts.
How long does one figure take?
A long session. A Figure often finishes in well under an hour; a Hero about 2 to 4 hours; an Epic is only proposed.
Does it work in Codex?
Yes, run it with $anatomy. Codex's sandbox may block the Chrome checks; the figure is still built.

Checked by AgentGid on Nov 5, 2026 against commit 1482e84 of the pack's own files. Related: wheresryan22/anatomy-community, vercel-labs/skills. agent.md for AI agents · Report a mistake

More design and frontend skill packs

All design and frontend skills

# Skill pack Skills GitHub stars Updated
1
nextlevelbuilder/ui-ux-pro-max-skill Your AI assistant gets a local design library: UI styles, colour palettes, font pairings and UX rules for many product types. Bef…
7 150K 2026-11-14
2
Leonxlnx/taste-skill Your AI coding assistant stops building the average landing page. It picks one of 20 researched design directions, finds real, cr…
1 116K 2026-11-08
3
tt-a1i/archify Your AI assistant turns a description, a Mermaid sketch or your project's code into an interactive diagram saved as one HTML file…
5 96.5K 2026-11-15
4
cathrynlavery/diagram-design Your AI assistant draws clean, editorial diagrams in your brand colours and fonts. You describe the diagram in plain words and ge…
1 67.2K 2026-11-12
5
Nutlope/hallmark Your AI assistant builds web pages that look designed, not machine-made. It asks once for your real material and picks one of fif…
1 55.2K 2026-11-11
6
alchaincyf/huashu-design One large design playbook for your AI assistant, written in Chinese. It makes clickable app prototypes, web pages, slide decks, i…
1 29.5K 2026-11-10