Your Agent Can Write Code. Can It Draw a Diagram Your Designer Won't Hate?
You've probably asked an AI agent to sketch out an architecture diagram at some point. And you've probably gotten back something that technically communicates the idea but looks like it crawled out of a 2015 wiki page. Boxes with drop shadows. Default fonts. That particular shade of blue nobody chose on purpose. Diagram Design is an agent skill that takes a different approach: it draws diagrams as a single self-contained HTML + SVG file, styled to match your brand, across 51 diagram types.
What It Does
Diagram Design is a skill that plugs into agent hosts that read Agent Skills—Cursor, Claude Code, Codex, Qoder, GitHub Copilot, Gemini CLI, Cline, Windsurf, and Amp are all listed as compatible. You describe the diagram you want in plain words, and the agent picks the diagram type, states its plan, and writes one .html file you can open by double-clicking.
The output is a single file combining HTML and SVG—no external dependencies to chase down, no build step, no rendering service. It covers 51 diagram types, so whether you need an architecture diagram, a quadrant chart plotting projects by impact versus effort, or a sequence diagram showing token refresh on a 401, there's presumably a type for it. The README's pitch is blunt about its aesthetic ambitions: "No shadows. No Mermaid slop." You can browse the gallery to see what that actually looks like before committing.
Why It's Cool
-
The single-file output is the right call. Diagrams are the kind of artifact that gets passed around—dropped into a ticket, attached to a design doc, opened on someone else's machine. One self-contained HTML file means no broken image links and no "you need to install this to view it" conversations. Double-click and it works.
-
Brand matching is a first-class feature, not an afterthought. You can point the skill at your own site with a prompt like "Onboard diagram-design to https://yoursite.com," and it pulls your palette and fonts so every diagram after that matches. If you've ever manually tweaked hex codes in a diagramming tool to make something look like it belongs in your docs, you'll appreciate that this is handled up front.
-
It plays nice with tools you already use. There's an import path from draw.io, Mermaid, Excalidraw, and PlantUML, plus PNG and SVG export. That matters—most teams aren't starting from zero. Being able to bring existing diagrams in (or get polished ones out) makes this easier to adopt without abandoning what you've already built.
-
The install is a one-liner.
npx skills add cathrynlavery/diagram-designworks across any host that reads Agent Skills. If you're in Claude Code, there's also a plugin marketplace route that gets you updates and slash commands, including an auto-update toggle (off by default for third-party marketplaces, so you'll need to flip it).
One honest note from the README: official builds only come from this repository. The maintainer (Cathryn Lavery, via her company LittleMight) publishes the plugin directory listings, and a listing under any other name is an unofficial copy. There's also a PRIVACY.md that documents what the skill sends over the network—worth a read if you're cautious about that sort of thing.
How to Try It
- Install the skill with the one-liner:
npx skills add cathrynlavery/diagram-design
- If you're on Claude Code and want automatic updates plus slash commands, use the plugin marketplace instead:
/plugin marketplace add cathrynlavery/diagram-design
/plugin install diagram-design@diagram-design
- Ask your agent for a diagram in plain words. Some examples straight from the README:
- "Make me an architecture diagram of my app: frontend, backend, database, Redis cache."
- "I need a quadrant showing Q2 projects by impact vs effort."
- "Give me a sequence of a bearer call with token refresh on 401."
- Optional but recommended: onboard your brand so future diagrams match your site.
- "Onboard diagram-design to https://yoursite.com"
- Open the resulting
.htmlfile by double-clicking. Done.
The repo is at github.com/cathrynlavery/diagram-design, with a gallery and a changelog if you want to see where it's been.
Final Thoughts
Diagram Design is aimed at a specific frustration: agents are good at generating structure but bad at generating things that look intentional. If you're regularly producing diagrams for docs, tickets, or presentations and you care how they look, this is a sensible way to close that gap without hand-tweaking SVG every time. It won't replace a designer for complex custom visuals, and 51 types won't cover every edge case—but for the everyday diagrams that fill up engineering docs, it's a practical shortcut. The single-file output and brand onboarding are the details that make it feel considered rather than just another prompt wrapper.
Follow @githubprojects for more developer tools and open source projects.