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.