From ct
Optimizes backend, API, database, and system performance via baseline measurement, profiling, strategy, implementation, and validation. For slow responses, query tuning, caching.
npx claudepluginhub pvillega/claude-templates --plugin ctThis skill uses the workspace's default tool permissions.
**No optimization without baseline measurement. No exceptions.**
Guides performance optimization workflow: profile baselines, identify bottlenecks, apply fixes for frontend (bundle size, rendering, images), backend (queries, caching), and database layers.
Identifies and fixes performance bottlenecks in code, databases, and APIs. Measures before/after execution times, profiles with DevTools/Node, optimizes queries/indexes/caching. Use for slow apps, APIs, or DB queries.
Profiles and optimizes frontend, backend, and database performance for scalable apps. Use for slow response times, scaling bottlenecks via Chrome DevTools, React Profiler, Node/Python profilers, Postgres/Mongo queries.
Share bugs, ideas, or general feedback.
No optimization without baseline measurement. No exceptions.
Skipped baseline? You cannot validate improvement. Period. Already started without measuring? STOP. Measure NOW before continuing. Already finished without measuring? Roll back to old code, measure, then re-apply changes and measure again.
Violating the letter of this process IS violating the spirit.
TodoWrite: Create items for each phase below.
Never skip measurement:
Measure with a reproducible tool under controlled conditions:
A curl wall-clock time is NOT a baseline. Use:
pg_stat_statements, EXPLAIN ANALYZE, slow query logcProfile, perfIf profiling contradicts your assumption, trust the profiler.
Before marking complete, ALL must be true:
| Thought | Reality |
|---|---|
| "Bottleneck is obvious, skip profiling" | 70% wrong without data. Profile first. |
| "We'll measure after" | Can't validate without before. Measure NOW. |
| "Manual testing / curl is enough" | Need reproducible metrics, not feelings. |
| "Production dashboards = baseline" | Different conditions, not controlled. Measure directly. |
| "Senior dev says cache everything" | That's a hypothesis, not a diagnosis. Profile first. |
| "Already changed the code, too late" | Roll back, measure old code, re-apply, measure again. |
| "No time to profile" | 15 min profiling saves hours of wrong-direction work. |
| "I've seen this pattern before" | This system is different. Measure THIS system. |
If you already made changes without measuring:
This costs 30-60 minutes. Shipping unvalidated "performance improvements" costs trust, debugging time, and potential regressions.