tailwindcss-fundamentals-v4

Migrate Tailwind CSS v3 projects to v4's CSS-first @theme workflow.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/moughamir/justwaitit-review --skill tailwindcss-fundamentals-v4-moughamir
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tailwindcss-fundamentals-v4
Source: https://github.com/moughamir/justwaitit-review/tree/main/.agents/skills/tailwindcss-fundamentals-v4
Command: npx skills add https://github.com/moughamir/justwaitit-review --skill tailwindcss-fundamentals-v4-moughamir

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Tailwind CSS projects often get stuck in outdated v3 patterns (like JavaScript config and theme() lookups), making it harder to adopt Tailwind CSS v4’s CSS-first workflow and modern design-token approach.

Core Features & Use Cases

  • Tailwind CSS v4 upgrade mindset: Covers the key breaking changes from v3 to v4 (Rust engine, CSS-first configuration, OKLCH color direction, and automatic content detection).
  • CSS-first theming with @theme: Shows how to define and organize design tokens (colors, fonts, spacing, breakpoints, radii, shadows, animations) using CSS variables.
  • Custom building blocks: Teaches @utility for static/functional utilities, @custom-variant for custom state variants, and @plugin for extending Tailwind with official or local plugins.
  • Migration pitfalls: Addresses common v4 behavior shifts like border and ring defaults and button cursor changes.
  • Design-system best practices (2025/2026): Recommends OKLCH tokens, fluid typography, fluid spacing, and accessible component patterns (e.g., touch targets, focus-visible rings).

Quick Start

Ask the AI to “show me how to set up Tailwind CSS v4 in a Vite project and configure a CSS-first @theme with OKLCH color tokens and one custom utility.”

Frequently Asked Questions about tailwindcss-fundamentals-v4

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

FAQPage Schema
How do I migrate my Tailwind CSS configuration from JavaScript to the v4 CSS-first @theme workflow?

Tailwind CSS v4 migration replaces v3 JavaScript configuration and theme() lookups with a CSS-first @theme workflow, authoring design tokens directly as CSS variables. This shift avoids common regressions like changed border and ring defaults.

How do I set up OKLCH color tokens in Tailwind CSS v4?

Set up OKLCH color tokens in Tailwind CSS v4 by defining them within the new @theme directive in your CSS entry point, utilizing CSS variables to establish a modern, perceptually uniform design system.

How do I create custom utilities and variants in Tailwind CSS v4?

Create custom utilities and variants in Tailwind CSS v4 using the @utility directive for static or functional utilities and the @custom-variant directive for custom state variants, extending your design system directly in CSS.

Does Tailwind CSS v4 work with Vite and Next.js?

Tailwind CSS v4 works with Vite, Next.js, and PostCSS-based frontends, utilizing a Rust engine and automatic content detection to streamline the CSS entry-point setup process without requiring JavaScript configuration.

What are the common migration pitfalls when upgrading to Tailwind CSS v4?

Common Tailwind CSS v4 migration pitfalls include behavior shifts in border and ring defaults, button cursor changes, and adapting to automatic content detection, which can cause styling regressions if not addressed.