domains / families / software-engineering / performance

performance

combined

Advise on Unity performance red flags Optimize web performance for faster loading and better user experience. Use when asked to "speed up my site", "optimize performance", "reduce load time", "fix slow loading", "improve page speed", or "performance audit".

When to use

• Reviewing performance
• Diagnosing frame drops
• Reducing allocations
• Planning pooling/optimization
• Speed up my site
• Optimize performance
• Reduce load time
• Performance audit

When not to use

• Speculative micro-optimizations
• Large refactors without a meaningful hotspot
• Replacing simple code with unreadable optimized code unless the hot path is real
• Non-performance Lighthouse categories

Skill page

Conflict

The three skills share the name 'performance' but target fundamentally different systems and workflows. The first is a Unity-specific C# review checklist (GC, Update loops, pooling). The second is a web performance optimization guide focused on Core Web Vitals, resource budgets, and browser tracing. The third is a UI/UX performance skill that enforces specific Web Vitals budgets and relies on a local design system kit. Because they address different domains (game engine vs. web platform vs. UI design system) and contain non-overlapping, material steps (e.g., Unity's 'hidden costs' vs. Web's 'Early Hints' vs. UI's 'kit check'), crowning one would hide the other two valid approaches. They must be combined to preserve the distinct procedures for each context.