figure
Skill1 starsChanged 23 days agoMITView on GitHub
Use when drawing a hand-drawn workflow, architecture, block or pipeline diagram of an AI or computer-vision model or system for docs, a paper or slides (high-level, low-level, system pipeline, the whole model in numbered module panels, or what changed between two versions of a model), annotating, translating or exporting such a figure, or rebuilding one with another font.
7 other projects use a version of this.
Adopted by
Most recently taken up by
- piabrota/gramaticotheir own version, first seen Nov 15, 2026
- DaeSeokSong/oh-my-ouroborostheir own version, first seen Nov 1, 2026
- Muuuun/luxastheir own version, first seen Oct 12, 2026
- vectorize-io/hindsighttheir own version, first seen Oct 8, 2026
- devskale/skale-skillstheir own version, first seen Oct 2, 2026
- denismrvoljak/claude-scholartheir own version, first seen Aug 16, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- vectorize-io/hindsight★ 61ksame name
- Muuuun/luxas★ 1.2ksame name
- richard-kim-79/archora-skills★ 49same name
- piabrota/gramatico★ 7same name
- DaeSeokSong/oh-my-ouroboros★ 3same name
- devskale/skale-skills★ 2same name
- denismrvoljak/claude-scholar★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 38
Ask and plan: Read ${CLAUDE_SKILL_DIR}/references/guide.md, then ask only the questions whose answer changes the figure, in one message, …
- Very specific: line 62
Never edit files under ${CLAUDE_SKILL_DIR}/ from a user project.
- Distinctive: line 64
Do not commit cached fonts or scratch PNGs, and do not restyle a committed figure unasked.
“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Figure
A figure is one spec file (<name>.figure.js) built into one self-contained HTML file in the rough.js hand-drawn
style. The kit draws the boxes, arrows and icons and checks the layout; the spec says what to draw and where. Every
shape, count, name and hyperparameter is read from the code or config it describes in this session, never from
memory; a fact you cannot confirm is left out or labelled UNVERIFIED, and listed in the final message.
Needs Python 3.10 or later and, for the check, Chrome or Chromium (google-chrome, chromium, or CHROME set to
the binary; a snap Chromium cannot read /tmp or hidden folders, so use a visible folder under home). The default
font is bundled, so a build works offline.
Choose the mode
| Mode | Shows | Boxes | Connectors (max) | Starter |
| High-level model | Blocks and the data between them | 4 to 7 | 8 | high-level.figure.js |
| Low-level model | Modules, tensor shapes, skip and fusion paths, losses | 10 to 20 | 24 | low-level.figure.js |
| System pipeline | Services, stores, queues, phases | 8 to 16 | 20 | pipeline.figure.js |
| Whole model or system | Every component in numbered module panels | 6 to 10 panels, 40 to 80 boxes | 30 | whole-model.figure.js |
| Model delta | What changed between two versions: before, numbered changes, after | up to 8 parts per side | 10 per side | delta.figure.js |
With no mode named, use high-level for "the model" and pipeline for "the system". Use delta only when asked what changed between two versions; a change of hyperparameters alone is a table, not a figure. Name the mode in the final message. Over budget a figure reads as a wall: merge repeated blocks into one box with a count, fold a module's internals into one box, drop side outputs, then split into an overview and one detail figure per module.
Workflow
- Read the facts from the model code and configs the user named; note the file each shape, count and name comes from. If you cannot read them (the path is wrong, or the code is not in the project), say so, ask for the path or the facts, and stop: give no block, layer name, shape or count, not even as an example or a draft plan.
- Ask and plan. Read
${CLAUDE_SKILL_DIR}/references/guide.md, then ask only the questions whose answer changes the figure, in one message, with defaults; give the mode, canvas, boxes, and what you merge or leave out, every box taken from what you read in step 1. - Start from the starter. Copy it from
${CLAUDE_SKILL_DIR}/templates/to the output folder as<name>.figure.js, keepFIGUREanddraw(k), and put the sources and build command in the header comment. For a whole-model, notes or translated edition read${CLAUDE_SKILL_DIR}/references/house-style.md; every helper, kind, icon and font is in${CLAUDE_SKILL_DIR}/references/kit.md. Build and check.
python3 "${CLAUDE_SKILL_DIR}/scripts/build_figure.py" <dir>/<name>.figure.js <dir>/<name>.html python3 "${CLAUDE_SKILL_DIR}/scripts/check_figure.py" <dir>/<name>.html --png <scratch>/<name>.pngThe check prints every layout issue and exits 1 on one; fix each in the spec, rebuild and recheck. For a paper or slide add
--bare,--scale 2and--svg <dir>/<name>.svg. Fixes for each message are in${CLAUDE_SKILL_DIR}/references/troubleshooting.md.- Look at the PNG with the Read tool for what the checker cannot see: an arrow pointing the wrong way, an icon too small or on text, a label the code does not support. Fix, rebuild and look again.
- Report the mode, the HTML and PNG paths, the defaults used and any unconfirmed fact, plus "Merged: ..." and "Left out: ...", and alt text for the PNG. Commit only when the user asks.
Constraints
- Never edit files under
${CLAUDE_SKILL_DIR}/from a user project; a figure that needs a new helper defines it in its owndraw(). - Do not commit cached fonts or scratch PNGs, and do not restyle a committed figure unasked; build the new one beside it.
- State the licence of any font other than the bundled Patrick Hand (OFL); Stay With Me is personal use only.
- Deliver exactly the figures asked for. To publish icons or figures to a design library the user runs
/design-sync.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

