check-theme

To audit for hardcoded colors and spacing, run a theme token audit that scans source files for non-token usage and reports violations grouped by type with file paths and line numbers.

A theme token violation report works by scanning source files to detect hardcoded colors, fonts, and spacing, then grouping violations by type with file paths and line numbers for code review remediation.

Yes, you can enforce design tokens in Next.js projects during CI pipelines by running an audit that checks class names for valid tokens like text-primary or bg-surface instead of arbitrary values.

The best way to detect non-token CSS usage in large frontend projects is to run an automated theme audit that scans for hardcoded values and enforces design tokens within class names for consistency.

Yes, the theme audit works with existing design tokens in React code reviews by checking class names for valid token usage such as bg-surface and flagging arbitrary values as violations.

Frontend design breaks when hardcoded colors override theme tokens because the hardcoded values bypass the centralized design system, causing CSS compatibility issues and visual inconsistencies across components.