audit

An accessibility and performance audit systematically checks your UI code for WCAG compliance, rendering bottlenecks, and responsive design flaws. The audit produces a scored report with 0-4 ratings, P0-P3 severity findings, and targeted remediation recommendations to fix defects before release.

Checking for AI-generated design anti-patterns requires a systematic technical audit of your components. The audit identifies implementation-level defects, assigns P0-P3 severity tags to each anti-pattern, and outputs targeted remediation recommendations mapped to fix commands.

Scoring your codebase for theming and responsive design involves running a technical audit during your code review or QA pass. The audit generates per-dimension 0-4 scores, a combined Health Score, and a rating band to quantify your implementation quality.

You can automate technical quality checks for pre-release component QA by running a systematic audit. The audit catches blocking accessibility problems, performance regressions, and theming gaps, producing a concise executive summary with prioritized findings to ensure pre-release stability.

The technical audit does not modify your source code when finding defects. It performs read-only systematic checks across accessibility, performance, theming, and anti-patterns, generating a scored report with remediation recommendations mapped to fix commands without altering your implementation.

You should include design context when running a code-level technical audit by running the /impeccable command first. Providing design context ensures the audit accurately identifies theming gaps, responsive design flaws, and anti-patterns against your intended UI implementation.