---
name: copy-tone-pass
description: Review UI copy against a tone sheet and flag off-voice strings with concrete rewrites. Use when an interface has grown copy from many hands and the voice has drifted - buttons, errors, empty states, confirmations, emails. The writer keeps the last word; this pass finds and proposes, never overwrites.
---

# Copy Tone Pass

## When to use

- UI copy comes from many authors and the voice has drifted
- A tone sheet or style guide exists (even a short one)

Do NOT use without a tone reference. If none exists, draft three
candidate tone rules from the best existing copy, get them confirmed,
and only then audit against them.

## Collect the strings

1. Gather user-visible strings: buttons, labels, errors, empty
   states, confirmations, toasts, emails, onboarding.
2. Group by surface (forms, errors, navigation, marketing) - tone
   rules often differ per surface, and an error page is not a
   settings label.
3. Note the source file for each string so findings land where the
   copy lives.
4. Cap the pass. On a large app, every string is a crawl, not a
   review: sample the top surfaces by traffic or the first N strings
   (default N=200), and state the coverage in the output.

## Judge against the sheet, not your taste

Flag a string only when it breaks a rule on the sheet:

- **Register**: too formal or too casual for the surface
- **Person and tense**: "we have created" vs "you created" drift
- **Jargon**: words the sheet bans (leverage, utilize, please note)
- **Blame**: errors that accuse the user ("you entered a bad...")
- **Caps and punctuation**: Title Case vs sentence case, exclamation
  marks where the sheet allows none

If a string is off-voice but breaks no written rule, list it under
"judgment calls" separately - do not invent rules to convict it.

## Propose, never overwrite

Each finding: the string, the rule it breaks, a suggested rewrite,
and why the rewrite follows the rule. One rewrite per string - three
options is indecision, not help.

## Output format

Grouped by surface, then by rule. End with counts per rule broken and
the three highest-visibility strings to fix first - visibility from a
usage signal you actually gathered (page views, entry-point screens).
If you have no traffic data, say so and rank by surface prominence;
never present a guess as traffic.

## Hard boundaries

- Never rewrite strings in place; the writer decides.
- Never flag style preferences as rule violations.
- Errors and legal-adjacent copy (deletion, payment, data export)
  get extra care: clarity beats voice there, every time.
