Agent-Skills.md

Agent Skills: ✍️ Skill: UX Writer Pro (v1.0.0)

Master of Human-Centric Microcopy & Narrative Design. Expert in clarity, active voice, and brand-aligned tone for interfaces.

UncategorizedID: yuniorglez/gemini-elite-core/ux-writer-pro

Repository

yuniorglez/gemini-elite-core
YuniorGlez
96

Install this agent skill to your local

pnpm dlx add-skill https://github.com/YuniorGlez/gemini-elite-core/tree/HEAD/skills/ux-writer-pro

Skill Files

Browse the full folder contents for ux-writer-pro.

Download Skill

Loading file tree…

skills/ux-writer-pro/SKILL.md

Skill Metadata

Name
ux-writer-pro
Description
"Master of Human-Centric Microcopy & Narrative Design. Expert in clarity, active voice, and brand-aligned tone for interfaces."

✍️ 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

  1. Audience Calibration: Identify the tone (Playful vs Professional vs Quirky).
  2. Ruthless Distillation: Cut every sentence in half. Then do it again. Remove jargon.
  3. Active Voice Audit: Convert "Passive" to "Active" (e.g., "Settings can be changed" → "Change settings").
  4. Empathy Check: Ensure error messages are helpful and non-blaming.
  5. 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)

  1. DO NOT repeat information. If the heading says "Settings", don't start the intro with "In the settings...".
  2. DO NOT use "We" or "Our" unless necessary. Focus on "You" (the user).
  3. DO NOT use jargon or internal technical terms.
  4. DO NOT use passive voice.
  5. DO NOT leave placeholder text (Lorum Ipsum) in production-grade code.

📂 Progressive Disclosure