Ux writing

Skill viktorbezdek/skillstack/ux-writing/skills/ux-writing

Skills I use and develop to deliver better outcomes faster and with less effort.

Install

npx -y skills add viktorbezdek/skillstack --skill ux-writing

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

10 stars10 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Write effective microcopy, error messages, button labels, and interface text using UX writing principles. Use when crafting microcopy, UX copy, interface text, error messages, button labels, empty states, or conversational UI text. NOT for generating documentation (use documentation-generator). NOT for writing marketing copy or brand voice guidelines (use storytelling for narrative, not UI microcopy). NOT for designing the UI itself (use frontend-design or navigation-design). NOT for content strategy or information architecture (use content-modelling).

SKILL.md

5.6 KB, as published. Nobody here has run it

UX Writing

Write clear, helpful, human interface text.

When to use this skill

Writing or rewriting button labels, error messages, form labels, empty states
Crafting conversational UI text (chatbots, onboarding flows, tooltips)
Improving the clarity of interface copy in an existing product
Setting up a tone-of-voice guide for a product's UI text
Reviewing UI copy for consistency across a product

When NOT to use this skill

Long-form documentation → use documentation-generator
Marketing copy or brand narratives → use storytelling
Designing UI layouts or components → use frontend-design or navigation-design
Content strategy or information architecture → use content-modelling

Decision tree

What are you writing?
  │
  ├─ A button label or CTA
  │   └─ Formula: [Verb] + [Object]. Start with the action, name the thing.
  │
  ├─ An error message
  │   └─ Formula: What happened + Why + What to do next. Never blame the user.
  │
  ├─ An empty state
  │   └─ Formula: Why it's empty + How to fill it. Encourage, don't shame.
  │
  ├─ A confirmation dialog
  │   └─ Formula: Consequence + Irreversibility (if any) + Clear action/negative buttons
  │
  ├─ A tooltip or help text
  │   └─ Formula: One sentence max. Explain the non-obvious, skip the obvious.
  │
  ├─ A loading or progress state
  │   └─ Formula: What's happening + How long (if known). Transparent, not silent.
  │
  └─ Onboarding or conversational UI flow
      └─ Map the emotional arc: uncertain → guided → confident. Adjust tone per step.

Core Principles

Principle	Description	Bad Example	Good Example
Clear	Simple words, active voice	"Authentication failed"	"Your password is incorrect"
Concise	Front-load key info	"In order to proceed, you must first"	"To continue,"
Useful	Provide next steps	"Error 404"	"Page not found. Try searching or go to homepage."
Human	Empathetic, conversational	"Invalid input"	"Please enter a valid email address"

Tone by Context

Context	Tone	Example
Success	Celebratory	"You're all set!"
Error	Helpful, not blaming	"Let's fix this"
Warning	Direct, honest	"This can't be undone"
Empty	Encouraging	"Create your first project"
Loading	Transparent	"Finding your files..."

UI Patterns

Buttons

X Click here    -> Download report
X Submit        -> Save changes

Formula: [Verb] + [Object]

Error Messages

X Error 404

-> Page not found
   Try searching or go to homepage.

Confirmation Dialogs

Delete "Report"?
This can't be undone.
[Delete] [Cancel]

Form Labels

Email address
[[email protected]]
We'll send a confirmation link.

Anti-Patterns

#	Anti-Pattern	Example	Fix	Why it matters
1	Blaming the user	"You entered an invalid email"	"Please enter a valid email address"	Implies fault; users feel accused instead of guided
2	Jargon and system language	"Error 500: Internal Server Error"	"Something went wrong on our end. Try again in a moment."	Users do not know what a 500 is; they need a human-readable explanation
3	Dead-end messages	"Error 404"	"Page not found. Try searching or go to homepage."	Without a next step, users are stranded and must guess what to do
4	Vague button labels	"OK", "Submit", "Cancel"	"Delete project", "Send invitation", "Save changes"	Generic labels force users to re-read surrounding context to infer what will happen
5	Overly formal tone	"Your request has been processed successfully"	"Done!" (unless context demands formality: legal, financial)	Robotic copy erodes trust and increases cognitive load for no added clarity
6	Inconsistent terminology	"Delete" in one place, "Remove" in another for the same action	Pick one term and use it everywhere; maintain a microcopy glossary	Inconsistent terms make users wonder if "delete" and "remove" do different things
7	Silent loading states	Spinner with no text	"Finding your files..." (+ time estimate if known: "This takes about 30 seconds")	Silent spinners feel broken; users refresh or abandon, making the wait worse
8	Progressive disclosure overload	Tooltip with 3 paragraphs of detail	Show the essential instruction; link or collapse deeper details	Helper text is for the next step, not the whole manual
9	Confirmations without consequences	"Are you sure?"	"Delete this project? All 23 tasks will be permanently removed."	Without consequences, users click through on autopilot; the confirmation is theater
10	Personality over clarity	"Oopsie-daisy, something borked!"	"Something went wrong. Try again or contact support."	The Clear principle always outranks Human. Users in error states need help, not humor