The scenario
Support needs reproducible context without account tokens, user content, full URLs with query strings or environment secrets.
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
An allowlisted output and a negative privacy check make the support feature safer to verify.
A concrete outcome
Add a Copy diagnostics action containing build identity, browser/version details and non-sensitive error identifiers.
The result can be assessed against an observable task rather than prompt length or confidence.
Boundaries and a method
Build from an explicit field allowlist and reuse the clipboard/error UI. Explain any field whose privacy properties are uncertain before including it.
This leaves implementation judgment while constraining the changes that would exceed the task.
Evidence that can disagree
Inspect the copied text with synthetic sensitive values present elsewhere in the page. Verify those values are absent and clipboard failure is handled.
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.