OpenParable
Skip to content
← Back to skills

172 Java Diagrams

Design
172-java-diagrams

172 Java Diagrams is an Agent Skill for design published in the majiayu000/claude-skill-registry repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Use when you need to generate Java project diagrams — including UML sequence diagrams, UML class diagrams, C4 model diagrams, and UML state machine diagrams — through a modular, step-based interactive process that adapts to your specific visualization needs. Part of the skills-for-java project

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/majiayu000/claude-skill-registry/blob/HEAD/skills/documents/172-java-diagrams/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/172-java-diagrams, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

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, and UML state machine 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
  • 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

Reference

For detailed guidance, examples, and constraints, see references/172-java-diagrams.md.