skills.rest
jacob-balslev
jacob-balslevCOMMUNITY
Explore all skills by this author →
GitHub

microcopy

Generate functional UI text with verb-first labels and structured messaging rules.

1|Updated May 6, 2026
Search Tags:#microcopy#ux writing#empty states#error messages#button labels#ui text#validation messaging
One-click install
npx skills add https://github.com/jacob-balslev/skill-graph --skill microcopy-jacob-balslev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: microcopy
Source: https://github.com/jacob-balslev/skill-graph/tree/main/marketplace/skills/microcopy
Command: npx skills add https://github.com/jacob-balslev/skill-graph --skill microcopy-jacob-balslev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Microcopy ensures interface text is clear, actionable, and consistent—so users know what will happen, what’s wrong, and what to do next.

Core Features & Use Cases

  • Button label precision: verb-first labels that match the real consequence (no generic “Submit/OK”).
  • High-performing empty states: acknowledge → explain → guide with a primary next-step action.
  • Safe, scannable messaging: tooltips, confirmation dialogs, errors, inline validation, toasts, loading/progress, and permission/onboarding copy that follow consistent structure.

Quick Start

Use microcopy to rewrite the UI text in your app so every button, empty state, tooltip, dialog, and error message becomes specific, actionable, and aligned with the skill’s functional UI rules.

Frequently Asked Questions about microcopy

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

FAQPage Schema
How do I write UX writing for empty states that actually guide users?▼

Effective empty states use an acknowledge–explain–guide structure, acknowledging the current state, explaining its value, and guiding users with a primary next-step action button to drive engagement.

What is the best way to write clear UI text for error messages and inline validation?▼

The best UI text for error messages follows a What–Why–What-to-do structure with blame-free phrasing, clearly explaining what went wrong, why it happened, and exactly what the user should do next.

How should I format button labels for better clarity and actionability?▼

Button labels should use verb-first wording that matches the real consequence of the action, avoiding generic terms like Submit or OK to ensure users know exactly what happens when they interact with the UI element.

Can I use structured microcopy rules for toast messages and loading progress indicators?▼

Yes, structured microcopy rules apply to toast messages and loading progress indicators by using progressive loading language and accessible, blame-free phrasing to keep users informed during interactive system processes.

Does UX writing need specific messaging structures for onboarding steps and permission dialogs?▼

UX writing for onboarding steps and permission dialogs requires consistent structural rules to ensure the UI text is scannable, actionable, and clearly communicates what users are agreeing to or setting up.

Why do generic confirmation dialogs fail and how can UI text fix them?▼

Generic confirmation dialogs fail because they lack specific context, which structured UI text fixes by applying consistent wording rules that make the confirmation action, consequence, and alternatives explicitly clear to the user.

Related Skills

Explore More Design & Creative Skills→
N1arkoN1arko
78

ux-copy

Writes and refines Russian UX texts for buttons, errors, forms, and more.

Community
Advanced
LutimiLutimi

ckm:ui-styling

Integrate shadcn/ui, Radix primitives, and Tailwind CSS into React interfaces.

Community
Advanced
stevengonsalvezstevengonsalvez

clarify

Rewrite unclear UX copy across error messages, labels, and tooltips.

Community
Intermediate
didclawapp-aididclawapp-ai
11

office-contract-draft

Generate contract drafts with predefined sections and standard formatting.

Community
Basic