audit

Audits interface quality across accessibility, performance, theming, and responsive design with severity-rated reports.

1|Updated Oct 20, 2024
One-click install
npx skills add https://github.com/SteveChandler/quiver --skill audit-stevechandler
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: audit
Source: https://github.com/SteveChandler/quiver/tree/main/.agents/skills/audit
Command: npx skills add https://github.com/SteveChandler/quiver --skill audit-stevechandler

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Interface quality issues like poor contrast, missing ARIA labels, hard-coded colors, and broken mobile layouts are easy to miss during development. This Skill systematically scans a frontend codebase across four quality dimensions and produces a prioritized, actionable audit report instead of vague impressions. ## Core Features & Use Cases - Multi-Dimensional Diagnostic Scan: Checks accessibility (WCAG contrast, ARIA, keyboard navigation, semantic HTML), performance (layout thrashing, expensive animations, bundle size), theming (design tokens, dark mode), and responsive design (touch targets, breakpoints, overflow). - Anti-Pattern Detection: Flags generic AI-generated design tells such as gradient text, glassmorphism, nested cards, and repetitive card grids. - Severity-Rated Report Generation: Produces a structured report with an executive summary, issues grouped by Critical/High/Medium/Low severity, systemic patterns, positive findings, and fix recommendations mapped to follow-up commands. - Use Case: Before shipping a new dashboard page, run an audit to receive a prioritized list of WCAG violations, performance bottlenecks, and theming inconsistencies, each mapped to a suggested remediation command. ## Quick Start Ask the assistant to audit the interface quality of a specific page or component and generate a severity-rated report with recommendations.

Frequently Asked Questions about audit

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

FAQPage Schema
How do I audit a web page for accessibility issues?▼

Run the audit to scan for WCAG violations including contrast ratios below 4.5:1, missing ARIA roles and labels, keyboard navigation problems, improper heading hierarchy, and missing alt text. Each finding includes severity, user impact, and a fix recommendation.

What does a frontend quality audit check?▼

The audit covers four dimensions: accessibility (WCAG standards), performance (layout thrashing, expensive animations, bundle size), theming (hard-coded colors, dark mode issues), and responsive design (touch targets under 44px, horizontal overflow, missing breakpoints).

Does the audit fix the issues it finds?▼

No, the audit only documents issues with severity ratings and recommendations. It deliberately avoids fixing anything, instead mapping each issue to a suggested follow-up command such as normalize, optimize, or harden for remediation.

How are audit findings prioritized?▼

Findings are grouped into Critical, High, Medium, and Low severity tiers based on user impact and WCAG conformance level. The report also identifies systemic patterns, highlights positive practices, and orders recommendations into immediate, short-term, and long-term actions.

When should I run an interface audit?▼

Run it before shipping new pages, after major design changes, or when preparing for accessibility compliance reviews. It works best as a periodic quality gate rather than a one-time check, since it tracks recurring systemic issues across components.