ux-writing

Featured

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.

Web & Frontend 564 stars 47 forks Updated 3 days ago MIT

Install

View on GitHub

Quality Score: 96/100

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

Skill Content

# UX Writing Interface text is interface design. This skill covers writing it: the frameworks Apple's writers use, the anatomy of the hardest components (alerts, errors, empty states, names), and the mechanical edits that improve any screen's copy in minutes. ## When This Skill Activates - Writing or reviewing user-facing copy: labels, buttons, alerts, onboarding, notifications - Naming a new feature, tier, or setting - Error messages that frustrate, empty states that dead-end, permission prompts that get denied - Localization prep (copy that survives translation) ## The PACE framework (Writing for Interfaces) Run every screen's copy through four questions: - **Purpose** — what must this screen communicate? Headers and buttons should carry the screen alone; know what to leave out. Hierarchy in words mirrors hierarchy in layout. - **Anticipation** — what will the user ask or do next? Write for that ("What comes next?"). - **Context** — where is the user right now (quiet home vs. busy airport, mid-task vs. idle)? That decides how much to say. - **Empathy** — write for a person having a problem, not for the system reporting one. ## Voice vs. tone - **Finding voice**: describe the app as a person, cluster the personality adjectives, keep 2–3 as your voice attributes — constant across the app, while tone flexes per moment (more directness for high-stakes info, sparing warmth in celebrations). - The test that recurs in every Apple session: **read it aloud**. Does it...

Details

Author
rshankras
Repository
rshankras/claude-code-apple-skills
Created
9 months ago
Last Updated
3 days ago
Language
Swift
License
MIT

Integrates with

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

Web & Frontend Solid

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 today
justinqwerty
AI & Automation Listed

sota-ux-writing

State-of-the-art UX writing and product-copy guidance (2026) covering voice and tone systems, plain language (ISO 24495-1), microcopy (buttons, labels, empty states, onboarding, notifications), error and feedback message craft, and the accessibility and localization of interface language (WCAG 2.2 language criteria, alt text, ICU pluralization, i18n-safe strings). Use when writing or reviewing ANY user-facing interface text — web, mobile, desktop, or CLI products — AND when auditing existing product copy for clarity, consistency, tone, accessibility, and localization readiness. Trigger keywords: UX writing, microcopy, product copy, content design, error message, empty state, button label, tooltip, onboarding copy, form label, placeholder, notification, toast, confirmation dialog, tone of voice, terminology, plain language, readability, alt text, i18n strings, localization, translation.

8 Updated 2 days ago
martinholovsky
Web & Frontend Listed

ux-copy-writer

You are an expert UX copywriter specializing in microcopy — the small bits of text that guide users through interfaces. Your copy is clear, human, concise, and helpful. ## Process 1. Identify the UI element needing copy (button, error, tooltip, empty state, etc.) 2. Understand the context and user's mental state 3. Write 3-5 variations of the copy 4. Select the best option based on clarity, tone, and brevity 5. Explain why the chosen copy works ## Output Format ### UI Element: \[type\] Variations: 1. 'Option 1' 2. 'Option 2' 3. 'Option 3' ✅ Recommended: 'Best option' Why this works: Explanation Tone: \[friendly/professional/playful/etc.\] Character count: \[X\] ## Microcopy Principles - Answers the user's next question before they ask it - Uses active voice: 'Save changes' not 'Changes will be saved' - Matches emotional context: error states should feel supportive, not blaming -...

0 Updated 1 weeks ago
prvthmpcypher