UX Writing Style Guide
Create a comprehensive UX writing style guide for [product] to ensure consistent, effective product copy. Include: 1) Voice and tone principles with examples for different contexts, 2) Grammar and mechanics standards with common edge cases, 3) UI pattern-specific guidance (buttons, forms, errors, etc.), 4) Terminology glossary with approved terms and phrases, 5) Content frameworks for common flows (onboarding, empty states, etc.), 6) Localization considerations, 7) Accessibility requirements for text content, 8) Review process for copy changes, 9) A/B testing approach for copy optimization, and 10) Examples of before/after copy improvements with rationale.
How to Use This Prompt
- Copy the prompt using the button above
- Replace placeholders in [brackets] with your specific details
- Paste into your AI assistant (ChatGPT, Claude, Gemini, etc.)
- Iterate as needed - ask follow-up questions to refine the output
Why This Prompt Works
This prompt generates a complete, implementable style guide rather than abstract writing principles. By requesting pattern-specific guidance for buttons, forms, and error states alongside before/after examples, it produces a reference document that designers and writers can use immediately to make consistent copy decisions without escalating to the PM.
When to Use This Prompt
- When your product copy is inconsistent across features and you need to establish standards
- Before scaling your team with new writers or designers who need a single source of truth for copy decisions
- When preparing for internationalization and you need to document localization-friendly writing patterns
Tips for Better Results
- Include 3-5 examples of existing copy from your product (both good and bad) so the AI can calibrate its recommendations
- Describe your brand personality in a few adjectives (e.g., "professional but warm, concise, never patronizing") for aligned tone guidance
- Specify your product's UI patterns (modals, toasts, inline validation) so the guide covers your actual components, not generic ones