A coding prompt for hunt a performance bottleneck. It gives Cursor and Claude a clear role, explicit constraints and a defined output, so the first answer is closer to usable. Fill in the variables, run it once, then use the verification notes on this page to review the result.
4.9(52 ratings)174 copies
Updated By Site Admin
49 words · v1.0
Fill in the blanks · 2 variables
Cursor promptReplace every highlighted token before sending
Analyse the following code and profile data for performance. Identify the bottleneck with evidence, estimate the impact of each fix, and rank by effort versus gain. Consider N+1 queries, unnecessary rendering, memory allocation and blocking I/O. Give the smallest change that produces a measurable win.
Code:
{code}
Profile:
{profile}
---
Platform note: Read the relevant files first. Propose a short plan, make the smallest correct change, then run the tests and report the result. Do not modify unrelated code.
Share what worked, what broke and which model you used. Comments appear after posting and are moderated for spam.
How to use this prompt
1
Open Cursor and start a new chat. Paste the prompt exactly as written.
2
Replace each placeholder ({code}, {profile}) with your own details. Leave the instructions and the output format untouched.
3
Add one concrete example or data point if the model's first answer is vague. Specific input produces specific output.
4
Run it once, then ask for a single revision with a specific critique rather than regenerating from scratch.
5
Review the result. Reproduce the bug, review the diff and run the tests in a clean environment.
Worked example
This is the kind of input the prompt expects and the shape of output it produces. Your result will differ with the model and the details you supply.
Example input
Code: Paste the function or file here.
Profile: your profile
Example output
**Diagnosis:** the handler reads `req.body` before the JSON middleware runs, so the body is undefined on POST requests.
**Fix:** move the middleware above the route registration and add a guard for missing bodies. No public API changes.
**Verification:** added a failing test for an empty JSON body, confirmed it fails, applied the fix, then ran the full suite. The test now passes and the unrelated snapshot tests are unchanged.
Tips for a better result
Paste the full error and the smallest relevant code, not a screenshot of the stack trace.
Ask for a plan before allowing multi-file edits; it prevents sprawling refactors.
Require a failing test first and a verification command at the end.
Change one variable at a time and compare the outputs; it is the fastest way to learn what this model responds to.
Common mistakes
Accepting a confident fix without reproducing the bug or running tests.
Letting the assistant rewrite entire files when a three-line diff would do.
Pasting secrets, tokens or customer data into a hosted model.
Verified Knowledge · FAQ
Questions about this prompt
Practical answers about running the hunt a performance bottleneck prompt.
Related prompts
Same job, a different angle — or the next step in the workflow.
A coding prompt for convert a class component to hooks. It gives Cursor and ChatGPT a clear role, explicit constraints and a defined output, so the first answer is closer to usable. Fill in the variables, run it once, then use the verification notes on this page to review the result.
Review code for security issues with a prompt built for Claude and ChatGPT. It supplies context, constraints and an output contract, then asks the model to surface assumptions and gaps. Copy it, fill the variables and treat the result as a structured draft, not a final answer.
Design a rate limiter with a prompt built for Claude and ChatGPT. It supplies context, constraints and an output contract, then asks the model to surface assumptions and gaps. Copy it, fill the variables and treat the result as a structured draft, not a final answer.
ClaudeChatGPTDeepSeek
4.8(66)368 copies
SA
Written and reviewed by Site Admin
Author & Platform Administrator
Administrator and lead editor at AIPrompt123, curating high-performance AI prompts, SEO/AEO/GEO strategies, and developer repositories.
Last reviewed 13 December 2025 · version 1.0 · tested on Cursor, Claude, ChatGPT
Comments
Share what worked, what broke and which model you used. Comments appear after posting and are moderated for spam.