Drawing with coding agents
The meltemi-diagrams skill teaches Claude Code, Codex, Cursor, GitHub Copilot,
Gemini CLI, Devin Desktop and other coding agents to draw diagrams as code: they write
.meltemi files, validate them with the command line and fix what it reports,
instead of drawing pictures by hand. The skill holds a workflow, a template, the rules that
save iterations, references for the language, layout, themes, C4, sequence diagrams, free
compositions, stories and converting, and complete examples.
One prompt
Paste this into your coding agent, in your project. The agent reads the setup prompt, installs the skill for the agents your project uses, draws a small sequence diagram of one of its flows, validates it until no diagnostic remains and tells you where the SVG is.
Set up Meltemi Diagrams in this project so you can draw diagrams as code, and prove it works — you'll need terminal access on this machine and Node 22.12 or later. First read https://diagrams.meltemi.dev/agent-setup/prompt.md and follow it. Install the meltemi-diagrams skill for the coding agents this project uses (ask me if it's unclear which) with `npx @meltemi/diagrams-cli@latest skill install`. Then prove it: write a small sequence diagram of one flow of this project, validate it until no diagnostic remains, export the SVG, and show me the validation's last line and where the SVG is. Never sign in to the cloud, never print or commit a token, and don't commit or change my project's configuration beyond the skill folders without asking me first.
The setup prompt needs the command line 1.10.0 or later; an agent that finds an older one
says so and stops. An agent without web access prints the same text with
npx @meltemi/diagrams-cli@latest skill prompt.
Installing the skill yourself
In your project's folder, without installing anything:
npx @meltemi/diagrams-cli@latest skill install --agent <names>
Or install the command line once, and run mdg skill install in each project:
npm install --global @meltemi/diagrams-cli
<names> is one or more names of the table, separated by commas, or
all, the default, for both folders. A folder several agents share is written
once. --user writes your own folders (~/.claude/skills,
~/.agents/skills), for every project. A copy already there is kept unless you
add --force, which replaces only the skill's own folder. The command writes
skill folders only, never AGENTS.md, CLAUDE.md or another file of
the project.
| Agent | Name | Folder |
|---|---|---|
| Claude Code | claude |
.claude/skills |
| Codex | codex |
.agents/skills |
| Cursor | cursor |
.agents/skills |
| GitHub Copilot | copilot |
.agents/skills |
| Gemini CLI | gemini |
.agents/skills |
| Windsurf | windsurf |
.agents/skills |
| Devin Desktop | devin |
.agents/skills |
| Any other agent that reads the cross-agent folder | agents |
.agents/skills |
What the agent proves
It writes one real flow of your project as a small sequence diagram under
diagrams/, or the sign-in of mdg init --template sequence in a
folder with no code to read. It validates the sheet until the last line reads
Checked 1 file: 0 errors, 0 warnings., exports the SVG beside it and tells you
that line, where the SVG is and which folders the skill went to.
What it never does
- Print, read, copy or commit a token (an
mdg_…value). - Sign in, push, pull, publish or run any other cloud command unless you ask for it.
- Commit or stage anything, or change your configuration, CI or agent instruction files beyond the skill folders, without asking you first.
- Add
--forceor--useron its own. - Install or download Node or any other tool on its own.
-
Draw a picture by hand, edit an exported SVG or retype a Mermaid or PlantUML source, which
mdg importconverts.
More
- The setup prompt, the text the agent follows.
- The documentation for agents, with how to ask for a diagram.
- The playground, to write and export diagrams in your browser.