tailwind

Integrate Tailwind v4 into Dean Stack projects via a shared Vite config.

1|Updated Apr 26, 2026
One-click install
npx skills add https://github.com/matthewharwood/dean-stack --skill tailwind-matthewharwood
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tailwind
Source: https://github.com/matthewharwood/dean-stack/tree/main/.claude/skills/tailwind
Command: npx skills add https://github.com/matthewharwood/dean-stack --skill tailwind-matthewharwood

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Tailwind v4 integration standardizes CSS tooling in Dean Stack by replacing multiple CSS configs with a single CSS-first workflow and a reusable Vite plugin.

Core Features & Use Cases

  • Co-located design-token driven CSS with a single shared Vite config for app and Storybook.
  • Enforces Tailwind v4 syntax via import "tailwindcss" and design tokens to generate utilities.
  • Use Case: When starting new components, apply design tokens and utilities with the shared config to ensure consistency across pages.

Quick Start

Apply the shared Tailwind v4/Vite config to your app to start styling with design tokens.

Frequently Asked Questions about tailwind

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

FAQPage Schema
How do I configure Tailwind v4 using Vite without a tailwind.config.js file?

Tailwind v4 can be configured using a CSS-first workflow by importing "tailwindcss" directly and driving utilities through design tokens, eliminating the need for a separate tailwind.config.js file.

What's the best way to share a Tailwind Vite config across an app and Storybook?

The best way to share a Tailwind Vite config across an app and Storybook is using a single shared Vite plugin that enforces design token driven CSS, ensuring styling consistency across both environments.

How does a CSS-first workflow with design tokens generate Tailwind utilities?

A CSS-first workflow generates Tailwind utilities by defining design tokens directly within CSS and applying them via the shared Vite config, ensuring co-located styling drives utility generation automatically.

Do I need a separate Tailwind configuration for Storybook theming?

You do not need a separate Tailwind configuration for Storybook theming when using a shared Vite config, which applies the same design tokens and Tailwind v4 syntax across both app and Storybook environments.

Why does Tailwind v4 replace multiple CSS configs in a Dean Stack project?

Tailwind v4 replaces multiple CSS configs in a Dean Stack project to standardize CSS tooling by enforcing a single CSS-first workflow and a reusable Vite plugin, ensuring consistent design tokens across all components.