audit

Audit front-end features for accessibility, performance, theming, responsive design, and anti-patterns.

5|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/Gyanano/Bower --skill audit-gyanano
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: audit
Source: https://github.com/Gyanano/Bower/tree/main/.agents/skills/audit
Command: npx skills add https://github.com/Gyanano/Bower --skill audit-gyanano

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill streamlines launch readiness by scoring accessibility, performance, theming, responsive design, and anti-pattern risks so teams can document verifiable technical gaps before deploying, and it enforces the frontend-design context gathering protocol (or /teach-impeccable when no prior context exists).

Core Features & Use Cases

  • Structured Diagnostic Scan rates every dimension on a 0-4 scale, highlighting contrast, ARIA, keyboard, performance, theming, responsiveness, and AI-antipattern compliance.
  • Severity-Based Reporting tags findings as P0-P3 with detailed location, impact, WCAG references, and command recommendations, keeping the audit focused on documentation instead of fixing.
  • Follow-Up Command Suggestions map specific problems to follow-up tasks such as /harden, /colorize, or /polish so teams know the next step.
  • Use Case: Run this skill on the Archive page or a new component before release to capture accessibility, performance, theming, responsive, and anti-pattern findings in a scored report.

Quick Start

Ask the audit skill to assess the Archive page, scoring accessibility, performance, theming, responsiveness, and anti-pattern exposure for a launch readiness report.

Frequently Asked Questions about audit

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

FAQPage Schema
How do I run a frontend audit for accessibility and performance before launch?▼

Run a frontend audit by scanning pages or components across accessibility, performance, theming, responsive design, and anti-patterns. The process generates a scored report with P0-P3 severity findings and recommends follow-up commands to document verifiable technical gaps before deploying.

What is a technical UI quality audit and what does it check?▼

A technical UI quality audit evaluates front-end features against WCAG guidelines and optimized delivery standards. It checks accessibility, performance, theming, responsive design, and anti-pattern exposure, producing a scored diagnostic report that highlights critical findings without attempting fixes.

How do I document WCAG compliance gaps in a frontend component?▼

Document WCAG compliance gaps by running a structured diagnostic scan that tags findings with P0-P3 severity, detailed location, impact, and WCAG references. This severity-based reporting keeps the audit focused on documentation and maps specific problems to follow-up command recommendations.

Can I use this audit to check responsive design and theming risks?▼

Yes, you can use this audit to validate responsive design and theming risks. It rates every dimension on a 0-4 scale, specifically highlighting contrast, theming, responsiveness, and AI-antipattern compliance alongside accessibility and performance checks.

Does the audit skill automatically fix accessibility and performance issues?▼

No, the audit skill does not attempt fixes. It strictly documents verifiable technical gaps by producing scored reports with severity tags and recommending follow-up commands like /harden, /colorize, or /polish so teams know the exact next step to resolve issues.

What's the best way to capture anti-pattern exposure in a new component?▼

The best way to capture anti-pattern exposure is applying a structured diagnostic scan before release. This evaluates AI-antipattern compliance on a 0-4 scale, tags findings with P0-P3 severity, and maps specific problems to follow-up tasks for launch readiness reporting.