back
loading skill details...
UX writing and interface copy. Use when writing or reviewing any user-facing text. Triggers on UX writing, microcopy, button labels, link text, error messages,…
Interface writing Clear and brief beats clever; consistent beats varied. The best error message is the interaction redesigned so the error cannot happen. How copy renders (capitalization via text-transform, truncation, smart punctuation) belongs to better-typography. Error markup and announcements (aria-invalid, live regions) belong to better-accessibility. Room for translated strings belongs to better-layout. Recon the existing voice Before writing or reviewing, read the copy nearby. Note the product's terminology, its localization conventions and any voice or content style guide. A deliberate brand voice is not a defect. Raise a departure from plain language only when it creates inconsistency, ambiguity, translation risk, or a tone the stakes don't support. One voice, flexible tone The product has one voice and its existing copy establishes it. A local edit does not get to invent a new one. Keep terms consistent: if it's "Archive" in the menu, it isn't "Move to storage" in the toast. Tone flexes with the stakes:
don't have the plugin yet? install it then click "run inline in claude" again.