Tool: technical audit (impeccable audit)
What it does
- Technical checks on a built interface: accessibility, performance, theming, responsiveness, and whether the code holds together.
- It lists issues for other commands to fix. It doesn't fix them itself.
When to reach for it
- Before release.
- You want a ranked list of faults rather than design opinions.
- impeccable routes many quality or contrast hits from the rule checker here.
How to use it
- Run
/impeccable audit <target>.
- Use it often?
/impeccable pin audit gives you /audit as its own shortcut.
- Scoring: five areas, 0 to 4 each, out of 20. Implementation integrity is marked critical. Bands: 18 to 20 Excellent, 14 to 17 Good, 10 to 13 Acceptable, 6 to 9 Poor, 0 to 5 Critical.
- Every finding gets a severity from P0 (blocking) to P3 (polish). Unsure? Would a user contact support about it? Then it's at least P1.
- It keeps P3s few and checks every finding before reporting it.
- It checks contrast, ARIA, keyboard traps, heading order, alt text and form labels.
- It flags a global "0.01ms" reduced-motion switch-off, and
will-change left on.
- For desktop apps (Electron and similar): open a DevTools port on 127.0.0.1, never exposed, and run
impeccable detect --cdp 9222 --target <url or title> --json.
- The source's form is
/impeccable <command> <target>, typed in your agent ($impeccable on Codex). Narrow targets get better results: one section beats a whole page.
What happened when we used it
- We ran its audit by hand, scoring against its rubric without installing it or running its checker.
- The page scored 2 out of 4 on accessibility and anti-patterns. Faint grey labels at about 2.5 to 1 contrast were raised to about 5.2 to 1, and fade-ins got a fallback so content can't stay hidden.
- It flagged about 14 MB of images as the main speed problem.
Source