Performancemanual
Bundle Size Budget
Ship features without bloating the client bundle — loop until size checks pass under your budget threshold.
Kickoff prompt
Start the "Bundle Size Budget" loop.
Goal: client bundle stays under the size-limit budget
Max iterations: 6
Between iterations run: npm run build && npm run size-limit
Exit when: size-limit exits 0
Step 1: Build and measure bundle size. If over budget, lazy-load or trim deps until size-limit passes.
Self-pace this loop. After each iteration, run the check command, read the output, and only continue if the exit condition is not met. Stop when the exit condition passes or max iterations is reached. Give a short status update each pass.Basic information
Category
Performance
Goal
client bundle stays under the size-limit budget
Max iterations
6
Check command
npm run build && npm run size-limit
Exit when
size-limit exits 0
Supported agents
Cursor
Steps
- 1
Measure bundle
Run the production build and bundle size check. Report total KB and the largest new chunks.
npm run build && npm run size-limit - 2
Trim or lazy-load
If over budget: dynamic-import heavy modules, remove unused deps, or split routes. No feature cuts unless necessary.