skills.rest
falentio
falentioCOMMUNITY
Explore all skills by this author →
GitHub

better-writing

Reviews and rewrites interface copy, error messages, and microcopy for clarity and consistency.

Updated Aug 22, 2026
Search Tags:#localization#microcopy#ux writing#content design#error messages#interface copy#copy review
One-click install
npx skills add https://github.com/falentio/cimi --skill better-writing-falentio
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: better-writing
Source: https://github.com/falentio/cimi/tree/main/.agents/skills/better-writing
Command: npx skills add https://github.com/falentio/cimi --skill better-writing-falentio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Product interfaces often ship with inconsistent terminology, vague error messages, and clever-but-confusing copy that frustrates users and breaks under translation. This Skill audits and rewrites UI text so every label, button, and message is clear, consistent, and actionable. ## Core Features & Use Cases - Copy Auditing: Reviews buttons, links, errors, empty states, placeholders, and settings labels against established UX writing principles like verb-first labels and descriptive link text. - Severity-Ranked Reporting: Groups findings by violated principle with HIGH/MEDIUM/LOW severity, before/after rewrites, and file locations, ending in a Block or Approve verdict. - Use Case: Before shipping a settings page, run a review to catch a toggle labeled "Don't send read receipts", a bare "Learn more" link, and an error saying "Oops! Something went wrong" — and get concrete rewrites for each. ## Quick Start Review the interface copy in my settings and checkout flows and report any writing issues with suggested rewrites.

Frequently Asked Questions about better-writing

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

FAQPage Schema
How do I review UI copy and microcopy for consistency?▼

Audit each element type against one rule set: verb-first button labels, links that describe their destination, one capitalization policy per element type, and errors that state the fix. Compare terminology across the flow so the same action keeps the same name everywhere.

How to write good error messages for web apps?▼

A good error message states how to fix the problem and sits next to the field that failed. Replace "Invalid name" with "Use only letters for your name", avoid blame, exclamation marks, and "oops", and phrase hints positively before the mistake happens.

Should buttons use sentence case or title case?▼

Pick one capitalization policy per element type and apply it everywhere. Sentence case is the safer default because it is calmer, has no per-word rules, and localizes cleanly; mixing "Save Changes" with "Discard changes" reads as sloppiness.

What makes a good empty state in product design?▼

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

When should UX writing review not block a release?▼

Only HIGH severity findings, where copy misleads the user or hides error recovery, should block. MEDIUM issues like voice or capitalization inconsistency and LOW wording polish can ship as follow-up work listed in the findings table.

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
swszzswszz
3

ontologian-sync

Synchronizes local ontology directory with global ~/.ologian store after preview and confirmation.

Community
Advanced
JenilRevaliyaJenilRevaliya

web-accessibility-auditor

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

Community
Intermediate
getsentrygetsentry
905

brand-guidelines

Generate UI and marketing copy aligned with specified writing guidelines.

Official
Intermediate