Tailwind CSS v4 — Utility-First CSS Framework
The most popular utility-first CSS framework, now with v4 engine rewritten in Rust. 10x faster builds, automatic content detection, and zero-config setup. 90,000+ GitHub stars.
Installation avec revue préalable
Cet actif nécessite une revue. Le prompt copié demande un dry-run, affiche les écritures, puis continue seulement après confirmation.
npx -y tokrepo@latest install 46f11f5d-bec2-46b8-89ba-fee11a265142 --target codexDry-run d'abord, confirmez les écritures, puis lancez cette commande.
What it is
Tailwind CSS is the most popular utility-first CSS framework. Version 4 rewrites the core engine in Rust, delivering 10x faster build times, automatic content detection (no more configuring content paths), and a simplified setup that requires zero configuration files.
Tailwind targets frontend developers who prefer composing UI directly in HTML with utility classes rather than writing custom CSS files. It is used by teams of all sizes, from solo developers to large enterprises.
How it saves time or tokens
Traditional CSS requires naming classes, organizing stylesheets, and managing specificity conflicts. Tailwind eliminates this: you write flex items-center gap-4 p-6 bg-white rounded-xl directly in your HTML. The v4 engine detects which classes you use automatically, so the final CSS bundle contains only what is needed.
For AI-generated UIs, Tailwind is ideal because LLMs can produce working UI code in a single HTML file without creating separate CSS files.
How to use
- Install Tailwind CSS v4:
npm install tailwindcss @tailwindcss/vite
- Import Tailwind in your CSS:
/* app.css */
@import "tailwindcss";
- Use utility classes in your HTML:
<div class="flex items-center gap-4 p-6 bg-white rounded-xl shadow-md">
<img class="w-12 h-12 rounded-full" src="avatar.jpg" />
<div>
<h2 class="text-lg font-semibold text-gray-900">Jane Smith</h2>
<p class="text-sm text-gray-500">Software Engineer</p>
</div>
</div>
Example
<!-- Responsive card grid with Tailwind v4 -->
<div class="grid grid-cols-1 md:grid-cols-2 lg:grid-cols-3 gap-6 p-8">
<div class="bg-white rounded-2xl p-6 shadow-sm hover:shadow-lg transition-shadow">
<h3 class="text-xl font-bold text-gray-900">Project Alpha</h3>
<p class="mt-2 text-gray-600">A description of the project.</p>
<div class="mt-4 flex gap-2">
<span class="px-2 py-1 bg-blue-100 text-blue-800 text-xs rounded-full">React</span>
<span class="px-2 py-1 bg-green-100 text-green-800 text-xs rounded-full">TypeScript</span>
</div>
</div>
</div>
Related on TokRepo
- AI Tools for Design -- Design tools and UI frameworks for developers
- AI Tools for Coding -- Development tools for frontend and full-stack work
Common pitfalls
- Tailwind v4 has breaking changes from v3. The configuration file format changed, and some utility names were renamed. Check the migration guide before upgrading.
- Long lists of utility classes can make HTML hard to read. Extract common patterns into components (React/Vue/Svelte) rather than creating custom CSS classes.
- Tailwind's JIT engine in v4 requires a build step. It does not work by including a CDN script in production (the CDN version is for prototyping only).
Questions fréquentes
The engine was rewritten in Rust for 10x faster builds. Content detection is automatic (no content paths in config). The setup is zero-config with just an @import statement. Some utility names and configuration patterns changed.
Yes. Tailwind works with any frontend framework or plain HTML. Use utility classes directly in JSX (React), templates (Vue), or any HTML-producing framework. Component extraction replaces the need for CSS abstractions.
Yes. Tailwind is used by thousands of production applications. The build step produces optimized, minified CSS containing only the utilities you use. Final bundle sizes are typically 5-15KB gzipped.
No. Tailwind maps utility classes to CSS properties. Understanding CSS (flexbox, grid, positioning, specificity) is still necessary. Tailwind is a productivity layer on top of CSS, not a replacement for understanding it.
Yes. Tailwind v4 uses CSS custom properties and @theme directives for customization. You can extend or override the default design tokens (colors, spacing, fonts) in your CSS file.
Sources citées (3)
- Tailwind CSS Blog— Tailwind CSS v4 engine rewritten in Rust for 10x faster builds
- Tailwind CSS Documentation— Utility-first CSS framework with automatic content detection
- Tailwind CSS GitHub— Zero-config setup with @import directive
En lien sur TokRepo
Source et remerciements
Created by Adam Wathan and Tailwind Labs. Licensed under MIT.
tailwindcss — ⭐ 90,000+
Thanks for making CSS productive and AI-friendly.
Fil de discussion
Actifs similaires
Skeleton — Adaptive Design System Powered by Tailwind CSS
An open-source UI toolkit that combines Tailwind CSS with framework-specific components for Svelte, React, and Next.js with built-in theming.
Pico CSS — Minimal Classless CSS Framework for Semantic HTML
A lightweight CSS framework that styles native HTML elements without requiring utility classes, delivering elegant default styling with a single stylesheet.
UnoCSS — Instant On-Demand Atomic CSS Engine
UnoCSS is the instant on-demand atomic CSS engine. Inspired by Tailwind/Windi but engine-first: define your own utilities, presets, and rules. 5x faster than Tailwind JIT with no parsing or AST overhead.
Windi CSS — On-Demand Utility-First CSS Framework
A next-generation utility-first CSS framework that generates styles on demand at dev time. Inspired by Tailwind CSS with added features like variant groups, shortcuts, and attributify mode for cleaner templates.