Audit front-end code for accessibility, performance, theming, and responsive issues.
npx skills add https://github.com/yahya-azeem/Pokedex --skill audit-yahya-azeem
Please help me install this Agent Skill. Skill: audit Source: https://github.com/yahya-azeem/Pokedex/tree/main/library/impeccable/skills/audit Command: npx skills add https://github.com/yahya-azeem/Pokedex --skill audit-yahya-azeem
Identify measurable technical quality issues in your UI—covering accessibility, performance, theming, responsive behavior, and common anti-patterns—then produce a scored, actionable review.
Ask to run the audit for a specific area by providing the feature, page, or component you want reviewed.
High-intent search queries and answers about installing and using this skill.
A frontend design audit detects measurable accessibility, performance, theming, responsive design, and anti-pattern issues in your code-level implementation. It produces a scored, actionable P0–P3 report of verifiable problems and severities for specific features or components.
Check front-end implementations for design anti-patterns and theming errors by verifying token usage, dark-mode behavior, and theme switching correctness. The audit flags critical design anti-pattern indicators and scoring them by severity.
Detect A11y gaps by auditing the front-end code for contrast problems, missing ARIA semantics, keyboard navigation issues, semantic HTML gaps, missing alt text, and form-label or error issues, generating a scored review of these accessibility failures.
Yes, you can audit responsive design components for fixed-width breakage, small touch targets, overflow risks, expensive rendering patterns, unoptimized assets, and bundle or render inefficiencies to ensure responsive behavior across implementations.
No, the audit does not automatically fix performance and accessibility issues. It strictly produces a scored P0–P3 report identifying verifiable problems, severities, and design anti-patterns, leaving the code-level fixes to the developer.
Yes, you need to run the frontend-design context protocol or teach-impeccable first. This prerequisite setup is required before the audit can detect accessibility, performance, theming, and responsive design anti-patterns in your front-end implementation.
nielpattinCorrect alignment, spacing, consistency, and micro-details in final deliverables.
sandrasocialAudit web codebases for accessibility, performance, theming, responsive design, and anti-patterns.
shwilliamsonEnforce BEM naming, CSS variables, and responsive patterns for CSS/SCSS.
mauriciodelrioAudit React and Next.js components for WCAG 2.2 AA accessibility violations.
