audit-style

To audit CSS for BEM conformance and design token compliance, scan your Astro components, SolidJS styles, and global CSS to detect invalid block__element--modifier selectors and hard-coded values. The process outputs a patch set and migration guidance aligned with your design system.

Refactoring hard-coded colors and spacing into design tokens involves scanning .astro and .tsx style definitions for raw values and replacing them with var(--tokens). This cross-file analysis flags non-compliant rules and generates before/after diffs for safe code migration.

Enforcing BEM naming and eliminating utility-first patterns requires a cross-file audit that targets overly specific selectors and ambiguous class structures. The audit proposes canonical renames and produces a migration map to standardize styles across Astro and SolidJS islands.

Yes, this CSS refactoring approach works with both Astro components and SolidJS islands. It performs cross-file analysis on .astro files, tsx style definitions, and global CSS to unify styling, enforce BEM naming, and ensure design token usage across the entire project.

Cross-file CSS analysis improves design system maintainability by surfacing non-compliant selectors and hard-coded typography or radii across Astro and SolidJS files. It generates a structured migration plan with patch examples, ensuring consistent token usage and reducing scattered styling rules.

Your CSS audit flags utility-first patterns as non-compliant because the design system explicitly enforces BEM naming conventions and requires design tokens for styling. This approach rejects utility classes to improve maintainability and ensure consistent structural naming across the codebase.