
Tailwind 4
- 590 installs
- 14.5k repo stars
- Updated August 4, 2026
- prowler-cloud/prowler
tailwind-4 is a prowler-cloud Claude Code skill that delivers instant, correct Tailwind CSS 4 patterns and prevents common className mistakes when styling React or Next.js interfaces.
About
tailwind-4 is a prowler-cloud skill at version 1.0 under Apache-2.0 license for Tailwind CSS 4 patterns and best practices. It includes a styling decision tree: use className for static Tailwind classes, style props for dynamic values, cn() for conditional variants, and avoid var() inside className when CSS variables are involved. Developers reach for tailwind-4 when working with Tailwind className, variants, or cn() in React or Next.js, especially during dynamic styling or CSS variable scenarios. Allowed tools span Read, Edit, Write, Glob, Grep, Bash, WebFetch, WebSearch, and Task, with auto_invoke when working with Tailwind classes.
- Styling Decision Tree that routes between className, style prop, and cn() utility
- Critical rules preventing var() inside className and arbitrary hex colors
- cn() utility implementation using clsx and tailwind-merge
- Semantic color mapping replacing custom CSS variables
- Scope-aware auto-invoke when working with Tailwind classes
Tailwind 4 by the numbers
- 590 all-time installs (skills.sh)
- Ranked #575 of 2,245 Frontend Development skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/prowler-cloud/prowler --skill tailwind-4Add your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 590 |
|---|---|
| repo stars | ★ 14.5k |
| Last updated | August 4, 2026 |
| Repository | prowler-cloud/prowler ↗ |
How do you use Tailwind CSS 4 className patterns in React?
Get instant, correct Tailwind CSS 4 patterns and avoid common className mistakes when styling React or Next.js interfaces.
Who is it for?
Frontend developers styling React or Next.js UIs with Tailwind CSS 4 who need correct className, cn(), and CSS variable handling.
Skip if: Developers on Tailwind CSS 3 or CSS-in-JS-only stacks who do not use Tailwind utility classes in React components.
When should I use this skill?
A user works with Tailwind className, variants, cn(), dynamic styling, or CSS variables in React or Next.js components.
What you get
Correct Tailwind CSS 4 className patterns, cn() conditional variants, and dynamic style prop usage in React or Next.js components.
- correct Tailwind className patterns
- cn() variant implementations
By the numbers
- Version 1.0
- Apache-2.0 license
Files
Styling Decision Tree
Tailwind class exists? → className="..."
Dynamic value? → style={{ width: `${x}%` }}
Conditional styles? → cn("base", condition && "variant")
Static only? → className="..." (no cn() needed)
Library can't use class?→ style prop with var() constantsCritical Rules
Never Use var() in className
// ❌ NEVER: var() in className
<div className="bg-[var(--color-primary)]" />
<div className="text-[var(--text-color)]" />
// ✅ ALWAYS: Use Tailwind semantic classes
<div className="bg-primary" />
<div className="text-slate-400" />Never Use Hex Colors
// ❌ NEVER: Hex colors in className
<p className="text-[#ffffff]" />
<div className="bg-[#1e293b]" />
// ✅ ALWAYS: Use Tailwind color classes
<p className="text-white" />
<div className="bg-slate-800" />The cn() Utility
import { clsx } from "clsx";
import { twMerge } from "tailwind-merge";
export function cn(...inputs: ClassValue[]) {
return twMerge(clsx(inputs));
}When to Use cn()
// ✅ Conditional classes
<div className={cn("base-class", isActive && "active-class")} />
// ✅ Merging with potential conflicts
<button className={cn("px-4 py-2", className)} /> // className might override
// ✅ Multiple conditions
<div className={cn(
"rounded-lg border",
variant === "primary" && "bg-blue-500 text-white",
variant === "secondary" && "bg-gray-200 text-gray-800",
disabled && "opacity-50 cursor-not-allowed"
)} />When NOT to Use cn()
// ❌ Static classes - unnecessary wrapper
<div className={cn("flex items-center gap-2")} />
// ✅ Just use className directly
<div className="flex items-center gap-2" />Style Constants for Charts/Libraries
When libraries don't accept className (like Recharts):
// ✅ Constants with var() - ONLY for library props
const CHART_COLORS = {
primary: "var(--color-primary)",
secondary: "var(--color-secondary)",
text: "var(--color-text)",
gridLine: "var(--color-border)",
};
// Usage with Recharts (can't use className)
<XAxis tick={{ fill: CHART_COLORS.text }} />
<CartesianGrid stroke={CHART_COLORS.gridLine} />Dynamic Values
// ✅ style prop for truly dynamic values
<div style={{ width: `${percentage}%` }} />
<div style={{ opacity: isVisible ? 1 : 0 }} />
// ✅ CSS custom properties for theming
<div style={{ "--progress": `${value}%` } as React.CSSProperties} />Common Patterns
Flexbox
<div className="flex items-center justify-between gap-4" />
<div className="flex flex-col gap-2" />
<div className="inline-flex items-center" />Grid
<div className="grid grid-cols-3 gap-4" />
<div className="grid grid-cols-1 md:grid-cols-2 lg:grid-cols-4 gap-6" />Spacing
// Padding
<div className="p-4" /> // All sides
<div className="px-4 py-2" /> // Horizontal, vertical
<div className="pt-4 pb-2" /> // Top, bottom
// Margin
<div className="m-4" />
<div className="mx-auto" /> // Center horizontally
<div className="mt-8 mb-4" />Typography
<h1 className="text-2xl font-bold text-white" />
<p className="text-sm text-slate-400" />
<span className="text-xs font-medium uppercase tracking-wide" />Borders & Shadows
<div className="rounded-lg border border-slate-700" />
<div className="rounded-full shadow-lg" />
<div className="ring-2 ring-blue-500 ring-offset-2" />States
<button className="hover:bg-blue-600 focus:ring-2 active:scale-95" />
<input className="focus:border-blue-500 focus:outline-none" />
<div className="group-hover:opacity-100" />Responsive
<div className="w-full md:w-1/2 lg:w-1/3" />
<div className="hidden md:block" />
<div className="text-sm md:text-base lg:text-lg" />Dark Mode
<div className="bg-white dark:bg-slate-900" />
<p className="text-gray-900 dark:text-white" />Arbitrary Values (Escape Hatch)
// ✅ OK for one-off values not in design system
<div className="w-[327px]" />
<div className="top-[117px]" />
<div className="grid-cols-[1fr_2fr_1fr]" />
// ❌ Don't use for colors - use theme instead
<div className="bg-[#1e293b]" /> // NORelated skills
FAQ
When should style props be used over className in tailwind-4?
The tailwind-4 skill directs developers to use className for static Tailwind classes and style props for dynamic values such as width percentages, following its Tailwind CSS 4 styling decision tree.
Can CSS variables go inside Tailwind className?
The tailwind-4 skill warns against using var() inside className when CSS variables are involved, recommending the documented Tailwind CSS 4 patterns for dynamic styling in React and Next.js.