Production-Ready Rule
•
**/*.{tsx,jsx,vue,svelte,html,css}
Tailwind CSS v4 & cn() Utility .cursorrules (.mdc)
High-velocity .cursorrules and .cursor/rules/*.mdc configuration for Tailwind CSS v4. Enforce cn() utility merging, mobile-first responsiveness, and prevent arbitrary class sprawl.
.cursor/rules/tailwind-css.mdc
---
description: Tailwind CSS v4 utility styling, cn() merging, and responsive design standards
globs: **/*.{tsx,jsx,vue,svelte,html,css}
alwaysApply: false
---
# Tailwind CSS v4 Standards
## Utility-First Discipline
- Use atomic utility classes directly. Do not create separate CSS files with @apply unless writing base typography.
- Always use the cn() helper (clsx + tailwind-merge) when conditionally merging classes.
- Follow mobile-first order: base classes first, then sm:, md:, lg:, xl:.
## Theming & Dark Mode
- Use semantic color classes (bg-background, text-foreground, border-border) so dark mode works out of the box.
- Avoid arbitrary hardcoded pixel values (e.g. w-[347px]). Use standard Tailwind spacing scale (w-80, w-96).
⭐
Using this rule in your open-source project? Reference in your README:
https://cursor.pacebowl.com/rules/tailwind-css
Frequently Asked Questions & Implementation Notes
How does it prevent CSS class conflicts?
It mandates wrapping dynamic class names inside the cn() helper using tailwind-merge to automatically resolve conflicting utility classes.
Is it compatible with Tailwind v4 CSS theme variables?
Yes, it emphasizes CSS variable based color tokens over hardcoded HEX values to support seamless dark/light mode switching.