web-quality
Skill1 starsChanged 3 months agoMITView on GitHub
Audit and fix interaction quality — a11y, focus, forms, touch targets, semantics, motion preferences. Use only when the task is an a11y/guidelines pass or form/dialog interaction fix. Prefer quality-check when the goal is ship/verify/regression; prefer product-design when multi-step product UX craft is unclear; frontend-design for full FE builds. Not for visual brand redesign, React performance alone (react-performance), or Playwright/e2e proof loops (browser-verify).
5 other projects use a version of this.
Adopted by
Most recently taken up by
- redhoram/claude-landing-templatetheir own version, first seen Nov 7, 2026
- TomSzenessy/AI_TEMPLATEtheir own version, first seen Oct 15, 2026
- Kaleemify/claude-skillstheir own version, first seen Sep 24, 2026
- INERATE/ateliertheir own version, first seen Sep 22, 2026
- georgekhananaev/claude-skills-vaulttheir own version, first seen May 25, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- georgekhananaev/claude-skills-vault★ 28same name
- INERATE/atelier★ 2same name
- Kaleemify/claude-skills★ 1same name
- redhoram/claude-landing-template★ 1same name
- TomSzenessy/AI_TEMPLATE★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository47 other files it gives its agents.
- data-apache-lakehouseSkill
- data-apiSkill
- dataSkill
- data-duckdbSkill
- data-identity-resolutionSkill
- data-pipeline-operationsSkill
- data-pokemon-tcg-foundationsSkill
- data-product-evalSkill
- data-reelsSkill
- data-semantic-qualitySkill
- data-table-lifecycleSkill
- html-designSkill
- ebay-listingSkill
- flutter-pro-ux-reviewSkill
- flutterSkill
- browser-testing-with-devtoolsSkill
- browser-verifySkill
- design-systemSkill
- frontend-designSkill
- mobile-app-echarts-visualSkill
- mobile-blog-chart-visualSkill
- mobile-chart-visualSkill
- mobile-product-uxSkill
- mockup-implementSkill
- product-designSkill
- product-ui-craftSkill
- prototypeSkill
- react-performanceSkill
- ui-exploreSkill
- visual-verifySkill
- high-retention-insight-reels-instagramSkill
- instagramSkill
- instagram-virality-insightsSkill
- marketing-cashvertisingSkill
- marketing-contagiousSkill
- marketing-going-viralSkill
- marketingSkill
- marketing-offersSkill
- marketing-storybrandSkill
- quality-checkSkill
- elements-of-styleSkill
- style-clarity-graceSkill
- writer-styleSkill
- writing-docsSkill
- writing-proseSkill
- writingSkill
- writing-technicalSkill
The file
Files
Web quality (a11y + interaction)
Job: Make UI correct and usable, not just pretty.
Sources (attribution)
- Vercel Web Interface Guidelines lineage and the public
web-design-guidelinesagent skill pattern (rule-oriented UI review: a11y, forms, focus, motion, typography practicality). - WCAG 2.2 practical AA checks (contrast, name/role/value, keyboard, target size where applicable).
- AccessLint-style concerns: contrast pairs, color-not-only status, descriptive link purpose — synthesized as checklists for agents.
Original checklist packaging for this repo; not a verbatim copy of any upstream skill file.
When to load
- Pre-merge UI review
- axe /
test:a11yfailures - Sheets, dialogs, sticky bars, custom controls
- Status colors, trend arrows, form errors
Audit workflow
- List surfaces in the change (routes/components).
- Walk the checklist below; fix blockers first.
- Re-run project a11y tests if present (
test:a11y, axe Playwright). - Note residual risks (e.g. chart canvas labels).
Checklist
Semantics & structure
- Real headings in order (
h1→h2…); no skip for style - Buttons are
<button>; links are<a href> - Lists/tables use semantic elements when presenting tabular data
- Landmarks: main, nav, dialog labeling
Keyboard & focus
- All interactive elements reachable by keyboard
- Visible focus rings (tokenized); never
outline-nonewithout replacement - Focus trap in modal/sheet; restore focus on close
- Esc closes overlay; Enter submits forms appropriately
- Custom widgets implement expected ARIA patterns
Forms
- Every input has a visible label (or properly associated aria-label)
- Errors identified in text, not color only
autocompletewhere relevant; correcttype- Disabled submit explained; no silent no-ops
Touch & targets
- Primary controls ≥ ~44×44 px hit area (padding OK)
- Spacing between adjacent actions reduces mis-taps
- Sticky footers don’t cover content or system gestures
Color & contrast
- Text meets contrast on actual surfaces (glossy glass often fails)
- Status not by color alone (icon + text)
- Charts: series distinguishable without hue-only (pattern/label)
Motion & media
prefers-reduced-motionrespected- No infinite decorative animation on product chrome
- Images: meaningful
altor empty alt if decorative
Feedback
- Loading regions:
role="status"/aria-busyon containers - Toasts don’t replace critical error UI
- Destructive actions confirm when irreversible
Output format (reviews)
Prefer terse findings:
path/to/File.tsx:42 — focus ring removed on Chip; keyboard users lose position
path/to/Sheet.tsx:18 — missing aria-labelledby on dialogHand off
| Need | Next skill |
| Visual density/spacing | product-ui-craft |
| Mobile sticky/safe-area | mobile-product-ux |
| Automated proof | browser-verify |
| Perf | react-performance |
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

