Changelog from raw commit history
writingGroups commits into user-facing changes, without inventing anything that is not in the log.
Audit interface copy for clarity
Rewrites button labels, errors, and empty states so they say what happened and what to do.
When to use it
Before shipping a flow, or when support tickets show people misreading the UI.
The prompt
Copy into your assistant
Audit the interface copy below.
For each string, decide whether it states:
- what happened, and
- what the person can do next.
Rewrite only the strings that fail. Keep the meaning identical; change nothing about the feature.
Rules:
- Buttons: verb plus object ("Save draft", not "Submit").
- Errors: what failed, why if known, and the next action. Never apologise and never blame the user.
- Empty states: say what will appear here and how to make it appear.
- No exclamation marks, no "Oops", no "Something went wrong" on its own.
Output a table: current string, problem, replacement.
Copy:
<strings>What to change
Include the screen name next to each string — the same sentence needs different copy on a settings page and a checkout page.
Why it works
The two-question test (what happened / what can I do) is mechanical enough to apply at scale, which is what makes an audit finishable.
More writing prompts
- Changelog from raw commit historyGroups commits into user-facing changes, without inventing anything that is not in the log.
- Landing copy from a feature listTurns what the product does into what it removes from the reader's day.
- Incident postmortem from a raw timelineTurns logs and a chat transcript into a blameless postmortem with contributing factors, not a culprit.
Going deeper
- Prompts that survive contact with realityUsing agents · Level 2
- Writing a skill that changes behaviorSkills and prompts · Level 2
- The last hour before launchRunning agents in production · Level 3