What problem does it solve? Unity gameplay scripts often grow into tightly-coupled god objects with unclear responsibilities, hidden dependencies, and mixed state lifecycles, making them hard to test, refactor, and hand off. This Skill provides a structured design review that catches these problems before they compound. ## Core Features & Use Cases - Design Review Checklist: Evaluates responsibility, MonoBehaviour vs ScriptableObject vs plain C# role choice, coupling, communication patterns, performance hotspots, lifecycle cleanup, Inspector UX, testability, and naming. - Data Lifecycle Boundary Analysis: Classifies every field as authoring-time, composition-time, or runtime-mutable state, with concrete assignment guidance (e.g., weapon stats in ScriptableObjects, cached Rigidbody references in Awake, HP exposed via read-only properties with events). - Structured Output Format: Delivers findings as Keep / Simplify / Refactor / Performance notes / Maintainability notes, focusing only on real hotspots rather than theoretical micro-optimizations. - Use Case: After generating a player controller and inventory system, run this review to discover that a public mutable speed field is being edited by both the Inspector and a power-up script, then refactor it into a runtime-mutable property with a change event. ## Quick Start Review my Unity gameplay scripts for coupling and maintainability issues and suggest the highest-value refactor.
