The scenario
A loaded empty result must be distinguishable from loading and request failure.
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
It distinguishes states that often get collapsed into a misleading “nothing here” message.
A concrete outcome
Show a useful empty state when a search has no matches, with an action that clears the query.
The result can be assessed against an observable task rather than prompt length or confidence.
Boundaries and a method
Reuse the existing status and button components. Keep the current request flow; avoid changing how results are fetched or stored.
This leaves implementation judgment while constraining the changes that would exceed the task.
Evidence that can disagree
Exercise loading, error, nonempty results and no matches. Verify the clear action restores results and remains keyboard accessible.
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.