audit

Runs technical quality checks across accessibility, performance, theming, and responsive design with scored reports.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Frontend codebases accumulate accessibility violations, performance regressions, hard-coded colors, and AI-generated design tells that are hard to spot manually. This Skill systematically audits code across five measurable dimensions and produces a prioritized report instead of vague impressions. ## Core Features & Use Cases - Five-Dimension Diagnostic Scan: Scores accessibility, performance, theming, responsive design, and anti-patterns each from 0-4 with explicit criteria, producing a total health score out of 20. - Severity-Tagged Findings: Documents every issue with P0-P3 severity, exact file and line location, user impact, violated WCAG standard, and a concrete fix recommendation. - Anti-Pattern Detection: Flags AI slop tells such as gradient text, glassmorphism, generic fonts, and nested cards, plus systemic issues like hard-coded colors repeated across components. - Use Case: Before shipping a new landing page, run the audit to get a scored report listing a P1 contrast violation in the hero, missing ARIA labels on the nav, and touch targets under 44px on mobile, each mapped to a follow-up fix command. ## Quick Start Ask the assistant to run an audit on a specific page or component, for example: audit the checkout page for accessibility, performance, and responsive issues.

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 against the target page or component to check contrast ratios below 4.5:1, missing ARIA roles and labels, keyboard navigation gaps, heading hierarchy, and form labeling. Each finding is tagged with severity and the specific WCAG criterion it violates.

What does a frontend technical quality audit check?

It checks five dimensions: accessibility, performance, theming, responsive design, and anti-patterns. Each dimension is scored 0-4 against explicit criteria, producing a total health score out of 20 with a rating band from Critical to Excellent.

Does the audit fix the issues it finds?

No, the audit only documents issues with severity, location, impact, and a recommended fix command. Remediation is delegated to follow-up commands such as /optimize, /normalize, or /polish, and you re-run the audit afterward to verify score improvement.

How are audit findings prioritized by severity?

Findings use four levels: P0 blocking issues that prevent task completion, P1 major issues including WCAG AA violations, P2 minor annoyances with workarounds, and P3 polish items. Recommended actions are ordered P0 first so critical fixes ship before cosmetic ones.

What AI design anti-patterns does the audit detect?

It flags common AI-generated design tells including gradient text, glassmorphism, hero metric sections, generic card grids, gray text on colored backgrounds, nested cards, and bounce easing. Three or more tells indicate a heavy AI aesthetic that needs design revision.