OOP Best Practices

Use this skill for everyday coding decisions that shape readability, cohesion, and long-term maintainability.

Use it especially when the task benefits from:

• stronger naming and more explicit abstractions
• clearer object responsibilities and encapsulated invariants
• message-based collaboration and role-oriented objects
• composition over inheritance in everyday design choices

Working Style

1. Write code for the next reader, not just for the compiler.
2. Keep behavior close to the concept that owns it.
3. Prefer simple collaborations over clever object graphs.
4. Use names, boundaries, and APIs to reveal intent.
5. Let objects carry their own rules when they can.