pbakaus_impeccable/source/commands/audit.md

name, description, context, args

name	description	context	args
audit	Perform comprehensive audit of interface quality across accessibility, performance, theming, and responsive design. Generates detailed report of issues with severity ratings and recommendations.	fork	name description required area The feature or area to audit (optional) false

Run systematic quality checks and generate a comprehensive audit report with prioritized issues and actionable recommendations. Don't fix issues - document them for other commands to address.

First: Use the frontend-design skill for design principles and anti-patterns.

Diagnostic Scan

Run comprehensive checks across multiple dimensions:

1. Accessibility (A11y) - Check for:

   • Contrast issues: Text contrast ratios < 4.5:1 (or 7:1 for AAA)
   • Missing ARIA: Interactive elements without proper roles, labels, or states
   • Keyboard navigation: Missing focus indicators, illogical tab order, keyboard traps
   • Semantic HTML: Improper heading hierarchy, missing landmarks, divs instead of buttons
   • Alt text: Missing or poor image descriptions
   • Form issues: Inputs without labels, poor error messaging, missing required indicators

2. Performance - Check for:

   • Layout thrashing: Reading/writing layout properties in loops
   • Expensive animations: Animating layout properties (width, height, top, left) instead of transform/opacity
   • Missing optimization: Images without lazy loading, unoptimized assets, missing will-change
   • Bundle size: Unnecessary imports, unused dependencies
   • Render performance: Unnecessary re-renders, missing memoization

3. Theming - Check for:

   • Hard-coded colors: Colors not using design tokens
   • Broken dark mode: Missing dark mode variants, poor contrast in dark theme
   • Inconsistent tokens: Using wrong tokens, mixing token types
   • Theme switching issues: Values that don't update on theme change

4. Responsive Design - Check for:

   • Fixed widths: Hard-coded widths that break on mobile
   • Touch targets: Interactive elements < 44x44px
   • Horizontal scroll: Content overflow on narrow viewports
   • Text scaling: Layouts that break when text size increases
   • Missing breakpoints: No mobile/tablet variants

5. Design Anti-Patterns - Check for:

   • Pure gray/black: Using #000, #808080, or untinted grays (should have subtle color tint)
   • Gray on color: Gray text on colored backgrounds (looks washed out—use a shade of the background color instead)
   • Nested cards: Cards inside cards (visual noise, flatten hierarchy)
   • Bounce/elastic easing: Dated animation curves (use ease-out-quart/quint/expo instead)
   • Redundant copy: Headers restating intros, repeated explanations
   • Placeholder as label: Using placeholder text as the only field label
   • Generic fonts: Defaulting to Inter/Roboto/Arial without intentional choice

6. AI Slop Detection (CRITICAL) - Does this look AI-generated? Check for:

   • AI color palette: Cyan-on-dark, purple-to-blue gradients, neon accents on dark backgrounds
   • Gradient text: Especially on metrics or headings—decorative rather than meaningful
   • Default dark mode with glowing accents: "Cool" without requiring design decisions
   • Monospace typography: Lazy shorthand for "technical/developer" vibes
   • Glassmorphism everywhere: Blur effects, glass cards, glow borders used decoratively
   • Hero metric layout: Big number, small label, supporting stats, gradient accent—it's a template
   • Sparklines as decoration: Tiny charts that look sophisticated but convey nothing
   • Identical card grids: Same-sized cards with icon + heading + text, repeated
   • Purple-to-blue gradients on white: The #1 "AI marketing site" tell
   • Rounded rectangles with generic shadows: Safe, forgettable, could be any AI output

CRITICAL: This is an audit, not a fix. Document issues thoroughly with clear explanations of impact. Use other commands (normalize, optimize, harden, etc.) to fix issues after audit.

Generate Comprehensive Report

Create a detailed audit report with the following structure:

AI Slop Verdict

Start here. Pass/fail: Does this look AI-generated? List specific tells if yes. Be brutally honest—this is the most important quality signal.

Executive Summary

• Total issues found (count by severity)
• Most critical issues (top 3-5)
• Overall quality score (if applicable)
• Recommended next steps

Detailed Findings by Severity

For each issue, document:

• Location: Where the issue occurs (component, file, line)
• Severity: Critical / High / Medium / Low
• Category: Accessibility / Performance / Theming / Responsive
• Description: What the issue is
• Impact: How it affects users
• WCAG/Standard: Which standard it violates (if applicable)
• Recommendation: How to fix it
• Suggested command: Which command to use (e.g., /normalize, /optimize, /harden)

Critical Issues

[Issues that block core functionality or violate WCAG A]

High-Severity Issues

[Significant usability/accessibility impact, WCAG AA violations]

Medium-Severity Issues

[Quality issues, WCAG AAA violations, performance concerns]

Low-Severity Issues

[Minor inconsistencies, optimization opportunities]

Patterns & Systemic Issues

Identify recurring problems:

• "Hard-coded colors appear in 15+ components, should use design tokens"
• "Touch targets consistently too small (<44px) throughout mobile experience"
• "Missing focus indicators on all custom interactive components"

Positive Findings

Note what's working well:

• Good practices to maintain
• Exemplary implementations to replicate elsewhere

Recommendations by Priority

Create actionable plan:

1. Immediate: Critical blockers to fix first
2. Short-term: High-severity issues (this sprint)
3. Medium-term: Quality improvements (next sprint)
4. Long-term: Nice-to-haves and optimizations

Suggested Commands for Fixes

Map issues to appropriate commands:

• "Use /normalize to align components with design system (addresses 23 theming issues)"
• "Use /optimize to improve performance (addresses 12 performance issues)"
• "Use /harden to improve i18n and text handling (addresses 8 edge cases)"

IMPORTANT: Be thorough but actionable. Too many low-priority issues creates noise. Focus on what actually matters.

NEVER:

• Report issues without explaining impact (why does this matter?)
• Mix severity levels inconsistently
• Skip positive findings (celebrate what works)
• Provide generic recommendations (be specific and actionable)
• Forget to prioritize (everything can't be critical)
• Report false positives without verification

Remember: You're a quality auditor with exceptional attention to detail. Document systematically, prioritize ruthlessly, and provide clear paths to improvement. A good audit makes fixing easy.