writing-for-interfaces

Writes, reviews, and rewrites user-facing interface copy using voice and tone principles.

1|Updated Aug 9, 2026
One-click install
npx skills add https://github.com/OMIXEC/all-in-one-swift-skills --skill writing-for-interfaces-omixec
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-for-interfaces
Source: https://github.com/OMIXEC/all-in-one-swift-skills/tree/main/skills/writing-for-interfaces
Command: npx skills add https://github.com/OMIXEC/all-in-one-swift-skills --skill writing-for-interfaces-omixec

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Interface text is often written as an afterthought, producing inconsistent, vague, or confusing copy across screens, alerts, buttons, and error messages. This Skill applies a structured voice-first workflow so every piece of UI text is clear, consistent, and appropriate to its context. ## Core Features & Use Cases - Voice and tone framework: Establishes a product voice (3-4 personality traits) from existing project files or through guided conversation, then dials tone up or down per situation. - Pattern-specific guidance: Covers alerts, error messages, destructive actions, empty states, onboarding, notifications, accessibility labels, buttons, and settings via a detailed patterns reference. - Copy review and rewrite: Shows original versus rewritten copy with rationale, prioritizing changes that confuse or block users, and flags terminology drift with word list suggestions. - Use Case: Ask the agent to review all confirmation dialogs in an app; it identifies vague button labels like "Yes/No" and rewrites them as specific actions like "Delete Album / Keep Album" with rationale. ## Quick Start Ask the agent to review and rewrite the error messages and button labels in your current screen or flow for clarity and consistency.

Frequently Asked Questions about writing-for-interfaces

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write better error messages for my app?▼

State what happened in plain language, explain why if helpful, and tell the user what to do next. Avoid jargon, error codes, interjections like "Oops!", and vague phrases like "Something went wrong." Name the specific thing that failed and provide a clear path forward.

How to review UX copy for consistency across screens?▼

Establish a voice definition first, then evaluate each element against it. Check that terminology stays consistent using a word list, verify button labels are specific verbs, and confirm tone matches each situation. Flag drift and suggest word list entries to maintain consistency.

What should button labels say instead of OK or Cancel?▼

Button labels should use specific verbs describing the actual action, such as "Save Changes," "Delete Album," or "Keep Subscription." Paired choices must be understandable independently, and "OK" should only appear for purely informational dialogs.

Does this skill work for marketing copy or blog posts?▼

No. This skill is scoped to text shown inside software interfaces, including apps, web, CLI output, modals, tooltips, and notifications. It explicitly excludes content marketing, blog posts, app store listings, API documentation, and brand guides.

How do I write accessibility labels for screen readers?▼

Label every interactive element succinctly, describe intent rather than appearance, and never include the element type since screen readers announce it. Update labels when state changes, label loading states, and use inclusive language such as "person" instead of assumed gender.