better-writing

Topics in the source

• Writing
• Inventory the existing strings first
• One voice, one vocabulary
• Address the reader directly
• Plain words over clever ones
• Build strings whole
• Verb-first buttons
• Links describe their destination

This skill writes and reviews interface copy such as labels, errors, empty states and confirmations, along with the terms that run through them. It matches the product's existing voice and flags copy that misleads people or leaves them without a way forward. 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. Rewording that merely suits your taste is not a finding. How copy renders, including text-transform, truncation and smart punctuation, belongs to better-typography. Error markup, announcements and the attributes that carry accessible names belong to better-accessibility. Room for translated strings belongs to better-layout. Before writing or reviewing, find where the copy lives and read the copy around the change: 1. Search for the translation call (t(, i18n., Notifications > Email". An error is an instruction, and it belongs beside the field that failed: | Bad | Good | | --- | --- | | That password is too short | Choose a password with at least 8 characters | | Invalid date | Enter a date as DD/MM/YYYY | | Oops! Something went wrong. | Unable to save

This is an excerpt. Refer to the complete source and its current requirements.