What problem does it solve? Tailwind CSS v4 introduced breaking changes in imports, tooling, utilities, and variants, and generic model knowledge is often outdated or wrong. This Skill grounds every answer in a locally synced snapshot of the official Tailwind v4 docs, so configuration, migration, and implementation guidance matches the real documentation. ## Core Features & Use Cases - Local docs snapshot: Syncs the official tailwindcss.com docs into references/docs/ with an index for fast topic lookup. - Migration guidance: Covers v3-to-v4 upgrade checks including @import "tailwindcss", new PostCSS/CLI/Vite packages, utility renames, and prefix syntax. - Engineering playbook: Provides an abstraction ladder (utilities, tokens, custom utilities, component classes) for implementation, refactor, and review tasks. - Use Case: When upgrading a project from Tailwind v3, ask the agent to verify breaking changes; it loads the upgrade guide and gotchas reference and flags issues like @tailwind directives or transform-none renames. ## Quick Start Ask the agent to run the sync script with the license flag to initialize the docs snapshot, then ask any Tailwind v4 question such as how to configure custom theme tokens.
