---

name: unity-performance-check description: Use before committing code or after major changes to verify performance. Catches expensive operations before they cause frame drops.

Unity Performance Check

Overview

Verify code performance BEFORE it causes problems in production. Frame drops ruin games.

When to Use

• Before committing new code
• After implementing Update/FixedUpdate logic
• When adding new systems
• Before major milestones
• When users report lag

The Quick Check (30 seconds)

Run these searches on changed files:

Copy// RED FLAGS - Fix these immediately:
GetComponent         // In Update? Cache it
Find(                // In Update? Never do this
FindObjectOfType     // Anywhere? Avoid if possible
new List             // In Update? Preallocate
new Dictionary       // In Update? Preallocate
.ToString()          // In Update? Cache or avoid
string +             // In Update? StringBuilder
foreach              // On non-List? May allocate

The Full Check (5 minutes)

Use the unity-performance-profiler agent:

CopyTask: Launch unity-performance-profiler agent with:
"Analyze [file/folder] for performance issues"

Performance Rules

Update Loop (60fps = 16.6ms budget)

Memory (GC spikes cause stutters)

VeilBreakers-Specific

Checklist

Before committing, verify:

• No GetComponent in Update/FixedUpdate
• No Find/FindObjectOfType anywhere
• No allocations in hot paths
• Collections preallocated
• Strings not concatenated in loops
• Events properly unsubscribed
• Object pooling for spawned objects

If Performance is Bad

1. Profile first - Don't guess, measure
2. Find the hotspot - Usually 1-2 methods
3. Fix the algorithm - O(n²) → O(n) > micro-optimizations
4. Cache results - Don't recalculate what hasn't changed
5. Batch operations - Process multiple items together
6. Use jobs/burst - For heavy math (advanced)