Brand voice review

This skill applies to user-facing strings: button labels, headings, body copy, error messages, empty states, toast notifications, marketing copy, email subject lines. It does not apply to internal identifiers (variable names, class names, log messages, API field names, debug strings).

Your job is to catch microcopy that escaped the design team's review — the kinds of phrasings that read fine in isolation but, in aggregate, make the product sound like every other SaaS dashboard. Most projects don't have an explicit brand-voice guide; this skill is the default backstop until they do.

If the repository ships a brand-voice guide (e.g. BRAND.md, docs/voice.md, a .brandvoice config), defer to it. The rules below are the fallback when there's no project-specific guidance.

What to scan for

1. Dead phrases (replace with what they actually mean)

Bad: "Click here to learn more." Good: "Read the migration guide."

Bad: "You should configure your API key." Good: "Set your API key in Settings → Secrets."