performance-and-caching
Installation
SKILL.md
Performance and caching
Speed comes from doing less work, then from doing it at the same time, and only last from remembering it. A cache added before measuring hides the slow part, adds stale data and a second source of truth. Read the file for the step:
| The step | Read |
|---|---|
| Find where the time goes; validate benchmark work, errors, tuning, limits and repeated comparisons; cut round trips; parallelize (never ahead of auth checks or for CPU work); index; Vercel thresholds; deterministic counts and steering a perf push | MEASURE.md |
| Push filtering, aggregation, ordering and limits into SQL; anti-joins, top N, window functions, sargable predicates, keyset pagination, index design and index regressions, full-text search | QUERIES.md |
Add, fix or remove a cache at any layer; Vercel CDN headers, Vary, 404s and immutable; what cacheLife proves; module-level and browser storage caches; large lookup data: fetch granularity, cache tiers, Bloom filters, indexed shards |
CACHING.md |
| Browser loading, media, layout shifts, long lists, main-thread work, interaction traces and Lighthouse gates | web-performance |
Read production metrics on Vercel with vercel metrics: setup checks and what each failure means, Observability Plus access and retention, the query catalog with documented metric names, the window, limit and rate rules, Core Web Vitals good limits, project vs team cost |
VERCEL-METRICS.md |
| Audit production cost and performance from metrics: candidate gates, bounded investigations, abstentions and evidence-backed recommendations | TELEMETRY-AUDIT.md |
Apply only the routes and checks for the selected job. Read a linked skill's named file from its installed folder when available, or from the linked source. Report an unavailable required reference instead of inventing it. [skill-authoring, DISTRIBUTION.md#composing-skills]