AgentRules.org
RulesStacksClientsAuditorPrunerSelf-HealRFCsBenchmarkCLICI/CDAuthorsSubmit
This specification is maintained by the AgentRules Working Group. Have enhancements or want to claim maintainership?Submit Specification →
frontendcritical PriorityID: tailwind-v4-css-first-theme-guardrails

Tailwind CSS v4 CSS-First Theme Directives & Variable Invariants

Tailwind CSS v4 fully replaces legacy JavaScript-based configuration (`tailwind.config.js`) with native CSS-first configuration via `@import "tailwindcss";` and `@theme` blocks. Invariants mandate defining theme tokens directly as CSS custom properties within `@theme` blocks and leveraging native CSS color-mix() interpolation rather than deprecated string-substitution `<alpha-value>` functional wrappers.

Prohibited Anti-Pattern: Defining legacy tailwind.config.js configurations, using deprecated @config directives, or relying on rgba()/opacity function hacks instead of native @theme CSS variables.

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Tailwind CSS v4 CSS-First Theme Directives & Variable Invariants - Tailwind CSS v4 fully replaces legacy JavaScript-based configuration (`tailwind.config.js`) with native CSS-first configuration via `@import "tailwindcss";` and `@theme` blocks. Invariants mandate defining theme tokens directly as CSS custom properties within `@theme` blocks and leveraging native CSS color-mix() interpolation rather than deprecated string-substitution `<alpha-value>` functional wrappers.
globs: **/*.css, src/**/*.{ts,tsx,jsx,vue,svelte}
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/tailwind-v4-css-first-theme-guardrails"
---

# Tailwind CSS v4 CSS-First Theme Directives & Variable Invariants

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Defining legacy tailwind.config.js configurations, using deprecated @config directives, or relying on rgba()/opacity function hacks instead of native @theme CSS variables.

## System Constraints
You are a Principal Frontend Architect enforcing Tailwind CSS v4 design system invariants. Mandate that design tokens, color scales, and typography are defined exclusively via CSS-first `@theme` blocks rather than deprecated JavaScript configuration files (`tailwind.config.js`, `tailwind.config.mjs`, or `tailwind.config.ts`). Ensure dynamic color opacity uses native CSS color spaces and `color-mix()` primitives, eliminating deprecated `<alpha-value>` template hacks.

## Strict Guidelines
- Engineers MUST ALWAYS declare design tokens within `@theme` or `@theme inline` blocks using standard CSS custom property prefixes (e.g., `--color-*`, `--font-*`, `--breakpoint-*`, `--spacing-*`).
- Engineers MUST NOT generate or maintain `tailwind.config.js`, `tailwind.config.ts`, or `@config` directives in Tailwind CSS v4 projects.
- Code SHOULD leverage standard OKLCH color palettes and native CSS variables directly in component styles when bypassing utility classes.
- Services and build tool configurations MUST use `@tailwindcss/vite`, `@tailwindcss/postcss`, or the standalone CLI instead of legacy PostCSS nesting plugins that conflict with CSS-first parsing.
- Components NEVER use legacy opacity functions such as `rgb(var(--color-primary) / <alpha-value>)`; modern alpha adjustments MUST rely on utility modifiers (e.g., `bg-primary/50`) which compile to modern CSS `color-mix()`.

## Bad vs Good Implementations
### Theme Token Definition: Legacy JS Config vs. v4 CSS-First @theme

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Legacy Tailwind v3 multi-file CSS imports combined with an external JavaScript configuration file and <alpha-value> replacement token are deprecated and trigger compilation warnings or failures in v4.
```css
/* tailwind.config.js (Deprecated in v4) */
// module.exports = {
//   theme: {
//     extend: {
//       colors: {
//         brand: {
//           500: 'rgb(var(--brand-500) / <alpha-value>)',
//         },
//       },
//     },
//   },
// };

@import "tailwindcss/base";
@import "tailwindcss/components";
@import "tailwindcss/utilities";
```

#### Production Standard (Correct)
> **Standard**: Pure CSS-first configuration using `@import "tailwindcss";` and `@theme` directives directly injects design variables into the Oxide engine with native `color-mix()` alpha transparency support.
```css
@import "tailwindcss";

@theme {
  --color-brand-500: oklch(0.65 0.24 260);
  --font-display: "Cabinet Grotesk", sans-serif;
  --spacing-18: 4.5rem;
  --breakpoint-3xl: 120rem;
}

/* Custom property automatically supports opacity modifiers like `bg-brand-500/20` */
```

### Dynamic Color Interpolation and Alpha Modifiers

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Manually applying rgba() hacks breaks with OKLCH/P3 color gamuts and violates Tailwind v4's CSS engine color resolution semantics.
```typescript
// Anti-pattern: Relying on raw RGB variable hacks for runtime transparency
export const Banner = ({ title }: { title: string }) => {
  return (
    <div
      style={{ backgroundColor: 'rgba(var(--brand-500), 0.75)' }}
      className="p-4 text-white"
    >
      <h3>{title}</h3>
    </div>
  );
};
```

#### Production Standard (Correct)
> **Standard**: Using standard Tailwind v4 opacity modifiers `bg-brand-500/75` compiles to performant `color-mix` CSS functions that preserve wide-gamut OKLCH values.
```typescript
export const Banner = ({ title }: { title: string }) => {
  // In Tailwind v4, dynamic alpha natively maps to color-mix(in oklab, var(--color-brand-500) 75%, transparent)
  return (
    <div className="p-4 text-white bg-brand-500/75 rounded-lg">
      <h3 className="font-display text-lg">{title}</h3>
    </div>
  );
};
```
Recommended MCP Servers (mcp-serverlist.com)

Equip agent with system tools to verify code for this stack.

CSS AST Analyzer MCP
Validates CSS-first directives, checking for missing @theme tokens and deprecated PostCSS directives.
Recommended Agent Skills (askills.dev)

Ready-to-use executable skill functions tailored to this stack.

Tailwind v4 Upgrade Tooling
CLI migration tool for upgrading tailwind.config.js configurations to native v4 @theme CSS blocks.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: Tailwind CSS v4 CSS-First Theme Directives & Variable Invariants

Tailwind CSS v4 CSS-First Theme Directives & Variable Invariants defines an industrial-grade behavioral standard for frontend engineering. Tailwind CSS v4 fully replaces legacy JavaScript-based configuration (`tailwind.config.js`) with native CSS-first configuration via `@import "tailwindcss";` and `@theme` blocks. Invariants mandate defining theme tokens directly as CSS custom properties within `@theme` blocks and leveraging native CSS color-mix() interpolation rather than deprecated string-substitution `<alpha-value>` functional wrappers. Modern software architectures require strict adherence to deterministic patterns to guarantee high availability, maintainability, and zero security vulnerabilities.

Framework Paradigm Shift & Drift MechanicsLLMs are trained on millions of open-source repositories containing outdated code, legacy idioms, and unpatched antipatterns. When coding assistants generate implementations for this stack, they default to common statistical tokens: Defining legacy tailwind.config.js configurations, using deprecated @config directives, or relying on rgba()/opacity function hacks instead of native @theme CSS variables. Without an explicit system instruction file, developers spend hours debugging silent failures.
Failure Modes & Production Blast Radius

Hazard Analysis: What Breaks Without This Rule

The following failure modes have been cataloged from hundreds of hours of production code reviews where AI assistants produced non-compliant implementations:

Failure ModeAI Symptom (The Anti-Pattern)SeverityProduction Impact & Remedy
AI Hallucination & Deprecation DriftDefining legacy tailwind.config.js configurations, using deprecated @config directives, or relying on rgba()/opacity function hacks instead of native @theme CSS variables.Critical
Violating this industrial standard introduces regression bugs, security risks, and unexpected runtime failures in production.
Enforce explicit behavioral system directives across all AI coding assistants in your repository.
Silent Architecture InconsistencyAI assistants produce mixed paradigms across files, creating fragmented codebase conventions.Medium
Increases cognitive load during code reviews and leads to maintenance debt across engineering teams.
Pin project conventions in .cursor/rules, CLAUDE.md, and AGENTS.md so all team agents follow identical guardrails.
Architectural Directives in Detail

Step-by-Step Production Directives

Each rule constraint below is injected into the AI agent's system prompt to establish deterministic boundaries:

1

Engineers MUST ALWAYS declare design tokens within `@theme` or `@theme inline` blocks using standard CSS custom property prefixes (e.g., `--color-*`, `--font-*`, `--breakpoint-*`, `--spacing-*`).

Engineers MUST ALWAYS declare design tokens within `@theme` or `@theme inline` blocks using standard CSS custom property prefixes (e.g., `--color-*`, `--font-*`, `--breakpoint-*`, `--spacing-*`).

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
2

Engineers MUST NOT generate or maintain `tailwind.config.js`, `tailwind.config.ts`, or `@config` directives in Tailwind CSS v4 projects.

Engineers MUST NOT generate or maintain `tailwind.config.js`, `tailwind.config.ts`, or `@config` directives in Tailwind CSS v4 projects.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
3

Code SHOULD leverage standard OKLCH color palettes and native CSS variables directly in component styles when bypassing utility classes.

Code SHOULD leverage standard OKLCH color palettes and native CSS variables directly in component styles when bypassing utility classes.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
4

Services and build tool configurations MUST use `@tailwindcss/vite`, `@tailwindcss/postcss`, or the standalone CLI instead of legacy PostCSS nesting plugins that conflict with CSS-first parsing.

Services and build tool configurations MUST use `@tailwindcss/vite`, `@tailwindcss/postcss`, or the standalone CLI instead of legacy PostCSS nesting plugins that conflict with CSS-first parsing.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
5

Components NEVER use legacy opacity functions such as `rgb(var(--color-primary) / <alpha-value>)`

Components NEVER use legacy opacity functions such as `rgb(var(--color-primary) / <alpha-value>)`; modern alpha adjustments MUST rely on utility modifiers (e.g., `bg-primary/50`) which compile to modern CSS `color-mix()`.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
Technical Questions & Answers

Frequently Asked Technical Questions

Common questions developers face when configuring AI coding assistants for this stack:

Q:Why is Tailwind CSS v4 CSS-First Theme Directives & Variable Invariants critical for AI coding assistants?

Tailwind CSS v4 fully replaces legacy JavaScript-based configuration (`tailwind.config.js`) with native CSS-first configuration via `@import "tailwindcss";` and `@theme` blocks. Invariants mandate defining theme tokens directly as CSS custom properties within `@theme` blocks and leveraging native CSS color-mix() interpolation rather than deprecated string-substitution `<alpha-value>` functional wrappers. Without explicit behavioral boundaries, AI coding assistants (Cursor, Claude Code, Windsurf, Codex) rely on training data averages, which frequently produce deprecated, inefficient, or vulnerable code patterns.

Q:How does adopting this rule prevent AI hallucinations?

This rule explicitly declares what the AI must avoid (Defining legacy tailwind.config.js configurations, using deprecated @config directives, or relying on rgba()/opacity function hacks instead of native @theme CSS variables.) and prescribes verified positive examples. Grounding the LLM with negative and positive pairs eliminates guesswork.

Q:Which AI coding environments are supported?

This specification is multi-platform compatible: Cursor (.cursor/rules/*.mdc & .cursorrules), Anthropic Claude Code (CLAUDE.md), Windsurf (.windsurfrules), Codex / Cline (AGENTS.md), and GitHub Copilot (.github/copilot-instructions.md).

Q:Can I combine this rule with other technology stacks?

Yes. Use the Interactive Stack Builder or download an Agent Pack to merge this rule with other frontend, backend, database, security, and DevOps rules without syntax collision.

Open Specification · CC BY 4.0·Free for Personal, Team & Commercial In-Repo Use

Citation & Open Source Attribution Guidelines

This specification is licensed under Creative Commons Attribution 4.0 International (CC BY 4.0). You are completely free to adapt and share this rule in your workspace. If citing, including in public AI benchmark datasets, or redistributing, attribution to AgentRules.org is required.

Related FRONTEND Rules

View all rules →
frontend
119

SolidStart 1.0 Server Functions & Async Boundaries Production Standard

SolidStart 1.0 relies on the Vinxi bundler to split `server$` closures into independent HTTP POST RPC endpoints. Direct lexical closure over client signals within `server$` scopes or failure to demarcate async boundaries with `<Suspense>` causes silent serialization failures, client-bundle secret leaks, and SSR hydration mismatches. Enforcing strict parameter passing, runtime input validation, and Solid async primitives maintains security and fine-grained reactivity across network boundaries.

frontend
119

Astro 5 Actions & Content Layer Production Standard

Enforces strict type safety and architectural correctness for Astro 5 Server Actions and the zero-waterfall Content Layer API. Prevents runtime contract mismatches, hydration mismatches, and unhandled mutation exceptions across dynamic and prerendered boundaries. Failure to follow these patterns leads to silent data fetching waterfalls, build-time cache corruptions, and unhandled server action exceptions.

frontend
51

Nuxt 4 Nitro Server Engine & Shared Directory Production Standard

Nuxt 4 enforces strict boundary segregation between client UI in the app/ directory, backend endpoints in server/, and universal contracts in shared/. Violating cross-boundary isolation or maintaining module-scoped state in Nitro server handlers causes catastrophic cross-request data corruption and hydration mismatches under concurrent production traffic. Architects must enforce request-isolated H3 event contexts, universal serialization schemas, and strict path-alias boundaries.

1 Rule in Stack

Tailwind