plantuml-diagram-generator

Provide your Architecture Blueprint, READMEs, and folder structure docs, then select which diagrams to generate. The Skill extracts actors, layers, classes, and integrations from those files and produces valid .puml code one diagram at a time, waiting for your approval before continuing.

This Skill supports Use Case, Component, Class (backend only), Package (frontend and backend), and Deployment diagrams. It also generates C4 Model Level 2 prompts for AI image generators, and is extensible to sequence, activity, state, and ER diagrams.

Yes, it adapts to any architecture by detecting layers, background jobs, external integrations, and databases from your documentation. It handles monorepos, MVC, Clean Architecture, microservices, Next.js fullstack, and serverless patterns.

Yes, Update mode compares existing .puml files against current documentation and reports which diagrams changed. It only regenerates diagrams with significant changes like new models, layers, endpoints, or integrations, after your approval.

Class diagrams are generated only for the backend because frontend code is organized around components and hooks rather than classical class hierarchies. Frontend structure is instead captured through Package diagrams showing folder organization and data flow.

The Skill never invents components or relationships, so diagrams are only as complete as the source documentation. Missing or outdated Blueprints and READMEs produce incomplete diagrams, and each diagram requires manual review before proceeding.