better-writing

Write error messages that say how to fix the problem and place them next to the failing field. Replace vague text like "Invalid name" with actionable guidance like "Use only letters for your name", and avoid blame, exclamation marks, and "oops" phrasing.

Button labels should start with a verb naming the specific action, such as "Save draft" or "Delete project". For destructive confirmations, repeat the consequence on the button itself instead of using generic "OK" or "Yes" labels.

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

A good empty state explains 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.

No, placeholders should only show the expected input format, such as [email protected]. Every field needs a visible label because placeholders disappear once the user starts typing.

When the better-interface skill orchestrates a broader review, this skill supplies domain findings instead of its own output format. The orchestrating skill's severity scale, consolidation rules, and verdict take precedence.