ux-writing

Writes mobile app microcopy for buttons, errors, empty states, and notifications.

1|Updated Aug 7, 2025
One-click install
npx skills add https://github.com/zzafergok/arktos --skill ux-writing-zzafergok
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ux-writing
Source: https://github.com/zzafergok/arktos/tree/main/.agent/skills/ux-writing
Command: npx skills add https://github.com/zzafergok/arktos --skill ux-writing-zzafergok

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing interface copy for mobile apps is error-prone: vague buttons, blame-filled error messages, and empty screens with no guidance confuse users and increase support load. This Skill provides structured patterns and length limits for every microcopy element. ## Core Features & Use Cases - Copy Patterns: Rules for headings, buttons, error messages, success messages, empty states, onboarding, push notifications, and form labels. - Length Reference: Concrete character and word limits for each UI element, from 2-4 word button labels to 100-character notification bodies. - App Store & Accessibility: Guidance for App Store descriptions, semantic labels, and WCAG contrast requirements. - Use Case: When building a payment screen, use this Skill to write a clear button label like "Proceed to payment", an inline validation message like "Phone number must be 10 digits", and a recovery-oriented error message. ## Quick Start Use the ux-writing skill to write the button labels, error messages, and empty state copy for my mobile checkout flow.

Frequently Asked Questions about ux-writing

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

FAQPage Schema
How do I write good error messages for mobile apps?▼

A good error message covers three things: what did not happen, the likely reason, and what the user can do next. Keep it to 12-18 words, avoid blaming the user, and never expose technical codes or jargon.

How to write button labels that users understand?▼

Use a verb-plus-object structure that names the action the button triggers, such as "Save changes" or "Delete account". Keep labels to 2-4 words and avoid context-free labels like "OK", "Submit", or "Confirm".

What should empty state copy include in an app?▼

Empty state copy should answer three questions: why the screen is empty, what the user can do, and the value of taking that action. Keep it to 1-2 short sentences, like "No favourites yet. Tap the heart icon on any product to save it here."

How long should push notification copy be?▼

Push notification titles should stay under 50 characters and bodies under 100 characters. Lead with value first and avoid manufactured urgency, which is a common reason users disable notifications.

What are common UX writing mistakes to avoid?▼

Common mistakes include blaming the user in errors, using placeholders to carry required information, writing headings that are too broad, and adding artificial urgency to notifications. Read copy aloud to test whether it sounds conversational.