Ui a11y reviewer

Frontend component validator against WCAG standards and aesthetic guidelines.From its SKILL.md

Install

npx -y skills add rafaelghif/antigravity-agents --skill ui-a11y-reviewer

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

One thing to look at

5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

1.8 KB, 375 tokens by cl100k_base, as published. Nobody here has run it

Ensure all frontend code adheres to the "Adaptive UI/UX" rules defined in AGENTS.md.

When generating new UI components.
During PR reviews for frontend changes.
Objective Skip Conditions: No modifications to .html, .jsx, .tsx, .css, .scss, .vue, .svelte files. No modifications to public/ or static/ assets. (Exception: Documentation-only changes).

Audit the UI against the explicit aesthetic criteria based on the context:
- For Consumer Views: Evaluate visual hierarchy (F-pattern or Z-pattern), consistent spacing system (read grid size from .agents/config.json), and micro-interactions (hover, focus, transition states < 300ms).
- For Admin Panels: Evaluate data density (maximize information) and utility (bulk actions, filtering, sorting).
- WCAG Compliance: Verify contrast (axe-core or pa11y), keyboard navigation (manual tab test to .agents/scratch/a11y-test-<date>.md), and ARIA properties (eslint-plugin-jsx-a11y).
- Responsive Design: Verify UI works at the viewports defined in .agents/config.json (Use Puppeteer/Playwright in the toolchain for automated viewport testing). Images use srcset. No horizontal scrolling.
- Mobile Accessibility: Verify touch targets ≥ 44px (WCAG 2.5.5). Test gesture navigation (swipe, pinch) for browser compatibility. Run Lighthouse mobile score → block if < 60.
If violations are found, immediately halt the process and refactor the code to comply before proceeding.