unity-testability

What problem does it solve? Unity developers often struggle to decide which logic should stay in MonoBehaviour classes and which should move into plain C# classes so it can be unit tested without a scene or GameObject dependencies. ## Core Features & Use Cases - Testability Review Questions: Evaluates whether logic can run without Transform, GameObject, or scene state, and whether configuration can be injected instead of read from static globals. - Refactoring Guidance: Identifies logic that should move to pure C#, logic that should stay Unity-facing, and suggested seams or interfaces. - Test Planning: Produces candidate EditMode and PlayMode test lists so teams can plan a concrete test strategy. - Use Case: When a MonoBehaviour grows complex, use this Skill to decide which rules and algorithms to extract into plain C# classes called from a thin Unity-facing wrapper, then plan EditMode coverage for the extracted logic. ## Quick Start Ask the assistant to review a Unity script and advise which logic should move to pure C# classes and which EditMode and PlayMode tests to write.