Agent skills4 min read
UX and accessibility skills compared
Open skills that make an agent write clear interface copy, handle errors and edge cases and pass WCAG, what each does best, and the merged ux skill I use.
An agent ships a signup form with a "Submit" button, a disabled state nobody can explain, an error that says "Something went wrong" and a placeholder that fails contrast. Each of those has a skill that would have caught it, written by a different author. For most projects I would install ux from molveau/skills. It merges Jakub Krehel's writing and accessibility skills, Paul Bakaus's clarify, harden and onboard commands from Impeccable, and Julien Thibeaut's fixing-accessibility into one playbook, with written calls where they disagree. If you need Lighthouse measurements or Vercel's guidelines checked live, one of the originals below is the better install.
The contenders
| Skill | Author | Licence | Best at | Lacks |
|---|---|---|---|---|
| better-writing and better-accessibility | Jakub Krehel | MIT | Interface copy and accessibility engineering with patterns | Layout resilience: long text, overflow, offline |
| Impeccable (clarify, harden, onboard) | Paul Bakaus | Apache-2.0 | Rewriting unclear copy, edge cases, first-run flows | Screen-reader and ARIA depth |
| fixing-accessibility | Julien Thibeaut (ibelick) | MIT | A focused audit-and-fix pass on HTML against WCAG | Copy and states |
| web-design-guidelines | Vercel | MIT | A file:line review against Vercel's Web Interface Guidelines |
Offline use: it fetches the rules at each review |
| web-quality-skills | Addy Osmani | MIT | Measured audits with Lighthouse and Chrome DevTools | Copy, onboarding and error wording |
| ux | Molveau Studio | MIT | Copy, states, resilience and accessibility in one pass, conflicts settled | Live measurement; a script of its own |
Each one, fairly
Jakub Krehel's better-writing and better-accessibility
Jakub's writing skill starts where it should: it inventories the strings and the translation files before changing a word, and treats a deliberate brand voice as the voice. His accessibility skill covers focus, keyboard, forms, screen readers and ARIA with reference patterns. If you want his judgment alone, install his repo.
Impeccable's clarify, harden and onboard, by Paul Bakaus
Three commands from Impeccable that own the words and the hard cases. clarify rewrites labels, errors and instructions, harden covers error handling, long text, i18n and overflow, and onboard designs first-run flows and empty states. Installing Impeccable gets you these with the rest of its vocabulary and its scripts.
fixing-accessibility, by Julien Thibeaut
A short, direct skill: audit the HTML, fix the ARIA labels, keyboard paths, focus, contrast and form errors, and avoid adding ARIA where native elements already work. His ui-skills repo also has baseline-ui, fixing-motion-performance and fixing-metadata, which I do not merge. Install it for a fast accessibility pass on a single component.
web-design-guidelines, by Vercel
Vercel's skill reviews files against its Web Interface Guidelines and reports each finding as file:line. It fetches the latest rules from the guidelines repo at every review, so it stays current but needs network access. It covers a wide surface (focus, forms, animation, touch, i18n, hydration) in one checklist, which makes it a good second reviewer next to any of the others.
web-quality-skills, by Addy Osmani
Addy's collection is measurement first. Its accessibility skill follows WCAG 2.2 and, when Chrome DevTools is available to the agent, runs a live Lighthouse audit and reads the rendered accessibility tree before touching code. If you want evidence from the rendered page rather than a reading of the source, install it next to ux.
What the merged skill adds
- Routing. One install. The
SKILL.mdsends copy to Jakub'sbetter-writing, unclear instructions toclarify, overflow and i18n toharden, first-run flows toonboard, and a WCAG fix tofixing-accessibility. - Pinned, unedited copies under
references/vendor/, at a pinned commit. A weekly GitHub Action checks upstream and opens an issue when a source moves; a person reviews each bump. - A playbook that settles disagreements. Placeholder contrast: Jakub treats placeholders as exempt, Impeccable asks 4.5:1, and the playbook takes 4.5:1 because WCAG 1.4.3 does not exempt them. Target sizes: build to 44px for touch and 40px dense, and report anything under 24px as a WCAG 2.5.8 failure. Empty states: a title, one sentence and one action, with a visual only when it is a real preview.
- Always-on rules an agent applies without being asked: buttons that name the action, errors beside the field that keep what the user typed, designed empty, loading, error and offline states, focus always visible, nothing conveyed by color alone.
- Neighbours with scripts.
uxhas no script of its own. Its full pass ends with a keyboard-only walk and a screen-reader walk, and anything not checked is reported as not verified. Theanti-slopdetector and themotionchecker cover the mechanical tells next to it.
Install
The skill alone, with the skills CLI:
npx skills add molveau/skills -s uxThe design bundle:
npx skills add molveau/skills -s anti-slop -s ui -s ux -s motion -s design-grill -s design-inspiration-indexIn Claude Code, all eleven skills as one plugin:
/plugin marketplace add molveau/skills
/plugin install molveau-skills@molveauEvery skill and bundle is on the skills page, and the source is at github.com/molveau/skills. Related comparisons: anti-slop skills, UI skills, motion skills.
Checklist
- Every button names what happens.
- Every error sits beside the field, says what to do next and keeps the input.
- Empty, loading, error, success and offline states each have copy and a next step.
- The flow works by keyboard alone, with focus visible at every step.
- Touch targets are 44px, and nothing under 24px ships.
- Long names and the longest locale do not break the layout.
- If you need a measured Lighthouse audit, it ran on the rendered page.
Stanislas Molveau
Founder, Molveau Studio
I design and build web and mobile products, and write these guides from teardowns of real apps rather than theory.