What problem does it solve? Unity code tightly coupled to MonoBehaviour, GameObject, and scene state is hard to unit test. This Skill helps you decide which logic should move into pure C# classes and which should stay Unity-facing, so you can build a practical EditMode/PlayMode test strategy. ## Core Features & Use Cases - Testability Review Questions: Structured prompts to check whether logic can run without Transform, GameObject, or scene state, and whether config can be injected instead of read from static globals. - Refactoring Guidance: Identifies logic to extract into plain C# classes called from thin MonoBehaviour wrappers, plus suggested seams and interfaces. - Test Planning: Produces candidate EditMode tests and PlayMode tests so you know what coverage each layer needs. - Use Case: You have a 300-line MonoBehaviour mixing input handling, scoring rules, and UI updates. Use this Skill to separate the scoring rules into a pure C# class, define an interface seam for input, and plan EditMode tests for the rules with PlayMode tests only for scene integration. ## Quick Start Ask the AI to review your Unity script for testability and suggest which logic to extract into pure C# classes with a plan for EditMode and PlayMode tests.