Run any Skill in Manus with one click

121-java-object-oriented-design

Stars0

Forks2

UpdatedMarch 19, 2026 at 20:26

Use when you need to review, improve, or refactor Java code for object-oriented design quality — including applying SOLID, DRY, and YAGNI principles, improving class and interface design, fixing OOP concept misuse (encapsulation, inheritance, polymorphism), identifying and resolving code smells (God Class, Feature Envy, Data Clumps), or improving object creation patterns, method design, and exception handling. Part of the skills-for-java project

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

jabrena

jabrena/cursor-rules-examples

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

2 files

SKILL.md

readonly

name	121-java-object-oriented-design
description	Use when you need to review, improve, or refactor Java code for object-oriented design quality — including applying SOLID, DRY, and YAGNI principles, improving class and interface design, fixing OOP concept misuse (encapsulation, inheritance, polymorphism), identifying and resolving code smells (God Class, Feature Envy, Data Clumps), or improving object creation patterns, method design, and exception handling. Part of the skills-for-java project
license	Apache-2.0
metadata	{"author":"Juan Antonio Breña Moral","version":"0.13.0-SNAPSHOT"}

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

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

Reference

For detailed guidance, examples, and constraints, see references/121-java-object-oriented-design.md.

More from this repository

same repository

014-agile-create-user-story

jabrena/cursor-rules-examples

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. Part of the skills-for-java project

2026-03-190

020-planning-enhance-ai-plan-mode

jabrena/cursor-rules-examples

Use when creating a plan using Plan model and enhancing structured design plans in Cursor Plan mode for Java implementations. Use when the user wants to create a plan, design an implementation, structure a development plan, or use plan mode for outside-in TDD, feature implementation, or refactoring work. Part of the skills-for-java project

2026-03-190

030-architecture-adr-general

jabrena/cursor-rules-examples

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. Part of the skills-for-java project

2026-03-190

031-architecture-adr-functional-requirements

jabrena/cursor-rules-examples

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. Part of the skills-for-java project

2026-03-190

032-architecture-adr-non-functional-requirements

jabrena/cursor-rules-examples

Facilitates conversational discovery to create Architectural Decision Records (ADRs) for non-functional requirements using the ISO/IEC 25010:2023 quality model. Use when the user wants to document quality attributes, NFR decisions, security/performance/scalability architecture, or design systems with measurable quality criteria. Part of the skills-for-java project

2026-03-190

033-architecture-diagrams

jabrena/cursor-rules-examples

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

2026-03-190

name	121-java-object-oriented-design
description	Use when you need to review, improve, or refactor Java code for object-oriented design quality — including applying SOLID, DRY, and YAGNI principles, improving class and interface design, fixing OOP concept misuse (encapsulation, inheritance, polymorphism), identifying and resolving code smells (God Class, Feature Envy, Data Clumps), or improving object creation patterns, method design, and exception handling. Part of the skills-for-java project
license	Apache-2.0
metadata	{"author":"Juan Antonio Breña Moral","version":"0.13.0-SNAPSHOT"}

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

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

Reference

For detailed guidance, examples, and constraints, see references/121-java-object-oriented-design.md.