audit-ui

Audit web UI quality across accessibility, interaction, forms, and layout.

75|6|Updated Jan 12, 2026
One-click install
npx skills add https://github.com/mblode/agent-skills --skill audit-ui
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit-ui
Source: https://github.com/mblode/agent-skills/tree/main/skills/audit-ui
Command: npx skills add https://github.com/mblode/agent-skills --skill audit-ui

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audits web UI quality across accessibility, interaction, forms, typography, navigation, layout, performance, motion, and microcopy to help teams review and refine frontend UI before merging or releasing.

Core Features & Use Cases

  • Comprehensive, criteria-driven checks across a11y, keyboard, forms, typography, navigation, layout, performance, motion, and microcopy.
  • Use case: pre-release QA, design QA, or when a user asks for a UI/UX/a11y audit to surface concrete fixes.

Quick Start

Scan the current project UI to surface accessibility, interaction, and typography issues and generate concrete, prioritized fixes.

Frequently Asked Questions about audit-ui

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit UI quality for accessibility issues before release?

Run a pre-release UI audit to check accessibility, interaction, and typography against a criteria-driven checklist. This surfaces practical, prioritized fixes with file:line references and concrete remediation steps across multiple frontend surfaces before release.

What is checked during a frontend UI and UX audit?

A frontend UI and UX audit checks accessibility, keyboard interaction, forms, typography, navigation, layout, performance, motion, and microcopy. It follows a criteria-driven checklist to identify practical fixes across multiple frontend surfaces before release.

Can I use a UI audit to find remediation steps for forms and navigation issues?

Yes, a UI audit surfaces concrete issues in forms and navigation and provides specific remediation steps. It outputs prioritized findings complete with file:line references to guide developers through fixing the identified UI quality problems.

What's the best way to run design QA on web UI components?

The best way to run design QA on web UI is using a comprehensive checklist audit covering a11y, layout, performance, and microcopy. This surfaces prioritized findings with concrete remediation steps and file:line references for actionable fixes.

Does a pre-release UI audit work for microcopy and motion issues?

Yes, a pre-release UI audit works for microcopy and motion issues. The audit evaluates web UI quality across nine specific areas including motion and microcopy to help teams refine frontend UI and surface practical fixes before releasing.