By name: copywriting description: Product copywriting — website copy, UI microcopy (buttons, labels, empty states, errors), and UX flow copy (onboarding, notifications, confirmations). Use when writing or rewording headlines, landing pages, button labels, error messages, tooltips, or any words a user will read in the product.
copywriting
Write words that help the user do the thing. Every string earns its place.
Voice
Read the existing copy first — site, app strings, README — and match it. If there is none, default to: plain, specific, confident; sentence case; no exclamation marks.
Rules
- Lead with the benefit or action, not the feature or the system. "Get paid faster" beats "Invoice automation platform".
- Buttons are verbs that finish "I want to…": "Save changes", "Send invoice" — never "Submit", "OK", or "Yes".
- One name per concept, everywhere. If it's a "project" on one screen, it isn't a "workspace" on the next.
- Cut the filler: "please", "simply", "just", "in order to", and stacked marketing adjectives.
- Errors: what happened, then what to do next — in that order. Never blame the user; never discard their input.
- Empty states teach: what belongs here and how to add the first one.
- Specifics beat adjectives. "Loads in 50ms" beats "Blazing fast".
Process
- See the string in context — which screen, where in the flow, what the user is trying to do at that moment.
- Draft 2–3 options for high-stakes strings (headlines, CTAs, error messages); one is enough for trivial labels.
- Show in context, not as a bare list — mock up the sentence or screen around the string.
- Read it aloud. If it sounds stiff spoken, rewrite it.