Write consistent, maintainable CSS following the project's methodology (Tailwind utility classes) while minimizing custom CSS and adhering to design system tokens. Use this skill when writing or editing CSS files, Tailwind classes in React components (.tsx, .jsx files), when implementing design system colors/spacing/typography, when using Tailwind utility classes, when deciding between framework utilities vs. custom CSS, when optimizing CSS for production with tree-shaking, when configuring Tailwind theme extensions, or when maintaining design consistency across the application.
Content & Writing
85 Stars
2 Forks
Updated Jan 19, 2026, 04:39 AM
Why Use This
This skill provides specialized capabilities for aiskillstore's codebase.
Use Cases
Developing new features in the aiskillstore repository
Refactoring existing code to follow aiskillstore standards
Understanding and working with aiskillstore's codebase structure
---
name: frontend-css
description: Write consistent, maintainable CSS following the project's methodology (Tailwind utility classes) while minimizing custom CSS and adhering to design system tokens. Use this skill when writing or editing CSS files, Tailwind classes in React components (.tsx, .jsx files), when implementing design system colors/spacing/typography, when using Tailwind utility classes, when deciding between framework utilities vs. custom CSS, when optimizing CSS for production with tree-shaking, when configuring Tailwind theme extensions, or when maintaining design consistency across the application.
---
# Frontend CSS
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.
## When to use this skill
- When writing or editing CSS files in the project
- When applying Tailwind CSS utility classes in React components (.tsx, .jsx files)
- When implementing design system tokens (colors, spacing, typography)
- When configuring Tailwind theme extensions using the `@theme` directive
- When deciding between using framework utilities vs. writing custom CSS
- When maintaining consistent styling patterns across components
- When optimizing CSS for production with purging/tree-shaking
- When avoiding unnecessary framework style overrides
- When working with the project's CSS methodology (Tailwind, BEM, utility-first, etc.)
- When implementing responsive styles using Tailwind breakpoints
- When ensuring CSS performance and bundle size optimization
## Instructions
For details, refer to the information provided in this file:
[frontend CSS](../../../agent-os/standards/frontend/css.md)
