vite-shadcn-tailwind4

Initialize Vite projects with shadcn/ui and Tailwind CSS v4 configuration.

Updated Jan 28, 2026
One-click install
npx skills add https://github.com/IgorWarzocha/realtime-dashboard-analytics-demo --skill vite-shadcn-tailwind4
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vite-shadcn-tailwind4
Source: https://github.com/IgorWarzocha/realtime-dashboard-analytics-demo/tree/main/.opencode/skill/vite-shadcn-tailwind4
Command: npx skills add https://github.com/IgorWarzocha/realtime-dashboard-analytics-demo --skill vite-shadcn-tailwind4

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a proven protocol to bootstrap shadcn/ui with Tailwind CSS v4 in a Vite project, enabling rapid UI scaffolding and a maintainable styling system from day one.

Core Features & Use Cases

  • Vite-specific setup: Proper integration of Tailwind v4 with Vite, including tsconfig references style and CSS entry conventions.
  • Shadcn UI installation: CLI-driven installation and component scaffolding with a ready-made design system.
  • Tailwind v4 configuration: Configuring CSS imports, theming tokens, and postcss/tailwind settings for consistent styling.
  • Use Case: Start a new Vite + React project with shadcn components and a Tailwind v4 setup, then iterate by adding components with minimal manual steps.

Quick Start

Initialize a Vite + React project and run through the shadcn + Tailwind v4 setup steps described in this skill to configure the project.

Frequently Asked Questions about vite-shadcn-tailwind4

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

FAQPage Schema
How do I set up shadcn/ui with Tailwind CSS v4 in a Vite project?

Setting up shadcn/ui with Tailwind CSS v4 in a Vite project involves configuring vite.config.ts with the Tailwind plugin, establishing CSS entry conventions for theming tokens, and defining TypeScript path aliases to enable seamless CLI operation for component scaffolding.

What is the correct way to configure TypeScript path aliases for the shadcn CLI in Vite?

Configuring TypeScript path aliases for the shadcn CLI in Vite requires using a tsconfig references style setup, which ensures the CLI can correctly resolve component imports and scaffold files into the proper directory structure during installation.

Can I upgrade an existing Vite app to use a shadcn design system with Tailwind v4?

Yes, you can upgrade an existing Vite app to use a shadcn design system with Tailwind v4 by modifying your existing vite.config.ts, updating PostCSS and Tailwind settings, and configuring CSS imports for the new theming tokens.

Does Tailwind v4 work with Vite without a separate PostCSS configuration file?

Tailwind v4 integrates with Vite using the dedicated Vite plugin rather than relying solely on traditional PostCSS configuration files; this Skill configures the necessary tailwind plugin settings within vite.config.ts to establish a consistent styling system.

Why does the shadcn/ui CLI fail to resolve components in my Vite setup?

The shadcn/ui CLI fails to resolve components in Vite setups when TypeScript path aliases are incorrectly configured; properly establishing tsconfig references and path aliases satisfies the CLI's resolution requirements for seamless operation.