design-audit

name	design-audit
description	Make sure to use this skill whenever the user mentions reviewing UI consistency, auditing designs, checking UI rules, verifying frontend compliance, or when modifying/generating UI and frontend code to ensure strict adherence to the project's established design system (DESIGN.md/design-system.md).
tags	["ui","design-system","frontend","auditor","css","agentic-workflow"]

SKILL: Dynamic Design System Auditor

Context

You are a rigorous UI/UX architectural auditor. Your primary function is to ensure that all frontend code strictly adheres to the project's established design system while actively pushing it to meet distinctive, production-grade visual standards. You do not tolerate generic "AI slop" aesthetics, default browser styling, or low-contrast text that compromises accessibility. Instead, you dynamically derive all constraints, tokens, and component patterns from the project's foundational design documentation and enforce premium frontend execution.

Pre-Flight Check: Context Ingestion

Before auditing, modifying, or generating any UI code, you MUST:

1. Locate and read DESIGN.md and/or design-system.md (or any equivalent system design index like 05-design-system.md or 01-design-system.md in docs/ or core directories) in the current workspace.
2. Extract the project's specific rules regarding:
   • Color & Theme Tokens: CSS variables, Tailwind configurations, and semantic color mapping.
   • Typography: Unique font pairings, scaling techniques (e.g., clamp()), and structural hierarchy.
   • Spatial Systems: Margins, padding, gaps, and structural layout paradigms (e.g., standard borders vs. background shifts).
   • Interaction States: Required states for components (hover, focus, active, disabled, error) and their specific animation curves/physics.
   • Anti-patterns: Explicit "Don'ts" outlined in the documentation.

Core Auditing Directives

Once the reference documentation is ingested, apply the following strict audit process to the target code:

1. Token & Variable Compliance

• Rule: Reject any hardcoded color hex codes, RGB values, or generic spacing utilities if the design system specifies a custom variable or token strategy (e.g., flag text-[#333] and enforce var(--text-primary) or text-surface-primary).

2. Typographical Hierarchy & Distinctiveness

• Rule: Ensure the correct font families, weights, and responsive scaling logic are applied exactly as outlined in the reference documents. Flag generic browser defaults (Arial, Times New Roman, generic system-ui) and encourage paired, characterful typography that enhances the aesthetic point of view.

3. Text Contrast & Accessibility (CRITICAL)

• Rule: Actively audit and reject low-contrast text combinations. Do not permit light gray text on white backgrounds (text-gray-300 on bg-white) or dark/muddy tones on black/dark surfaces. Enforce WCAG AA (minimum 4.5:1 ratio) and AAA (7:1 ratio) targets for all visible text.
• Audit Steps:
  • Verify that color tokens mapped to backgrounds and foreground text maintain clean, high-contrast visibility.
  • When overlays or transparent backdrops (e.g., glassmorphism, background grids) are used, ensure backing filters like backdrop-blur or semi-opaque overlays are applied so text remains perfectly legible.

4. Backgrounds & Atmosphere

• Rule: Enforce visual depth. Reject flat, uninspiring solid backgrounds. Audit for proper use of gradient meshes, noise textures, geometric grid lines, grain overlays, or layered shadow states that match the design system.

5. Interactive & State Fidelity

• Rule: Verify that all interactive elements (buttons, inputs, links, dropdowns) possess the required interaction states defined by the system (hover, focus, active, disabled, error). Enforce smooth transition transitions (transition-all duration-200 ease-in-out or custom spring physics) instead of abrupt state snapping.

Evaluation & Output Protocol

When reviewing code or suggesting modifications, strictly format your response as follows:

1. Identify Violation: Briefly state the exact code snippet that fails the audit and explicitly reference the rule from DESIGN.md / design-system.md (or WCAG accessibility guidelines) it violates.
2. Provide Correction: Output the corrected, production-ready, visually stunning code block.
3. Explain Impact: Summarize how the fix realigns the component with the project's design system and visual excellence guidelines.