Drop David into Claude and get a Senior UX Writer who writes every word a user sees when they interact with a digital product - button labels, onboarding flows, error messages, empty states, tooltips, push notifications, form field copy, and product content style guides that make the interface almost invisible because users always know exactly what to do next.
Bad UX writing creates confusion, errors, drop-off, and support tickets. Good UX writing is almost invisible. David is built on three principles he never breaks: say what it does not what it is ("Save changes" not "Submit"), write for the user's goal not the system's action ("Your account is ready" not "Account creation process completed successfully"), and if the user has to read the error message the product has already failed them - make the fix path immediate and obvious. For every button label or critical UI copy, he provides 3+ options because these are design decisions with measurable impact.
What you get
-
→
Microcopy and UI text - button and CTA label options (3+ variants per element), navigation items and menu labels, page titles and headings within product interfaces, tooltip and contextual help text, loading state messages, modal and dialog box copy, and form field copy covering labels, placeholders, and helper text
-
→
Error messages and validation copy - error messages structured as what went wrong, why, and how to fix it, form field validation messages, permission error and system error sets, success and confirmation states, push notification copy for mobile apps, and transactional email notification copy
-
→
Onboarding flow copy - screen-by-screen onboarding copy for new users, feature introduction and discovery copy, walkthrough and tutorial text, permission request rationale that explains why the app needs access, and empty state prompts that encourage first actions without pressure
-
→
Product content style guides and terminology - product-specific content style guide sections, terminology glossaries that enforce consistent labelling across the product, UX copy audits of existing interfaces with specific rewrite recommendations, and GDPR-aware consent language and data collection notification copy
-
→
Help and support content - help centre article drafts, in-product help and guidance copy, chatbot scripts for support contexts, knowledge base content for complex product features, and FAQ content structured to reduce support ticket volume on the most common user confusion points
-
→
App store listing copy - iOS and Android App Store title, description, and screenshot caption copy, accessibility-aware alt text standards, inclusive language review for product interfaces, and A/B copy testing frameworks for critical conversion points in onboarding and activation flows
Push Notification Copy
David writes every push notification as a small spec: what it says, when it fires, where the tap goes and how the user can switch it off.
-
Anatomy: title, front-loaded body, verb action buttons and the exact screen the tap opens
-
Examples by type: transactional, reminders, social, status changes, re-engagement and promotional, each with what it must say
-
Respectful by default: no false urgency or guilt, token fallbacks, lock-screen-safe versions and a permission priming screen
-
Spec sheet: trigger, audience, opt-out category, frequency cap, 3 title and body options, localisation notes and what to measure