Individual skill

ux-writing

Write and review the words inside a product — button labels, error messages, empty states, confirmations, settings labels, placeholders, notifications — and the documentation prose around it, including READMEs, docs pages and release notes. Grounds the wording in the JTBD corpus (the anxiety force tells you what a confirmation must defuse) and hands the result to respondent-panel to find out whether strangers read it the way you meant. Use when writing or reviewing any user-facing string. Triggers on UX writing, microcopy, interface copy, button labels, error messages, empty states, placeholder text, settings labels, confirmation dialog, notification copy, README wording, rewrite these docs, release notes copy, "what should this button say", "rewrite this error", "перепиши текст кнопки".

humane/skills/ux-writing/SKILL.md

Read pinned source

Source commit e7d867ddcc8cb5a34ecf5eaacaee8fc5aa117c93

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Instructions only
Last checked
Nov 5, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
40
Repository last updated
Oct 15, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# UX Writing

**Announce at start:** "I'm using the humane:ux-writing skill to write and review the words inside this product."

The words are part of the interface, not a layer applied to it. A control that
names its exact action needs no tooltip; an error that says what to do next
needs no support ticket. Clear beats clever, consistent beats varied, and the
best error message is the interaction redesigned so the error cannot happen.

## What this skill owns, and what it doesn't

Owns: the **source wording** of every user-facing string, and the decision about
what a string must accomplish.