ux-writing

Solid

Create user-centered, accessible interface copy (microcopy) for digital products including buttons, labels, error messages, notifications, forms, onboarding, empty states, success messages, and help text. Use when writing or editing any text that appears in apps, websites, or software interfaces, designing conversational flows, establishing voice and tone guidelines, auditing product content for consistency and usability, reviewing UI strings, or improving existing interface copy. Applies UX writing best practices based on four quality standards — purposeful, concise, conversational, and clear. Includes accessibility guidelines, research-backed benchmarks (sentence length, comprehension rates, reading levels), expanded error patterns, tone adaptation frameworks, and comprehensive reference materials.

Web & Frontend 51 stars 4 forks Updated yesterday MIT

Install

View on GitHub

Quality Score: 83/100

Stars 20%
57
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# UX Writing Write clear, concise, user-centered interface copy (UX text/microcopy) for digital products and experiences. This skill provides frameworks, patterns, and best practices for creating text that helps users accomplish their goals. ## When to Use This Skill Use this skill when: - Writing interface copy (buttons, labels, titles, messages, forms) - Editing existing UX text for clarity and effectiveness - Creating error messages, notifications, or success messages - Designing conversational flows or onboarding experiences - Establishing voice and tone for a product - Auditing product content for consistency and usability ## Core UX Writing Principles ### The Four Quality Standards Every piece of UX text should be: 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** - Use 40-60 characters per line maximum - Every word must have a job - Break dense text into scannable chunks - Front-load important information - Eliminate deadwood phrases ("in order to" → "to", "due to the fact that" → "because", "at this point in time" → "now") - Replace phrasal verbs with direct verbs ("find out" → "discover", "set up" → "configure", "carry out" → "perform") - Avoid stacking modifiers — one adjective is usually enough **Clarity** - Use pl...

Details

Author
cuellarfr
Repository
cuellarfr/design-skills
Created
5 months ago
Last Updated
yesterday
Language
HTML
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

Web & Frontend Listed

ux-writing

Create user-centered, accessible interface copy (microcopy) for digital products including buttons, labels, error messages, notifications, forms, onboarding, empty states, success messages, and help text. Use when writing or editing any text that appears in apps, websites, or software interfaces, designing conversational flows, establishing voice and tone guidelines, auditing product content for consistency and usability, reviewing UI strings, or improving existing interface copy. Applies UX writing best practices based on four quality standards — purposeful, concise, conversational, and clear. Includes accessibility guidelines, research-backed benchmarks (sentence length, comprehension rates, reading levels), expanded error patterns, tone adaptation frameworks, and comprehensive reference materials.

8 Updated 2 days ago
justinqwerty
Web & Frontend Solid

ux-writing

Write or review UI copy — buttons, errors, empty states, microcopy, notifications, labels — using the voice & tone system (clear, concise, useful, human, honest) with the what→why→how error formula and inclusive-language rules. Use when the user needs interface copy, error messages, empty-state text, or a copy review.

731 Updated today
plugin87
Web & Frontend Featured

ux-writing

Interface copy that works — voice/tone, the PACE framework, alert anatomy, naming features, empty states, error messages, and the small-word edits that measurably improve UX. Distilled from Apple's writing sessions (2017–2026). Use when writing or reviewing any user-facing text — labels, alerts, onboarding, notifications, empty states, paywalls — or naming a feature.

664 Updated 1 months ago
rshankras