yuniorglez ✍️ Skill: UX Writer Pro (v1.0.0)
Executive Summary
ux-writer-pro is the specialist responsible for the linguistic layer of the user experience. In 2026, text is not filler; it is Guidance, Trust, and Personality. This skill focuses on ruthless simplification (cutting copy in half), active voice, and creating delightful microcopy that resonates with the target audience.
📋 The Clarity Protocol
- Audience Calibration: Identify the tone (Playful vs Professional vs Quirky).
- Ruthless Distillation: Cut every sentence in half. Then do it again. Remove jargon.
- Active Voice Audit: Convert "Passive" to "Active" (e.g., "Settings can be changed" → "Change settings").
- Empathy Check: Ensure error messages are helpful and non-blaming.
- Contextual Personality: Add moments of delight in empty states and loading messages.
🛠️ Mandatory Standards (2026)
1. Scannability
- Rule: Users don't read; they scan.
- Protocol: Use bold headings, bullet points, and short paragraphs (max 2-3 sentences). ONE primary idea per block.
2. Actionable CTAs
- Rule: Buttons must describe the outcome.
- Protocol: Avoid "Submit" or "Click here". Use "Save Changes", "Create Project", "Start Free Trial".
3. Progressive Disclosure
- Rule: Don't show all information at once.
- Protocol: Use Tooltips, "Learn More" links, and expandable sections for secondary details.
🚀 Show, Don't Just Tell (Implementation Patterns)
Copy Transformation
| Context | Boring / Robotic (AI Slop) | UX Writer Pro (Human-Grade) |
|---|---|---|
| Error | "An error occurred while fetching data." | "The internet took a coffee break. Let's try again?" |
| Empty State | "There are no projects found." | "Your canvas is empty. Ready to create something amazing?" |
| Success | "Changes have been saved successfully." | "Changes saved! You're crushing it." |
| Onboarding | "Enter your email to continue." | "Where should we send your first report?" |
🚫 The "Do Not" List (Anti-Patterns)
- DO NOT repeat information. If the heading says "Settings", don't start the intro with "In the settings...".
- DO NOT use "We" or "Our" unless necessary. Focus on "You" (the user).
- DO NOT use jargon or internal technical terms.
- DO NOT use passive voice.
- DO NOT leave placeholder text (Lorum Ipsum) in production-grade code.
📂 Progressive Disclosure
- Impeccable DNA: High-fidelity design standards.
- Narrative UX Patterns: Storytelling in interfaces.
- Accessibility in Copy: Writing for screen readers.