write-ux-microcopy

Write and review interface strings including CTAs, error messages, empty states, and labels using NN/g frameworks.

1|Updated Jul 13, 2026
One-click install
npx skills add https://github.com/dineshrevunuru/SuperSkills --skill write-ux-microcopy-dineshrevunuru
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-ux-microcopy
Source: https://github.com/dineshrevunuru/SuperSkills/tree/main/write-ux-microcopy
Command: npx skills add https://github.com/dineshrevunuru/SuperSkills --skill write-ux-microcopy-dineshrevunuru

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Interface copy often ships generic, vague, or off-voice — buttons labeled "Submit", links saying "Learn more", errors reading "Oops! Something went wrong". This Skill applies Nielsen Norman Group microcopy frameworks to write or audit every string inside an interface so each one is clear, constructive, and in the product's voice. ## Core Features & Use Cases - Type-specific patterns: A decision tree routes each string to its own ruleset — CTA labels, 4Ss link labels, error messages, empty states, confirmation dialogs, field labels, helper text, tooltips, and loading strings. - NN/g framework grounding: Applies the 3 C's (Clear > Concise > Character), 3 I's (Inform/Influence/Interact), 4Ss link-label tests, and error-message guidelines with a lint checklist and anti-pattern table. - Voice discipline: Requires an explicit voice source (VOICE-DNA doc, writing-voice skill, or a derived 3-adjective spec) before writing, and always delivers one recommended string with rationale rather than an unpicked menu. - Use Case: A booking app's payment fails. The Skill rewrites the banner from "Oops! Something went wrong" to "Payment didn't go through. Your bank declined the card — no charge was made", renames the button to "Retry payment", and fixes the field error to name the exact problem. ## Quick Start Ask the AI to write or review the copy for a specific screen, for example: "Write the error message, button label, and empty state for my checkout screen using the UX microcopy skill."

Frequently Asked Questions about write-ux-microcopy

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

FAQPage Schema
How do I write a good error message for a form?

Structure every error as what happened plus why (only if it helps the user) plus the constructive next step. Make it precise, blame-free, human-readable, and shown inline next to the field after the user finishes it, never mid-typing or as a raw error code.

What should a button or CTA label say?

Use a verb plus the specific object, such as "Create account" or "Pay $40", so the label states exactly what happens next. Avoid generic labels like "Submit", "OK", or "Yes/No"; repeat the action instead, as in "Delete files" / "Keep files".

Why is "Learn more" a bad link label?

"Learn more" fails all four 4Ss tests: it is not specific, not substantial out of context, and indistinguishable in a screen reader's links-only list, which is an accessibility failure. Replace it with the destination noun, like "Compare plans" or "Download the report (PDF)".

When should I use a confirmation dialog versus undo?

Reserve confirmation dialogs for destructive, irreversible, or costly actions, with the title as the action question and buttons as action verbs. For reversible actions, prefer undo, because confirming everything trains click-through blindness that defeats the one confirmation that matters.

When should I not use this microcopy skill?

Do not use it for long-form content like articles or case studies, for deciding which UI states a screen needs and their layout, or for AI chatbot dialog behavior and AI failure-state design. Those belong to separate writing-voice, UI-states, and conversational-interface skills.