Skip to content
UX Writing

UX Writing Skill

Write and audit interface microcopy, from buttons to error messages, against four checkable quality standards.

GitHub

Install

Install with the skills CLI

One command for Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf and dozens of other agents. Needs Node.js; the skill is fetched straight from content-designer/ux-writing-skill.

$ npx skills add content-designer/ux-writing-skill

Run it in a terminal. The CLI finds the agents installed on your machine, asks which ones to add the skill to, and whether to install it into the folder you ran it from or for all your projects. It also lists the skills in the repository so you can pick UX Writing.

Other ways to install

  1. Open the skill on GitHub and download the folder that holds its SKILL.md.
  2. Put it at ~/.claude/skills/ux-writing/, where Claude Code picks it up in every project.

No scripts or references next to it? Saving the SKILL.md alone as ~/.claude/skills/ux-writing/SKILL.md works too.

Using another agent? Its personal skills folder
Codex
~/.agents/skills/
Cursor
~/.cursor/skills/
GitHub Copilot
~/.copilot/skills/
Gemini CLI
~/.gemini/skills/
Windsurf
~/.codeium/windsurf/skills/
OpenCode
~/.config/opencode/skills/

About

  • Four quality standards with concrete, checkable benchmarks
  • Pattern library for buttons, errors, empty states, and onboarding
  • Reading-level and comprehension benchmarks baked into guidance
  • Voice and tone adaptation framework for different product contexts

UX Writing is a standalone skill focused entirely on interface copy, meaning the buttons, labels, error messages, notifications, form hints, empty states, and onboarding text that make up a product's voice but rarely get the same editorial attention as marketing copy. It is built around four quality standards, purposeful, concise, conversational, and clear, and backs each with concrete, checkable guidance rather than vague advice, including a 40-60 character line-length target, a seventh-grade reading level for general audiences, roughly 85 percent active voice, and second-person address.

It provides pattern libraries for common UI text types, such as titles, error messages, empty states, confirmations, and tooltips, each with purpose, format conventions, and examples, plus frameworks for establishing and adapting a product's voice and tone across different contexts. Accessibility is core to the skill rather than an afterthought, with comprehension research and plain-language guidance baked into the same recommendations used for clarity and concision. Use it any time text is being written or edited for an app, website, or software interface, whether drafting new copy, auditing an existing product for consistency, or reviewing UI strings before ship. It is explicitly compatible with any agent supporting the Agent Skills spec, not just Claude.

SKILL.md

The instructions your agent loads, as published by content-designer (Christopher Greer).

SKILL.md

UX Writing

Write clear, concise, user-centered interface copy (UX text/microcopy) for digital products and experiences.

Core UX Writing Principles
The Four Quality Standards
  1. Purposeful — Helps users or the business achieve goals
  2. Concise — Uses the fewest words possible without losing meaning
  3. Conversational — Sounds natural and human, not robotic
  4. Clear — Unambiguous, accurate, and easy to understand
Key Best Practices

Conciseness: 40-60 characters per line maximum; every word must have a job.
Clarity: plain language (7th grade reading level for general, 10th for professional); avoid jargon.
Conversational Tone: write how you speak; active voice ~85% of the time.
User-Centered: focus on user benefits, not features; second-person ("you") language.

UX Text Patterns
Titles
  • Purpose: Orient users to where they are
  • Format: Noun phrases, sentence case
  • Examples: "Account settings", "Your library", "Create new post"
Install

Skill: Anti-Slop Design

by Ferousco-dev

Featured

Stops AI-generated UI from defaulting to purple gradients and templated hero sections by forcing a named design direction first.

122 views 27 copies

Audits Core Web Vitals through the Chrome DevTools MCP server — LCP, INP, CLS plus FCP, TBT and Speed Index — and traces each one back to the render-blocking resource or layout shift causing it.

Browse all skills →