§ Corrective
/voice
UX writing discipline — register, specificity, voice.
What it does
Most AI-generated copy apologizes before describing what failed. The opening “Oops!” — the warmth-padding sentence — the generic “Try again” at the bottom. /voice replaces this friendly-professional SaaS template with copy that respects the audience: errors that name the failure, buttons that name the action, empty states that introduce the space rather than null-checking it.
Like the other correctives, it uses a smart-default autonomy model. Small replacements (specific verbs, removed apologetics, dropped warmth-padding) get applied directly. Larger voice-character shifts — moving from formal to casual, technical to plain, friendly to direct — are surfaced for your approval before executing.
Interactive
Hero — primary CTA
Signup section
Join 10,000+ people finding their stillpoint.
When to use it
- Errors begin with “Oops!” or apologize before describing what failed.
- Buttons are labeled with generic verbs (“Submit”, “Continue”, “Get Started”) that don’t name the action they trigger.
- Empty states say “No data available” or similar — placeholders that describe absence rather than guiding action.
- Helper text restates the label rather than adding what the user couldn’t infer.
- Confirmations say “Success!” or “Done!” without naming what was saved or completed.
- Voice drifts across surfaces — formal in one area, casual in another, with no character-driven reason.
How to use it
By default /voice runs a full pass across errors, empty states, confirmations, button labels, and helper text. Pass a scope to focus on one type of copy, or describe the surfaces you want corrected. Voice character is calibrated to the project context — /voice doesn’t inject warmth into a precision-oriented product, and won’t strip directness from a product whose context calls for it.
- /voice errors
- /voice ctas
Anti-patterns it addresses
- “Oops! Something went wrong” — the AI-default error opener that apologizes before saying what failed.
- “Submit”, “Continue”, “Get Started”, “Learn more” — generic CTAs that don’t name what the action does.
- “No data available” / “No results found” — empty states that describe absence rather than guiding the user toward action.
- Helper text that paraphrases the label (“Email: enter your email address”).
- “Success!” / “Done!” confirmations that don’t name what was saved or completed.
- Voice drift — formal language in one surface, casual in another, with no character-driven reason for the difference.