Frontend CSS

Enforce consistent CSS styling by applying a standardized CSS methodology—such as Tailwind, BEM, or CSS modules—across all frontend files. This Skill automatically validates adherence to your project's chosen approach, flagging violations in naming conventions, specificity, and design token usage to maintain uniformity across components and pages.

Prevent specificity conflicts and style duplication by enforcing design tokens for colors, spacing, and typography alongside your CSS methodology. This Skill lints CSS files to catch redundant declarations, validate specificity rules, and ensure design tokens replace custom values, reducing bloated stylesheets and maintenance overhead.

Yes. This Skill guides design token integration with Tailwind utility classes, ensuring consistent application across buttons, cards, and other components. When styling new UI elements, it automatically applies project design tokens and Tailwind utilities, maintaining visual consistency while minimizing custom CSS.

Configure CSS linting and naming convention rules—such as BEM class patterns or Tailwind utility validation—in your project tooling. This Skill applies those standards across your frontend files, automatically flagging violations in class naming, responsive design rules, and style guide adherence to catch issues during development.

If CSS deviates from your project's methodology, this Skill flags violations in naming conventions, specificity, and design token usage. The linting feedback highlights exactly which files and rules need correction, helping you maintain consistency and prevent technical debt from accumulating in your stylesheets.

Custom CSS should be minimal when using design tokens and Tailwind. This Skill validates CSS files to ensure design tokens and utility classes are prioritized, flagging unnecessary custom styles and optimizing production builds by purging unused declarations while maintaining visual consistency.