What problem does it solve? Unity code often tangles business logic inside MonoBehaviour classes tied to GameObjects, Transforms, and scene state, making it nearly impossible to unit test. This Skill helps you decide what logic should move into pure C# classes and what should stay Unity-facing, so you can build a practical test strategy. ## Core Features & Use Cases - Testability Review Questions: Structured prompts to check whether logic can run without scene state, whether config can be injected, and whether a thin MonoBehaviour wrapper is enough. - EditMode vs PlayMode Guidance: Helps you decide which test type fits each piece of logic instead of defaulting to slow PlayMode tests. - Seam and Interface Suggestions: Recommends meaningful abstraction seams without over-engineering tiny scene-bound scripts. - Use Case: You have a 300-line MonoBehaviour handling inventory rules and UI. Use this Skill to identify which rules can move to a plain C# class, then plan EditMode tests for them while keeping only rendering logic Unity-facing. ## Quick Start Ask the agent to review this MonoBehaviour script and suggest how to make it testable with EditMode unit tests.
