ux-writing

# 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...