Writing For Interfaces
Define product voice once, then write or review buttons, errors, empty states, and flows so UI copy stays clear and consistent across the app.
Overview
Writing for Interfaces is an agent skill most often used in Build (also Validate landing and Ship review) that applies a voice-first workflow to UI copy.
Install
npx skills add https://github.com/andrewgleave/skills --skill writing-for-interfacesWhat is this skill?
- Four-step voice-first workflow: establish voice, evaluate task type, apply principles, consult patterns reference
- Searches CLAUDE.md, AGENTS.md, and style guides before inventing new tone
- Handles new copy, review, rewrite, and terminology tasks with pattern-specific guidance
- references/patterns.md supplies detailed rules for common interface situations
- Install via npx skills add with /writing-for-interfaces slash command
- 4-step voice-first workflow
- patterns reference file for common interface situations
Adoption & trust: 523 installs on skills.sh; 29 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your agent-generated UI text sounds generic, inconsistent, or vague because no shared voice or interface patterns guide the strings.
Who is it for?
Solo founders polishing SaaS or mobile UI who want repeatable microcopy rules instead of one-off chat rewrites.
Skip if: Long-form marketing essays or legal policy drafting—use content or legal workflows instead of interface pattern guidance.
When should I use this skill?
User invokes /writing-for-interfaces or asks to review, write, or rewrite UI copy for clarity, purpose, and consistency.
What do I get? / Deliverables
Screens and flows get copy aligned to a defined product voice with pattern-checked clarity for the requested task type.
- Voice definition or confirmation tied to project docs
- Revised or new interface strings with pattern-backed rationale
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Build/frontend is the canonical shelf because interface copy ships inside components, modals, and onboarding—not only in marketing docs. Frontend subphase covers in-product strings and microcopy that users see on every screen, which this skill’s voice-first workflow targets directly.
Where it fits
Draft settings and billing labels after a feature sprint so tone matches the rest of the dashboard.
Align hero and CTA copy on a prototype page with in-app voice before you commit to brand words.
Run a full UI copy review for confusing errors and inconsistent terminology before public launch.
How it compares
Use a voice-first interface copy workflow instead of asking the model to ‘make it sound better’ without product context.
Common Questions / FAQ
Who is writing-for-interfaces for?
Builders and designers shipping web or mobile products who need consistent, purposeful UI strings across agent-assisted edits.
When should I use writing-for-interfaces?
While building frontend flows, when reviewing a landing prototype in Validate, and during Ship review passes on onboarding or error copy.
Is writing-for-interfaces safe to install?
It is instructional copy guidance without shell requirements; review the Security Audits panel on this Prism page for the upstream skills package.
SKILL.md
READMESKILL.md - Writing For Interfaces
# Writing for Interfaces Skill ## Install ```bash npx skills add andrewgleave/skills --skill writing-for-interfaces --global ``` ## Example Prompt ```text /writing-for-interfaces Review and evaluate all UI copy for clarity, purpose, and consistency. ``` ## Skill Structure This repository follows the **Agent Skills** open standard. Each skill is self-contained with its own logic, workflow, and reference materials. ```text writing-for-interfaces/ ├── SKILL.md — Core instructions, principles, and voice/tone guidance ├── references/ │ └── patterns.md — Detailed guidance for common interface patterns └── README.md ``` ## How it Works When activated, the agent applies a voice-first workflow: 1. **Establish voice**: Search for an existing voice definition in project files (`CLAUDE.md / AGENTS.md`, style guides, design docs). If none exists or the existing copy is inconsistent, walk the user through defining one — what the product does, who it's for, where it's used, and what personality traits define it. An established and consistent voice is the foundation for all copy decisions. 2. **Evaluate the request**: Determine whether the task is new copy, a review, a rewrite, or terminology work and identify which interface patterns apply. 3. **Apply voice and principles**: Check that copy sounds like the defined voice. Dial tone qualities up or down for the situation and then apply the core principles. 4. **Evaluate**: Consult the patterns reference for situation-specific guidance on structure, tone, and common pitfalls. 5. **Apply changes**: Rewrite existing copy inline or draft from scratch. Show original → rewrite with a brief rationale tied to voice and principles. Prioritise changes that confuse or block users before polish. 6. **Update terminology reference**: Flag terminology drift and suggest word list entries to keep voice and phrasing consistent across the interface. The user should be able to review the changes and approve or reject them. ## Sources Many principles are distilled from Apple's interface writing guidance and generalised for product interfaces more broadly: - [**Human Interface Guidelines** — Writing](https://developer.apple.com/design/human-interface-guidelines/writing/) - [**Human Interface Guidelines** — Alerts](https://developer.apple.com/design/human-interface-guidelines/alerts/) - [**Human Interface Guidelines** — Accessibility](https://developer.apple.com/design/human-interface-guidelines/accessibility/) - [**WWDC 2019** — Writing Great Accessibility Labels](https://developer.apple.com/videos/play/wwdc2019/254/) - [**WWDC 2022** — Writing for Interfaces](https://developer.apple.com/videos/play/wwdc2022/10037/) - [**WWDC 2024** — Adding Personality to Your App Through UX Writing](https://developer.apple.com/videos/play/wwdc2024/10140/) - [**WWDC 2025** — Make a Big Impact with Small Writing Changes](https://developer.apple.com/videos/play/wwdc2025/404/) - [**Apple Style Guide**](https://help.apple.com/applestyleguide/) # Interface copy patterns Detailed guidance for common interface writing situations. Each pattern should be applied through the lens of your product's voice and tone — the voice stays consistent, the tone adapts to the situation. These patterns cover common cases, not every interface element. For anything not listed here, apply the core principles and voice framework from the main skill document. ## Table of contents 1. [Alerts and dialogs](#alerts-and-dialogs) 2. [Error messages](#error-messages) 3. [Destructive actions](#destructive-actions) 4. [Empty states](#empty-states) 5. [Onboarding and setup flows](#onboarding-and-setup-flows) 6. [Notifications](#notifications) 7. [Accessibility labels](#accessibility-labels) 8. [Buttons and actions](#buttons-and-actions) 9. [Instructional and inline copy](#instructional-and-inline-copy) 10. [Settings and preferences](#settings-and-preferences) --- ## Alerts and dialogs Alerts interrupt what someone is doing. E