121-java-object-oriented-design
This Claude Code skill reviews and refactors Java code for object-oriented design quality, addressing SOLID, DRY, and YAGNI principles, class and interface design, OOP concept misuse, code smells like God Class and Feature Envy, and patterns for object creation, method design, and exception handling. Use it when analyzing existing Java code for design improvements or when refactoring to enhance maintainability and adherence to object-oriented best practices.
git clone --depth 1 https://github.com/jabrena/cursor-rules-java /tmp/121-java-object-oriented-design && cp -r /tmp/121-java-object-oriented-design/skills/121-java-object-oriented-design ~/.claude/skills/121-java-object-oriented-designSKILL.md
# Java Object-Oriented Design Guidelines Review and improve Java code using comprehensive object-oriented design guidelines and refactoring practices. **What is covered in this Skill?** - Fundamental design principles (SOLID, DRY, YAGNI) - Class and interface design: composition over inheritance, immutability, accessibility minimization, accessor methods - Core OOP concepts: encapsulation, inheritance, polymorphism - Object creation patterns: static factory methods, Builder, Singleton, dependency injection, avoiding unnecessary objects - OOD code smells: God Class, Feature Envy, Inappropriate Intimacy, Refused Bequest, Shotgun Surgery, Data Clumps - Method design: parameter validation, defensive copies, careful signatures, empty collections over nulls, Optional usage - Exception handling: checked vs. runtime exceptions, standard exceptions, failure-capture messages, no silent ignoring **Scope:** The reference is organized by examples (good/bad code patterns) for each core area. Apply recommendations based on applicable examples. ## Constraints Before applying any OOD changes, ensure the project compiles. If compilation fails, stop immediately — do not proceed until resolved. After applying improvements, run full verification. - **MANDATORY**: Run `./mvnw compile` or `mvn compile` before applying any change - **SAFETY**: If compilation fails, stop immediately and do not proceed — compilation failure is a blocking condition - **VERIFY**: Run `./mvnw clean verify` or `mvn clean verify` after applying improvements - **BEFORE APPLYING**: Read the reference for detailed examples, good/bad patterns, and constraints - **EDGE CASE**: If request scope is ambiguous, stop and ask a clarifying question before applying changes - **EDGE CASE**: If required inputs, files, or tooling are missing, report what is missing and ask whether to proceed with setup guidance ## When to use this skill - Review Java code for object-oriented design - Refactor Java code for object-oriented design - Improve Java code for object-oriented design - Fix OOP concept misuse in Java code - Identify and resolve code smells in Java code - Improve object creation patterns in Java code - Improve method design in Java code - Improve exception handling in Java code ## Workflow 1. **Compile project before OOD changes** Run `./mvnw compile` or `mvn compile` and stop immediately if compilation fails. 2. **Read OOD reference and assess code** Read `references/121-java-object-oriented-design.md` and identify applicable SOLID/OOP/code-smell improvements. 3. **Apply focused refactorings** Implement the selected object-oriented design improvements while preserving behavior. 4. **Verify with full build** Run `./mvnw clean verify` or `mvn clean verify` after applying improvements. ## Reference For detailed guidance, examples, and constraints, see [references/121-java-object-oriented-design.md](references/121-java-object-oriented-design.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