audit

Audits frontend interfaces for accessibility, performance, theming, and responsive design issues.

Updated Mar 4, 2026
One-click install
npx skills add https://github.com/gmolike/Claude-Template --skill audit-gmolike
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit
Source: https://github.com/gmolike/Claude-Template/tree/main/.agents/skills/audit
Command: npx skills add https://github.com/gmolike/Claude-Template --skill audit-gmolike

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Frontend quality issues like poor contrast, missing ARIA labels, hard-coded colors, and broken mobile layouts often go unnoticed until users complain. This Skill systematically scans your interface code across accessibility, performance, theming, and responsive design dimensions, producing a prioritized report instead of silently fixing things. ## Core Features & Use Cases - Multi-Dimensional Diagnostic Scan: Checks WCAG contrast ratios, ARIA attributes, keyboard navigation, layout thrashing, animation performance, design token usage, dark mode support, touch target sizes, and viewport breakpoints. - Anti-Pattern Detection: Flags AI-generated design tells such as gradient text, glassmorphism, generic fonts, nested cards, and bounce easing against the frontend-design skill guidelines. - Severity-Ranked Report: Generates a structured audit report with Critical/High/Medium/Low findings, impact explanations, WCAG references, and recommended follow-up commands like /normalize or /optimize. - Use Case: Before shipping a new feature, run an audit on your components directory to catch WCAG AA violations and hard-coded colors, then hand off the prioritized findings to fix-focused commands. ## Quick Start Ask the assistant to audit the components in your feature directory for accessibility, performance, theming, and responsive design issues and produce a severity-ranked 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 React component for accessibility issues?

Run the audit against your component directory to check contrast ratios below 4.5:1, missing ARIA roles and labels, keyboard navigation gaps, and improper heading hierarchy. The report lists each issue with its WCAG reference and severity rating.

What does a frontend quality audit check for?

The audit covers four dimensions: accessibility (contrast, ARIA, keyboard navigation), performance (layout thrashing, expensive animations, bundle size), theming (hard-coded colors, dark mode), and responsive design (touch targets, fixed widths, breakpoints).

Does the audit fix the issues it finds?

No, the audit only documents issues with severity ratings, impact explanations, and recommendations. It suggests follow-up commands like /normalize, /optimize, or /harden to actually fix the identified problems.

Can I audit a specific feature instead of the whole app?

Yes, the audit accepts an optional area argument to scope the scan to a specific feature or directory. Omitting the argument runs the comprehensive check across the broader interface codebase.

Why does the audit flag gradient text and glassmorphism?

These are classified as AI-generated design anti-patterns defined in the frontend-design skill guidelines. The audit's Anti-Patterns Verdict section identifies such tells to help interfaces avoid a generic AI-generated appearance.