better-writing

Reviews and improves product copy, microcopy, and interface text for consistency and clarity.

6.7k|239|Updated Jul 10, 2026
One-click install
npx skills add https://github.com/jakubkrehel/skills --skill better-writing-jakubkrehel
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: better-writing
Source: https://github.com/jakubkrehel/skills/tree/main/skills/better-writing
Command: npx skills add https://github.com/jakubkrehel/skills --skill better-writing-jakubkrehel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Inconsistent, ambiguous, or unhelpful interface copy confuses users and erodes trust. This Skill audits and rewrites product copy—buttons, errors, empty states, links, and settings labels—against established UX writing principles. ## Core Features & Use Cases - Copy Review with Severity Ratings: Classifies findings as HIGH, MEDIUM, or LOW and reports them in a structured table with before/after suggestions. - Voice and Terminology Consistency: Recon of existing copy to match the product's established voice, terminology, and capitalization policy. - Pattern Guidance: Covers verb-first buttons, actionable error messages, forward-pointing empty states, descriptive links, and placeholder usage. - Use Case: Before shipping a new settings page, run a writing review to catch a bare "Yes/No" confirmation dialog, an "Oops!" error message, and inconsistent title case across toggles. ## Quick Start Review the copy in my checkout flow and report any writing issues with suggested fixes.

Frequently Asked Questions about better-writing

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

FAQPage Schema
How do I review UX writing and microcopy in my project?▼

Run a writing review over your source files to check every label against the action it invokes, every error for a stated fix, and terminology against surrounding copy. Findings are grouped by principle with severity ratings and before/after suggestions.

How to write good error messages for forms?▼

An error message should state how to fix the problem and sit beside the field that failed. Phrase hints positively, avoid blame and exclamation marks, and show format hints before the mistake happens rather than after.

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 across languages.

Does this skill check accessibility or typography issues?▼

No, it deliberately scopes to copy content only. Error markup and live regions belong to accessibility review, while capitalization rendering via CSS and truncation belong to typography review.

When should placeholder text not be used as a label?▼

Placeholders vanish on input, so they must never be the only label for a field. Use them only to show the expected format, such as name@example.com, while keeping a visible label on every field.