033-architecture-diagrams
This Claude Code skill generates five types of architecture diagrams for Java projects, UML sequence, class, state machine, C4 model (levels 1–3 only), and ER diagrams, using PlantUML syntax through a validated, step-based interactive process. Use it when you need to visualize Java project structure, workflows, component relationships, or database schemas with diagram generation that first validates the Maven project state.
git clone --depth 1 https://github.com/jabrena/cursor-rules-java /tmp/033-architecture-diagrams && cp -r /tmp/033-architecture-diagrams/skills/033-architecture-diagrams ~/.claude/skills/033-architecture-diagramsSKILL.md
# 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, and ER (Entity Relationship) 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 at Context/Container/Component levels only (levels 1–3; Code/Level 4 not generated) - UML state machine diagram generation for entity lifecycles and business workflows - ER diagram generation from SQL schema (DDL, migrations) using PlantUML Chen notation - 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 ## 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 APPLYING**: Read the reference for detailed good/bad examples, constraints, and safeguards for each diagram generation pattern - **C4 LIMIT**: C4 diagrams restricted to levels 1, 2, 3 only (Context, Container, Component); never generate Level 4 (Code) diagrams ## When to use this skill - Generate UML diagram - Create sequence diagram - Create class diagram - Create state machine diagram - Create C4 diagram - Generate ER diagram ## Workflow 1. **Validate project state** Run `./mvnw validate` or `mvn validate` before applying any diagram generation. Step constraints: - If validation fails, stop and ask to resolve errors first 2. **Read reference and configure diagram scope** Read `references/033-architecture-diagrams.md`, identify requested diagram types, and confirm output organization strategy (single-file, separate-files, or integrated docs). 3. **Generate PlantUML diagrams** Create requested diagrams in PlantUML syntax (sequence, class, C4 levels 1-3 only, state machine, ER) using project inputs and context. Step constraints: - Never generate C4 Level 4 (Code) diagrams 4. **Validate and finalize outputs** Check generated diagrams for syntax correctness and consistency with selected scope before final delivery. ## Reference For detailed guidance, examples, and constraints, see [references/033-architecture-diagrams.md](references/033-architecture-diagrams.md).
Use when you need to generate a checklist document with Java system prompts, following the embedded template exactly and producing INVENTORY-SKILLS-JAVA.md in the project root. This should trigger for requests such as Create Java system prompts checklist; Generate INVENTORY-SKILLS-JAVA.md; Use @001-skills-inventory. Part of cursor-rules-java project
Use when you need to generate a checklist document with embedded agents inventory, following the embedded template exactly and producing INVENTORY-AGENTS-JAVA.md in the project root. This should trigger for requests such as Create embedded agents inventory checklist; Generate INVENTORY-AGENTS-JAVA.md; Use @002-agents-inventory. Part of cursor-rules-java project
Use when you need to install the embedded robot agents into either .cursor/agents or .claude/agents, selecting the destination interactively and copying the embedded agent definitions from project assets. This should trigger for requests such as Install embedded agents; Bootstrap .cursor/agents; Bootstrap .claude/agents; Copy robot agents. Part of cursor-rules-java project
Guides the creation of agile epics with comprehensive definition including business value, success criteria, and breakdown into user stories. Use when the user wants to create an agile epic, define large bodies of work, break down features into user stories, or document strategic initiatives. This should trigger for requests such as Create an agile epic; Write an epic; I need to create an epic; Define an epic; Epic definition. Part of cursor-rules-java project
Guides the creation of detailed agile feature documentation from an existing epic. Use when the user wants to split an epic into feature files, derive features with scope and acceptance criteria, or plan feature documentation for stakeholders or engineering. This should trigger for requests such as Create features from an epic; Split epic into features; Feature files from epic; Derive features from epic. Part of cursor-rules-java project
Guides the creation of agile user stories and Gherkin feature files. Use when the user wants to create a user story, write acceptance criteria, define Gherkin scenarios, or author BDD feature files. This should trigger for requests such as Create a user story; Write a user story; I need to write a user story. Part of cursor-rules-java project
Use when you need to generate Architecture Decision Records (ADRs) for a Java project through an interactive, conversational process that systematically gathers context, stakeholders, options, and outcomes to produce well-structured ADR documents. This should trigger for requests such as Generate ADR; Create Architecture Decision Record; Document architecture decision; Architecture Decision Record for Java. Part of cursor-rules-java project
Facilitates conversational discovery to create Architectural Decision Records (ADRs) for functional requirements covering CLI, REST/HTTP APIs, or both. Use when the user wants to document command-line or HTTP service architecture, capture functional requirements, create ADRs for CLI or API projects, or design interfaces with documented decisions. This should trigger for requests such as Create ADR for functional requirements; Document functional requirements; Capture functional requirements; Generate functional requirements in an ADR. Part of cursor-rules-java project