performance-engineer

Diagnose and optimize system performance across frontend, backend, databases, and infrastructure using measured evidence.

2|Updated Aug 21, 2026

Search Tags:#benchmarking #performance optimization #profiling #latency #load testing #core web vitals #database optimization

Ready to run

npx skills add https://github.com/suhanr/next-gen-claude-skills --skill performance-engineer-suhanr

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: performance-engineer
Source: https://github.com/suhanr/next-gen-claude-skills/tree/main/skills/13-performance-engineer
Command: npx skills add https://github.com/suhanr/next-gen-claude-skills --skill performance-engineer-suhanr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Slow applications, unexplained latency, and resource bottlenecks are hard to fix without a disciplined measurement process. This Skill replaces guesswork with an evidence-based workflow: baseline, profile, isolate the bottleneck, change one variable, and re-benchmark. ## Core Features & Use Cases - Measurement-First Optimization: Establishes baselines, profiles CPU/memory/I/O, and identifies dominant bottlenecks before changing code. - Full-Stack Coverage: Addresses Core Web Vitals, HTTP caching, backend latency, database query plans, load testing, and mobile/game frame-time budgets. - Regression Guarding: Automates performance checks and documents trade-offs so optimizations do not silently regress. - Use Case: A web application's p95 API latency doubled after a release. Use this Skill to capture a baseline, trace the slow database query plan, apply an index fix, and verify the improvement with a repeatable benchmark. ## Quick Start Ask the assistant to profile your slow endpoint or page, identify the dominant bottleneck, and produce a benchmark-backed optimization plan.

Frequently Asked Questions about performance-engineer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I diagnose a slow website or API endpoint?▼

Start by measuring a representative baseline, then use profiling or distributed tracing to find the dominant bottleneck. Change one variable at a time and re-run the same benchmark to confirm the improvement is real.

How to improve Core Web Vitals for a web application?▼

Measure current Core Web Vitals values first, then address the largest contributor such as render-blocking resources, oversized assets, or slow server responses. Verify each change against the same metrics to avoid regressions.

What is the correct process for database query optimization?▼

Inspect the query execution plan to find full scans or missing indexes, then apply a targeted fix and re-measure. Avoid changing schema or queries based on intuition without baseline timing evidence.

When should I run load, stress, or soak testing?▼

Run load tests to validate expected capacity, stress tests to find breaking points, and soak tests to detect memory leaks or degradation over time. Always test against a defined performance objective tied to user-visible impact.

Why do performance optimizations sometimes make things worse?▼

Optimizations fail when applied without measurement, when they shift the bottleneck elsewhere, or when they add caching and concurrency complexity with hidden trade-offs. Re-benchmarking after each single change prevents this.

What are the limitations of performance tuning without production data?▼

Synthetic benchmarks may not reflect real traffic patterns, data distributions, or infrastructure constraints. Results should be labeled as assumptions until verified against representative production-like conditions.