skills.rest
leonardoacosta
leonardoacostaCOMMUNITY
Explore all skills by this author →
GitHub

better-writing

Reviews and writes UX microcopy including buttons, errors, empty states, and placeholders.

Updated Aug 2, 2026
Search Tags:#microcopy#ux writing#empty states#error messages#button labels#interface copy#copy review
One-click install
npx skills add https://github.com/leonardoacosta/agents --skill better-writing-leonardoacosta
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: better-writing
Source: https://github.com/leonardoacosta/agents/tree/main/skills/better-writing
Command: npx skills add https://github.com/leonardoacosta/agents --skill better-writing-leonardoacosta

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Inconsistent, vague, or confusing interface copy erodes user trust and makes products harder to use. This Skill provides a systematic set of principles for writing and reviewing user-facing text so buttons, errors, links, and empty states are clear, consistent, and actionable. ## Core Features & Use Cases - Twelve Copy Principles: Covers verb-first button labels, error messages that say how to fix the problem, empty states with a next action, placeholders as format examples, consistent capitalization, and one flow vocabulary. - Structured Review Output: Reports findings in a severity-ranked table (HIGH/MEDIUM/LOW) with before/after quotes, file locations, verification steps, and a Block/Needs changes/Approve verdict. - Use Case: While reviewing a settings screen, the Skill flags a toggle labeled "Don't send read receipts" and rewrites it as "Send read receipts", and replaces an "Oops! Something went wrong." toast with "Unable to save. Check your connection and try again." ## Quick Start Review the interface copy in my checkout flow and report findings with severity, before/after text, and a verdict.

Frequently Asked Questions about better-writing

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

FAQPage Schema
How do I write better error messages for forms?▼

Error messages should state how to fix the problem and appear next to the failing field. Replace "Invalid name" with "Use only letters for your name", avoid blame and exclamation marks, and phrase hints positively before the mistake happens.

How should button labels be written in UI copy?▼

Button labels should start with a verb naming the specific action, like "Save draft" or "Delete project". Confirmation dialogs must repeat the consequence, offering "Delete project" and "Cancel" instead of bare "Yes" and "No".

Should UI text use title case or sentence case?▼

Pick one capitalization policy per element type and apply it consistently. Sentence case is the safer default because it is calmer, avoids per-word case rules, and localizes cleanly across languages.

What makes a good empty state in a product interface?▼

An empty state should say what the place is and how to fill it, with one clear next action such as a "Create a project" button. Search empty states should name the query and offer an exit like clearing filters.

When should placeholders not be used as field labels?▼

Placeholders should only show the expected input format, such as [email protected], and never serve as the field's only label. Placeholders vanish on input, so every field needs a persistent visible label.

Related Skills

Explore More Design & Creative Skills→
lushly-devlushly-dev
4

design-content

Guide UX writing for user-facing interface text and terminology.

Official
Basic
AppiumTestDistributionAppiumTestDistribution
100

generate-appclaw-flow

Generate AppClaw YAML flow files with variable interpolation and parser validation.

Official
Advanced
JenilRevaliyaJenilRevaliya

web-accessibility-auditor

Audit and implement WCAG 2.2 AA accessibility in HTML and UI components.

Community
Intermediate
learnn-comlearnn-com

capability-assess-architecture

Assess and adopt a system architecture pattern using a resolution cascade and guidelines.

Official
Advanced