css-development:validate

To audit CSS for consistency, use a validation workflow that checks semantic naming conventions, improper Tailwind @apply usage, and utility-only classes to guide refactoring toward semantic components.

Checking dark mode coverage involves validating CSS files against established dark mode patterns to spot gaps in theme support, ensuring accessibility considerations and theme variants are fully implemented across components.

Performing a pre-merge CSS review requires executing a structured checklist that validates class naming, utility usage, test coverage, and accompanying documentation to ensure quality assurance before merging changes.

Yes, CSS validation is applicable to refactoring tasks by flagging non-semantic names and Tailwind-utility-only classes, guiding updates toward semantic components and improving consistency across a project.

A structured CSS validation workflow checks class naming, utility usage, dark mode coverage, tests, and accompanying documentation by loading CSS files and executing a TodoWrite-based checklist to systematically review styles.

A Tailwind CSS audit flags utility-only classes to enforce consistency, guiding refactors away from improper @apply usage and toward semantic component naming patterns for better long-term maintainability.