tailwind-v4-shadcn

Configure Tailwind v4 with shadcn/ui in Vite React projects.

77|3|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/FlorianBruniaux/starmapper --skill tailwind-v4-shadcn-florianbruniaux
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tailwind-v4-shadcn
Source: https://github.com/FlorianBruniaux/starmapper/tree/main/.agents/skills/tailwind-v4-shadcn
Command: npx skills add https://github.com/FlorianBruniaux/starmapper --skill tailwind-v4-shadcn-florianbruniaux

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Tailwind v4 with shadcn/ui setup is often error-prone due to conflicting configuration paths, plugin loading approaches, and theming intricacies; this skill bundles production-ready patterns, migration guidance, and references to streamline adoption in modern React projects.

Core Features & Use Cases

  • Production-ready integration of Tailwind v4 and shadcn/ui for React projects using Vite.
  • Clear guidance on CSS variable architecture, dark mode with ThemeProvider, and proper @plugin usage for Tailwind v4.
  • Quick-start support for migrating from older setups and resolving common gotchas with v4.

Quick Start

Run the exact steps described in this skill to initialize Tailwind v4 + shadcn/ui in a React project.

Frequently Asked Questions about tailwind-v4-shadcn

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

FAQPage Schema
How do I configure Tailwind v4 with shadcn/ui in a React project?

Configure Tailwind v4 with shadcn/ui by using the @plugin directive, mapping variables with @theme inline, and ensuring components.json config is empty. This streamlines integration and theming across Vite + React setups.

What is the correct CSS variable architecture for shadcn/ui dark mode in Tailwind v4?

The correct CSS variable architecture for shadcn/ui dark mode in Tailwind v4 requires mapping variables with @theme inline and enforcing dark mode provider integration through a ThemeProvider to handle toggling.

Can I migrate an existing shadcn/ui setup to Tailwind v4?

Yes, you can migrate existing shadcn/ui setups to Tailwind v4. The process provides clear migration guidance to resolve common gotchas, including conflicting configuration paths and plugin loading approaches.

Why does my Tailwind v4 @plugin directive fail with shadcn/ui?

Tailwind v4 @plugin directive failures with shadcn/ui often stem from conflicting plugin loading approaches. Proper usage requires ensuring components.json config is empty for v4 compatibility to avoid these errors.

Do I need a ThemeProvider for shadcn/ui dark mode with Tailwind v4?

Yes, you need a ThemeProvider for shadcn/ui dark mode with Tailwind v4. The setup enforces dark mode provider integration to properly manage and toggle CSS variable architecture.

What are the limitations of setting up Tailwind v4 and shadcn/ui manually?

Manual setup of Tailwind v4 and shadcn/ui is error-prone due to conflicting configuration paths, plugin loading intricacies, and theming complexities, which production-ready patterns and references resolve.