audit

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

Updated Apr 16, 2026
One-click install
npx skills add https://github.com/IkeaNorweegway/Classroom-Tools --skill audit-ikeanorweegway
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit
Source: https://github.com/IkeaNorweegway/Classroom-Tools/tree/main/.claude/skills/audit
Command: npx skills add https://github.com/IkeaNorweegway/Classroom-Tools --skill audit-ikeanorweegway

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Frontend code often ships with hidden accessibility violations, performance bottlenecks, hard-coded colors, and AI-generated design tells that are hard to catch manually. This Skill systematically audits code across five quality dimensions and produces a prioritized, actionable report instead of vague feedback. ## Core Features & Use Cases - Five-Dimension Diagnostic Scan: Scores accessibility, performance, theming, responsive design, and anti-patterns each from 0-4, producing a total Audit Health Score out of 20 with rating bands. - Severity-Tagged Findings: Documents every issue with P0-P3 severity, exact file/line location, user impact, violated WCAG standards, and concrete fix recommendations. - AI Slop Detection: Specifically flags AI-generated design tells like gradient text, glassmorphism, generic fonts, and card grids. - Use Case: Before releasing a new landing page, run the audit to discover missing ARIA labels, hard-coded hex colors breaking dark mode, and touch targets under 44px, then follow the recommended fix commands in priority order. ## Quick Start Ask the AI to run an audit on a specific feature, page, or component to get a scored technical quality report with prioritized fixes.

Frequently Asked Questions about audit

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

FAQPage Schema
How do I audit frontend code for accessibility issues?

Run the audit on a feature, page, or component to check contrast ratios below 4.5:1, missing ARIA roles and labels, keyboard navigation gaps, semantic HTML problems, and form labeling issues. Each finding is tagged with severity and the WCAG standard it violates.

What does a frontend technical quality audit check?

It checks five dimensions: accessibility (WCAG compliance), performance (layout thrashing, expensive animations, lazy loading), theming (design tokens, dark mode), responsive design (touch targets, breakpoints, overflow), and anti-patterns including AI-generated design tells.

How is the audit health score calculated?

Each of the five dimensions is scored 0-4 based on defined criteria, totaling 20 points. Rating bands range from Excellent (18-20) down to Critical (0-5), with each band indicating how much remediation work is needed.

Does the audit fix the issues it finds?

No, the audit only documents issues without modifying code. It recommends specific follow-up commands mapped to each finding, ordered by P0-P3 priority, so other tools handle the actual fixes.

What are P0 to P3 severity levels in code audits?

P0 issues block task completion and need immediate fixes, P1 issues cause significant difficulty or WCAG AA violations, P2 issues are annoyances with workarounds, and P3 issues are polish items with no real user impact.