The scenario
The displayed rows are already authorized for the current user. Required columns are the existing visible text columns.
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 prompt defines which data may leave the app and tests encoding rather than download liveness alone.
A concrete outcome
Let users download the currently filtered rows as CSV in their displayed order.
The result can be assessed against an observable task rather than prompt length or confidence.
Boundaries and a method
Inspect existing export and CSV-encoding utilities. Reuse a correct encoder, preserve permissions, and exclude hidden/internal fields. Report any ambiguity in the column contract.
This leaves implementation judgment while constraining the changes that would exceed the task.
Evidence that can disagree
Verify commas, quotes, newlines, empty cells, filtered selection and row order. Compare parsed values rather than only checking that a file downloads.
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.