agentsclimarketplace

Clarify

Skill educlopez/ui-craft/cli/assets/codex/skills/clarify

Design engineering system for AI coding agents — ship UI with craft-level quality. Install as an agent skill.

Install
npx -y skills add educlopez/ui-craft --skill clarify

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

What its author says it does

Copied from the file, not written here

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.

SKILL.md

2.8 KB, as published. Nobody here has run it

<!-- 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 $ARGUMENTS. 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."
  6. Destructive actions — the noun lives in the button. "Delete {projectName}" > "Delete". The dialog confirms; the button commits.
  7. Case — sentence case by default. Title Case only for branded product names. Never ALL CAPS (exception: 11-13px category labels, already in SKILL.md).
  8. Voice — clear > clever. Active voice. Short sentences. Real words ("cancel" not "discontinue", "start" not "initiate").

Knob-agnostic — clarity is not tunable. Run the full checklist regardless of CRAFT_LEVEL.

References to read: references/copy.md (microcopy voice + patterns), references/accessibility.md (error message expectations for screen readers).

Output format — the Review Format table:

BeforeAfterWhy

Prioritize by impact (errors and destructive actions first, then CTAs, then helper copy). End with a one-paragraph summary of the overall voice shift. If the user says "apply", edit the code and re-print the table with file paths.

Next step: /critique — copy changes shift hierarchy; re-read the surface after (rung 1).

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.