audit

Run a technical quality audit by targeting specific pages or components to score accessibility, performance, theming, and responsive design. The audit generates a prioritized P0–P3 issue report with locations, impacts, standards guidance, and recommended remediation commands.

Detecting UI anti-patterns and AI-slop requires a technical quality audit that flags common implementation issues. This process scores your codebase against key UX dimensions and outputs a severity-tagged report to ensure the interface remains intentional and maintainable.

You cannot automatically fix responsive design and theming issues during a technical audit. The audit generates a prioritized P0–P3 report detailing impacts, standards references, and recommended remediation commands without performing any auto-fixing.

Yes, the technical quality audit requires context preparation via the /impeccable command before scoring your codebase. Once prepared, it evaluates accessibility, performance, theming, responsive design, and anti-patterns to document measurable technical issues.

Your technical audit report includes P0 through P3 severity ratings to help you prioritize what to fix next across accessibility, performance, theming, and responsive design. The actionable issue list pairs each rating with specific impacts and standards guidance.

You need a technical quality audit when reviewing pages, features, or components in a codebase prior to release or after UI and system changes. It scores accessibility, performance, theming consistency, and responsive behavior to highlight concrete problems.