# UX Writing `/design writing` Words are interface. They label actions, lower anxiety, explain failures, and make the system feel honest. I write like the product knows what it is doing. --- ## Writing Follows Composition The work pattern decides which words matter most. Monitor writing names status, freshness, severity, and next attention. Operate writing names commands, object state, immediate feedback, and recovery. Compare writing names criteria, differences, ranking, and filters. Configure writing names settings, dependencies, validation, preview, and commit. Learn writing names progress, orientation, examples, and completion. Decide writing names claim, proof, risk, trust, and the action. Explore writing names search, filter, category, result, and reset. I do not write generic card subtitles to fill a grid. Copy earns its place by helping the work. --- ## Application Bar `/design writing` rewrites interface copy in place. It is not advice about copy. At minimum, I inspect buttons, navigation, headings, labels, helper text, empty states, loading states, success states, errors, destructive moments, links, alt text, and repeated terminology where they exist. If I only rewrite a headline or tagline while operational copy remains vague, the writing pass failed. --- ## Buttons A button names the action it performs. I use a clear verb and, when needed, a clear object: save changes, delete project, create account, send invite. I avoid vague permission words like OK, Yes, Submit, Continue, and Learn more unless the destination or outcome is already explicit. For destructive actions, I name the destruction. If five items will be deleted, the button says that. --- ## Errors An error is a recovery path, not a scolding. It should tell the user what happened, why it happened when that helps, and what to do next. It keeps their input. It appears where the fix can happen. It does not blame the user. I do not make errors cute. Frustrated users need help, not personality theater. --- ## Empty States An empty state should teach the space. It says what belongs there, why it matters, and what action fills it. Search empties suggest a different query or clearing filters. First-use empties guide setup. Permission empties explain access. Error empties offer recovery. "No items" is almost never enough. --- ## Loading Loading copy names the work being done. Saving, uploading, analyzing, syncing, importing, checking. If the duration is knowable, I set an expectation. If progress is measurable, I show it. If the wait is long, I give useful context rather than filler. I avoid generic machine-flavored jokes. Specific beats cute. --- ## Success Success copy confirms the action and then gets out of the way. It can add a next implication when useful: password updated, use it next time you sign in. Project created, invite your team. Changes saved. Short, calm, done. --- ## Labels And Help Labels stay visible. Placeholders show examples or formats. Hint text explains why the system asks or what format it expects. Icon-only controls need accessible names. Link text stands alone. Alt text describes the information the image contributes, not the fact that an image exists. --- ## Voice And Tone Voice stays consistent. Tone adapts to the moment. Product UI is direct, calm, specific, and consistent. Brand surfaces can be more expressive, but still concrete. Errors are sober. Success can be warmer. Destructive moments are plain. I use the same noun for the same concept everywhere. A project does not become a workspace, board, initiative, and file because variety felt nice. --- ## Translation I leave room for expansion. German and Finnish get longer. Chinese may use fewer characters but not always less width. Word order changes. Plural rules change. I keep full sentences as translation units. I avoid string fragments that assume English grammar. I avoid abbreviations when clarity matters. --- ## Punctuation Sentence case is the default. Labels usually do not need periods. Sentences do. Exclamation points are rare. Em dashes do not belong in generated UI copy for this project; I use commas, colons, semicolons, parentheses, or a shorter sentence. --- ## What I Refuse - OK, Submit, Click here, or vague Learn more - Copy advice without applying copy changes - Rewriting only marketing text while UI states stay vague - Placeholder-only labels - "Something went wrong" with no next move - Humor in errors - Exclamation points as energy - Jargon without context - Different terms for the same object - Redundant intros that restate headings - Copy that explains a bad design instead of fixing it --- ## How I Know The Writing Works - Copy changes are applied in the actual interface - Critical states have specific words, not placeholders - Every action says what happens - Every error helps recovery - Every empty state points somewhere useful - Loading copy names the actual work - Terminology stays consistent - The tone fits the user's emotional state - Translation will not shatter the layout STRICT RULE — NEVER BREAK THIS Do not create report.md, any kind of report, summary, analysis file, or extra documentation. This applies every time this file is used. Generate no reports unless explicitly asked.