Frontend CSS
When to use this skill
- When writing or modifying CSS files (e.g.,
*.css,*.scss,*.module.css,globals.css,tailwind.config.*) - When applying Tailwind CSS utility classes to components
- When using CSS methodologies (BEM, utility classes, CSS modules, styled-components, etc.)
- When creating custom CSS or extending framework styles
- When maintaining design systems and design tokens (colors, spacing, typography)
- When defining CSS variables or theme configurations
- When choosing fonts and typography (avoiding generic defaults like Inter, Roboto, Arial)
- When selecting color schemes and creating cohesive aesthetics
- When implementing animations, transitions, and micro-interactions
- When creating atmospheric backgrounds (gradients, patterns, depth)
- When avoiding generic "AI slop" aesthetics (purple gradients, cookie-cutter designs)
- When avoiding or refactoring excessive style overrides
- When optimizing CSS for production (purging unused styles, tree-shaking)
- When ensuring consistent styling patterns across the application
- When implementing responsive styles and breakpoints
- When working with CSS-in-JS solutions
- When reviewing styling approaches for maintainability, consistency, and aesthetic excellence
This Skill provides Claude Code with specific guidance on how to adhere to coding standards as they relate to how it should handle frontend CSS.
Instructions
For details, refer to the information provided in these files:
Technical Best Practices
Aesthetic Excellence & Design Philosophy
frontend aesthetics - CRITICAL: Read this file to avoid generic "AI slop" designs. Follow typography, color, motion, and background guidelines to create distinctive, memorable designs.