What problem does it solve?
Helps developers decide which logic should be moved out of Unity-facing classes into pure C# so code can be reliably unit tested and decoupled from scene state.
Core Features & Use Cases
- Targeted Review Questions: Focuses on whether code depends on Transform, GameObject, or global static state and whether configuration can be injected.
- Refactor Recommendations: Identifies logic to extract to plain C#, logic that should remain Unity-facing, and suggests seams/interfaces for dependency injection and mocking.
- Test Planning: Produces candidate EditMode and PlayMode test ideas and outlines which behaviors require scene-driven validation versus isolated unit tests.
- Use Case: When converting a feature to be testable (for CI, faster iteration, or clearer responsibilities), use this Skill to plan seams and test coverage.
Quick Start
Analyze the MonoBehaviour file 'PlayerController.cs' and recommend which methods and dependencies to extract into pure C#, suggest seams/interfaces, and list candidate EditMode and PlayMode tests.