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 normal code review. This Skill provides a structured, high-signal checklist for diagnosing these issues before they reach production. ## 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 per-frame allocations from LINQ, string formatting, closures, and boxing. - Hidden Cost Analysis: Explains counter-intuitive traps such as write-permission serialization costs, correlated random seeds, and Debug.Log executing in release builds. - Structured Review Output: Produces findings organized into 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, run this review on the suspect scripts to pinpoint whether the cause is allocation churn, uncached component lookups, or physics updates at the wrong cadence. ## Quick Start Ask the assistant to review your Unity scripts for performance red flags and frame-drop causes using the unity-performance skill.
