Superior UI Audit

Audit one coherent product surface against the system that actually governs it. Prefer a small set of well-proven findings to a long list of stylistic opinions.

Boundaries

• Treat product source as read-only.
• Do not install dependencies, format files, or modify generated artifacts while auditing.
• Render or interact with the UI only when requested or when available read-only tooling makes it necessary to prove a visual claim.
• Keep functional bugs, accessibility defects, performance issues, and code quality outside the report unless the user includes them in scope.
• If the user asks to fix the UI, this audit skill does not override that request; use the implementation workflow instead.

Trace the surface

Start from the route, screen, component family, or user journey in scope. Follow the actual path through layouts, compositions, components, variants, tokens, and resolved styles. Similar names and nearby files are candidates, not proof that an owner affects the surface.

Record the surface, relevant owners, design sources, explicit exceptions, and the current revision when available.

Reconstruct the local contract