Clean OOP Architecture

Use this skill for code quality decisions that go beyond syntax: boundaries, responsibilities, coupling, cohesion, naming, refactoring, and testability.

Core Principle

Prefer code that is easy to change safely:

• One clear reason to change per class or module.
• Behavior grouped by responsibility, not by convenience.
• Dependencies point inward toward stable abstractions.
• Domain logic is testable without Unity scenes, Firebase, network, or UI.
• Framework code adapts the domain; it does not become the domain.

First Read

Before changing code, inspect: