What problem does it solve? Tailwind CSS v4 replaces the JavaScript config file with a CSS-first @theme {} block, which breaks old habits and causes confusing issues like tokens not generating utility classes or not appearing on :root. This Skill provides the correct v4 workflow for managing design tokens, extracting repeated utility patterns, and debugging broken classes in globals.css. ## Core Features & Use Cases - Token Authoring: Add color, font, and spacing tokens inside @theme {} with correct prefixes (--color-*, --font-*, --spacing-*) so utilities like bg-brand-primary generate automatically. - Component Extraction: Extract repeated multi-class patterns into @layer components with @apply when a pattern appears 3+ times across files. - Debugging Workflow: Diagnose why a token is missing from :root in DevTools, why a utility class is not applying, or why v3 directives break the build. - Use Case: A developer needs a new accent-terracotta color for a Next.js 15 site. The Skill adds --color-accent-terracotta: #C4704A; to @theme {} in globals.css, making bg-accent-terracotta and text-accent-terracotta available instantly with no rebuild. ## Quick Start Add a new terracotta accent color token to my Tailwind v4 theme and show me which utility classes it generates.