audit

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

Updated May 4, 2026
One-click install
npx skills add https://github.com/Gito125/gideon_portfolio --skill audit-gito125
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: audit
Source: https://github.com/Gito125/gideon_portfolio/tree/main/.github/skills/audit
Command: npx skills add https://github.com/Gito125/gideon_portfolio --skill audit-gito125

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Frontend codebases accumulate accessibility violations, performance regressions, hard-coded styles, and AI-generated design tells that are hard to spot manually. This Skill systematically audits a feature, page, or component and produces a scored report with prioritized, actionable findings. ## Core Features & Use Cases - Five-Dimension Diagnostic Scan: Scores accessibility, performance, theming, responsive design, and anti-patterns on a 0-4 scale, producing a total health score out of 20 with a rating band. - Severity-Tagged Findings: Documents every issue with P0-P3 severity, exact file and line location, user impact, violated WCAG or design standard, and a concrete fix recommendation. - AI Slop Detection: Flags AI-generated design tells such as gradient text, glassmorphism, generic fonts, and card-grid layouts, with a brutally honest pass/fail verdict. - Use Case: Before shipping a new landing page, run the audit to catch missing ARIA labels, layout-thrashing animations, hard-coded colors bypassing design tokens, and undersized mobile touch targets, then follow the recommended fix commands in priority order. ## Quick Start Ask the assistant to run an audit on a specific page or component, for example: audit the checkout page for accessibility, performance, and responsive issues.

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 page for accessibility issues?▼

Run the audit against the target page or component to check contrast ratios, ARIA roles, keyboard navigation, semantic HTML, alt text, and form labeling. Each finding is tagged with severity, the WCAG standard it violates, and a specific fix recommendation.

What does a frontend technical quality audit check?▼

It checks five dimensions: accessibility, performance, theming, responsive design, and anti-patterns. Each dimension is scored 0-4 and combined into a health score out of 20 with a rating band from Critical to Excellent.

How are audit findings prioritized?▼

Every issue is tagged P0 through P3. P0 blocks task completion, P1 is a major issue or WCAG AA violation, P2 is a minor annoyance, and P3 is polish. Recommended fix commands are listed in that priority order.

Does the audit fix the issues it finds?▼

No, it only documents issues with locations, impact, and recommendations. Fixes are delegated to follow-up commands such as /optimize, /adapt, or /polish, which the report suggests in priority order.

Can the audit detect AI-generated design patterns?▼

Yes, the anti-patterns dimension specifically flags AI design tells like gradient text, glassmorphism, generic fonts, hero metrics, and card grids. It gives a pass/fail verdict on whether the design looks AI-generated.

When should I re-run the audit?▼

Re-run it after applying the recommended fixes to verify the score improved and no regressions were introduced. It works best as a repeatable checkpoint before each release.