frontend-design-auditor

Audits frontend components against Gestalt principles, WCAG AA standards, and design token governance.

1|Updated Sep 3, 2026
One-click install
npx skills add https://github.com/sabiscore/the-yap-engine --skill frontend-design-auditor-sabiscore
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: frontend-design-auditor
Source: https://github.com/sabiscore/the-yap-engine/tree/main/.ai/skills/frontend-design-auditor
Command: npx skills add https://github.com/sabiscore/the-yap-engine --skill frontend-design-auditor-sabiscore

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Frontend designs often ship with vague or inconsistent quality issues — poor contrast, broken spacing rhythm, missing focus states — that are hard to diagnose without a structured framework. This Skill turns subjective design feedback into a specific, actionable audit grounded in named principles and measurable criteria. ## Core Features & Use Cases - Six-Dimension Audit: Evaluates visual hierarchy, typography, color and contrast, spacing and layout, accessibility, and motion against concrete thresholds like 4.5:1 contrast ratios and 44×44px touch targets. - Structured Audit Report: Separates critical issues from improvements and polish, cites the exact WCAG criterion or Gestalt principle violated, and always includes a "What's Working" section. - Corrected Code Output: Rewrites provided JSX, HTML/CSS, or Tailwind components with all critical issues fixed, design token variables replacing raw values, and inline comments explaining every change. - Use Case: Paste a React component that "feels off" and receive a prioritized report identifying a 3.2:1 contrast failure (WCAG 1.4.3), inconsistent spacing off the 8px grid, and missing focus rings — plus the corrected code using a proposed token set. ## Quick Start Ask the AI to audit the attached component code or screenshot for accessibility, spacing, and visual hierarchy issues and return corrected code.

Frequently Asked Questions about frontend-design-auditor

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

FAQPage Schema
How do I audit a frontend component for accessibility issues?▼

Submit the component code or a screenshot and request an accessibility audit. The audit checks keyboard navigability, focus ring visibility, ARIA roles, touch target sizes of at least 44×44px, and contrast ratios against WCAG AA criteria with specific criterion IDs cited.

How to check color contrast for WCAG AA compliance?▼

WCAG AA requires body text contrast of at least 4.5:1, large text at least 3:1, and UI components at least 3:1. The audit verifies these ratios with actual computed numbers rather than subjective impressions and flags failures by criterion ID such as 1.4.3.

What input formats does a UI design audit accept?▼

The audit accepts screenshots or images of the UI, pasted component code in JSX, HTML/CSS, or Tailwind, written design descriptions, and Figma URLs. When code is provided, both the inferred visual output and implementation quality are reviewed.

Can I get corrected code from a design audit?▼

Yes. When component code is provided, the audit returns a corrected version with all critical issues resolved, raw hex and pixel values replaced by design token variables, and inline comments marking every changed line with its reason.

What are the limitations of automated UI design feedback?▼

Feedback on screenshots and descriptions relies on inferred visual output rather than rendered behavior, so dynamic states and real contrast measurements may need verification in a browser. Figma URLs are interpreted from available context only, not direct file access.