Skip to content
Skills Library
Design & UX · Writing

write-ui-microcopy

/write-ui-microcopy

Use when writing any words inside the UI — button verbs, labels, empty/error/success messages, tooltips, confirmations, onboarding. Copy is interface; make it specific, in the product's voice, and helpful at the moment of friction. Not generic CTAs.

Repository
truecast ↗
Licence
MIT
Last repository change
17.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 17.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use when writing any words inside the UI — button verbs, labels, empty/error/success messages, tooltips, confirmations, onboarding. Copy is interface; make it specific, in the product's voice, and helpful at the moment of friction. Not generic CTAs.

Original author description

Use when writing any words inside the UI — button verbs, labels, empty/error/success messages, tooltips, confirmations, onboarding. Copy is interface; make it specific, in the product's voice, and helpful at the moment of friction. Not generic CTAs.

How it works

  1. The rules
  2. The voice discipline
  3. The AI register is not a voice (the microcopy scrub)
  4. The discipline
Original SKILL.md headings · 59 lines, 715 words
SKILL.md preview
---
name: write-ui-microcopy
description: Use when writing any words inside the UI — button verbs, labels, empty/error/success messages, tooltips, confirmations, onboarding. Copy is interface; make it specific, in the product's voice, and helpful at the moment of friction. Not generic CTAs.
---
# Write UI microcopy — words are interface

The words *inside* the UI are part of the design, not an afterthought for "content" — a label, a button
verb, an error line steers behavior more than most pixels. Microcopy is yours (the product's *external*
positioning and marketing copy is the marketer's — consult them when the line carries brand weight, but
the in-product words are interface and they're yours).

## The rules
1. **Verbs the user actually wants.** Not "Submit," "Get Started," "Learn More" — the specific action:
   "Connect repo," "Re-run build," "Talk it through →." The button says what happens when you press it.
2. **Labels in the user's language** (match-to-real-world, heuristic #2) — not internal jargon or DB
   field names. The label is what the user would call the thing.
3. **Errors: name what's wrong + the way out** (heuristic #9). Not "Error 500" / "Something went wrong" —
   "We couldn't reach the server. Retry, or check your connection." Plain language, honest, no dead end.
4. **Empty states say something specific** (`design-the-states`) — what this is for and the next step, in
   voice; never "Nothing here yet 🎉."
5. **Confirmations for the destructive** — name the consequence ("Delete 3 items? This can't be undone"),
   give the escape. Match the friction to the stakes.
6. **Set expectations** — especially for slow or AI work: "This usually takes a few seconds"
   (`design-the-ai-interaction`).

## The voice discipline
- **Consistent voice** across the product — one personality (direct, honest, calm — match the product's).
  Decide the voice once and **write it down**: a mini voice spec in this project's `instance/` — five
  words we use, five we never use, one reference error message, one reference empty state. "Off-voice"
  then cites a spec line, not a feeling; and the spec is derived from *this* product's users
  (`research-the-user`), not a house default.
- **The user's vocabulary, not yours** — labels and messages use the words this audience uses for these
  things (an on-call SRE and a first-run consumer don't get the same register, density, or patience).
- **Concise** — every word earns its place; users scan, they don't read. Front-load the meaning.
- **Honest, not cute** — humor and emoji rarely survive the user who's frustrated or confused at that
  exact moment; respect the user's intent over a quip.
- **Clear over clever** — if a clever line risks ambiguity, the plain line wins. Clarity is the job.

## The AI register is not a voice (the microcopy scrub)
Unedited model output has a recognizable in-product register, and users have learned to read it as
"nobody wrote this." Scrub for it wherever copy was generated (clusters, not single hits — era: 2026):

- **Exclamation cheer.** "You're all set! 🎉" "Great choice!" — the model celebrates; a product speaks.
  State what happened and what's next.
- **Apology theater.** "Oops! Something went wrong on our end. Don't worry —" is three tells in one line:
  the mascot "Oops," the vague failure, the instruction to feel. Name what broke + the way out (rule 3).
- **Hedge padding.** "It looks like you may not have any projects yet" — the user either has projects or
  doesn't; the softener is the model's, not the product's. "No projects yet. Create one."
- **Chatbot pleasantries in chrome.** "Sure!", "Let's get you set up!", "Feel free to…" in buttons,
  tooltips, onboarding — conversational filler where an interface should be an instrument.
- **Explaining feelings instead of the state.** Copy that narrates emotion ("We know this is
  frustrating…") instead of giving the fact and the action. Empathy in UI is a working way out, fast.
- **The cold read at the worst moment.** Read every error/empty/confirmation as the user who just lost
  work at 2am. The register that survives *that* read ships; the writer of the line doesn't get to be
  its judge.

## The discipline
- Microcopy is most load-bearing exactly where the user is stuck (error, empty, confirmation) — write
  those with the most care, not the least.
- Test labels for ambiguity in a `usability-test` — if two users read a label two ways, it's a bug.
- Pull in the **marketer** when in-UI copy bleeds into positioning/brand voice; pull in the
  **product-manager** when the words imply a promise about what the product does.

Versions

The database has no other skills named write-ui-microcopy.

Database snapshot: 13.11.2026 · package version 4d6b082b32cb (SHA-256 digest of the entire package)

Downloads in the last 30 days: 1 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 95ux-microcopy
    Write or improve UX microcopy — button labels, error and empty states, tooltips, form labels, notifications, and confirmations — so it's clear, concise, action-oriented, and on-voice. Trigger when asked to write microcopy, improve a button label or error message, write copy for…
  • 90ux-copy
    Use to write or review microcopy — CTAs, error messages, empty states, confirmation dialogs, tooltips, onboarding text.
  • 100ux-writer
    Use this skill when crafting microcopy, UI text, or in-product writing—error messages, tooltips, button labels, empty states, onboarding flows, and confirmation dialogs. Trigger phrases: ''write microcopy for'', ''write UI copy'', ''write error messages'', ''write onboarding…
  • 100open-ds-write
    Write interface copy in the voice of an Open DS scheme. Use when you write labels, errors, success or empty messages, confirmations or hints.
  • 100microcopy
    Write UX microcopy — error messages, empty states, tooltips, button labels, helper text, modals, 404/500 pages, onboarding. Plain language, action-oriented, ≤8 words for buttons, never blames user. Wraps `writer`. Use when the user says 'error message', 'empty state', 'tooltip…
  • 100ux-writing
    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…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.