Better Writing is an agent skill for interface copy. It starts by inventorying the strings a product already has, the nouns used for objects and the verbs used for actions, then writes or reviews new copy with those terms and one consistent voice.
It flags copy that misleads people or leaves them without a way forward, such as vague errors, generic link text and double-negative toggles. A deliberate brand voice is respected unless it creates ambiguity or translation risk.
What You Get
- A term inventory built from translation calls and locale files, so new copy reuses the product’s own nouns, verbs and case policy
- Rewrites of errors into instructions, such as a password rule stated as a requirement and a failed save with a next step
- Destructive flow templates: a title naming the action and object, a body stating what is lost and buttons that pair a verb with an object
- Empty-state patterns that say what the place is and offer one next action, with filtered variants that name the query
- A detection table for strings such as Click here, Oops, Are you sure, successfully and concatenated plurals
Common Use Cases
- Rewriting vague error messages across a signup form
- Replacing a Yes and No confirmation dialog with a clear verb and object
- Fixing toggles labeled with Don’t or Disable so they describe the on state
- Replacing string concatenation and singular and plural ternaries with a message with plural arguments
What Makes It Unique
It prefers undo over confirmation for reversible, frequent actions and reserves typed confirmation for destroying accounts, workspaces or repositories. It treats taste as a non-finding: rewording that only suits the reviewer is out, while inconsistency, ambiguity and dead ends are in.
Under The Hood
The skill is a SKILL.md with a patterns reference and a reporting reference. It has no scripts. The agent searches your code for translation calls and locale files such as JSON, po and strings files, reads the surrounding copy and checks each label, error and term against the inventory. Strings that come from a server or CMS and cannot be seen are marked Not verified. A review leaves files untouched, and edits happen when you ask for fixes.