Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →zzafergok/ux-writing
Create user-centered, accessible interface copy (microcopy) for digital products including buttons, labels, error messages, notifications, forms, onboarding, empty states, success messages, and help text.
Passed 20 of 22 test cases with the skill, and 15 of 22 without it.
and 3 more in the full report
5 fixed15 passed either way2 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
Give me a top bar screen heading for the screen where users manage their security credentials and notification preferences.
| Checked | Without skill | With skill |
|---|---|---|
| The screen heading is framed as a noun phrase in sentence case | Missed | Passed |
| The screen heading length remains under 40 characters | Passed | Passed |
The instructions your model reads when the skill loads.
Every word is a decision. The right word moves the user forward; the wrong word stops them, confuses them, or makes them anxious.
The quality of UX copy is measured against four questions. These questions should be run through for every new piece of text before it is finalised.
Purposeful. Does this text help the user reach their goal, or does it simply fill space? Concise. Can I communicate the same meaning with fewer words? Conversational. Would a real person say this to someone in front of them? Clear. Is there any possible way to misread this?
Headings tell the user where they are. They are written as noun phrases in sentence case. On screens that require an action, the heading clearly states what the task is.
"Account settings" and "Choose a payment method" are effective headings. "Settings" is too broad. "Please make a selection" is unnecessarily formal.
The verb-plus-object structure is used throughout. The button label names the action it triggers. Context-free labels such as "OK", "Yes", or "Next" are avoided.
"Save changes", "Delete account", and "Proceed to payment" are clear button labels. "Submit" and "Confirm" often leave users uncertain about what will happen. For destructive actions such as deletion or cancellation, the label must clearly reflect the consequence — the user needs to know what they are about to lose.
An error message covers three things: what did not happen, the likely reason, and what the user can do next. The third element is the most important — without a recovery path, the user is stuck.
Poor: "An error occurred."
Good: "Payment failed. Check your card details and try again."
Poor: "Invalid input."
Good: "Email address must include @."
test cases passed, vs 15 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.