Get the FREE Ultimate OpenClaw Setup Guide →

ux-writing

Scanned
npx machina-cli add skill anthropics/knowledge-work-plugins/ux-writing --openclaw
Files (1)
SKILL.md
1.6 KB

UX Writing

Write clear, concise, and helpful interface copy.

Principles

  1. Clear: Say exactly what you mean. No jargon, no ambiguity.
  2. Concise: Use the fewest words that convey the full meaning.
  3. Consistent: Same terms for the same things everywhere.
  4. Useful: Every word should help the user accomplish their goal.
  5. Human: Write like a helpful person, not a robot.

Copy Patterns

CTAs

  • Start with a verb: "Start free trial", "Save changes", "Download report"
  • Be specific: "Create account" not "Submit"
  • Match the outcome to the label

Error Messages

Structure: What happened + Why + How to fix

  • "Payment declined. Your card was declined by your bank. Try a different card or contact your bank."

Empty States

Structure: What this is + Why it's empty + How to start

  • "No projects yet. Create your first project to start collaborating with your team."

Confirmation Dialogs

  • Make the action clear: "Delete 3 files?" not "Are you sure?"
  • Describe consequences: "This can't be undone"
  • Label buttons with the action: "Delete files" / "Keep files" not "OK" / "Cancel"

Voice and Tone

Adapt tone to context:

  • Success: Celebratory but not over the top
  • Error: Empathetic and helpful
  • Warning: Clear and actionable
  • Neutral: Informative and concise

Source

git clone https://github.com/anthropics/knowledge-work-plugins/blob/main/design/skills/ux-writing/SKILL.mdView on GitHub

Overview

UX Writing is the craft of crafting clear, concise, and helpful interface copy. It focuses on essential principles—clear, concise, consistent, useful, and human—to guide users with intention. It also uses patterns for CTAs, error messages, empty states, and confirmations, tuned to context and tone.

How This Skill Works

UX writing applies core principles to UI text, validating that each word serves a user goal. It leverages established patterns for CTAs, errors, empty states, and confirmations, and adapts tone to context (success, error, warning, neutral) to improve usability.

When to Use It

  • Designing a CTA label that clearly reflects the outcome (e.g., 'Create account' vs 'Submit').
  • Writing empathetic, actionable error messages that explain what happened and how to fix.
  • Creating empty state copy that explains why there is nothing yet and what to do next.
  • Designing confirmation dialogs with explicit consequences and labeled action buttons.
  • Ensuring consistent terminology and tone across the UI.

Quick Start

  1. Step 1: Identify the primary user goal and the screen’s outcome.
  2. Step 2: Write copy using established patterns: clear CTAs, actionable errors, informative empty states, and explicit confirmations.
  3. Step 3: Validate tone, consistency, and conciseness; adjust based on context and user feedback.

Best Practices

  • Start CTAs with action verbs and tie the outcome to the label.
  • Be specific and avoid jargon; explain exactly what will happen.
  • Use consistent terms for the same concepts across screens.
  • Keep copy concise, useful, and human—avoid robotic language.
  • Match tone to context (success, error, warning, neutral) and provide actionable guidance.

Example Use Cases

  • Start free trial
  • Payment declined. Your card was declined by your bank. Try a different card or contact your bank.
  • No projects yet. Create your first project to start collaborating with your team.
  • Delete 3 files? with buttons labeled 'Delete files' / 'Keep files'
  • This can't be undone

Frequently Asked Questions

Add this skill to your agents
Sponsor this space

Reach thousands of developers