home / skills / steveclarke / dotfiles / i-audit

i-audit skill

/ai/skills/i-audit

This skill performs a comprehensive interface audit across accessibility, performance, theming, and responsive design, delivering prioritized issues and

npx playbooks add skill steveclarke/dotfiles --skill i-audit

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
6.2 KB
---
name: i-audit
description: Perform comprehensive audit of interface quality across accessibility, performance, theming, and responsive design. Generates detailed report of issues with severity ratings and recommendations.
user-invokable: true
args:
  - name: area
    description: The feature or area to audit (optional)
    required: 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 i-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. **Anti-Patterns (CRITICAL)** - Check against ALL the **DON'T** guidelines in the i-frontend-design skill. Look for AI slop tells (AI color palette, gradient text, glassmorphism, hero metrics, card grids, generic fonts) and general design anti-patterns (gray on color, nested cards, bounce easing, redundant copy).

**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:

### Anti-Patterns Verdict
**Start here.** Pass/fail: Does this look AI-generated? List specific tells from the skill's Anti-Patterns section. Be brutally honest.

### 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 (prefer: /i-extract, /i-distill, /i-arrange, /i-harden, /i-clarify, /i-critique, /i-delight, /i-onboard, /i-colorize, /i-animate, /i-audit, /i-quieter, /i-bolder, /i-typeset, /i-polish, /i-normalize, /i-overdrive, /i-adapt, /i-optimize — or other installed skills you're sure exist)

#### 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 available commands. Prefer these: /i-extract, /i-distill, /i-arrange, /i-harden, /i-clarify, /i-critique, /i-delight, /i-onboard, /i-colorize, /i-animate, /i-audit, /i-quieter, /i-bolder, /i-typeset, /i-polish, /i-normalize, /i-overdrive, /i-adapt, /i-optimize. You may also suggest other installed skills you're sure exist, but never invent commands.

Examples:
- "Use `/i-normalize` to align with design system (addresses N theming issues)"
- "Use `/i-optimize` to improve performance (addresses N performance issues)"
- "Use `/i-harden` to improve resilience (addresses N 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.

Overview

This skill performs a systematic, comprehensive audit of interface quality across accessibility, performance, theming, and responsive design. It produces a prioritized report of issues with clear severity ratings and actionable recommendations. The audit documents problems and suggests specific follow-up commands; it does not modify code.

How this skill works

The tool runs diagnostic scans across five dimensions: Accessibility, Performance, Theming, Responsive Design, and Anti-Patterns (referencing frontend design DON'Ts). It detects concrete failures (contrast ratios, missing ARIA, layout thrashing, hard-coded colors, touch-target sizes, etc.), assigns severity, explains user impact, and links each finding to a recommended fix command. The output is a structured report including an anti-patterns verdict, executive summary, detailed findings by severity, systemic patterns, positive findings, prioritized recommendations, and suggested commands to remediate.

When to use it

  • Before a release to catch accessibility or responsive regressions
  • When onboarding a new design system or auditing a legacy UI
  • As part of a performance sprint to identify render and bundle issues
  • When evaluating theme/dark-mode readiness
  • During design reviews to detect AI-generated or anti-pattern visuals

Best practices

  • Run the audit early and often; prioritize critical accessibility fixes first
  • Map recurring issues to tokenization and componentization to avoid repeats
  • Use the suggested command mappings to group fixes: theming, performance, or accessibility
  • Include code locations and reproduction steps in findings to reduce verification time
  • Limit noise by elevating only verified failures and consolidating duplicates

Example use cases

  • Generate a sprint backlog of accessibility and performance fixes with severity and owner suggestions
  • Audit a mobile-first redesign to surface touch-target, breakpoint, and horizontal-scroll issues
  • Review a component library for hard-coded colors and inconsistent tokens before theming work
  • Assess a marketing site for AI-style anti-patterns (gradient text, generic fonts) before launch

FAQ

Does the audit change code automatically?

No. The skill documents issues and recommends commands or steps but does not modify files.

Which commands will it recommend to fix issues?

It maps issues to available commands such as /i-normalize, /i-optimize, /i-harden, /i-colorize, /i-animate, /i-arrange, and /i-clarify based on the issue type.