tailwind-v4-shadcn

Automate Tailwind v4 and shadcn/ui setup in Vite React projects.

961|99|Updated Oct 20, 2025
One-click install
npx skills add https://github.com/jezweb/claude-skills --skill tailwind-v4-shadcn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tailwind-v4-shadcn
Source: https://github.com/jezweb/claude-skills/tree/main/skills/tailwind-v4-shadcn
Command: npx skills add https://github.com/jezweb/claude-skills --skill tailwind-v4-shadcn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires tailwindcss, @tailwindcss/vite, clsx, tailwind-merge, react, react-dom, @types/node, @vitejs/plugin-react, vite, typescript, tw-animate-css, and includes references (resource) components.

What problem does it solve?

This Skill eliminates the frustrating setup errors and debugging time when configuring Tailwind v4 with shadcn/ui, preventing common issues like tw-animate-css errors and broken dark mode.

Core Features & Use Cases

  • Error-Free Setup: Automatically prevents 5 common Tailwind v4 configuration errors that waste hours of debugging.
  • Production-Ready Architecture: Provides battle-tested CSS variable patterns for automatic dark mode switching.
  • Use Case: Imagine you're starting a new React project and need Tailwind v4 with shadcn/ui. Use this Skill to get a working setup in under a minute instead of spending hours troubleshooting.

Quick Start

Set up a new Vite + React project with Tailwind v4 and shadcn/ui components.

Frequently Asked Questions about tailwind-v4-shadcn

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

FAQPage Schema
How do I set up Tailwind v4 with shadcn/ui in a React project without configuration errors?

Tailwind v4 setup with shadcn/ui automates initialization, dark-mode integration, and CSS-variable theming to prevent common errors like tw-animate-css failures and duplicate @layer base rules. This Skill provides a ready-to-run configuration for Vite + React stacks in under a minute.

What are the common Tailwind v4 configuration mistakes I should avoid?

Tailwind v4 configuration errors include improper CSS variable mapping, missing @theme inline declarations, skipped base-style application, disabled automatic dark mode, and tw-animate-css conflicts. This Skill prevents all five by enforcing the four-step architecture: define CSS root variables, map with @theme, apply base styles, and enable automatic dark mode.

Can I migrate from Tailwind v3 to v4 with shadcn/ui components?

Migration from Tailwind v3 to v4 requires updating configuration patterns, CSS-variable theming, and dark-mode handling. This Skill covers the complete migration path for Vite + React projects, including resolving duplicate @layer base issues and ensuring shadcn/ui components work without errors.

How do I implement automatic dark mode with Tailwind v4 and CSS variables?

Automatic dark mode with Tailwind v4 uses CSS variables mapped through @theme inline declarations and requires defining root variables, applying base styles, and enabling automatic mode in configuration. This Skill provides production-tested patterns and prevents dark-mode switching failures.

Does Tailwind v4 work with shadcn/ui components out of the box?

Tailwind v4 requires specific setup steps to work reliably with shadcn/ui—including CSS-variable theming, color-variable mapping, and error prevention for tw-animate-css and @layer conflicts. This Skill automates that integration so shadcn/ui components render correctly with zero configuration overhead.

What's the difference between Tailwind v3 and v4 configuration for React projects?

Tailwind v4 shifts to a CSS-first workflow using @theme inline, root CSS variables, and automatic dark mode instead of v3's config-first approach. This Skill demonstrates the v4 architecture pattern and handles the migration from v3 configuration files and dark-mode setup.