plantumllisted
Generate PlantUML diagrams — class, sequence, use case, activity, state, component, deployment, object, entity-relationship/data-model, C4 model (context/container/component/dynamic/deployment), timing, mindmap, WBS, Gantt, network, ArchiMate, JSON/YAML, and wireframe (salt) diagrams — for software architecture, system design, and documenting complex codebases. Use whenever asked to create, draw, sketch, generate, or update a UML diagram, architecture diagram, sequence diagram, class diagram, ER/data-model diagram, deployment diagram, component diagram, C4 diagram, state machine, or any software-engineering diagram, or when PlantUML, .puml files, or "UML diagram" comes up — even without saying "PlantUML" by name, just describing wanting a diagram of code, architecture, API flow, or a database schema. Also use to render an existing .puml file to SVG/PNG/PDF, or to debug broken PlantUML syntax.
matiaspakua/notaire · ★ 0 · Data & Documents · score 54
Install: claude install-skill matiaspakua/notaire
# PlantUML diagram generation
Generate diagrams as PlantUML source (`.puml`), then render them to an image.
PlantUML is a plain-text diagramming language — every diagram is code, which
is exactly why it fits software projects well: diagrams live in version
control next to the system they describe, and can be regenerated instead of
manually redrawn every time the design changes.
## Workflow
1. **Figure out which diagram type(s) actually answer the user's question.**
"Diagram the architecture" is underspecified — a request to see how
systems talk to each other needs a different diagram than a request to
see a class hierarchy or a request to see what happens during one API
call. See the decision guide below, or the fuller one in
`references/diagram-types.md`. For a non-trivial system, plan a *set* of
diagrams rather than forcing everything into one (see "Documenting a real
project" below) — say which diagrams you're producing and why before
writing them.
2. **Write the `.puml` source directly** with the Write tool. Look up the
skeleton for the chosen diagram type in `references/diagram-types.md`
rather than guessing at syntax from memory — PlantUML has a lot of
diagram-specific vocabulary and getting the element keywords right the
first time avoids a debug round-trip. For C4 or cloud-icon diagrams, check
`references/stdlib-and-icons.md` for the right `!include` path.
3. **Render it**: `scripts/render.sh <file.puml> <format> <output-dir>`