Skip to main content
Agent skill

Tailwind Design System

Build scalable design systems with Tailwind CSS v4, design tokens, component libraries, and responsive patterns. Use when creating component libraries, implementing design systems, or standardizing UI patterns.

Get started

Get the complete skill folder, including its scripts and reference files.

When to use this skill

Use Tailwind Design System when an AI agent needs a reusable SKILL.md workflow for this job: Build scalable design systems with Tailwind CSS v4, design tokens, component libraries, and responsive patterns. Use when creating component libraries, implementing design systems, or standardizing UI patterns.

When not to use it

Skip Tailwind Design System when the task is outside the writing category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.

How to install

Where will you use it?

Install scope
Claude Code folder setup
mkdir -p ~/.claude/skills/tailwind-design-system
# Save SKILL.md to ~/.claude/skills/tailwind-design-system/SKILL.md
  1. Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/tailwind-design-system/SKILL.md. For a shared project, commit the folder at .claude/skills/tailwind-design-system/ instead.
  2. Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
  3. For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.

Full install guide for Claude, Cursor, and Codex →

Try a starter prompt

After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.

Starter prompt
Use the Tailwind Design System skill for this task: Creating a component library with Tailwind v4. Confirm any required inputs or files before making changes.

What supports this recommendation?

84/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.

Documentation
92/100
Practical detail
92/100
Source evidence
63/100
Source signals
80/100
Model compatibility evidence
  • claudeuntested

    No model-specific signal or recorded compatibility test was found.

  • chatgptuntested

    No model-specific signal or recorded compatibility test was found.

  • geminiuntested

    No model-specific signal or recorded compatibility test was found.

  • copilotuntested

    No model-specific signal or recorded compatibility test was found.

  • llamauntested

    No model-specific signal or recorded compatibility test was found.

  • perplexityuntested

    No model-specific signal or recorded compatibility test was found.

  • mistraluntested

    No model-specific signal or recorded compatibility test was found.

  • grokuntested

    No model-specific signal or recorded compatibility test was found.

Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.

What this skill does

# Tailwind Design System (v4)

Build production-ready design systems with Tailwind CSS v4, including CSS-first configuration, design tokens, component variants, responsive patterns, and accessibility.

> **Note**: This skill targets Tailwind CSS v4 (2024+). For v3 projects, refer to the [upgrade guide](https://tailwindcss.com/docs/upgrade-guide).

## When to Use This Skill

- Creating a component library with Tailwind v4 - Implementing design tokens and theming with CSS-first configuration - Building responsive and accessible components - Standardizing UI patterns across a codebase - Migrating from Tailwind v3 to v4 - Setting up dark mode with native CSS features

## Key v4 Changes

| v3 Pattern | v4 Pattern | | ------------------------------------- | --------------------------------------------------------------------- | | `tailwind.config.ts` | `@theme` in CSS | | `@tailwind base/components/utilities` | `@import "tailwindcss"` | | `darkMode: "class"` | `@custom-variant dark (&:where(.dark, .dark *))` | | `theme.extend.colors` | `@theme { --color-*: value }` | | `require("tailwindcss-animate")` | CSS `@keyframes` in `@theme` + `@starting-style` for entry animations |

## Quick Start

```css /* app.css - Tailwind v4 CSS-first configuration */ @import "tailwindcss";

/* Define your theme with @theme */ @theme { /* Semantic color tokens using OKLCH for better color perception */ --color-background: oklch(100% 0 0); --color-foreground: oklch(14.5% 0.025 264);

--color-primary: oklch(14.5% 0.025 264); --color-primary-foreground: oklch(98% 0.01 264);

--color-secondary: oklch(96% 0.01 264); --color-secondary-foreground: oklch(14.5% 0.025 264);

--color-muted: oklch(96% 0.01 264); --color-muted-foreground: oklch(46% 0.02 264);

--color-accent: oklch(96% 0.01 264); --color-accent-foreground: oklch(14.5% 0.025 264);

--color-destructive: oklch(53% 0.22 27); --color-destructive-foreground: oklch(98% 0.01 264);

--color-border: oklch(91% 0.01 264); --color-ring: oklch(14.5% 0.025 264);

--color-card: oklch(100% 0 0); --color-card-foreground: oklch(14.5% 0.025 264);

/* Ring offset for focus states */ --color-ring-offset: oklch(100% 0 0);

/* Radius tokens */ --radius-sm: 0.25rem; --radius-md: 0.375rem; --radius-lg: 0.5rem; --radius-xl: 0.75rem;

/* Animation tokens - keyframes inside @theme are output when referenced by --animate-* variables */ --animate-fade-in: fade-in 0.2s ease-out; --animate-fade-out: fade-out 0.2s ease-in; --animate-slide-in: slide-in 0.3s ease-out; --animate-slide-out: slide-out 0.3s ease-in;

@keyframes fade-in { from { opacity: 0; } to { opacity: 1; } }

@keyframes fade-out { from { opacity: 1; } to { opacity: 0; } }

@keyframes slide-in { from { transform: translateY(-0.5rem); opacity: 0; } to { transform: translateY(0); opacity: 1; } }

@keyframes slide-out { from { transform: translateY(0); opacity: 1; } to { transform: translateY(-0.5rem); opacity: 0; } } }

/* Dark mode variant - use @custom-variant for class-based dark mode */ @custom-variant dark (&:where(.dark, .dark *));

/* Dark mode theme overrides */ .dark { --color-background: oklch(14.5% 0.025 264); --color-foreground: oklch(98% 0.01 264);

--color-primary: oklch(98% 0.01 264); --color-primary-foreground: oklch(14.5% 0.025 264);

--color-secondary: oklch(22% 0.02 264); --color-secondary-foreground: oklch(98% 0.01 264);

--color-muted: oklch(22% 0.02 264); --color-muted-foreground: oklch(65% 0.02 264);

--color-accent: oklch(22% 0.02 264); --color-accent-foreground: oklch(98% 0.01 264);

--color-destructive: oklch(42% 0.15 27); --color-destructive-foreground: oklch(98% 0.01 264);

--color-border: oklch(22% 0.02 264); --color-ring: oklch(83% 0.02 264);

--color-card: oklch(14.5% 0.025 264); --color-card-foreground: oklch(98% 0.01 264);

--color-ring-offset: oklch(14.5% 0.025 264); }

/* Base styles */ @layer base { * { @apply border-border; }

body { @apply bg-background text-foreground antialiased; } } ```

## Core Concepts

### 1. Design Token Hierarchy

``` Brand Tokens (abstract) └── Semantic Tokens (purpose) └── Component Tokens (specific)

Example: oklch(45% 0.2 260) → --color-primary → bg-primary ```

### 2. Component Architecture

``` Base styles → Variants → Sizes → States → Overrides ```

## Detailed patterns and worked examples

Detailed pattern documentation lives in `references/details.md`. Read that file when the navigation tier above is insufficient.

Intended uses

  • Creating a component library with Tailwind v4
  • Implementing design tokens and theming with CSS-first configuration
  • Building responsive and accessible components
  • Standardizing UI patterns across a codebase
  • Migrating from Tailwind v3 to v4
  • Setting up dark mode with native CSS features

Implementation notes

  • Review the source instructions and adapt inputs before running the workflow.

Try it, then tell us how it went

A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.