ui-audit

Audits web UI quality across accessibility, interaction, forms, typography, navigation, layout, performance, motion, and microcopy. Use when reviewing or refining frontend UI before merge or release, or when the user asks for a UI, UX, or accessibility audit.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "ui-audit" with this command: npx skills add mblode/agent-skills/mblode-agent-skills-ui-audit

UI Audit

Final-pass audit workflow for web interfaces. Focuses on concrete issues with concrete fixes.

Trigger Cues

Use this skill when:

  • The user asks for a UI quality audit, design QA, polish pass, or pre-release review
  • The task requires accessibility, keyboard, form usability, typography, or interaction checks
  • The request includes loading/error/empty states, responsiveness, or visual stability checks
  • The request mentions visual hierarchy, dense product chrome, headers, tabs, sidebars, icons, or separator cleanup

Audit Workflow

Copy and track this checklist during the audit:

Audit progress:
- [ ] Step 1: Scope changed surfaces and select relevant categories
- [ ] Step 2: Run CRITICAL checks first (a11y, interaction, forms)
- [ ] Step 3: Run HIGH/MEDIUM checks for the same surfaces
- [ ] Step 4: Report findings with file:line and concrete fixes
- [ ] Step 5: Re-check touched files and mark passes
  1. Audit only changed pages/components unless a full sweep is requested.
  2. Prioritize CRITICAL and HIGH findings before medium-priority polish.
  3. For motion behavior, also apply ui-animation for timing/easing/reduced-motion details.
  4. After fixes, rerun the relevant rules before finalizing.
  5. When hierarchy or chrome cleanup is in scope, use the navigation, layout, and extra-polish sections in craft-checklist.md before reporting.

Rule Categories by Priority

PriorityCategoryImpactPrefix
1Accessibility and SemanticsCRITICALa11y-
2Keyboard and InteractionCRITICALinteraction-
3Forms and ValidationCRITICALforms-
4Typography and ReadabilityHIGHtype-
5Navigation and FeedbackHIGHnav-
6Layout and ResilienceHIGHlayout-
7Performance and Visual StabilityHIGHperf-
8Motion and Theme BehaviorHIGHmotion-
9Content and MicrocopyMEDIUMcopy-

Quick Reference

Read only what is needed for the current audit scope:

  • Category map and impact rationale: rules/_sections.md
  • Rule-level guidance and examples: rules/<prefix>-*.md
  • Full craft sweep: craft-checklist.md
  • Typography deep sweep: typography-checklist.md

Example rule files:

rules/a11y-semantic-html-first.md
rules/forms-inline-errors-first-focus.md
rules/perf-image-dimensions-and-priority.md

Each rule file contains:

  • Why the rule matters
  • Incorrect example
  • Correct example

Review Output Contract

Report findings in this format:

## UI Audit Findings

### path/to/file.tsx
- [CRITICAL] `a11y-icon-controls-labeled`: Icon button is missing an accessible name.
  - Fix: Add `aria-label="Close dialog"` (or visible text label).

### path/to/clean-file.tsx
- ✓ pass
  • Group findings by file.
  • Use file:line when line numbers are available.
  • State issue and propose a concrete fix.
  • Include clean files as ✓ pass.

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

Security

audit-ui

No summary provided by upstream source.

Repository SourceNeeds Review
-114
mblode
Security

audit-typography

No summary provided by upstream source.

Repository SourceNeeds Review
Security

typography-audit

No summary provided by upstream source.

Repository SourceNeeds Review