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.

That includes documentation prose — READMEs, docs pages, release notes, onboarding guides. The principles below were written for interface strings and most transfer directly (accuracy, one vocabulary, nothing does double duty, no selling); where a principle is interface-specific it is marked. A doc that contradicts the thing it documents is a HIGH finding, not a typo.