What problem does it solve? Unity gameplay scripts often grow into tightly-coupled god objects with hidden dependencies, per-frame allocations, and unclear state ownership. This Skill provides a structured design review checklist that catches these problems before or after scripts are written. ## 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 Model: Classifies every field as authoring-time, composition-time, or runtime-mutable state, with concrete assignment examples and guidance on preventing mixed-ownership bugs. - Structured Output Format: Produces review results organized as Keep, Simplify, Refactor, Performance notes, and Maintainability notes. - Use Case: After generating a player controller and enemy AI scripts, run this review to catch a public mutable HP field, an uncached GetComponent call in Update, and a config value that belongs in a ScriptableObject. ## Quick Start Ask the AI to review your Unity gameplay scripts using the script design checklist and report the highest-value refactor, real performance hotspots, and maintainability issues.
