What problem does it solve?
Tailwind CSS v4 moved all configuration from legacy JavaScript files to CSS-first directives, breaking existing workflows for developers used to earlier Tailwind versions. Manually syncing theme colors with project brand skills is error-prone and leads to inconsistent styling across assets. This skill eliminates that friction by providing clear, step-by-step guidance for v4 configuration, theming, and brand color synchronization.
Core Features & Use Cases
- CSS-first Configuration Guidance: Covers all Tailwind v4 directives including @theme, @theme inline, @import, @plugin, @source, and @custom-variant, with reference documentation for full syntax details.
- Multi-Pattern Theming Workflows: Provides step-by-step processes for flat static themes, light/dark mode with runtime switching, and dark-only single-theme projects.
- Brand Skill Synchronization: Includes logic to detect project brand skills, enforce a single source of truth for brand colors, and propagate updates between brand records and Tailwind theme tokens to avoid drift.
- Use Case: For example, if you need to update your SaaS product's primary brand color across light and dark modes, this skill walks you through updating the canonical brand record first, then propagating the change to your Tailwind CSS entry file to ensure consistency.
Quick Start
Use the tailwind skill to update your project's primary brand color and sync it across all active theme modes.