design-consistency-auditor

A design consistency audit detects hardcoded hex colors, arbitrary Tailwind values, and inline color styles by applying targeted grep rules across your codebase. It checks for missing theme classes and generates prioritized issue findings to correct design system drift.

Auditing dark mode and accessibility across multiple apps involves scanning for missing theme classes, semantic HTML gaps, and ARIA coverage. It checks contrast targets and keyboard behavior across the whole workspace to produce actionable reporting outputs.

Yes, the UI audit specifically targets Tailwind tokens by searching for arbitrary Tailwind values and hardcoded hex colors that bypass the design system. It flags these violations alongside spacing inconsistencies to generate prioritized issue findings.

You verify responsive design patterns and component consistency by running a targeted audit that checks spacing, typography, and component patterns. It uses a structured audit template and checklists to score UI coherence and identify best-practice violations across apps.

Yes, you can run a quick design audit on specific apps rather than scanning the entire monorepo. The auditor applies to multi-app workflows and uses YAML discovery metadata to scope its grep search rules for color usage and accessibility issues.

The audit relies on targeted grep and search rules to detect non-semantic click handlers, inline color styles, and missing theme classes. It requires YAML discovery metadata to function, meaning unstructured or heavily abstracted codebases may yield incomplete prioritized findings.