audit

Audit frontend components and pages with scored P0-P3 severity reports.

5|1|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/Catsofsuffering/CCGS --skill audit-catsofsuffering
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit
Source: https://github.com/Catsofsuffering/CCGS/tree/main/templates/skills/impeccable/audit
Command: npx skills add https://github.com/Catsofsuffering/CCGS --skill audit-catsofsuffering

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a systematic, implementation-focused audit to identify measurable technical quality issues across accessibility, performance, theming, responsive design, and anti-patterns so teams can prioritize fixes with clear severity and remediation guidance.

Core Features & Use Cases

  • Multi-dimension scoring: Scores Accessibility, Performance, Theming, Responsive Design, and Anti-Patterns on a 0–4 scale and aggregates a 0–20 health score with rating bands.
  • Actionable reporting: Produces an executive summary, detailed findings tagged P0–P3 with locations, impact, standards (e.g., WCAG), and explicit remediation recommendations mapped to follow-up commands.
  • Governance & workflow: Enforces mandatory context gathering via frontend-design and teach-impeccable, and recommends a prioritized set of remedial commands to drive iterative fixes and re-audits.
  • Use case: Run this audit on a component library or page prior to release to surface accessibility blockers, performance regressions, theme inconsistencies, and common AI-design anti-patterns.

Quick Start

Run an implementation-level audit of the product page header and components to generate a scored report with P0–P3 findings and recommended fix commands.

Frequently Asked Questions about audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run an accessibility and performance audit on frontend components?

To run a frontend audit on components, the Skill checks accessibility, performance, theming, and responsive design implementation. It outputs a scored report with P0-P3 severity findings and concrete remediation recommendations for identified issues.

What is a frontend technical audit for component libraries?

A frontend technical audit systematically identifies measurable quality issues across accessibility, performance, theming, responsive design, and anti-patterns. It scores each dimension on a 0-4 scale, aggregating a 0-20 health score to help teams prioritize fixes.

Can I use this audit to detect anti-patterns in my frontend codebase?

Yes, you can use this audit to detect common AI-design anti-patterns in your frontend codebase. It evaluates code against established standards, tagging findings with severity classifications and explicit remediation recommendations.

How do I check WCAG compliance and responsive design issues before a release?

Check WCAG compliance and responsive design issues by running an implementation-level audit on your pages or components. It applies measurable checks, produces an executive summary, and outputs prioritized remedial commands to drive iterative fixes.

Does this frontend audit require any external dependencies to run?

No, this frontend audit requires no external dependencies to run. It enforces mandatory context gathering via frontend-design and teach-impeccable workflows, but operates independently to generate scored reports with P0-P3 findings.

What is the best way to prioritize frontend accessibility and performance fixes?

The best way to prioritize frontend fixes is using a scored audit report with P0-P3 severity classifications. This approach maps concrete remediation recommendations to follow-up commands, allowing teams to address critical blockers iteratively.