audit

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams shipping frontend interfaces often lack a systematic way to catch accessibility violations, performance regressions, theming inconsistencies, and responsive design failures before users do. This Skill runs a structured diagnostic scan and produces a prioritized audit report instead of ad-hoc fixes. ## Core Features & Use Cases - Multi-Dimensional Diagnostic Scan: Checks accessibility (contrast, ARIA, keyboard navigation, semantic HTML), performance (layout thrashing, expensive animations, bundle size), theming (hard-coded colors, 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 against the frontend-design skill's guidelines. - Severity-Rated Report Generation: Produces an executive summary, findings grouped by Critical/High/Medium/Low severity with WCAG references, systemic pattern analysis, and a prioritized remediation plan mapped to fix commands. - Use Case: Before a product launch, run the audit on your checkout flow to receive a report listing a missing focus indicator on the payment button (Critical, WCAG A), hard-coded hex colors in 15 components (High), and touch targets under 44px on mobile (Medium), each with a recommended fix command. ## Quick Start Ask the assistant to audit the checkout page for accessibility, performance, theming, and responsive design issues and generate a severity-rated 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 skill against the target feature or page. It checks contrast ratios below 4.5:1, missing ARIA roles and labels, keyboard navigation problems, heading hierarchy, alt text, and form labeling, then reports each finding with its WCAG standard and severity.

What does a frontend quality audit report include?▼

The report contains an anti-patterns verdict, an executive summary with issue counts by severity, detailed findings grouped as Critical, High, Medium, and Low, systemic pattern analysis, positive findings, and a prioritized remediation plan mapped to suggested fix commands.

Can the audit skill fix the issues it finds?▼

No, the audit only documents issues with impact explanations and recommendations. It deliberately avoids fixing anything and instead maps each finding to a follow-up command such as /normalize, /optimize, or /harden that performs the actual remediation.

Does the audit check responsive design and mobile usability?▼

Yes, it checks for fixed widths that break on mobile, touch targets smaller than 44x44 pixels, horizontal overflow on narrow viewports, text scaling failures, and missing mobile or tablet breakpoints.

What performance problems does a frontend audit detect?▼

It detects layout thrashing from reading and writing layout properties in loops, animations on layout properties instead of transform and opacity, missing lazy loading, unoptimized assets, unnecessary imports, and missing memoization causing extra re-renders.