Performance Profiling Plan
Sets a target and measures before optimising, so effort goes where the time actually is rather than where it feels slow.
Free — no card needed
Create a free account
to open Performance Profiling Plan — and the other 364 prompts across 21 categories.
Already have an account?
Running it, start to finish
- Write the target as a number on a specific operation.
- Instrument per stage and find the layer holding the time.
- Change one thing, re-measure, then add a regression guard.
What you get back
The output this produces, every time.
- Requires a numeric target at a percentile, without which the work has no stopping point.
- Finds which layer holds the time before looking inside any of them.
- Names what is not worth optimising, since halving a small share buys almost nothing.
Getting better results
Where this usually goes wrong, and how to avoid it.
- Never optimise on intuition. It is wrong often enough that acting on it wastes most of the effort. Measure the layers first, always.
- Set the target on a percentile. Averages hide the tail, and the tail is what people actually complain about.
- Add the guard before moving on. Without a benchmark or an alert, the same regression returns and the same week is spent again.
More Coding prompts
All Coding →- Coding
Refactor With a Safety Net
Plans a refactor as a sequence of individually safe, individually shippable steps, with the characterisation tests that make each one verifiable.
ClaudeChatGPT000Open → - Coding
Review for the Bug, Not the Style
A code review that hunts correctness failures and states the exact input that breaks each one, instead of listing naming preferences.
ClaudeChatGPTGemini000Open → - Coding
Database Migration Plan
Plans a schema change that ships without downtime, in steps that are each independently safe and reversible.
ClaudeChatGPT000Open →
Written for The AI University. Every prompt in this library is original work — authored, tested and revised here, not collected from elsewhere. 365 of them, free with an account.