claude-design-auditor-skill
Design Auditor is a Claude skill that audits UI/design inputs against 18 categories (including accessibility/WCAG and ethics/dark patterns). It can analyze Figma files via Figma MCP, as well as code (HTML/CSS/React/Vue), screenshots, and written descriptions, producing scored reports, prioritized issues, and developer handoff/export artifacts (e.g., Markdown, before/after diffs). It supports English and Korean.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
The provided content does not specify transport (TLS) enforcement, auth mechanism, scope model, or secret-handling practices. Given it integrates with Figma via MCP, authorization and least-privilege should be verified, but the README does not document these details. The skill is designed to analyze code and design assets; ensure that any included artifacts are handled according to the hosting platform’s privacy/security policies. No dependency/SBOM or CVE hygiene information is provided.
⚡ Reliability
Best When
You want a developer-friendly, rule-based second opinion on design quality (including WCAG-aligned accessibility and ethics/dark-pattern heuristics) for web UIs and design-system components, especially when you can provide Figma links or code/screenshots.
Avoid When
You need definitive legal/regulatory compliance assurance, or you cannot provide enough artifacts (e.g., only vague descriptions) for the rule checks to be reliable.
Use Cases
- • Audit UI designs for typography, color/contrast, spacing/layout, and visual hierarchy
- • Run accessibility-focused checks (WCAG-related, including touch targets, focus states, labels, reading order)
- • Assess ethics/dark-pattern risks (e.g., deceptive UX, coercive flows, consent/privacy issues)
- • Review code for design rule compliance and generate before/after diffs for fixes
- • Validate Figma designs and (optionally) apply fixes in-place via Figma MCP
- • Create developer handoff reports (CSS spec tables, accessibility checklists, critical fixes)
- • Export audit results as Markdown for Notion/GitHub/Linear/Jira
Not For
- • Replacing professional accessibility audits or legal/consumer-rights review for compliance claims
- • Doing exhaustive UX research or usability testing with real users
- • Designing brand systems requiring strong brand/visual identity governance beyond rule-based checks
- • Guaranteeing that an interface is free from dark patterns or fully compliant with all jurisdictional requirements
Interface
Authentication
No API authentication details are provided in the provided README for the skill itself. Figma MCP is mentioned as an integration path, but the specific auth mechanism (OAuth scopes, tokens, domain restrictions) is not documented in the supplied content.
Pricing
Pricing is not described in the provided README content.
Agent Metadata
Known Gotchas
- ⚠ Figma MCP step/workflow is described at a high level; tool/operation granularity and failure modes (e.g., partial page selection, variable access errors) are not detailed in the supplied README.
- ⚠ Because the skill performs edits in Figma 'via MCP' (claimed), agents should be cautious about unintended edits and confirm scope/permissions before applying fixes.
- ⚠ The repository content provided does not include explicit machine-readable error codes, so agent retries/error handling may be less deterministic than with a typical API.
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for claude-design-auditor-skill.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-03-30.