Bundle Size Budget

Ship features without bloating the client bundle — loop until size checks pass under your budget threshold.

2 copies · 11 views

Use loop copies the kickoff. Share copies the loop link. Open in Cursor / Claude Code only pre-fill that prompt — they do not install hook files. Download loop saves a README and kickoff into .cursor/loops/bundle-size-budget/ — no hooks required. Full install guide

Guardrails

Hardened

Anti-gaming rules

Rules the agent must follow so it cannot cheat the exit condition.

Do not modify the check command or exit criteria to force success
Do not skip, disable, or bypass checks to pass the exit condition
If stuck after several iterations, stop and report blockers instead of gaming metrics

How to run this loop

Prompt only

Run “Bundle Size Budget” in your agent

Deeplinks and “Open in Cursor” only paste the kickoff prompt. They do not install hook files — your agent cannot tell whether files are on disk until you add them yourself.

Two separate pieces

Kickoff prompt — tells the agent the goal, check command, exit condition, and how to self-pace between passes.

1
Copy or open the kickoff prompt
Click Use loop to copy the kickoff into your clipboard. Open in Cursor and Open in Claude Code only open the agent with that prompt — they do not configure automation for you.
2
Paste into your coding agent
Start a chat in Cursor, Claude Code, Codex, or any agent. Paste the kickoff. The prompt includes the goal, iteration limit, shell check, and first step.
3
Agent self-paces until done
The agent runs the loop: act → run check command → read output → repeat until the exit condition is met or max iterations is reached. No install step is required for prompt-only loops.

Full guide with Cursor /loop notes: How to install loops

manual trigger

Performance

Manual start

Measure bundle

Trim or lazy-load

Bundle size is under the configured budget

Rendering diagram…

Steps

What the agent does on each pass.

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.

Kickoff prompt

Copy this into your coding agent to start the loop.

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.

Related loops

Quality

manual

4 copies

A11y Audit Until Clean

Run automated accessibility checks on changed routes, fix violations, and repeat until the audit is clean.

Start the "A11y Audit Until Clean" loop. Goal: zero serious accessibility violations on changed UI Max iterations: 8 Between iterations run: npm run test:a11y Exit when: a11y audit exits 0 Step 1: Run the a11y audit on changed routes. Fix each violation, prioritizing keyboard and screen reader issues. 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.

a11y

quality

frontend

by loops!

View