audit
by pbakausRun technical quality checks across accessibility, performance, theming, responsive design, and anti-patterns. Generates a scored report with P0-P3 severity ratings and actionable plan. Use when the user wants an accessibility check, performance audit, or technical quality review.
Overview
What is the audit Skill?
audit is a specialized tool for running systematic technical quality checks on frontend codebases. It focuses on five key areas: accessibility, performance, theming, responsive design, and anti-patterns. The skill generates a scored report with severity ratings (P0–P3) and provides an actionable plan for remediation. This makes it ideal for teams aiming to ensure high standards in web accessibility, performance optimization, and overall frontend quality.
Who Should Use audit?
audit is designed for frontend developers, UI/UX designers, and technical leads who need to assess and document the quality of web interfaces. It is especially useful when you want a clear, objective audit of code-level issues before starting remediation or deeper design reviews.
Problems Solved
- Identifies accessibility gaps (e.g., contrast, ARIA, keyboard navigation)
- Flags performance bottlenecks
- Checks for theming consistency
- Assesses responsive design implementation
- Detects common frontend anti-patterns
How to Use
Installation Steps
-
Install the audit skill:
Use the following command to add the skill to your project:npx skills add https://github.com/pbakaus/impeccable --skill audit -
Review Key Files:
- Start with
SKILL.mdfor a full skill overview and usage notes. - Check
README.md,AGENTS.md, andmetadata.jsonfor supporting documentation. - Explore the
rules/,resources/,references/, andscripts/folders for additional context and helper scripts.
- Start with
Running an Audit
- Preparation:
- Invoke
/frontend-designfirst to gather design context and ensure anti-patterns and principles are loaded. - If no design context exists, run
/teach-impeccableas instructed in the skill documentation.
- Invoke
- Audit Execution:
- Run the audit skill with the relevant argument (e.g., feature, page, or component name).
- The skill will scan the codebase and output a JSON report with scores and severity levels for each dimension.
- Next Steps:
- Use the generated report to prioritize fixes. The audit skill documents issues but does not automatically resolve them.
When to Use audit
- Before major releases or code reviews
- When onboarding new projects or teams
- As part of continuous integration for frontend quality assurance
FAQ
What does the audit skill check?
The audit skill systematically reviews accessibility, performance, theming, responsive design, and anti-patterns in your frontend code. It outputs a scored report with severity ratings and actionable recommendations.
Does audit fix issues automatically?
No, audit identifies and documents technical issues but does not apply fixes. Use the report to guide remediation with other tools or manual updates.
Is audit suitable for design critiques?
No, audit focuses on code-level, measurable aspects of frontend quality. For design critiques, use complementary skills or workflows.
Where can I find more details?
Open the Files tab in the repository to explore all supporting documentation, including nested references and helper scripts. Start with SKILL.md for the most relevant guidance.
