performance-engineer
/performance-engineer
Performance Engineer (/perf) — measures and optimizes performance across the stack: Core Web Vitals (LCP/INP/CLS), bundle/asset budgets, frontend rendering, backend latency & throughput, profiling & flame graphs, database query performance, caching, and load testing. Use when something is slow, you need to set/enforce performance budgets, profile a hot path, run a load test, or audit Web Vitals. Invoke during /rev for perf review and alongside /sre for capacity. NOT for reliability/SLOs & incident response (that's /sre) — /perf is about speed/efficiency, not uptime.
- Author
- olehsvyrydov ↗
- Repository
- AI-development-team ↗
- Licence
- MIT
- Last repository change
- 09.08.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 09.08.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Performance Engineer (/perf) — measures and optimizes performance across the stack: Core Web Vitals (LCP/INP/CLS), bundle/asset budgets, frontend rendering, backend latency & throughput, profiling & flame graphs, database query performance, caching, and load testing. Use when something is slow, you need to set/enforce performance budgets, profile a hot path, run a load test, or audit Web Vitals. Invoke during /rev for perf review and alongside /sre for capacity. NOT for reliability/SLOs & incident response (that's /sre) — /perf is about speed/efficiency, not uptime.
Original author description
Performance Engineer (/perf) — measures and optimizes performance across the stack: Core Web Vitals (LCP/INP/CLS), bundle/asset budgets, frontend rendering, backend latency & throughput, profiling & flame graphs, database query performance, caching, and load testing. Use when something is slow, you need to set/enforce performance budgets, profile a hot path, run a load test, or audit Web Vitals. Invoke during /rev for perf review and alongside /sre for capacity. NOT for reliability/SLOs & incident response (that's /sre) — /perf is about speed/efficiency, not uptime.
How it works
- Gate Check (workflow)
- When to use (and when not)
- Core expertise
- Standards
SKILL.md preview
--- name: performance-engineer description: "Performance Engineer (/perf) — measures and optimizes performance across the stack: Core Web Vitals (LCP/INP/CLS), bundle/asset budgets, frontend rendering, backend latency & throughput, profiling & flame graphs, database query performance, caching, and load testing. Use when something is slow, you need to set/enforce performance budgets, profile a hot path, run a load test, or audit Web Vitals. Invoke during /rev for perf review and alongside /sre for capacity. NOT for reliability/SLOs & incident response (that's /sre) — /perf is about speed/efficiency, not uptime." --- # Performance Engineer (/perf) **Command:** `/perf` · **Category:** Quality ## Gate Check (workflow) Consult the **`workflow-engine`** skill first. `/perf` owns **`PERF_OK`** (`soft`). - **Trigger:** hot paths, performance-budget-bearing changes, or a flagged regression. - **On pass:** budgets met (Web Vitals / latency / bundle size) with evidence → record `PERF_OK`. If a budget is missed, follow the **soft-gate policy** — warn and record the skip + reason, and escalate to the team rather than hard-blocking (unless the workflow is configured to treat perf budgets as `hard`). Participates in code review (`/rev`) for performance. ## When to use (and when not) - **Use for:** Core Web Vitals audits, Lighthouse/bundle analysis, profiling (CPU/memory/flame graphs), backend latency/throughput tuning, slow-query analysis, caching strategy, load/stress testing, performance budgets in CI. - **Hand off instead when:** uptime/SLO/incident → **/sre**; schema/index design → **/dba**; infra autoscaling → **devops-engineer**; feature implementation → **/fe** / **/be**. ## Core expertise - **Frontend:** Web Vitals (LCP/INP/CLS), critical path, code-splitting, lazy loading, image/asset optimization, hydration cost, bundle budgets. - **Backend:** latency profiling, N+1 detection, connection pools, async/concurrency, payload size, pagination. - **Database (with /dba):** query plans, indexing impact, slow-query logs. - **Caching:** HTTP, CDN, app-level, memoization, invalidation. - **Measurement:** Lighthouse, WebPageTest, k6/Gatling, profilers (pprof, async-profiler, Chrome DevTools), p50/p95/p99 thinking. ## Standards - **Measure first, optimize second** — never guess; profile and quantify before/after. - Performance budgets live in **CI** and fail the build when breached (when configured). - Report in percentiles (p95/p99), not averages; tie numbers to user impact.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · olehsvyrydov/AI-development-team | 100 | MIT |
| rmyndharis/antigravity-skills | 100 | MIT |
| agentic-swe/agentic-swe | 100 | MIT |
| zhaono1/agent-playbook | 100 | MIT |
| charlieviettq/awesome-agent-skill | 100 | MIT |
| rade-nugroho/agentic-enteprises-skill | 100 | MIT |
Database snapshot: 13.11.2026 · package version c662d831ea97 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100lighthouse-perf
Use when a web frontend needs Core Web Vitals (LCP, INP, CLS) checked on every PR, or its first performance budgets drafted. Sets up Lighthouse CI with Google's thresholds at the 75th percentile, per-route budgets by page type, resource-size budgets, report artifacts and PR comments. - 100performance
Web performance optimization. Covers frontend, backend, and database optimization. Use for performance reviews. USE WHEN: user mentions "performance", "slow", "optimization", "Core Web Vitals", "LCP", "INP", "CLS", "bundle size", "lazy load", "caching", "N+1 query", "memory… - 100performance-profiler
Performance profiling and optimization for web apps — Core Web Vitals (LCP, INP, CLS), Lighthouse audits, bundle analysis, backend profiling (CPU, memory, DB queries), N+1 detection, caching strategies (Redis, CDN, HTTP), and performance budgets. Use when user asks to improve… - 95web-performance
Use this skill when the user says 'Core Web Vitals', 'LCP', 'INP', 'CLS', 'page is slow', 'improve Lighthouse score', 'long tasks', 'web-vitals library', 'field data vs lab data', 'CrUX'. It diagnoses and fixes Core Web Vitals with field measurement (web-vitals, CrUX), LCP… - 100performance
Performance optimization for Next.js — bundle analysis, Core Web Vitals (LCP/CLS/INP), SSR streaming, code splitting, memory leaks, caching strategies, Lighthouse CI. Use when optimizing page speed, debugging slow renders, reducing bundle size, or setting up performance budgets. - 100web-performance
Diagnoses and fixes Core Web Vitals - LCP, INP, and CLS - through an ordered audit procedure with concrete code-level changes for images, fonts, JavaScript, and third-party scripts. Use when someone asks "why is my page slow", "how do I fix my LCP", "we're failing Core Web…