Individual skill
ux-writing
Judgment for text read by someone who wasn't there when it was written: user-facing output, error and help text, docs, comments, and generated deliverables. Use when that text is the substance of the work or under review.
skills/ux-writing/SKILL.md
Source commit 8e149b335e963954e9c4bafba00eedbd7de060ed
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 6, 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)
- 227
- Repository last updated
- Nov 2, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- agents-md Repository topic
- ai-agents Repository topic
- ai-coding Repository topic
- claude-code Repository topic
- codex-cli Repository topic
- coding-agents Repository topic
- coding-standards Repository topic
- developer-tools Repository topic
- llm Repository topic
- design Derived category
- writing Derived category
- docs Derived category
- design-interface Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# UX Writing & Docs
User-visible text is product behavior and carries the same quality bar as
code. Every rule below is distilled from a real defect caught in review, and
keeps its counter-example because the reasoning is the point. When in doubt,
re-read the output as the user who just hit the problem.
## Status output & diagnostics
- **Report effective values, not stored ones.** A status display answers
"what will happen when I run this", so resolve values exactly the way the
runtime does, including environment variables and layered config.
*Counter-example: a config viewer printed "API key set: no" while an env
var held the key the next run would actually use.*