audit

Audits interfaces for accessibility, performance, theming, and responsive design issues with severity-rated reports.

Updated Mar 24, 2026
One-click install
npx skills add https://github.com/Ssrrb/cerramos-codebase --skill audit-ssrrb
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: audit
Source: https://github.com/Ssrrb/cerramos-codebase/tree/main/.codex/skills/audit
Command: npx skills add https://github.com/Ssrrb/cerramos-codebase --skill audit-ssrrb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Interface quality problems like poor contrast, missing ARIA labels, layout thrashing, and hard-coded colors often go unnoticed until they hurt users. This Skill runs a systematic diagnostic scan across accessibility, performance, theming, and responsive design, then produces a prioritized report so teams know exactly what to fix first. ## Core Features & Use Cases - Multi-Dimensional Diagnostic Scan: Checks accessibility (WCAG contrast, ARIA, keyboard navigation), performance (layout thrashing, expensive animations), theming (design tokens, dark mode), and responsive design (touch targets, breakpoints). - Anti-Pattern Detection: Flags AI-generated design tells such as gradient text, glassmorphism, generic fonts, and nested cards by cross-referencing the frontend-design skill's guidelines. - Severity-Rated Report Generation: Produces a structured audit report with an executive summary, issues grouped by Critical/High/Medium/Low severity, systemic patterns, positive findings, and recommended fix commands. - Use Case: Before shipping a new checkout page, run an audit to catch WCAG AA contrast violations, undersized mobile touch targets, and hard-coded colors, then route each issue to the appropriate fix command like /normalize or /optimize. ## Quick Start Ask the assistant to audit the current interface or a specific area for accessibility, performance, theming, and responsive design issues and generate a prioritized report.

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 interface for accessibility issues?▼

Run the audit to scan for contrast ratios below 4.5:1, missing ARIA roles and labels, broken keyboard navigation, improper heading hierarchy, and form inputs without labels. Each finding includes its WCAG standard, user impact, and a recommended fix command.

What does a frontend quality audit check for?▼

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

Does the audit fix the issues it finds?▼

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

How are audit findings prioritized in the report?▼

Findings are grouped into Critical, High, Medium, and Low severity tiers based on user impact and WCAG level violated. The report also includes an executive summary with the top issues, systemic patterns, and a phased remediation plan from immediate to long-term.

Can the audit detect AI-generated design anti-patterns?▼

Yes, the report starts with an anti-patterns verdict that flags common AI design tells such as gradient text, glassmorphism, hero metrics, card grids, generic fonts, nested cards, and bounce easing, cross-referenced against the frontend-design skill guidelines.