audit

Overview

What is the audit skill?

The audit skill is designed for frontend developers and teams who need to systematically assess the technical quality of their codebase. It checks for accessibility (A11y), performance, theming consistency, responsive design, and common anti-patterns. The skill produces a scored report with severity ratings (P0-P3) and actionable plans, helping you prioritize improvements and maintain high standards.

Who should use audit?

• Frontend engineers seeking to validate code quality
• QA teams focusing on accessibility and performance
• Project leads preparing for compliance or launch
• Anyone needing a structured, code-level audit (not a design critique)

Problems solved

• Identifies accessibility gaps (contrast, ARIA, keyboard navigation, semantic HTML, alt text, forms)
• Flags performance bottlenecks
• Highlights theming and responsive design issues
• Detects anti-patterns and technical debt
• Provides clear severity ratings and next steps

How to Use

Installation steps

1. Install the audit skill using:

   npx skills add https://github.com/pbakaus/impeccable --skill audit
   

2. Review the SKILL.md file for detailed instructions and scoring criteria.

Preparation

• Before running audit, invoke /frontend-design to gather design context and anti-patterns. If no design context exists, run /teach-impeccable first.
• The audit skill focuses on measurable technical aspects; it does not fix issues but documents them for follow-up.

Running the audit

• Use the skill to scan your frontend codebase. It checks five key dimensions:
  • Accessibility (A11y)
  • Performance
  • Theming
  • Responsive design
  • Anti-patterns
• Each dimension is scored from 0 (critical issues) to 4 (excellent compliance).
• The output is a comprehensive report with severity ratings (P0-P3) and actionable recommendations.

File structure and review

• Start with SKILL.md for workflow and scoring details.
• Explore supporting files such as README.md, AGENTS.md, metadata.json, and folders like rules/, resources/, references/, or scripts/ for additional context.

FAQ

Is audit suitable for design reviews?

No. The audit skill performs code-level technical checks. For design critiques, use /frontend-design or related skills.

What does the audit report include?

The report covers accessibility, performance, theming, responsive design, and anti-patterns, each scored and prioritized by severity.

Can audit fix issues automatically?

No. Audit documents issues and provides actionable plans. Use other skills or manual fixes to address findings.

Where can I find scoring criteria?

Scoring details and checklists are in SKILL.md. Open the Files tab for the full file tree and helper scripts.

When should I use audit?

Use audit before launches, compliance checks, or as part of regular code quality reviews to ensure your frontend meets technical standards.