Write clear interface copy and recovery steps

better-writing writes and reviews interface copy, including labels, errors, empty states, confirmations and the terminology shared across a flow. It matches the product's existing voice and flags wording that misleads people or leaves them without a next step. A deliberate brand voice is preserved; taste alone does not make wording a defect. Departures from plain language become findings when they introduce inconsistency, ambiguity, translation risk or an inappropriate tone.

The workflow begins by locating translation calls and their locale files, alongside any copy supplied by a CMS or API. It inventories nouns for objects, verbs for actions, capitalization by element type and existing style guidance. New strings reuse that vocabulary. Multi-step flows keep consistent progression terms, and tone changes with stakes: lighter for onboarding or success, neutral for settings, calm for errors and explicit for security or data loss.

Instructional copy addresses the reader directly, removes unnecessary words and avoids idioms or humor that will not translate. Perspective stays consistent, possessives stay restrained and device language matches the interaction. Complete messages use placeholders and locale plural rules rather than concatenated fragments. Numbers, dates and lists use Intl formatting.

Button labels begin with an action verb, and icon-button names describe actions rather than glyphs. Links name their destinations so they remain meaningful outside surrounding text. Capitalization follows one policy for each element type. Toggle labels describe the enabled state, and references to settings link directly rather than narrating a navigation path. Placeholders provide realistic examples in the accepted format.

Errors state what failed and how to recover, next to the failed field, without blame or playful language. Known requirements appear as helper text before failure. Repeated errors can call for an interaction redesign. Frequent reversible actions favor undo; irreversible actions, bulk destruction or effects on other people require confirmation that names the action, object and consequence. Destructive buttons use explicit verb-and-object labels, and high-impact object deletion can require typing the object's name.

Empty states orient the reader and offer a clear next action. Filtered emptiness names the query and provides an exit. Persistent information belongs elsewhere because an empty state disappears when content arrives. An empty state can provide orientation and a next step:

<p class="font-medium">No projects yet</p>
<p class="text-sm text-zinc-500">Projects keep your tasks and files together.</p>
<button class="mt-4">Create a project</button>

Use it for an authorized interface-copy review or requested writing changes. Reviews remain read-only unless implementation is requested. Connected services require authorization, and synthetic fixtures avoid private customer data. It preserves the established voice and unrelated work rather than imposing a new style on a local edit.

Inputs include components, locale files and surrounding strings. Verification checks labels against actual actions, errors for recovery instructions and terms against the inventory. Unseen server or CMS strings are marked Not verified. Findings are grouped by principle and severity, with locations, before, after and user impact. HIGH covers misleading copy, missing error recovery or destructive actions with neither confirmation nor undo. MEDIUM covers inconsistent voice, terms or capitalization; LOW covers isolated wording polish. Any remaining HIGH yields Block; otherwise the report ends Approve within inspected coverage.

better-typography owns rendering and truncation, better-accessibility owns error markup and name-bearing attributes, better-layout owns translated-string space, and better-colors owns destructive-action color. The workflow is adapted from jakubkrehel/skills under the MIT license.