mkl-write-ux-copy

Write and revise UI microcopy grounded in actual product behavior.

11|1|Updated Sep 13, 2026
One-click install
npx skills add https://github.com/00200200/maintainer-skills-lab --skill mkl-write-ux-copy-00200200
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mkl-write-ux-copy
Source: https://github.com/00200200/maintainer-skills-lab/tree/main/providers/cursor/.cursor/skills/mkl-write-ux-copy
Command: npx skills add https://github.com/00200200/maintainer-skills-lab --skill mkl-write-ux-copy-00200200

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Interface copy often promises actions the product cannot perform, breaks localization tokens, or ignores length limits. This Skill writes and revises labels, errors, empty states, and confirmations based on verified product behavior so the copy stays accurate and actionable. ## Core Features & Use Cases - Behavior-grounded microcopy: Inspects the relevant UI and handlers so button labels and error messages match what the product actually does. - Localization-safe editing: Preserves string keys, interpolation tokens, markup, accessible names, and ICU plural syntax unless a structural change is requested. - Length and tone control: Fits the requested tone, locale, and character budget, measuring final strings and accounting for dynamic values. - Use Case: An upload over {max_mb} MB is rejected with no retry. The Skill replaces "Oops! Something went wrong" with "This file exceeds {max_mb} MB. Choose a smaller file." plus a "Choose file" button, keeping the token exact. ## Quick Start Ask the assistant to rewrite the error message and button label for the file upload flow, keeping the {max_mb} token and matching the actual recovery action.

Frequently Asked Questions about mkl-write-ux-copy

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

FAQPage Schema
How do I write error messages that match actual product behavior?▼

Inspect the relevant UI and handlers first, then state the actionable problem without blaming the user and give a supported recovery step. Never imply an action the product cannot perform or claim data was saved without implementation evidence.

How to write UI microcopy with character limits?▼

Measure the final string against the stated limit and account for dynamic values separately, since a short template does not prove every rendered message fits. State the counting convention when it could affect acceptance, and check the real layout when available.

Can I edit ICU message format strings without breaking plurals?▼

Yes, but inspect the ICU format before editing branches. Preserve interpolation tokens, plural syntax, markup, and string keys unless the user explicitly requests a structural change.

What should an empty state message include?▼

An empty state should explain what belongs in that space and how the user can add it. Ground the guidance in what the product actually supports rather than promising features that do not exist.

When should I ask clarifying questions about UX copy?▼

Ask when unknown product behavior determines whether the copy would be misleading, such as whether an action is reversible. Style choices like tone preferences usually do not need clarification.