frontend-design-auditor

Audits frontend components and UI designs against WCAG accessibility and design token standards.

1|Updated Aug 25, 2026
One-click install
npx skills add https://github.com/sabiscore/swarmxq --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/swarmxq/tree/main/.ai/skills/frontend-design-auditor
Command: npx skills add https://github.com/sabiscore/swarmxq --skill frontend-design-auditor-sabiscore

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Frontend designs often ship with vague visual flaws, accessibility violations, and inconsistent spacing or typography that are hard to diagnose without a structured review framework. This Skill turns subjective design feedback into specific, actionable findings grounded in Gestalt principles, WCAG AA criteria, and design token governance. ## Core Features & Use Cases - Six-Dimension Audit: Evaluates visual hierarchy, typography, color and contrast, spacing and layout, accessibility, and motion for any component or page. - Structured Audit Report: Separates critical issues from improvements and polish, with every finding citing the specific WCAG criterion or design principle violated. - Corrected Code Output: Rewrites provided JSX, HTML, or Tailwind code using design token variables with inline comments explaining each change. - Use Case: A developer pastes a React card component and asks why it feels off. The audit identifies a 3.8:1 contrast ratio failing WCAG 1.4.3, inconsistent 13px padding breaking the spacing scale, and a missing focus ring, then returns corrected code using tokens. ## Quick Start Ask the assistant to audit the attached UI screenshot or pasted component code for accessibility, spacing, and visual hierarchy issues.

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 UI component for accessibility issues?

Paste the component code or a screenshot and request an accessibility audit. The review checks contrast ratios against WCAG AA thresholds, keyboard navigability, focus ring visibility, ARIA roles, touch target sizes of at least 44x44px, and reduced-motion support.

How to check color contrast for WCAG AA compliance?

WCAG AA requires a 4.5:1 contrast ratio for body text, 3:1 for large text, and 3:1 for UI components. The audit reports actual numeric ratios rather than subjective impressions and flags failures with specific criterion IDs like 1.4.3.

What inputs can I use for a design review?

You can submit a UI screenshot, pasted JSX, HTML, CSS, or Tailwind code, a written design description, or a Figma URL. When code is provided, both the inferred visual output and the implementation quality are reviewed.

Does the audit fix my component code or just report issues?

It does both. After the structured report, it returns corrected code 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 design feedback?

The audit infers visual output from code rather than rendering it, so subtle rendering issues may be missed. Figma URLs are handled only through contextual inference, and audits follow fixed standards like WCAG AA rather than brand-specific guidelines.