audit

Audit web frontends for accessibility, performance, theming, and responsive issues.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill identifies and documents quality issues across accessibility, performance, theming, and responsive design so teams can prioritize meaningful fixes without guessing where to start.

Core Features & Use Cases

  • Multi-dimensional diagnostic scans that surface contrast, ARIA, keyboard, semantic HTML, performance, theming, and responsive issues with severity ratings.
  • Actionable, prioritized reports that include location, impact, WCAG/standard references, and recommended remediation commands mapped to existing skills.
  • Use Case: Run a pre-release audit on a checkout flow to identify critical accessibility violations, performance regressions, and theme inconsistencies and produce a sprint-ready remediation plan.

Quick Start

Audit the checkout page for accessibility, performance, theming, and responsive issues and return a prioritized report with locations, severities, impacts, and recommended remediation commands.

Frequently Asked Questions about audit

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

FAQPage Schema
How do I run a comprehensive UI audit for accessibility and performance issues?

Run a comprehensive UI audit by scanning web frontends, pages, or components to identify accessibility, performance, theming, and responsive design issues. The audit produces a prioritized, severity-rated report with locations, impacts, and recommended remediation commands.

Can I check WCAG compliance and keyboard accessibility for a specific page before release?

Yes, you can check WCAG compliance and keyboard accessibility by applying the audit to specific pages or components during release checks. It surfaces contrast, ARIA, semantic HTML, and keyboard issues with severity ratings and WCAG standard references.

Does the UI audit provide actionable remediation steps or just a list of problems?

The UI audit provides actionable remediation steps, not just a list of problems. It generates a sprint-ready, prioritized report that includes issue locations, impact explanations, WCAG standard references, and recommended remediation commands mapped to existing skills.

What's the best way to identify responsive design and theming inconsistencies in a checkout flow?

The best way to identify responsive design and theming inconsistencies is to run a multi-dimensional diagnostic scan on the checkout flow. The scan surfaces these issues with severity ratings, allowing teams to prioritize meaningful fixes without guessing where to start.

When do I need to perform an accessibility and performance audit on my web frontend?

You need to perform an accessibility and performance audit during pre-release checks, accessibility compliance reviews, or design critiques. It identifies critical violations, performance regressions, and theme inconsistencies to produce a sprint-ready remediation plan.

Will this audit detect ARIA misuse and semantic HTML structural problems?

Yes, the audit will detect ARIA misuse and semantic HTML structural problems. It performs multi-dimensional diagnostic scans that specifically surface contrast, ARIA, keyboard, and semantic HTML issues alongside performance and responsive design flaws.