Review buttons, errors, empty states, confirmations and notifications, and rewrite the ones that fail.
audit_copy
Before: what you give it
The example input, as sent.
button: Submit button: Cancel button: Delete workspace error: Something went wrong. Please try again. error: Invalid email address entered. error: Error 403 empty_state: No results. empty_state: You haven't added any clients yet. confirmation: Your changes have been saved successfully! notification: Hey there! Just a quick heads up that your trial is ending soon, so be sure to check out our plans.
After: what comes back
The answer from a real run on 2026-10-24, shown in full. Nothing is edited by hand.
"Something went wrong. Please try again."
Issue: Does not say what failed or whether the person's work was saved, so they cannot tell if retrying will lose data.
Fix: [What failed]. Your changes have not been saved. Try again.
"Cancel"
Issue: Ambiguous whether this closes the dialog or cancels the underlying action (e.g. an order, a subscription), which matters because the two have different consequences.
"Submit"
Issue: Names the mechanism, not the outcome, so the reader cannot tell what will actually happen when pressed.
"Error 403"
Issue: Raw status code with no explanation of what happened or what to do next.
Fix: You don't have permission to view this. Contact your administrator for access.
"Invalid email address entered."
Issue: Passive blame framing ('entered') and gives no instruction on how to fix it.
Fix: Enter a valid email address.
"Your changes have been saved successfully!"
Issue: Exclamation mark adds cheerfulness not present in the original intent, and 'successfully' is redundant with 'saved'.
Fix: Your changes have been saved.
"Hey there! Just a quick heads up that your trial is ending soon, so be sure to check out our plans."
Issue: Reason for interruption is buried past the first six words, tone is overly casual, no end date is given, and 'check out our plans' is not a clear action; read hours later 'soon' is meaningless.
Fix: Your trial ends on [date]. Upgrade to keep using [product].
"No results."
Issue: Does not say why there are no results or what to try next.
Fix: No results for '[search term]'. Try a different search.
"You haven't added any clients yet."
Issue: States the empty condition but offers no first action to take.
Fix: You haven't added any clients yet. Add your first client to get started.
What you get
Each string that has a real problem, the reason it fails, and a replacement. Strings that already work come back untouched.
What gets better
Every message says what happened and what to do next, in one consistent voice.
When to use it
Before shipping UI copy, or when an agent has generated a screen full of strings.
What it cannot do
Up to 60 strings per call. It checks clarity and tone, not whether the wording fits your brand guide, and replacements keep placeholders like [date] for you to fill.
Run it
Two free calls a day with no key. Send your own Anthropic key in an x-anthropic-key header to lift the limit.
curl -X POST https://verdict.allthepossibles.com/api/audit_copy -H 'content-type: application/json' -d '{"strings":[{"text":"Submit","context":"button"},{"text":"Cancel","context":"button"},{"text":"Delete workspace","context":"button"},{"text":"Something went wrong. Please try again.","context":"error"},{"text":"Invalid email address entered.","context":"error"},{"text":"Error 403","context":"error"},{"text":"No results.","context":"empty_state"},{"text":"You haven'\''t added any clients yet.","context":"empty_state"},{"text":"Your changes have been saved successfully!","context":"confirmation"},{"text":"Hey there! Just a quick heads up that your trial is ending soon, so be sure to check out our plans.","context":"notification"}]}'
The other reviews
- critique_experience
Find the problems in a design before a user or an engineer does, ranked by how badly each one hurts.
- generate_state_matrix
List every state a feature can be in, including the ones nobody drew.
- map_journey
Map the stages around a goal and name the entries, exits and interruptions the flow forgot.
- find_assumptions
Pull the unchecked beliefs out of a brief and turn each into a question you could answer this week.
- check_terminology
Find one concept that goes by several names across your UI, docs and API.