ux-writing

Review and write UI microcopy using pattern libraries and audit checklists.

Updated Jun 1, 2026
One-click install
npx skills add https://github.com/j-cogburn/d3 --skill ux-writing-j-cogburn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ux-writing
Source: https://github.com/j-cogburn/d3/tree/main/tests/project-t01/.d3/skills/ux-writing
Command: npx skills add https://github.com/j-cogburn/d3 --skill ux-writing-j-cogburn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Poorly written UI microcopy creates user confusion, increases interaction friction, and leads to unnecessary support requests. This Skill provides structured, actionable guidance for agents to write clear, concise, and effective UI text that improves the overall user experience.

Core Features & Use Cases

  • Pattern Libraries: Pre-built formulas and real-world examples for button labels, error messages, empty states, confirmation dialogs, onboarding copy, tooltips, and loading states.
  • Tone & Voice Guidelines: Clear rules for adapting tone to different contexts (errors, success states, destructive actions) to maintain consistent, user-friendly communication.
  • Audit Tools: A practical checklist and red flag criteria to evaluate existing microcopy for clarity, conciseness, and usefulness.
  • Use Cases: Writing new UI copy for features, auditing existing product microcopy, designing user flows that require copy, and fixing copy flagged as confusing in UX reviews.

Quick Start

Use the ux-writing skill to rewrite the payment failure error message to clearly explain the issue and provide users with a specific step to resolve it.

Frequently Asked Questions about ux-writing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write clear UI microcopy for error messages and button labels?

To write clear UI microcopy, apply structured pattern libraries and tone guidelines that ensure button labels and error messages are concise, useful, and conversational. This reduces user friction and eliminates confusing text that drives support tickets.

What is UX writing and when do I need to audit existing product microcopy?

UX writing is the practice of crafting clear UI text for user flows. You need to audit existing product microcopy when confusing or inconsistent copy appears in UX reviews, using a checklist and red flag criteria to evaluate clarity, conciseness, and usefulness.

How do I fix a payment failure error message to reduce user frustration?

Fix a payment failure error message by rewriting it to clearly explain the specific issue and provide users with an actionable step to resolve it. Following tone guidelines for destructive or error states maintains consistent, user-friendly communication.

What's the best way to maintain consistent tone across empty states, onboarding copy, and tooltips?

The best way to maintain consistent tone across empty states, onboarding copy, and tooltips is to apply clear voice guidelines that adapt tone to different contexts. Pre-built pattern libraries provide real-world formulas to standardize all UI text creation.

Can I use a copy audit checklist to evaluate tooltip content and confirmation dialogs?

Yes, you can use a copy audit checklist to evaluate tooltip content and confirmation dialogs. The checklist applies red flag criteria to assess existing microcopy across all UI text types, ensuring it meets standards for clarity and usefulness.

Why does unclear microcopy increase support ticket volume and how can I prevent it?

Unclear microcopy increases support ticket volume by creating user confusion and interaction friction. Prevent it by using structured pattern libraries for loading states and confirmation dialogs, applying audit tools to catch confusing text before release.