ui-auditor

Purpose

Audit a UI implementation (code, screenshot, or both) for visual consistency and design quality — spacing, alignment, hierarchy, and adherence to the project's existing design patterns.

When to Use

• After implementing or changing a UI, before it ships.
• Reviewing a screen/component that feels "off" but it's unclear why.
• Comparing a new UI against the rest of the app for consistency.

For narrower, deeper dives, pair with Responsive Checker, Accessibility Auditor, Design System Guardian, or UI Text Formatter — this skill covers general visual quality across all of those areas at a lighter level.

What to Analyze

1. Spacing & alignment — inconsistent gaps, misaligned elements, uneven padding between visually-similar components.
2. Visual hierarchy — is the most important element actually the most prominent? Does heading/body/caption sizing create clear scan order?
3. Consistency with the rest of the app — does this screen reuse existing components/patterns, or does it quietly reinvent a button/card/input style that already exists elsewhere?
4. Color & contrast usage — colors used with clear purpose (not decoratively inconsistent), sufficient contrast for readability.
5. State coverage — does the UI account for empty, loading, error, and populated states, not just the "happy path" screenshot?
6. Density & whitespace — is the layout too cramped or too sparse relative to the content's importance and the rest of the app's density?

Output Format

• Findings grouped by area (Spacing, Hierarchy, Consistency, Color/Contrast, State Coverage).
• Each finding: what's inconsistent/wrong, where (component/screen), and a concrete fix (exact spacing value, which existing component to reuse, etc.).
• Flag anything that's a design-system violation specifically, and note that Design System Guardian can do a deeper token-level pass if useful.