design-consistency-auditor

Detects hardcoded colors, off-scale spacing, and design-token drift across frontend codebases.

Updated Sep 5, 2026
One-click install
npx skills add https://github.com/pohlai88/afenda-xforge-v5 --skill design-consistency-auditor-pohlai88
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-consistency-auditor
Source: https://github.com/pohlai88/afenda-xforge-v5/tree/main/.agents/skills/design-consistency-auditor
Command: npx skills add https://github.com/pohlai88/afenda-xforge-v5 --skill design-consistency-auditor-pohlai88

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Frontend codebases accumulate design debt: hardcoded hex colors that break dark mode, arbitrary Tailwind values outside the spacing scale, and one-off components that duplicate the design system. This Skill audits your code against the project's own tokens and class conventions to find and report that drift. ## Core Features & Use Cases - Design-Token Drift Detection: Scans TSX/JSX files for hardcoded hex colors, arbitrary Tailwind values, and inline styles that bypass semantic tokens. - Multi-Dimension Audit: Reviews color palette, typography, spacing, component patterns, accessibility, responsive design, animation, and dark mode with weighted scoring. - Report Templates: Ships a full audit report template and a 30-minute quick-audit checklist for structured, prioritized findings. - Use Case: Before shipping a new feature, ask for a design consistency audit of the changed app to catch hardcoded colors, missing ARIA labels, and non-semantic HTML before review. ## Quick Start Ask the assistant to audit a specific app or component for design consistency, for example by requesting a check of color palette usage and hardcoded colors in your frontend app.

Frequently Asked Questions about design-consistency-auditor

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

FAQPage Schema
How do I find hardcoded hex colors in a React codebase?

Run grep for hex patterns like #[0-9a-fA-F]{6} across your TSX and JSX files, plus searches for arbitrary Tailwind values like bg-[#...] and inline style attributes. The audit then maps each violation to the correct semantic theme token.

What does a design consistency audit check?

It checks eight weighted dimensions: color palette, typography, spacing, component patterns, accessibility, responsive design, animation, and dark mode. Each category is scored and combined into an overall design health score out of 100.

Does this work with any Tailwind CSS design system?

Yes, the audit discovers the project's own tokens and class conventions from the codebase rather than assuming a naming scheme. It identifies actual card, modal, button, and input patterns before measuring consistency against them.

How is this different from an accessibility audit?

Design consistency auditing focuses on token usage, visual patterns, and design debt, while accessibility auditing targets WCAG conformance, ARIA, keyboard access, and screen readers. The skill defers deep WCAG work to a separate accessibility skill.

When should I run a design consistency audit?

Run quick audits weekly on new features, a full audit of one app monthly, and a complete design system review quarterly. It is most useful before shipping features or when design debt is suspected.