Loop/Prompt Library / Speed, performance & cost
🔁 Save a speed baseline after release
After each release, runs the standard speed tests and saves the results so future changes can be compared.
Use it when: You just shipped and want a clear 'before' snapshot for next time.
🛑 Stops when: The new baseline is saved with the exact version, setup, and results.
Copy this loop
Release [version] just finished. Run our standard benchmarks: [list or command]. Record the results along with the exact version, environment, benchmark version, and test conditions. Save them as the new baseline in [file or location]. If a benchmark fails, retry it once, then mark it failed and do not overwrite the old baseline for it. Stop when every benchmark is recorded or marked failed.
Review every change the agent makes before you keep it. Set a budget or round limit — the prompt includes one.
Idea from Forward Future's Loop Library · by Matthew Berman. Prompt rewritten in plain English by FixKit AI.
More loops like this
Lighter first page load
Shrinks how much a website downloads before the first screen shows, without changing how anything looks.
Trim unused styles
Removes unused styling code one piece at a time and keeps the removal only if every page looks exactly the same.
Super-fast pages
Keeps speeding up the app until every page loads in under a target time, like 50 milliseconds.
Smooth game frame rate
Measures a game's frame rate in the same scene each time, fixes the biggest slowdown, and keeps only changes that help.
Snappy buttons and transitions
Checks that buttons, hovers, and page changes in a design system respond fast enough, and fixes the slowest ones.
Faster test suite
Makes tests run faster without testing less.