web-performance

Topics in the source

• Web Performance
• Mode 1 -- Default (always on, inside your current task only)
• Mode 2 -- Audit (on request: "audit perf", "why is it slow")
• Report format
• Use by the lead
• Reference Guide
• Forbidden

Web Performance gives domain experts 31 performance rules (numbered 1-31, stable across reports) in two modes. Default mode is always on: while writing code for its task, the expert applies the relevant rules by itself. Audit mode runs on request: baseline measurement, every rule reviewed with evidence, absent rules ranked by gain, then a STOP for the owner's validation before any fix. The skill is advisory. It never builds architecture (job queue, Redis, tracing, regions, load balancing) without the owner's go, and the audit phase never edits code. When you write or change code, apply these as defaults -- no request needed, no refactor of code your task does not touch: | Area | Default | |---|---| | Images | Framework image component (next/image, Astro / ), WebP/AVIF, sizes, explicit dimensions; loading="lazy" below the fold, never on the LCP image | | Loading UI | Skeleton matching the final layout when the layout is known; spinner only for unknown shape or short actions | | Inputs | Debounce search/autocomplete; cancel stale requests (AbortController) | | Data fetching | Independent requests in parallel (Promise.all, Http::pool); one shared cache (TanStack Query, fetch cache, se

This is an excerpt. Refer to the complete source and its current requirements.