tailwind-v4-shadcn

Automates Tailwind v4 + shadcn/ui setup for React projects with Vite integration and dark mode support.

Updated Mar 20, 2026
One-click install
npx skills add https://github.com/dvegaa20/alia --skill tailwind-v4-shadcn-dvegaa20
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tailwind-v4-shadcn
Source: https://github.com/dvegaa20/alia/tree/main/.agents/skills/tailwind-v4-shadcn
Command: npx skills add https://github.com/dvegaa20/alia --skill tailwind-v4-shadcn-dvegaa20

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines building production-ready Tailwind v4 + shadcn/ui setups for React projects, reducing setup time and configuration errors.

Core Features & Use Cases

  • Tailwind v4 + shadcn/ui integration with Vite and React
  • Dark mode support via ThemeProvider and CSS variable architecture
  • Clear guidance on common v4 pitfalls, configuration, and patterns

Quick Start

Install and initialize a React project with Tailwind v4 and shadcn/ui using the provided setup.

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?

You can set up Tailwind v4 with shadcn/ui by using an automated configuration that integrates Vite, applies the CSS variable architecture, and initializes ready-to-use components. This removes manual configuration errors and reduces setup time.

Does Tailwind v4 work with shadcn/ui and Vite for dark mode?

Yes, Tailwind v4 works with shadcn/ui and Vite for dark mode by utilizing a ThemeProvider and mapping CSS variables via the @theme inline directive. This architecture ensures proper dark mode toggling and styling inheritance.

What is the best way to configure CSS variables for shadcn/ui in Tailwind v4?

The best way to configure CSS variables for shadcn/ui in Tailwind v4 is mapping them via @theme inline. This approach aligns with the clean config requirements by removing tailwind.config.ts and using the @tailwindcss/vite plugin.

Why do I need to remove tailwind.config.ts when using Tailwind v4 with shadcn/ui?

You need to remove tailwind.config.ts because Tailwind v4 transitions to a CSS-first configuration model using @theme inline. This shift requires removing the JS config file and adopting the @tailwindcss/vite plugin for proper integration.

Can I use @tailwindcss/vite to integrate shadcn/ui components without manual configuration?

Yes, you can use @tailwindcss/vite to integrate shadcn/ui components without manual configuration. The automation handles the Vite integration, applies the necessary CSS variables, and prepares ready-to-use shadcn/ui components.

What are common Tailwind v4 pitfalls when configuring shadcn/ui in React?

Common Tailwind v4 pitfalls when configuring shadcn/ui include improper CSS variable mapping and failing to remove tailwind.config.ts. The setup provides clear guidance on these v4 patterns to ensure a production-ready configuration.