tailwind-4

Apply Tailwind CSS 4 patterns to React projects with cn() and design tokens.

1|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/wildbitca/ai-resources --skill tailwind-4-wildbitca
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tailwind-4
Source: https://github.com/wildbitca/ai-resources/tree/main/skills/gpm-curated-tailwind-4
Command: npx skills add https://github.com/wildbitca/ai-resources --skill tailwind-4-wildbitca

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Tailwind CSS 4 patterns and best practices to help frontend teams write consistent, accessible, and maintainable styles while avoiding common pitfalls like using var() in className or hex color literals.

Core Features & Use Cases

  • Clear decision guidance for when to use cn() and how to compose utility classes.
  • Practical rules for color, theming, dark mode, and responsive layouts across React/JSX and CSS files.
  • Real-world use cases showing how to structure styles for common components (buttons, cards, forms) with Tailwind 4.

Quick Start

Follow these guidelines to implement Tailwind 4 patterns in your project.

Frequently Asked Questions about tailwind-4

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What's the best way to structure Tailwind 4 utility classes in React components?

Avoid using var() directly in className strings and replace hex color literals with Tailwind 4 design token configurations. This maintains theming consistency and accessibility across dark mode and responsive layouts without hardcoding CSS values.

When should I use the cn() function with Tailwind CSS 4?

Apply Tailwind CSS 4 patterns to frontend styling tasks across React projects by configuring tailwind.config.* files and following practical rules for theming and responsive layouts. This ensures consistent, accessible, and maintainable styles across common components like buttons, cards, and forms.

Does Tailwind 4 work with existing tailwind.config.* setups in React projects?

Yes, Tailwind 4 works with React projects by applying patterns across tsx, jsx, css, and tailwind.config.* files. It specifies safety and consistency requirements to ensure styles remain maintainable across your existing frontend tooling stack.

Why should I avoid hex colors and var() in Tailwind 4 className attributes?

Avoiding hex colors and var() in Tailwind 4 className attributes prevents hardcoded values from bypassing the design token system. This maintains theming consistency and dark mode support while keeping utility classes aligned with best practices.