kanban-board-mcp / hand-drawn-diagrams
AGENTS.md1 starsChanged 3 days agoMITView on GitHub
AI skill that converts natural language prompts into hand-drawn Excalidraw diagrams with hosted edit URLs, animated SVGs, and PNGs. This skill follows a strict 3-step process. Never skip steps or reorder them. Load references/activation-routing.xml and references/fundamental-shapes.md first, then one route guide from references/. Both files must exist before Step 3 begins. Deliver the full Edit URL as a clickable link. Offer animation at the end. Write to workspace only if the user specifies a path or explicitly asks.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- muthuishere/hand-drawn-diagramsword for word, first seen Apr 17, 2026
Other versions1 project uses a version of this.
Word for word · 1
- muthuishere/hand-drawn-diagrams★ 78100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
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.
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 32,671 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository24 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- .github/skills/hand-drawn-diagrams/CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- canvas-designSkill
- baSkill
- consultantSkill
- critical-thinkingSkill
- cybersecuritySkill
- debuggerSkill
- designerSkill
- doc-writerSkill
- frontend-designSkill
- git-workflowSkill
- hand-drawn-diagramsSkill
- marketingSkill
- philosopherSkill
- pmSkill
- psychologistSkill
- qcSkill
- remotion-best-practicesSkill
- setup-copilotSkill
- technical-leadSkill
- test-data-generatorSkill
- unit-testingSkill
The file
We split this AGENTS.md into the rules it gives an agent
5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 28
Write two files (in /tmp/hand-drawn-diagrams/<slug>/ by default):
- Distinctive: line 60
Use when available for PNG and animated SVG rendering:
- Distinctive: line 82
Write to workspace only if the user specifies a path or explicitly asks.
- Very specific: line 96
Run open_diagram.py — opens browser with open.html launcher.
- Very specific: line 98
If in /tmp, offer: "Want me to save the source file to your project?"
≈ “Common” is an estimate: at least 1 in 5 of the 41,581 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
AGENTS.md
Project: hand-drawn-diagrams
AI skill that converts natural language prompts into hand-drawn Excalidraw diagrams with hosted edit URLs, animated SVGs, and PNGs.
Agent Workflow
This skill follows a strict 3-step process. Never skip steps or reorder them.
Step 1 — Route (steps/step-01-route.md)
Pick one diagram type from the routing table:
| Route | Keywords |
teachers | teach, explain simply, lesson, compare, ELI5 |
ideation | brainstorm, cluster notes, opportunity map |
ux | journey, wireflow, sitemap, screen flow |
sales-funnel | funnel, drop-off, conversion, leads |
technical-explainer | architecture, API, protocol, event flow |
medical | condition, diagnosis, treatment, patient |
creative-raw | open/explicit creative mode |
page-mockup | webpage, dashboard, landing page, UI |
Load references/activation-routing.xml and references/fundamental-shapes.md first, then one route guide from references/.
Step 2 — Draw (steps/step-02-draw.md)
Write two files (in /tmp/hand-drawn-diagrams/<slug>/ by default):
diagram.excalidraw— complete.excalidrawJSON with non-emptyelementsarraydiagram.animationinfo.json— animation spec with story pattern and element order
Both files must exist before Step 3 begins.
Step 3 — Validate & Deliver (steps/step-03-validate.md)
# 1. Validate first — fix all errors before proceeding
cd scripts && uv run python validate_excalidraw.py "/tmp/hand-drawn-diagrams/<slug>/diagram.excalidraw"
# 2. Generate hosted URLs only after validation passes
cd scripts && uv run python get_excalidraw_urls.py "/tmp/hand-drawn-diagrams/<slug>/diagram.excalidraw"Deliver the full Edit URL as a clickable link. Offer animation at the end.
Tool Usage
Rendering tools (always cd scripts first, use uv run)
| Tool | When to use |
validate_excalidraw.py | Always — before URL generation |
open_diagram.py | After validation — writes open.html, opens browser, prints short local path |
get_excalidraw_urls.py | Fallback only — prints raw hosted URLs when open_diagram.py unavailable |
edit_excalidraw.py | Open diagram directly in hosted editor (legacy) |
render_excalidraw.py | PNG export (Playwright fallback) |
render_animated_svg.py | Animated SVG (Playwright fallback) |
Chrome DevTools MCP (preferred over Playwright)
Use when available for PNG and animated SVG rendering:
mcp__plugin_chrome-devtools-mcp_chrome-devtools__new_pagemcp__plugin_chrome-devtools-mcp_chrome-devtools__navigate_pagemcp__plugin_chrome-devtools-mcp_chrome-devtools__wait_formcp__plugin_chrome-devtools-mcp_chrome-devtools__evaluate_script(extract SVG)mcp__plugin_chrome-devtools-mcp_chrome-devtools__take_screenshot(PNG)mcp__plugin_chrome-devtools-mcp_chrome-devtools__close_page
Excalidraw MCP (for checkpointing)
mcp__claude_ai_excalidraw__export_to_excalidrawmcp__claude_ai_excalidraw__create_viewmcp__claude_ai_excalidraw__save_checkpoint/read_checkpoint
File Location Rules
| Artifact | Default location |
.excalidraw | /tmp/hand-drawn-diagrams/<slug>/diagram.excalidraw |
.animationinfo.json | /tmp/hand-drawn-diagrams/<slug>/diagram.animationinfo.json |
.animated.svg | User's current project/workspace directory |
.png | User's current project/workspace directory |
Write to workspace only if the user specifies a path or explicitly asks.
Diagram Rules
- Monochrome by default — no fills unless essential for clarity
- Sketch font — same font across all elements
- 1–5 word labels — never write sentences or paragraphs inside shapes
- No floating arrows — bind with
startBinding/endBinding - Bind text to containers — use
containerId+boundElements - One concept per box — split instead of cramming
- Non-overlapping layout — use grid from
references/element-templates.md
Delivery Pattern
- Run
open_diagram.py— opens browser withopen.htmllauncher. Deliver the printed local path as[Open diagram](file:///tmp/.../open.html). Never paste the raw hosted URL — it is too long to be usable. - Offer: "Want a video version? I can render it as an animated diagram (~10s)"
- If in
/tmp, offer: "Want me to save the source file to your project?" - PNG only if user explicitly asked for an image
Critical Rules
- Never render before the
.excalidrawfile exists and validates clean - Never run
get_excalidraw_urls.pybeforevalidate_excalidraw.pyexits 0 - Never write source files to the user's workspace without being asked
- Always write
.animated.svgto the user's workspace (it is the video deliverable) - Never skip or reorder the 3 steps — even if video was the original request
Testing
cd scripts
uv run pytest # full test suite
uv run pytest -m "not slow" # skip Playwright/Chromium browser testsReferences
references/index.md— index of all reference documentsreferences/activation-routing.xml— full routing rulesreferences/fundamental-shapes.md— shape vocabularyreferences/json-schema.md—.excalidrawJSON formatreferences/element-templates.md— grid layout + element templatesreferences/animation-spec.md— animation story patternsreferences/quality-checklist.md— diagram quality criteria
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.

