Audit Performance

Overview

Generate a performance budget audit against Core Web Vitals (LCP, INP, CLS), bundle size, and API latency. Defines thresholds, identifies violations, and provides actionable recommendations for image optimization, code splitting, lazy loading, and caching improvements.

Workflow

1. Read engineering context -- Scan .chalk/docs/engineering/ for architecture docs, existing performance budgets, and infrastructure configuration. Check the codebase for build configuration (webpack, vite, next.config) and existing performance tooling.

2. Parse the audit target -- Extract from $ARGUMENTS the page, feature, or endpoint to audit. If unspecified, audit the most critical user-facing page (typically the landing page or main dashboard).

3. Determine the next file number -- Read filenames in .chalk/docs/engineering/ to find the highest numbered file. The next number is highest + 1.

4. Define performance budgets -- Set thresholds (use existing budgets from docs if available, otherwise use industry standards):

   Metric	Good	Needs Improvement	Poor
   LCP	< 2.5s	2.5-4.0s	> 4.0s