Use when you need to generate Java project diagrams — including UML sequence diagrams, UML class diagrams, C4 model diagrams, UML state machine diagrams, UML Deployment Diagrams, ER (Entity Relationship) diagrams, and bounded-context diagrams — through a modular, step-based interactive process that adapts to your specific visualization needs. This should trigger for requests such as Generate UML diagram; Create sequence diagram; Create class diagram; Create state machine diagram; Create deployme
SkillScore88Maintained
Automatic
◆Coding pack
Last verified 8/20/2026
What it changes
Passed 20 of 23 test cases with the skill, and 9 of 23 without it.
12 fixed10 passed either way3 still failing0 broke
Pass-rate lift
+48 pp
Tokens
+142%
Agent turns
0%
Response time
-49%
Model gemini-3.6-flashMeasured 8/20/2026v122 of 25 cases passed with skill · 23 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 12
Prompt
We have created several .puml files in the diagrams directory. What exact local command flag should be passed to PlantUML to perform syntax verification without rendering images?
What was checked, without and with the skill
Checked
Without skill
With skill
Specifies the -checkonly flag for PlantUML syntax validation
Missed
Passed
case-08 · gemini-3.6-flash · 8/20/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md266 lines8 files
Java Diagrams Generator with modular step-based configuration
Generate comprehensive Java project diagrams through a modular, step-based interactive process that covers UML sequence diagrams, UML class diagrams, C4 model diagrams, UML state machine diagrams, UML Deployment Diagrams, ER (Entity Relationship) diagrams, and bounded-context diagrams using PlantUML syntax. This is an interactive SKILL.
What is covered in this Skill?
UML sequence diagram generation for application workflows and API interactions
UML class diagram generation for package structure and class relationships
C4 model diagram generation for Context, Container, and Component diagrams
UML state machine diagram generation for entity lifecycles and business workflows
UML Deployment Diagram generation for runtime topology, nodes, execution environments, deployed components, data stores, queues, external systems, and communication paths
ER diagram generation from SQL schema (DDL, migrations) using PlantUML Chen notation
Bounded-context diagram generation for DDD context maps across one or more repositories
PlantUML syntax for all diagram types
File organization strategies: single-file, separate-files, or integrated with existing documentation
Final diagram validation with PlantUML syntax checking
PlantUML validation and PNG/SVG rendering with a trusted local PlantUML installation or repository-approved wrapper
Constraints
Before applying any diagram generation, ensure the project validates. If validation fails, stop immediately — do not proceed until all validation errors are resolved.
MANDATORY: Run ./mvnw validate or mvn validate before applying any diagram generation
SAFETY: If validation fails, stop immediately — do not proceed until all validation errors are resolved
BEFORE READING DIAGRAM REFERENCES: Run the question flow embedded in this SKILL.md first. Ask the diagram preference questions one by one, collect selected diagram families and output preferences, then read only the implementation references selected by the user's answers
C4 SCOPE: C4 diagrams are restricted to Context, Container, and Component diagrams
SUPPLY CHAIN: Generated PlantUML diagrams must use trusted local includes only; do not use remote !include URLs for C4 or icon libraries
TOOLING SAFETY: Use only trusted local PlantUML tooling or a repository-approved wrapper; do not pull or run remote container images as part of this skill
Use when you need GitHub CLI (`gh`) installation/authentication guidance and an operator-only GitHub issue inventory workflow. The agent does not ingest GitHub issue, milestone, body, comment, title, label, or summary text; requirements analysis must use repository-owned planning artifacts, with issue numbers only for traceability. This should trigger for requests such as GitHub issue inventory workflow; GitHub CLI setup for issues; Prepare issue traceability lists; Analyze repository planning a