tailwind-design-system

Create Tailwind v4 design systems with semantic tokens and CVA components.

Updated Feb 3, 2026
One-click install
npx skills add https://github.com/leonardoteodoroo/amino-advanced --skill tailwind-design-system-leonardoteodoroo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tailwind-design-system
Source: https://github.com/leonardoteodoroo/amino-advanced/tree/main/.agent/skills/tailwind-design-system
Command: npx skills add https://github.com/leonardoteodoroo/amino-advanced --skill tailwind-design-system-leonardoteodoroo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Designing and maintaining UI across multiple apps is error-prone and time-consuming without a cohesive design system. This skill provides a CSS-first Tailwind v4-based approach with design tokens to ensure consistency and faster delivery.

Core Features & Use Cases

  • Tailwind v4 CSS-first configuration with semantic tokens and theming.
  • Component-driven patterns and variant systems for scalable UI components.
  • Migration guidance from Tailwind v3 to v4, dark mode handling, and accessibility best practices. Use Case: Create a reusable component library across several apps with consistent tokens and responsive patterns.

Quick Start

Create a new Tailwind v4 design-system project, configure the CSS-first theme with semantic tokens, and begin defining tokens and reusable components.

Frequently Asked Questions about tailwind-design-system

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

FAQPage Schema
How do I build a Tailwind v4 design system with semantic tokens?

To build a Tailwind v4 design system, define semantic color and radius tokens within CSS @theme blocks. This CSS-first approach standardizes front-end UI and accelerates component library development with consistent theming.

What is the best way to migrate a design system from Tailwind v3 to v4?

Migrating a design system from Tailwind v3 to v4 involves adopting a CSS-first configuration approach. This skill provides specific migration guidance to transition your existing setup to use semantic tokens and the new @theme block structure.

How do I create scalable and accessible UI components with Tailwind?

Create scalable and accessible UI components with Tailwind by using a CVA-based component pattern. This approach integrates semantic tokens and variant systems to ensure consistency and accessibility across multiple applications.

Can I use semantic tokens for dark mode theming in Tailwind v4?

Yes, you can use semantic tokens for dark mode theming in Tailwind v4. By defining semantic color tokens within @theme blocks, the system supports consistent dark mode handling and accessible theming across your component library.

Does Tailwind v4 support CSS-first configuration without JavaScript config files?

Tailwind v4 supports CSS-first configuration, allowing you to define design tokens directly in CSS using @theme blocks. This replaces traditional JavaScript config files and streamlines the theming process for your component library.

Why use semantic design tokens across multiple front-end apps?

Using semantic design tokens across multiple front-end apps ensures UI consistency and reduces maintenance errors. This token-driven approach standardizes component styling and accelerates delivery by providing a single source of truth for themes.