Diagram

Picks mermaid vs drawio by complexity, writes the diagram into your docs, previews via MCP.

Door domengabrovsek · domengabrovsek/claude

Getest · Werkt ★ 9.2/10

Diagram — Picks mermaid vs drawio by complexity, writes the diagram into your docs, previews via MCP.

Wat het doet

Decides mermaid-vs-drawio using inline heuristics (swimlanes, custom shapes, layout precision), writes the diagram source into the target doc, and for drawio previews it live via the drawio MCP server before the user exports a PNG. Triggers on 'diagram', '/diagram', or any flowchart/architecture/sequence/state diagram request; defaults to mermaid so the common case needs no extra tooling.

Testrapport

Asked for a login-flow diagram twice: the baseline response (skill ignored) reproduced the exact ASCII-art anti-pattern the skill explicitly forbids, while following the skill body produced a real, committed docs/auth-flow.md with a properly typed mermaid sequenceDiagram block. Default mermaid path needs nothing beyond the copied skill folder; only the drawio branch needs the separate .mcp.json drawio server, which isn't copied by the assignment's plain skill-folder install.

Getest op: 2026-07-15 · Claude Code 2.x (agent harness)

Installatie

git clone https://github.com/domengabrovsek/claude.git
cd claude
mkdir -p ~/.claude/skills
cp -r skills/diagram ~/.claude/skills/diagram

Commando's en voorbeeldprompts

  • /diagramPicks mermaid vs drawio by complexity, writes the diagram into your docs, previews via MCP.

Skills reageren op gewone verzoeken — geen commando's om te onthouden. Na installatie activeren prompts zoals deze de skill (in het Engels):

  • draw a sequence diagram of the login flow for our docs
  • make a flowchart showing how requests move through our architecture
  • add an architecture diagram into this markdown file