tailwind-design-system
wshobson/agents
Build scalable design systems with Tailwind CSS v4, design tokens, and responsive component patterns.
What is tailwind-design-system?
A skill for creating production-ready design systems using Tailwind CSS v4's CSS-first configuration, design tokens, and component libraries. Use this when implementing design systems, creating component libraries, standardizing UI patterns, or migrating from Tailwind v3 to v4.
- Define semantic design tokens using OKLCH color space and CSS custom properties
- Configure dark mode with native CSS @custom-variant instead of config files
- Build component variants, sizes, and states using Tailwind v4 patterns
- Set up responsive and accessible component patterns
- Migrate projects from Tailwind v3 to v4 with updated syntax
- Create animations and keyframes within @theme blocks
How to install tailwind-design-system
npx skills add https://github.com/wshobson/agents --skill tailwind-design-system- Tailwind CSS v4 (2024+) installed in your project
- Node.js and npm or equivalent package manager
- Basic familiarity with CSS and Tailwind utility classes
How to use tailwind-design-system
- 1.Replace your tailwind.config.ts with CSS-first @theme configuration in your main CSS file
- 2.Import Tailwind v4 using @import "tailwindcss" instead of @tailwind directives
- 3.Define semantic color tokens using OKLCH format in the @theme block
- 4.Set up dark mode using @custom-variant dark instead of darkMode config option
- 5.Create component variants and responsive patterns using the new v4 syntax
- 6.Reference detailed patterns in references/details.md for complex component architectures
Use cases
- Building a reusable component library for a design system
- Implementing consistent theming across a large codebase
- Setting up dark mode support with class-based switching
- Standardizing spacing, typography, and color tokens across teams
- Migrating an existing Tailwind v3 project to v4
- Frontend engineers building design systems
- Product teams standardizing UI patterns
- Teams migrating from Tailwind v3 to v4
- Component library maintainers
- Designers implementing design tokens in code
tailwind-design-system FAQ
Tailwind v4 uses CSS-first configuration with @theme blocks instead of tailwind.config.ts, replaces @tailwind directives with @import "tailwindcss", uses @custom-variant for dark mode, and supports OKLCH color space for better color perception. Animations are now defined as @keyframes within @theme.
OKLCH provides better perceptual uniformity, making it easier to create accessible color systems with consistent contrast and brightness across different hues. It's more intuitive for designing semantic color tokens.
Use @custom-variant dark (&:where(.dark, .dark *)) in your CSS, then define dark mode overrides in a .dark selector block. This replaces the darkMode: "class" configuration from v3.
Yes, but some v3 plugins may need updates. Built-in features like animations are now handled through @theme blocks and @keyframes, reducing the need for external plugins.
Use a hierarchical token structure: Brand Tokens (abstract values) → Semantic Tokens (purpose-driven) → Component Tokens (specific usage). Define all tokens in @theme and reference them with semantic class names like bg-primary, text-muted-foreground.
Full instructions (SKILL.md)
Source of truth, from wshobson/agents.
name: tailwind-design-system description: 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.
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.
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
/* 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.
Related skills
More from wshobson/agents and the wider catalog.

task-coordination-strategies
Decompose complex tasks, design dependency graphs, and coordinate multi-agent work across teams.

team-communication-protocols
Structured messaging protocols for coordinating agent teams: direct messages, broadcasts, plan approval, and graceful shutdown.

team-composition-analysis
Design optimal team structures, hiring plans, compensation strategies, and equity allocation for early-stage startups pre-seed through Series A.

team-composition-patterns
Design optimal multi-agent team compositions with sizing heuristics, preset configurations, and agent type selection.

temporal-python-testing
Test Temporal workflows with pytest, time-skipping, and mocking strategies.

terraform-module-library
Build reusable Terraform modules for AWS, Azure, GCP, and OCI following infrastructure-as-code best practices.