domains / families / software-engineering / performance-optimization

performance-optimization

combined

Optimizes application performance across frontend, backend, queries, and databases. Use when performance requirements exist, when you suspect performance regressions, when Core Web Vitals or load times need improvement, when N+1 query patterns need fixing, or when profiling reveals bottlenecks. Find and fix game performance problems methodically — measure with the engine profiler first, reason about the frame-time budget, locate the CPU-vs-GPU bottleneck, then apply the right fix: object pooling, draw-call batching, fewer allocations/GC spikes, and asset budgets. Engine- neutral method that pairs with each engine's profiler. Use when the user mentions performance, optimize, low/dropping FPS, frame drops, stutter, lag, profiler, frame budget, draw calls, batching, garbage collection/GC spikes, object pooling, or "the game runs slow".

When to use

• Performance requirements exist in the spec (load time budgets, response time SLAs)
• Users or monitoring report slow behavior
• Core Web Vitals scores are below thresholds
• You suspect a change introduced a regression
• Building features that handle large datasets or high traffic
• Use when the frame rate is low or uneven, the game stutters/hitches, or it must hit a target
• Use to decide *what* to optimize: profile, read the frame budget, and identify whether the CPU
• Use to apply specific fixes: object pooling, draw-call/batch reduction, removing per-frame

When not to use

• Use this skill only when the task clearly matches its upstream source and local project context.
• Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.
• Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.

Skill page

Conflict

The copies share the same high-level 'measure, identify, fix, verify' philosophy, but they target fundamentally different domains. The addyosmani and sickn33 copies are web-application focused (Core Web Vitals, Lighthouse, N+1 queries, HTTP/2), while the gamedev-skills copy is game-engine focused (frame budgets, draw calls, object pooling, GPU vs CPU bottlenecks). Because the specific steps, tools, and metrics are disjoint, crowning one would hide the other's domain-specific procedures.