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.
npx skills add rshankras/claude-code-apple-skills --skill ux-writing --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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
- When This Skill Activates
- The PACE framework (Writing for Interfaces)
- Voice vs. tone
- The four small edits (biggest impact per minute)
- Alert anatomy (Writing Great Alerts)
- Naming features (Craft Clear Names, WWDC26)
- Empty states, permissions, localization
- Output Format
- References
What does the ux-writing skill do?
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.
How do I install it?
Run `npx skills add rshankras/claude-code-apple-skills --skill ux-writing --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From rshankras/claude-code-apple-skills, a repository with 589 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.