What problem does it solve? Unity projects often accumulate hidden performance problems—per-frame allocations, repeated GetComponent calls, excessive Update loops—that cause frame drops and GC spikes but are hard to spot during code review. This Skill provides a structured, high-signal checklist for diagnosing these issues without speculative micro-optimizations. ## Core Features & Use Cases - Red Flag Detection: Identifies common Unity performance anti-patterns including repeated Find/GetComponent calls in hot paths, frequent Instantiate/Destroy suitable for pooling, and avoidable per-frame allocations from LINQ, closures, boxing, and string formatting. - Hidden Cost Analysis: Explains counter-intuitive traps where cost is paid for the possibility of work—write-permission serialization overhead, correlated random seeds, and Debug.Log executing in release builds. - Prioritized Output: Delivers findings organized as confirmed red flags, likely red flags, changes worth doing now, and expected gain categories (clarity, frame time, GC, scalability). - Use Case: When a Unity game stutters during gameplay, use this Skill to review MonoBehaviour scripts and get a prioritized list of allocation and hot-path fixes before touching the profiler. ## Quick Start Ask the assistant to review my Unity scripts for performance red flags and suggest which optimizations are worth doing now.
