/clarify
UX copy review across buttons, errors, empty states, and form hints — critiques by default, applies only on request. Use when copy feels vague, generic, or AI-sounding, or when the user says "fix the labels", "improve error messages", or "review the copy". Invoke when the user
One skill from ui-craft.
shell
$ npx -y skills add educlopez/ui-craft --skill clarify --agent claude-codeInstalls just this skill. Get the whole plugin for auto-invocation.
How it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/clarify
Context preview
The summary Claude sees to decide when to auto-load this skill.
UX copy review across buttons, errors, empty states, and form hints — critiques by default, applies only on request. Use when copy feels vague, generic, or AI-sounding, or when the user says "fix the labels", "improve error messages", or "review the copy". Invoke when the user
Stats
Stars209
Forks9
LanguageGo
LicenseMIT
Ships with ui-craft
SKILL.md
clarify.SKILL.md
--- name: clarify description: "UX copy review across buttons, errors, empty states, and form hints — critiques by default, applies only on request. Use when copy feels vague, generic, or AI-sounding, or when the user says "fix the labels", "improve error messages", or "review the copy". Invoke when the user asks for clarify on their UI, or mentions 'clarify' alongside design / UI / frontend work." --- <!-- HARNESS MIRROR — do not edit here. Canonical source: skills/ or commands/. After editing source, copy into cli/assets/<harness>/ and repo-root harness mirrors. --> **Context:** this sub-skill is one lens of the broader `ui-craft` skill. If the `ui-craft` skill is also installed, read its SKILL.md first for Discovery + Anti-Slop + Craft Test, then apply the specific lens below. Clarify the copy in the target the user described. Load the `ui-craft` skill. **Default mode: critique, not edit.** Return the copy diff in a Review Format table. Only apply changes if the user says "apply". **Checklist — walk the UI and flag every instance:** 1. **Button labels** — verb + object. "Send invite" > "Submit". "Delete project" > "Delete". Never "OK", "Submit", "Click here". 2. **Errors** — inline, specific, actionable. "Email already in use — sign in or use another address." Never "Something went wrong." 3. **Empty states** — one line explaining why empty + one CTA. "No projects yet. Create your first." not "It's empty here!" 4. **Form hints** — below the field, persistent, not just validation-triggered. "Must include a number and a symbol" as helper text, not as an error after submit. 5. **Confirmation language** — past tense, subject-first. "Project deleted." > "Successfully deleted project."
