Recovering something lost

Author: jabrena

.cursor/rules/121-java-object-oriented-design.mdc

@@ -13,6 +13,18 @@ You are a Senior software engineer with extensive experience in Java software de
 
 Apply comprehensive guidelines for robust Java object-oriented design and refactoring. Follow core principles like SOLID, DRY, and YAGNI, implement best practices for class and interface design including favoring composition over inheritance and designing for immutability. Master encapsulation, inheritance, and polymorphism, and identify and refactor common object-oriented design code smells such as God Classes, Feature Envy, and Data Clumps to promote maintainable, flexible, and understandable code.
 
+### Implementing These Principles
+
+These guidelines are built upon the following core principles:
+
+1.  **Adherence to Fundamental Design Principles**: Embrace foundational principles like SOLID, DRY, and YAGNI. These principles are key to building systems that are robust, maintainable, flexible, and easy to understand.
+2.  **Effective Class and Interface Design**: Employ best practices for designing classes and interfaces. This includes favoring composition over inheritance to achieve flexibility, programming to an interface rather than an implementation to promote loose coupling, keeping classes small and focused on a single responsibility, and designing for immutability where appropriate to enhance simplicity and thread-safety.
+3.  **Mastery of Core OOP Concepts**: Thoroughly understand and correctly apply the pillars of object-oriented programming:
+*   **Encapsulation**: Protect internal state and expose behavior through well-defined interfaces.
+*   **Inheritance**: Model true "is-a" relationships, ensuring subclasses are substitutable for their base types (Liskov Substitution Principle).
+*   **Polymorphism**: Allow objects of different types to respond to the same message in their own way, simplifying client code.
+4.  **Proactive Code Smell Management**: Develop the ability to identify common object-oriented design "code smells" (e.g., God Class, Feature Envy, Data Clumps, Refused Bequest). Recognizing and refactoring these smells is crucial for improving the long-term health, maintainability, and clarity of the codebase.
+
 ## Examples
 
 ### Table of contents
@@ -298,4 +310,4 @@ class OrderManager {
 
 - Apply object-oriented design principles to improve code quality and maintainability
 - Refactor code to follow SOLID principles and eliminate design smells
-- Verify code changes compile and pass tests
+- Verify code changes compile and pass tests

spml/src/main/resources/121-java-object-oriented-design.xml

@@ -24,6 +24,18 @@
 
     <goal>
         Apply comprehensive guidelines for robust Java object-oriented design and refactoring. Follow core principles like SOLID, DRY, and YAGNI, implement best practices for class and interface design including favoring composition over inheritance and designing for immutability. Master encapsulation, inheritance, and polymorphism, and identify and refactor common object-oriented design code smells such as God Classes, Feature Envy, and Data Clumps to promote maintainable, flexible, and understandable code.
+
+        ### Implementing These Principles
+
+        These guidelines are built upon the following core principles:
+
+        1.  **Adherence to Fundamental Design Principles**: Embrace foundational principles like SOLID, DRY, and YAGNI. These principles are key to building systems that are robust, maintainable, flexible, and easy to understand.
+        2.  **Effective Class and Interface Design**: Employ best practices for designing classes and interfaces. This includes favoring composition over inheritance to achieve flexibility, programming to an interface rather than an implementation to promote loose coupling, keeping classes small and focused on a single responsibility, and designing for immutability where appropriate to enhance simplicity and thread-safety.
+        3.  **Mastery of Core OOP Concepts**: Thoroughly understand and correctly apply the pillars of object-oriented programming:
+            *   **Encapsulation**: Protect internal state and expose behavior through well-defined interfaces.
+            *   **Inheritance**: Model true "is-a" relationships, ensuring subclasses are substitutable for their base types (Liskov Substitution Principle).
+            *   **Polymorphism**: Allow objects of different types to respond to the same message in their own way, simplifying client code.
+        4.  **Proactive Code Smell Management**: Develop the ability to identify common object-oriented design "code smells" (e.g., God Class, Feature Envy, Data Clumps, Refused Bequest). Recognizing and refactoring these smells is crucial for improving the long-term health, maintainability, and clarity of the codebase.
     </goal>
 
     <examples>

spml/src/test/resources/121-java-object-oriented-design.mdc

@@ -13,6 +13,18 @@ You are a Senior software engineer with extensive experience in Java software de
 
 Apply comprehensive guidelines for robust Java object-oriented design and refactoring. Follow core principles like SOLID, DRY, and YAGNI, implement best practices for class and interface design including favoring composition over inheritance and designing for immutability. Master encapsulation, inheritance, and polymorphism, and identify and refactor common object-oriented design code smells such as God Classes, Feature Envy, and Data Clumps to promote maintainable, flexible, and understandable code.
 
+### Implementing These Principles
+
+These guidelines are built upon the following core principles:
+
+1.  **Adherence to Fundamental Design Principles**: Embrace foundational principles like SOLID, DRY, and YAGNI. These principles are key to building systems that are robust, maintainable, flexible, and easy to understand.
+2.  **Effective Class and Interface Design**: Employ best practices for designing classes and interfaces. This includes favoring composition over inheritance to achieve flexibility, programming to an interface rather than an implementation to promote loose coupling, keeping classes small and focused on a single responsibility, and designing for immutability where appropriate to enhance simplicity and thread-safety.
+3.  **Mastery of Core OOP Concepts**: Thoroughly understand and correctly apply the pillars of object-oriented programming:
+*   **Encapsulation**: Protect internal state and expose behavior through well-defined interfaces.
+*   **Inheritance**: Model true "is-a" relationships, ensuring subclasses are substitutable for their base types (Liskov Substitution Principle).
+*   **Polymorphism**: Allow objects of different types to respond to the same message in their own way, simplifying client code.
+4.  **Proactive Code Smell Management**: Develop the ability to identify common object-oriented design "code smells" (e.g., God Class, Feature Envy, Data Clumps, Refused Bequest). Recognizing and refactoring these smells is crucial for improving the long-term health, maintainability, and clarity of the codebase.
+
 ## Examples
 
 ### Table of contents
@@ -298,4 +310,4 @@ class OrderManager {
 
 - Apply object-oriented design principles to improve code quality and maintainability
 - Refactor code to follow SOLID principles and eliminate design smells
-- Verify code changes compile and pass tests
+- Verify code changes compile and pass tests