Performance optimization

Optimizes by measurement: takes a baseline, fixes the one proven bottleneck, re-measures against noise and reverts neutral changes, with worked fixes for N+1 queries, indexes, caching and bundles. Use when something is slow or misses a performance budget.

CodingPack: Agent Skills by Addy Osmani267 linesperformance-optimization
Author
Source
addyosmani/agent-skills/skills/performance-optimization @ 8c99fa3
License
MIT · Copyright (c) 2025 Addy Osmani

About this skill

What it does

The skill forbids optimizing on a hunch. Work goes in five steps: measure a baseline, find the actual bottleneck, fix that one thing, measure again, and guard the metric against regression. Measuring combines synthetic tools (Lighthouse, DevTools) with real-user data (web-vitals, CrUX), and a decision tree maps each symptom to what to measure first.

The strictest part is keep-or-revert. The agent re-measures exactly the way it took the baseline, changes one thing at a time and compares the gain with run-to-run noise. A neutral result is reverted, and so is a win that turned a test red. Every attempt, kept or reverted, goes into a ledger in the PR or a PERF.md, so a dead idea is not tried twice. The last step is a budget in CI (bundle size, Lighthouse CI) plus field monitoring of p75.

The folder ships references/optimization-patterns.md, worked fixes the agent opens only once the bottleneck is known: N+1 queries, unbounded lists, reading EXPLAIN ANALYZE before adding an index, connection pool sizing, responsive images, React re-renders, code splitting and cache design (layer, key, invalidation, stampede). Both files also point to ../../references/performance-checklist.md in the author's repository, which is not installed.

When to use it, and when not

Use it when the spec sets a load-time or latency budget, users or monitoring report slowness, Core Web Vitals miss their thresholds, a change looks like a regression, or a feature handles large data or heavy traffic.

Skip it while there is no evidence of a problem: the skill treats optimization without a measurement as complexity that costs more than it gains.

How to run it

The install command below puts SKILL.md, the patterns file and the licence in place. The agent picks the skill up by its description when performance comes up; to call it yourself:

  • Claude Code: /performance-optimization, or ask for the skill by name.
  • Codex: $performance-optimization.
  • Cursor: type / in the Agent chat and pick performance-optimization.

Example: /performance-optimization The orders page went from 1.2 s to 3 s after last week's release. Measure first, then fix the biggest cost.

How it differs from similar skills

Performance review reads code and returns ranked findings, each with a cost estimate and the measurement that would confirm it; it does not run the fix-and-remeasure loop. SQL query review checks a query for wrong results first and speed second; here query plans are one bottleneck among many, frontend included. Memory leak hunt goes deep on heap growth, which this skill only lists as a symptom. Web performance audit measures one page load through Chrome DevTools MCP and returns ranked recommendations, with no fix-and-remeasure loop. React and Next.js performance rules and Django performance review check one stack's code against known patterns, with no before-and-after measurement. Only this skill has the strict revert rule and the ledger of attempts.

Install

Run one command — it saves SKILL.md and the files it uses into your agent's skills folder. Claude Code and Codex pick up a new skill without a restart; if it does not show up, restart the agent.

Claude Code — macOS, Linux
curl -fsSL --create-dirs -o ~/.claude/skills/performance-optimization/SKILL.md https://anymodel.org/en/skills/addy-osmani/performance-optimization/SKILL.md -o ~/.claude/skills/performance-optimization/LICENSE https://anymodel.org/en/skills/addy-osmani/performance-optimization/LICENSE -o ~/.claude/skills/performance-optimization/references/optimization-patterns.md https://anymodel.org/en/skills/addy-osmani/performance-optimization/references/optimization-patterns.md
Codex, Cursor — macOS, Linux
curl -fsSL --create-dirs -o ~/.agents/skills/performance-optimization/SKILL.md https://anymodel.org/en/skills/addy-osmani/performance-optimization/SKILL.md -o ~/.agents/skills/performance-optimization/LICENSE https://anymodel.org/en/skills/addy-osmani/performance-optimization/LICENSE -o ~/.agents/skills/performance-optimization/references/optimization-patterns.md https://anymodel.org/en/skills/addy-osmani/performance-optimization/references/optimization-patterns.md
Claude Code — Windows PowerShell
foreach ($f in 'SKILL.md','LICENSE','references/optimization-patterns.md') { $p = Join-Path "$HOME\.claude\skills\performance-optimization" $f; New-Item -ItemType Directory -Force (Split-Path $p) | Out-Null; Invoke-WebRequest "https://anymodel.org/en/skills/addy-osmani/performance-optimization/$f" -UseBasicParsing -OutFile $p }
Codex, Cursor — Windows PowerShell
foreach ($f in 'SKILL.md','LICENSE','references/optimization-patterns.md') { $p = Join-Path "$HOME\.agents\skills\performance-optimization" $f; New-Item -ItemType Directory -Force (Split-Path $p) | Out-Null; Invoke-WebRequest "https://anymodel.org/en/skills/addy-osmani/performance-optimization/$f" -UseBasicParsing -OutFile $p }

Any other agent: save the file into its skills folder, or give it the link to the file: https://anymodel.org/en/skills/addy-osmani/performance-optimization/SKILL.md

SKILL.md

Raw

Performance Optimization

Overview

Measure before optimizing. Performance work without measurement is guessing — and guessing leads to premature optimization that adds complexity without improving what matters. Profile first, identify the actual bottleneck, fix it, measure again. Optimize only what measurements prove matters.

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

When NOT to use: Don't optimize before you have evidence of a problem. Premature optimization adds complexity that costs more than the performance it gains.

Core Web Vitals Targets

Metric Good Needs Improvement Poor
LCP (Largest Contentful Paint) ≤ 2.5s ≤ 4.0s > 4.0s
INP (Interaction to Next Paint) ≤ 200ms ≤ 500ms > 500ms
CLS (Cumulative Layout Shift) ≤ 0.1 ≤ 0.25 > 0.25

The Optimization Workflow

1. MEASURE  → Establish baseline with real data
2. IDENTIFY → Find the actual bottleneck (not assumed)
3. FIX      → Address the specific bottleneck
4. VERIFY   → Measure again; keep or revert
5. GUARD    → Add monitoring or tests to prevent regression

Step 1: Measure

Two complementary approaches — use both:

  • Synthetic (Lighthouse, DevTools Performance tab): Controlled conditions, reproducible. Best for CI regression detection and isolating specific issues.
  • RUM (web-vitals library, CrUX): Real user data in real conditions. Required to validate that a fix actually improved user experience.

Frontend:

// Synthetic: Lighthouse in Chrome DevTools (or CI)
// Chrome DevTools → Performance tab → Record
// Chrome DevTools MCP → Performance trace

// RUM: Web Vitals library in code
import { onLCP, onINP, onCLS } from 'web-vitals';

onLCP(console.log);
onINP(console.log);
onCLS(console.log);

Backend:

// Response time logging
// Application Performance Monitoring (APM)
// Database query logging with timing

// Simple timing
console.time('db-query');
const result = await db.query(...);
console.timeEnd('db-query');

Where to Start Measuring

Use the symptom to decide what to measure first:

What is slow?
├── First page load
│   ├── Large bundle? --> Measure bundle size, check code splitting
│   ├── Slow server response? --> Measure TTFB in DevTools Network waterfall
│   │   ├── DNS long? --> Add dns-prefetch / preconnect for known origins
│   │   ├── TCP/TLS long? --> Enable HTTP/2, check edge deployment, keep-alive
│   │   └── Waiting (server) long? --> Profile backend, check queries and caching
│   └── Render-blocking resources? --> Check network waterfall for CSS/JS blocking
├── Interaction feels sluggish
│   ├── UI freezes on click? --> Profile main thread, look for long tasks (>50ms)
│   ├── Form input lag? --> Check re-renders, controlled component overhead
│   └── Animation jank? --> Check layout thrashing, forced reflows
├── Page after navigation
│   ├── Data loading? --> Measure API response times, check for waterfalls
│   └── Client rendering? --> Profile component render time, check for N+1 fetches
└── Backend / API
    ├── Single endpoint slow? --> Profile database queries, check indexes
    ├── All endpoints slow? --> Check connection pool, memory, CPU
    └── Intermittent slowness? --> Check for lock contention, GC pauses, external deps

Step 2: Identify the Bottleneck

Common bottlenecks by category:

Frontend:

Symptom Likely Cause Investigation
Slow LCP Large images, render-blocking resources, slow server Check network waterfall, image sizes
High CLS Images without dimensions, late-loading content, font shifts Check layout shift attribution
Poor INP Heavy JavaScript on main thread, large DOM updates Check long tasks in Performance trace
Slow initial load Large bundle, many network requests Check bundle size, code splitting

Backend:

Symptom Likely Cause Investigation
Slow API responses N+1 queries, missing indexes, unoptimized queries Check database query log
Memory growth Leaked references, unbounded caches, large payloads Heap snapshot analysis
CPU spikes Synchronous heavy computation, regex backtracking CPU profiling
High latency Missing caching, redundant computation, network hops Trace requests through the stack

Step 3: Fix the Bottleneck

Fix the one thing Step 2 identified, nothing else. The anti-patterns below are the usual suspects; each entry gives the rule and the signature to recognize it, and links to a worked fix in references/optimization-patterns.md. Open the one you need when you reach that code, not before.

Backend

  • N+1 queries. One query per row is the most common backend bottleneck. Fetch the relation in the same query (join/include) instead of in the loop. Pattern.
  • Unbounded data fetching. Every list endpoint paginates with a limit and a stable order. Pattern.
  • Queries that ignore their index. "Add an index" is the guess; EXPLAIN ANALYZE is the measurement. A Seq Scan where you expected an index, a rows= estimate off by an order of magnitude, and a Sort node above the scan each call for a different fix; a bad rows= estimate means stale statistics, so run ANALYZE rather than adding an index. Index for the shape of the query (equality columns first, then the range or sort column). A plain index will not help a query on a low-selectivity dominant value (a partial index serves the rare value), a leading wildcard (needs trigram or full-text), or a function applied to the column (index the expression, as in WHERE lower(email) = ?), and every index taxes every write. Re-run the plan afterwards; an index that did not change it is a revert. Pattern.
  • Connection pool exhaustion. Signature: every endpoint slows at once, time is spent waiting for a connection rather than executing, and the database shows mostly idle sessions. One pool per process, sized so instances × max stays under the database's connection ceiling. Bigger is not faster; it relocates the queue to the database where it is harder to see. With unbounded instance counts (serverless, autoscaling), multiplex through a proxy (pgbouncer, RDS Proxy) instead of raising max. Pattern.
  • Missing caching. Cache what is expensive to produce and read far more often than it changes; caching an already-fast query adds a network hop and a staleness bug in exchange for nothing. Pick the layer deliberately (in-process, shared, CDN). Every input that changes the response belongs in the key (tenant, locale, permissions, feature flags): a key that omits the viewer is how one user's data gets served to another. Choose one invalidation strategy (TTL, event or tag based, versioned keys) and state the acceptable staleness window explicitly. Guard hot keys against the stampede: serve stale while one request recomputes, or coalesce concurrent misses behind a single in-flight promise. Never cache what must be fresh (balances, permissions, inventory at checkout). Pattern; request coalescing, write strategies, and negative caching in ../../references/performance-checklist.md.

Frontend

  • Missing image optimization. Every image declares width and height (CLS). The LCP image gets fetchpriority="high", modern formats (AVIF, WebP) through <picture>, and srcset/sizes for resolution switching; below-the-fold images get loading="lazy" and decoding="async". Pattern.
  • Unnecessary re-renders. An object or function created in render is a new reference every time and re-renders every child that receives it. Hoist constants; reserve React.memo and useMemo for work the profile shows is expensive, since overuse is its own cost. Pattern.
  • Large bundle size. Modern bundlers tree-shake ESM named imports on their own; the real gains are route-level code splitting and lazy-loading heavy, rarely-used features behind Suspense. Profile before changing import styles. Pattern.

Step 4: Verify (Keep or Revert)

A fix is a hypothesis until you re-measure. This step decides whether it survives.

Re-measure the way you measured the baseline: same command, same conditions, same fixed budget (wall-clock, sample count, or request count). A baseline taken on a cold cache against a result taken on a warm one measures the cache, not your change.

Change one thing at a time. Three optimizations landed together produce one number, and you cannot attribute it. If they must ship together, measure each in isolation first.

Beat the noise, not just the mean. Repeat the measurement and compare the delta against run-to-run variance. A 3% gain inside ±5% variance is not a gain; it is a different sample.

Then decide, strictly:

Result vs. baseline Action
Past the threshold, tests green Keep. Commit with the before/after numbers in the message.
Within noise (no measurable change) Revert.
Worse Revert.
Improved, but a test went red Revert. A regression wearing a win's clothing.

"Neutral" is a revert, not a keep. This is the step teams skip: the change is already written, throwing it away feels wasteful, so it lands unmeasured, and the codebase accretes complexity that never bought anything. Code you keep, you maintain forever. Make it pay for itself.

Correctness gates the metric. The suite stays green and the number moves. An "optimization" that wins by dropping work the product needed (skipping a validation, caching something that must be fresh, removing an await that was load-bearing) is a regression, not a win.

Log every attempt, including the reverted ones

Reverted work leaves no trace in git history, which is exactly why the same dead idea gets tried again next quarter. Keep a short ledger so a discarded idea stays discarded:

Idea Baseline → Result Verdict Why
Memoize the row component INP 240ms → 235ms reverted Inside noise (±15ms). Rows weren't the bottleneck.
Virtualize the list INP 240ms → 90ms kept Long tasks gone from the trace.
Preconnect to the API origin LCP 2.8s → 2.8s reverted Already same-origin.

A section in the PR description or a PERF.md in the repo both work. What matters is that the next person (or the next agent) reads it before proposing an experiment, and doesn't re-run one that already failed.

Step 5: Guard Against Regression

Guard the metric the user actually feels, not every available number. Use the same LCP, INP, p95 latency, or other primary metric that justified the fix.

Use two complementary layers when the surface is user-facing:

  • Synthetic CI gate: Catch reproducible regressions before merge with a performance budget. Repeat noisy measurements or compare a median/trend so normal run-to-run variance does not turn the gate into a flaky check.
  • Field monitoring: Alert on a meaningful p75 movement in RUM data. Use attributed web-vitals data to locate the cause; treat CrUX's rolling window as confirmation rather than an immediate alert.

When either guard fires, return to Step 1 and establish a fresh baseline before proposing another fix.

Set budgets and enforce them:

JavaScript bundle: < 200KB gzipped (initial load)
CSS: < 50KB gzipped
Images: < 200KB per image (above the fold)
Fonts: < 100KB total
API response time: < 200ms (p95)
Time to Interactive: < 3.5s on 4G
Lighthouse Performance score: ≥ 90

Enforce in CI:

# Bundle size check
npx bundlesize --config bundlesize.config.json

# Lighthouse CI. The CLI package is @lhci/cli; unscoped `lhci` on npm is not it.
npx --package=@lhci/cli lhci autorun

See Also

For detailed performance checklists, optimization commands, and anti-pattern reference, see ../../references/performance-checklist.md.

Common Rationalizations

Rationalization Reality
"We'll optimize later" Performance debt compounds. Fix obvious anti-patterns now, defer micro-optimizations.
"It's fast on my machine" Your machine isn't the user's. Profile on representative hardware and networks.
"This optimization is obvious" If you didn't measure, you don't know. Profile first.
"Users won't notice 100ms" Research shows 100ms delays impact conversion rates. Users notice more than you think.
"The framework handles performance" Frameworks prevent some issues but can't fix N+1 queries or oversized bundles.
"The query is slow, add an index" Read the plan first. The index may already exist and be unusable, and every index taxes writes forever.
"Just cache it" Caching an already-cheap call buys nothing and adds a staleness bug. Cache what is expensive and re-read far more than written.
"Raise the pool size, we're running out of connections" A pool bigger than the database can serve moves the queue somewhere less visible. Find what holds connections.
"It didn't help much, but it doesn't hurt" Neutral changes are a revert. You pay maintenance on them forever and got nothing back.
"We already wrote it, may as well keep it" Sunk cost. The measurement doesn't care how long the change took to write.
"The improvement is obvious, no need to re-measure" Then re-measuring is cheap and proves it. Unmeasured wins are how neutral complexity lands.

Red Flags

  • Optimization without profiling data to justify it
  • N+1 query patterns in data fetching
  • An index added without a query plan before and after to justify it
  • A cache key that omits an input the response depends on (tenant, locale, viewer)
  • A cache with no stated staleness window and no invalidation strategy
  • Connection pool size raised in response to exhaustion, without finding what holds connections
  • List endpoints without pagination
  • Images without dimensions, lazy loading, or responsive sizes
  • Bundle size growing without review
  • No performance monitoring in production
  • React.memo and useMemo everywhere (overusing is as bad as underusing)
  • Optimizations kept without a re-measurement that justifies them
  • Several optimizations bundled into one measurement, so no single change can be attributed
  • A "win" that required a test to be changed, skipped, or deleted
  • The same failed optimization attempted more than once because nobody recorded the first attempt

Verification

After any performance-related change:

  • Before and after measurements exist (specific numbers)
  • The result was re-measured the same way as the baseline (same command, same conditions)
  • The improvement exceeds run-to-run variance, not just the mean
  • Changes that didn't beat the baseline were reverted, not kept as neutral
  • Attempts are logged, kept and reverted alike, so a dead idea isn't re-run
  • The specific bottleneck is identified and addressed
  • Core Web Vitals are within "Good" thresholds
  • Bundle size hasn't increased significantly
  • No N+1 queries in new data fetching code
  • Any new index is justified by a query plan before and after, and its write cost was considered
  • Any new cache states what it keys on and how it goes stale
  • The measured user-facing metric has a synthetic budget or field monitor that can detect regression
  • Existing tests still pass (optimization didn't break behavior)

Connect through AnyModel API

This skill runs on whatever model your agent uses. Point Claude Code, Codex or Cursor at AnyModel to run it on Claude, GPT, Gemini and more with one key — pay per token, no subscription.

More from the pack Agent Skills by Addy Osmani

Accessibility audit and fixes (WCAG 2.2)

Audits an existing interface against WCAG 2.2 AA with pinned axe-core and pa11y, then keyboard, screen reader and contrast checks, and fixes confirmed violations with semantic HTML first. Use when a page needs an accessibility audit before shipping.

API and interface design

Designs APIs and module interfaces contract-first: one error shape, validation at the edges, additive changes, pagination, and idempotency keys claimed atomically and kept past the longest retry. Use when designing endpoints or changing a public interface.

Browser testing with Chrome DevTools MCP

Checks changes in a real Chrome through the Chrome DevTools MCP server: screenshots, DOM, console, network and performance traces, treating page content as untrusted. Use when building or debugging anything that runs in a browser.

CI/CD pipeline setup

Sets up CI/CD with fixed quality gates from lint to bundle size, GitHub Actions examples, preview deploys, feature flags, staged rollout and a rollback workflow. Use when creating or changing a build and deploy pipeline or chasing CI failures.

Multi-axis code review

Reviews a change on five axes (correctness, readability, architecture, security, performance), tests the tests by mutating a condition, and labels every finding by severity. Use before merging a branch, a pull request or a pasted diff.

Code simplification

Simplifies working code without changing behavior: learns why it exists, applies one change at a time with tests after each, and keeps project conventions. Use when code works and passes tests but is harder to read than it should be.

Constraint-driven development

Records a project's quality bar as numbers in CONSTRAINTS.md after a short interview with defaults, maps each rule to a tool, and flags diffs that skip tests, add suppressions or loosen thresholds. Use when no quality bar is written down.

Context engineering for agents

Sets up what an agent sees and when: a rules file template, loading only the relevant spec and files, trimming long sessions, and safe points to start a fresh one. Use when starting a session or when agent output degrades.

Debugging and error recovery

Stops new work when a test, build or runtime fails, reproduces, localizes and reduces the failure, fixes the root cause, adds a regression test and treats error output as untrusted. Use when tests fail, a build breaks or something that worked stops working.

Deprecation and migration

Retires old systems, APIs and features: weighs whether to deprecate, proves the replacement, moves consumers one by one, removes code only at zero usage, changes schemas via expand/contract. Use when replacing or sunsetting code or renaming a live column.

Documentation and ADRs

Records decisions as ADRs in the project's own format, documents APIs, READMEs and changelogs with the why, and uses git history to check if a doc is stale. Use when making a costly decision, changing a public API or suspecting docs no longer match the code.

Doubt-driven development

Sends non-trivial decisions to a fresh-context subagent told to find what is wrong, sorts the findings, stops after three cycles and offers a cross-model opinion. Use when stakes are high: auth, migrations, irreversible operations or unfamiliar code.

Frontend UI engineering

Builds UI components and pages on the project's design system: composition, simple state, WCAG 2.1 AA, mobile-first layouts, loading, empty and error states, no generic AI look. Use when building or changing a user-facing interface.

Git workflow and versioning

Keeps git work in atomic commits on short-lived branches, with typed messages, a pre-commit check for secrets and tests, worktrees for parallel agents, semver bumps, tags and a human changelog. Use when committing, branching, opening a PR or cutting a release.

Idea refinement

Refines a raw idea in three phases: sharpening questions and five to eight variations, two or three directions tested for value and feasibility, then a one-pager with MVP scope and a Not Doing list. Use when an idea is vague or a plan needs stress-testing.

Incremental implementation

Builds changes in thin vertical, contract-first or risk-first slices, each tested, verified and committed before the next, with strict scope, feature flags and revertable steps. Use when a change spans several files or a task is too big to land in one step.

Interview me

Interviews the user one question at a time, each with a guessed answer and a confidence number, until the agent can predict the next replies, then confirms a statement of intent before any spec or code. Use when a request leaves who, why or success unclear.

Observability and instrumentation

Instruments a feature with structured JSON logs and request IDs, RED and USE metrics with bounded labels, OpenTelemetry traces and symptom-based alerts with runbooks, then tests the telemetry. Use when a feature, job or integration is headed for production.

Planning and task breakdown

Breaks a spec into small vertical-slice tasks with acceptance criteria, verification steps, sizes, dependency order and checkpoints, saved to tasks/todo.md or a named tracker. Use when a spec is ready but the work is too big to start in one go.

Security hardening

Hardens code with a short threat model, always, ask-first and never rules, and patterns for injection, XSS, access control, SSRF, secrets, dependencies, personal data and LLM output. Use when code handles user input, auth, sensitive data or outside services.

Shipping and launch

Prepares a production launch with a pre-launch checklist, a feature-flag rollout from 5% to 100%, thresholds for advancing or rolling back, an error-budget gate, a rollback plan and first-hour checks. Use when a feature or major change is about to ship.

Source-driven development

Grounds framework code in official docs: reads exact versions from the dependency file, fetches the relevant page, follows the documented API and cites full URLs, flagging anything unverified. Use when framework-specific code must match the version in use.

Spec-driven development

Writes a spec before code, surfacing assumptions and covering objective, commands, structure, style, tests and boundaries, then gates plan, tasks and code on approval, with capability maps and delta specs. Use when new work has vague requirements.

Test-driven development, red-green-refactor

Drives changes with red-green-refactor: finds the repository's own test commands, writes the failing test first, reproduces each bug with a test before fixing it, and sets rules on mocks and naming. Use when adding logic, fixing a bug or changing behavior.