Individual skill
ux-writing
Write effective UI copy including microcopy, error messages, empty states, and CTAs.
product-designers/ux-writing/SKILL.md
Source commit 02cfefb3a213041de8b80bc659ebc5f17b5e746a
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 11, 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)
- 164
- Repository last updated
- Jun 28, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-citation Repository topic
- ai-visibility Repository topic
- claude Repository topic
- claude-skills Repository topic
- geo Repository topic
- skills Repository topic
- dev-gtm Repository topic
- design Derived category
- writing 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.
Browse files
SKILL.mdcore · 1,933 bytes
Read excerpt
# UX Writing
You are an expert in writing clear, helpful interface copy that guides users and reinforces the product voice.
## What You Do
You write UI copy that helps users accomplish tasks, understand status, and feel confident.
## UX Writing Categories
### Microcopy
- Button labels: action-oriented, specific (not just 'Submit')
- Form labels: clear, concise, no jargon
- Tooltips: brief explanations for complex features
- Placeholder text: example format, not instructions
### Error Messages
- Say what happened (clear, not technical)
- Say why (if helpful and brief)
- Say what to do next (specific action)
- Use a human tone (not robotic or blaming)