setup-ux-copy

name: setup-ux-copy description: Enforce UX text style hooks for UI strings and prose. Use when checking sentence case, action labels, banned phrases, inclusive language, Redpanda terms, or Markdown prose style.

Repo/code changes: run /deslop before commit, push, PR, or merge. Two PostToolUse hooks on Edit/Write: one for code-string UX copy, one for prose.

Ban exclamation points in UI strings
Ban "successfully" (use past-tense verb: "Topic created")
Ban "click here" and bare "here" link text
Ban blame language ("Oops", "Uh oh", "Whoops")
Ban "Yes"/"No" button labels (use action verbs)
Ban non-inclusive terms (whitelist/blacklist -> allowlist/denylist, master/slave -> leader/follower)
Warn possessive pronouns in titles/nav ("My Settings" -> "Settings")
Warn bold/italic/monospace in string literals
Warn ALL CAPS for emphasis (not acronyms)
Warn Title Case (3+ consecutive capitalized words)
Warn spelled-out numbers (1-9 as numerals in UI)
Warn "and/or" (use "and", "or", or "A, B, or both")
Warn "etc.", "e.g.", "i.e.", "please", "via", "There is/are" starters
Warn generic CTA labels ("Submit", "OK", "Done") -- name the action
Warn vague error copy ("Invalid input", "Something went wrong") -- state cause + recovery
Warn dead-end empty states ("No data", "No items found") -- explain why + next step

Microcopy must guide and reassure: labels, errors, placeholders, tooltips, toasts.
CTA text owns the action: "Save changes" beats "Submit".
Front-load scannable copy: lead with the object or result users need.
Error messages say what happened and how to recover.
Placeholders are examples or hints only; never the label.
Success messages are specific and brief: "Saved" or "Topic created", not "Done".
Destructive language is explicit: delete, remove, revoke, disconnect. Do not soften permanent loss.
Contextual help sits near the thing it explains and should remove the next question.
Numeric formatting, truncation, and locale-sensitive text are part of UX copy quality.
Labels, helper text, placeholders, tooltips, and errors each do different work; cut redundant writing.
Stress copy with long localized strings, huge numbers, empty/error/offline states, and destructive actions.
Product naming can add identity only when clarity and recovery language stay intact.

Enforce product name capitalization (Admin API, Schema Registry, HTTP Proxy, Redpanda Console)
Warn on "the console" (use "Redpanda Console")

// allow: ux-copy [reason] anywhere in file skip all checks.

For documentation, READMEs, PR description files, and any markdown prose.

Ban em dashes (Unicode U+2014). Use commas, periods, or parentheses.
Ban canned AI openers ("Let's dive in", "Here's why", "In conclusion", "In today's digital landscape").
Ban AI-tell words (hard list): delve, tapestry, realm, pivotal, underscore.
Warn AI-tell words (soft list): leverage, foster, intricate, nuanced, robust, comprehensive, significantly, showcase.
Warn "not just X, but Y" / "not just X, it's Y" contrast framing.
Warn heavy transitions (Moreover, Furthermore, Additionally, Nevertheless).
Warn Latin abbrevs (e.g., i.e., etc.).
Warn rule-of-three praise lists (e.g., "fast, efficient, and reliable").

Fenced code, indented code, inline code spans, and URLs are stripped before matching to reduce false positives.

 or // allow: prose-style [reason] anywhere in file skips all checks.

Add to hooks config: PostToolUse (matcher: Edit|Write):

Copy GLOSSARY.md to project root or docs/. Pair with ubiquitous-language community skill.