The scenario
A reproducible search request is slow, but no component has been established as the cause.
Required context: a selected repository matching this scenario, relevant task evidence, and access to its instructions and checks. Use redacted or synthetic data where appropriate.
Adapt the complete prompt
Edits stay in this browser tab. Saving bookmarks the original example; export your edited version to keep it elsewhere.
Why this is a strong example
The deliverable is a measurement-backed next step, not an unsupported performance rewrite.
A concrete outcome
Map the request path for the slow search endpoint and identify the next discriminating measurement.
The result can be assessed against an observable task rather than prompt length or confidence.
Boundaries and a method
Trace UI timing, network handling, server work and database calls. Keep this investigation read-only and use redacted request details. Do not optimize based on a guess.
This leaves implementation judgment while constraining the changes that would exceed the task.
Evidence that can disagree
Record measured timings where available, distinguish them from estimates, and propose one experiment that separates the leading causes.
These checks describe what would make acceptance justified; asking for them does not mean they ran.
A safe way to encounter uncertainty
If the repository contradicts these assumptions, required access is unavailable, or a consequential product decision is missing, explain the conflict and pause the dependent work. Preserve unrelated changes.
Consequential uncertainty stays visible rather than being converted into an invented requirement.