$pwd:

performance-optimization

Name: Performance Optimization
Author: pvillega

// Use when creating performance optimization plan for backend, API, or general system performance. Enforces BASELINE → PROFILE → OPTIMIZE → VALIDATE sequence. Triggers: "optimize API", "backend slow", "API latency", "database performance", "query optimization", "server response time". For "Core Web Vitals" in backend/API context, use this skill. For frontend UI accessibility + performance (WCAG, Lighthouse accessibility), use frontend-production-quality instead. If thinking "bottleneck is obvious" - profile first.

$ git log --oneline --stat

stars:2

forks:2

updated:1 décembre 2025 à 16:37

SKILL.md

readonly

package.json

"author": "pvillega"

"repository": "pvillega/claude-templates"

$ git clone

$ download --local

[HINT] Téléchargez le répertoire complet incluant SKILL.md et tous les fichiers associés

related-imports.ts

// Skills associés

import optimizationquality-report

from "edwardmonteiro"

import setting-up-synthetic-monitoring

from "jeremylongshore"

692

import metric-governance-kit

from "gtmagents"

import performance-monitoring

from "Dmccarty30"

import workflow-management

from "onesmartguy"

import performance-auditor

from "Claymore-Q"

import project-status-manager

from "fuchsst"

import kpi-dashboard-design

from "wshobson"

22,962

import implementing-real-user-monitoring

from "jeremylongshore"

692

import tracking-service-reliability

from "jeremylongshore"

692

import analyzing-system-throughput

from "jeremylongshore"

692

import analyzing-network-latency

from "jeremylongshore"

692

name

performance-optimization

description

Use when creating performance optimization plan for backend, API, or general system performance. Enforces BASELINE → PROFILE → OPTIMIZE → VALIDATE sequence. Triggers: "optimize API", "backend slow", "API latency", "database performance", "query optimization", "server response time". For "Core Web Vitals" in backend/API context, use this skill. For frontend UI accessibility + performance (WCAG, Lighthouse accessibility), use frontend-production-quality instead. If thinking "bottleneck is obvious" - profile first.

Performance Optimization

MANDATORY FIRST STEP

TodoWrite: Create 20+ items (5 sections × 4 items)

Baseline measurement (tool, current value, target, conditions)
Bottleneck analysis (profile, identify slowest, root cause)
Optimization strategy (prioritize, evaluate approaches, expected improvement)
Implementation (files, config, local verification)
Validation (re-measure, compare, check regressions)

Never skip measurement:

70% of "obvious" bottlenecks are wrong → Profile first
40% of optimizations without baseline cause regressions

5-Section Process

1. Baseline Measurement (BEFORE implementation)

Tool + current value (e.g., "Lighthouse: LCP = 4.2s on 3G")
Target metric (e.g., "LCP < 2.5s")
Conditions recorded

2. Bottleneck Analysis

Profile with tool (Chrome DevTools, pg_stat_statements, DataDog)
Identify slowest operation + time (e.g., "Chart.js render = 2.8s, 67% of total")
Root cause (N+1 queries, large bundle, blocking render)

3. Optimization Strategy

Prioritize by impact (2.8s → 0.5s = 82% faster)
Evaluate 2-3 approaches
Expected improvement

4. Implementation

Files + changes
Configuration
Local verification

5. Validation

Re-measure same tool + conditions
Compare before/after
Check no regressions (FID, CLS, functionality)

Verification Checkpoint

Before marking complete:

✅ Baseline measured with specific tool + value
✅ Profile identifies bottleneck with % of total time
✅ Validation re-measures with same tool/conditions

Red Flags

Thought	Reality
"Bottleneck is obvious"	70% wrong without profiling
"We'll measure after"	Can't validate improvement
"Manual testing is enough"	Need metrics, not feelings