PlantUML Diagrams
Text-based UML/sequence/component diagram skill for version-controlled architecture docs in Claude Code and Cursor.
Overview
PlantUML skills turn natural-language system descriptions into sequence, component, and UML diagrams that live as text in git. Ideal for API interaction docs and design reviews where Draw.io binaries are heavy and Excalidraw is too informal.
Work with LimeDock
Using this skill? LimeDock can wire it into a durable automation you own.
Skills show what's possible. LimeDock builds and runs the owned marketing, sales, and ops automations around them.
We sell owned automations for SaaS teams — live workflows that plug into Slack, CRM, and your internal platform — not just a skill list.
Link
Installation guide
Install a PlantUML-compatible agent skill from your marketplace, or add a SKILL.md that instructs the agent to emit `.puml` files and render via the PlantUML CLI/docker:
# Example render toolchain
brew install plantuml # or use docker plantuml/plantumlStore diagrams under `docs/architecture/*.puml`.
How to use it
Ask for a sequence or component diagram as PlantUML source. Commit the `.puml` file; render in CI or locally. Prefer text diffs in PRs.
Example prompts
- “Create a PlantUML sequence diagram showing API Gateway, Lambda, DynamoDB, and S3.”
- “Emit a component diagram for our billing bounded context as docs/architecture/billing.puml.”
- “Update the auth sequence diagram to include refresh-token rotation.”
Use cases and examples
- API Gateway ↔ Lambda ↔ DynamoDB sequence diagrams
- Component diagrams for modular monolith boundaries
- Version-controlled design docs in PRs
- Teaching system design with editable text diagrams
Prerequisites
- PlantUML CLI or Docker image for rendering
- Agreement to keep diagrams as text in-repo
Tips
- Excalidraw for workshops; PlantUML for durable docs; AWS Cloud Diagrams for cloud topology.
- Cited alongside Draw.io / Excalidraw in architecture skill roundups.