tailwind-v4

Configure Tailwind v4 design tokens with CSS-first @theme blocks.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/mattdowney/ai-skills --skill tailwind-v4-mattdowney
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tailwind-v4
Source: https://github.com/mattdowney/ai-skills/tree/main/tailwind-v4
Command: npx skills add https://github.com/mattdowney/ai-skills --skill tailwind-v4-mattdowney

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Tailwind v4 patterns provide a CSS-first approach that reduces the need for complex JavaScript config while delivering consistent design tokens and theming across UI projects.

Core Features & Use Cases

  • CSS-first configuration using the @theme block to define tokens like colors, spacing, and typography.
  • Token-to-utility mapping enables consistent theming and rapid UI iterations across apps.
  • Use cases include setting up new Tailwind v4 projects, adding custom utilities, and migrating from JS-based config to CSS-based theming.

Quick Start

Set up Tailwind v4 by adding a CSS file with an @import 'tailwindcss' and an @theme block that defines colors, spacing, and typography.

Frequently Asked Questions about tailwind-v4

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

FAQPage Schema
How do I configure Tailwind v4 using a CSS-first approach instead of JavaScript?

Tailwind v4 uses a CSS-first configuration approach where you define design tokens directly in a CSS file using the @theme block, replacing complex JavaScript config files for theming and utility generation.

What is the @theme block in Tailwind v4 and how does it handle design tokens?

The @theme block is a CSS directive in Tailwind v4 used to define design tokens like colors, spacing, and typography, which automatically maps these CSS variables to utility classes for consistent UI.

How do I set up a new Tailwind v4 project with custom utilities and theming?

Set up Tailwind v4 by creating a CSS file with @import 'tailwindcss' and an @theme block to define your custom colors, spacing, and typography tokens for rapid UI iteration.

Can I migrate an existing Tailwind configuration to CSS-based theming in v4?

Yes, you can migrate from JavaScript-based config to CSS-based theming by moving your existing design tokens into the Tailwind v4 @theme block to maintain consistent utilities across components.

Why use CSS variables for design tokens instead of a JavaScript config file in Tailwind?

Using CSS variables for design tokens reduces the need for complex JavaScript configuration, enabling faster scaffolding of consistent design systems and allowing direct token-to-utility mapping in your stylesheet.