audit

Audit code-level pages and components for accessibility, performance, theming, responsive design, and anti-patterns.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill identifies measurable implementation issues across accessibility, performance, theming, responsive design, and common anti-patterns so teams can prioritize engineering work and reduce release risk. It produces a scored, evidence-backed report with P0-P3 severity ratings and actionable recommendations rather than making code changes.

Core Features & Use Cases

  • Multi-dimension diagnostics: Systematic checks for a11y (contrast, ARIA, keyboard), performance (render, bundle, assets), theming (tokens, dark mode), responsive behavior, and design anti-patterns.
  • Scored output: Per-dimension 0–4 scoring, aggregate health score, and a clear Rating band for release readiness.
  • Triage-ready issues: Issues tagged P0–P3 with location, impact, standards (e.g., WCAG), remediation steps, and suggested follow-up commands.
  • Use Case: Run before a release or PR review to quantify technical debt on a page, component, or feature and create an actionable backlog of fixes.

Quick Start

Run the audit on the landing page component to generate a scored P0–P3 report and prioritized remediation plan.

Frequently Asked Questions about audit

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

FAQPage Schema
How do I run a technical code review for accessibility and performance before a release?▼

Run a technical code review to inspect implementation artifacts across accessibility, performance, theming, and responsive design. This process generates a scored, evidence-backed report with P0–P3 severity ratings and actionable remediation steps to quantify release readiness.

What is the best way to identify and prioritize UI design anti-patterns in my components?▼

Identify UI design anti-patterns by applying systematic multi-dimension diagnostics to your components during development. You get a triage-ready backlog of issues tagged by severity, detailing location, impact, and standards like WCAG for prioritized remediation.

Can I audit responsive design and dark mode theming without automatically modifying my code?▼

Yes, you can audit responsive design and dark mode theming without code modifications. The audit inspects implementation artifacts to evaluate theming tokens and responsive behavior, producing a scored report rather than making direct code changes.

Does a technical quality audit require design context before checking for common anti-patterns?▼

Yes, a technical quality audit requires design context gathered via the impeccable protocol before checking for anti-patterns. This context ensures the systematic checks accurately measure implementation issues against intended design specifications.

How does a scored technical audit report help reduce release risk for web components?▼

A scored technical audit report reduces release risk by providing an aggregate health score and clear rating band for web components. It identifies measurable implementation issues across multiple dimensions, enabling teams to prioritize engineering work effectively.

What limitations exist when auditing accessibility issues like contrast and ARIA implementation?▼

A key limitation when auditing accessibility issues like contrast and ARIA is that the process produces findings and recommended follow-up commands without applying fixes. Teams must manually execute the suggested remediation steps to resolve the identified standards violations.