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).
SkillScore92Maintained
Automatic
◆Design & UX Review pack
Last verified 8/17/2026
What it changes
Passed 22 of 24 test cases with the skill, and 18 of 24 without it.
Without skill75%
With skill92%
Checks it passed that the model alone missed
The selected feature name is 'Balance'
The alert title rule specifies one sentence or less
The framework evaluation covers Purpose, Anticipation, Context, and Empathy
and 2 more in the full report
5 fixed17 passed either way1 still failing1 broke
Pass-rate lift
+17 pp
Tokens
+44%
Agent turns
0%
Response time
-24%
Model gemini-3.6-flashMeasured 8/17/2026v122 of 24 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 5
Prompt
When evaluating an interface screen's text against comprehensive interface design principles, list the four fundamental PACE questions/dimensions to analyze.
What was checked, without and with the skill
Checked
Without skill
With skill
The framework evaluation covers Purpose, Anticipation, Context, and Empathy
Missed
Passed
case-14 · gemini-3.6-flash · 8/17/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md94 linessingle file
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 sound like the best
version of your app talking?
❌ Jargon ("it can make people feel left out"); ❌ personality at the cost of usefulness.
The four small edits (biggest impact per minute)
Cut filler: "easily," "quickly," "simply," "just" — ✅ "Enter your license plate to pay
for parking" ❌ "Simply enter your license plate number to quickly pay for parking."
Kill repetition — merge redundant sentences: ❌ "We're running late. Your driver won't
make it on time. They'll be there in 10 minutes." ✅ "Delivery delayed 10 minutes."
Lead with the why — benefit before action: ✅ "To get reservation updates, enter your