UX Writing Skill: Interface Copy for AI Agents

What is the ux-writing skill?

Design systems fix visual consistency, but the words in an interface still depend on whoever wrote them. The ux-writing skill puts a content designer's method in front of your agent so error messages, labels and empty states follow one standard.

The README credits Christopher Greer, a Staff Content Designer at Stripe, and lists Content Design, Strategic Writing for UX, Nicely Said and Google Material writing guidelines as its foundations. The SKILL.md sits at the repository root.

What changes in your agent's output

• Button labels follow a verb plus object pattern, so Save changes replaces Submit, and Read our privacy policy replaces Click here.
• Errors say what failed, why and what to do next, instead of Something went wrong or a bare code.
• Copy is checked in four passes for purpose, brevity, conversational tone and clarity before the agent hands it back.
• Tone shifts with the user's state: calm and solution-focused for failures, serious and transparent when data could be lost.

The interface text patterns it covers

• Titles, buttons and links, form labels, helper text and placeholders.
• Four error types: inline validation, system errors, blocking errors and permission requests.
• Success messages, empty states, notifications and onboarding.
• Voice and tone, with a voice chart template and a content usability checklist that scores text.

Who the ux-writing skill is for

Best for

• Product teams without a dedicated writer who still want interface copy that follows a consistent standard.
• Design system and content teams that want guidelines applied at scale instead of reviewed string by string.
• Anyone generating UI with an agent who wants clear microcopy rather than generic placeholders. Pair it with web-design-reviewer for a visual check.

Not for

• ChatGPT. The README states that ChatGPT cannot install or use skills, though Codex CLI and IDE can.
• Visual layout and styling. The skill covers the words in an interface, so look at frontend-design for how the interface is built.
• Long-form marketing copy. The SKILL.md scope is text inside apps, websites and software interfaces.

Use it with UiChemy

Interface copy often starts in a design file. The README describes reviewing copy in Figma through your agent. Fix the wording there, then bring the design into WordPress with UiChemy Figma to WordPress. Click Get Started on uichemy.com.

How to install UX Writing Skill: Interface Copy for AI Agents

git clone https://github.com/content-designer/ux-writing-skill.git

1. Clone the repository

   Run git clone https://github.com/content-designer/ux-writing-skill.git. SKILL.md sits at the repository root, so the whole repo is the skill.

2. Copy the skill files

   Put SKILL.md with its docs, examples, references and templates folders into the folder your agent loads skills from. The repo's build script packages exactly those files.

3. Restart the agent

   The README says to restart your agent or IDE after installing so the skill is picked up.

4. Invoke it

   The skill activates on its own when you write or edit interface copy. In Codex you can call it with $ux-writing, and in Cursor with @ux-writing.

Check that it loaded

Ask the agent to write an error message for when a payment fails. The answer should state what failed, the likely cause and a recovery step, in plain empathetic wording.

Read the official instructions on GitHub

Key features

• Four quality standardsEvery string is judged as purposeful, concise, conversational and clear, giving the agent a measurable test instead of a vague request to improve the text.
• Button and link rulesLabels use an active verb plus an object in sentence case, such as Save changes or View details. Generic labels like OK, Submit and Click here are flagged.
• Four error patternsInline validation, system errors, blocking errors and permission requests each get a pattern. Examples include Upload failed, file is too large, choose a file under 10MB.
• Empty states and success messagesEmpty states explain why nothing is there and offer a call to action. Success messages are past tense and specific, like Changes saved or Email sent.
• Voice and tone frameworkVoice stays constant while tone adapts to purpose, context, emotional state and stakes. Frustrated, confused, confident, cautious and successful users each get guidance.
• Four-phase editing processThe agent edits for purpose, then brevity, then conversational tone, then clarity. It reads the result as if spoken before finalizing it.
• Accessibility guidanceDescriptive link text, error text paired with an icon rather than color alone, visible labels instead of placeholder-only fields and a 4.5:1 contrast minimum.
• Research-based benchmarksButtons run 2 to 4 words, titles 3 to 6 words, errors 12 to 18 words, and instructions about 14 words, with reading levels matched to the audience.
• Reference templatesA voice chart template, a content usability checklist with scoring, pattern examples and fillable templates for errors, empty states and onboarding flows.

Frequently asked questions