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-directives-guardrail

Mandating Tailwind CSS v4 CSS-First Theme Directives and Native Color Interpolation

Tailwind CSS v4 fully deprecates JavaScript-based configuration (`tailwind.config.js`) in favor of native CSS-first configuration via `@theme` directives and modern CSS variables. Engineering agents must enforce `@import "tailwindcss";`, replace legacy `@tailwind` directives, and map design tokens exclusively through CSS custom properties with native color space interpolation (OKLCH) instead of legacy hex-based opacity workarounds.

Prohibited Anti-Pattern: Persisting tailwind.config.js and legacy @tailwind directives in Tailwind CSS v4 environments

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Mandating Tailwind CSS v4 CSS-First Theme Directives and Native Color Interpolation - Tailwind CSS v4 fully deprecates JavaScript-based configuration (`tailwind.config.js`) in favor of native CSS-first configuration via `@theme` directives and modern CSS variables. Engineering agents must enforce `@import "tailwindcss";`, replace legacy `@tailwind` directives, and map design tokens exclusively through CSS custom properties with native color space interpolation (OKLCH) instead of legacy hex-based opacity workarounds.
globs: **/*.css, src/**/*.{ts,tsx}, app/**/*.{ts,tsx}
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/tailwind-v4-css-first-theme-directives-guardrail"
---

# Mandating Tailwind CSS v4 CSS-First Theme Directives and Native Color Interpolation

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Persisting tailwind.config.js and legacy @tailwind directives in Tailwind CSS v4 environments

## System Constraints
You are a Principal Frontend Architect enforcing Tailwind CSS v4 architectural standards. You MUST reject all generation of `tailwind.config.js` or `tailwind.config.ts`, legacy `@tailwind base;` directives, and manual opacity calculation hacks. Mandate `@import "tailwindcss";`, pure `@theme` blocks, CSS custom property token definitions using modern OKLCH color spaces, and standard CSS `color-mix()` interpolation.

## Strict Guidelines
- Engineers MUST NEVER create or reference `tailwind.config.{js,cjs,mjs,ts}` in Tailwind CSS v4 projects.
- Engineers MUST replace legacy `@tailwind base; @tailwind components; @tailwind utilities;` directives with a single `@import "tailwindcss";` entrypoint.
- Engineers MUST configure theme tokens, breakpoints, typography, and color scales directly in CSS using the `@theme` block (or `@theme inline` / `@theme default`).
- Design token colors in `@theme` MUST be defined using modern perceptual color spaces (preferably `oklch(...)`) to support seamless opacity modifications and high dynamic range displays.
- Dynamic color adjustments and variable-driven opacity MUST leverage native CSS `color-mix()` syntax instead of legacy string interpolation or manual opacity utility hacks.
- Custom arbitrary values referencing theme variables MUST reference CSS custom properties directly via `var(--*)` syntax matching the `@theme` token definitions.
- Custom plugins MUST be configured via CSS functional directives (`@utility`, `@variant`) rather than JavaScript `plugins` arrays.

## Bad vs Good Implementations
### Configuring Global Theme Tokens (CSS-First vs Legacy JS)

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Tailwind v4 deprecates the `@tailwind` triplet directives and `tailwind.config.js`. The complex `<alpha-value>` CSS variable hack is obsolete and fragile.
```css
/* Legacy Tailwind v3 Architecture: globals.css */
@tailwind base;
@tailwind components;
@tailwind utilities;

/* Requires external tailwind.config.js with theme.extend.colors: {
     brand: '#3b82f6',
     surface: 'rgba(var(--surface), <alpha-value>)'
   } */
```

#### Production Standard (Correct)
> **Standard**: Defines theme variables natively in CSS using `@theme`. Tailwind v4 automatically exposes these tokens as utility classes (`bg-brand`, `font-display`) and provides native opacity modifier support (`bg-brand/50`) without JS overhead.
```css
/* Modern Tailwind v4 Architecture: app.css */
@import "tailwindcss";

@theme {
  --color-brand: oklch(0.62 0.21 259.8);
  --color-brand-muted: oklch(0.85 0.08 259.8);
  --color-surface: oklch(0.98 0.01 260);

  --font-display: 'Inter', -apple-system, BlinkMacSystemFont, sans-serif;
  --breakpoint-3xl: 120rem;
}
```

### Dynamic Theme Variable Interpolation in Component Code

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Direct hex string concatenation fails with standard design tokens, breaks under wide-gamut CSS color formats like OKLCH, and accesses internal implementation details (`--tw-border-opacity`).
```typescript
// Bad: Relying on legacy arbitrary variable wrappers and hex interpolation
import React from 'react';

export const BadStatusBadge = ({ statusColor }: { statusColor: string }) => {
  // Anti-pattern: String concatenation with hex opacity and obsolete config classes
  return (
    <span
      style={{ backgroundColor: `${statusColor}1A`, color: statusColor }}
      className="px-2.5 py-0.5 rounded-full text-xs font-semibold border border-[var(--tw-border-opacity)]"
    >
      Active
    </span>
  );
};
```

#### Production Standard (Correct)
> **Standard**: Uses standard CSS `color-mix()` targeting the OKLCH color space for robust dynamic opacity derivation that aligns perfectly with Tailwind v4's internal color engine.
```typescript
// Good: CSS-first native color interpolation and modern arbitrary styling
import React, { CSSProperties } from 'react';

interface StatusBadgeProps {
  tokenColorVariable: string; // e.g., 'var(--color-brand)'
}

export const GoodStatusBadge = ({ tokenColorVariable }: StatusBadgeProps) => {
  const dynamicStyles: CSSProperties = {
    backgroundColor: `color-mix(in oklch, ${tokenColorVariable} 15%, transparent)`,
    color: tokenColorVariable,
    borderColor: `color-mix(in oklch, ${tokenColorVariable} 30%, transparent)`,
  };

  return (
    <span
      style={dynamicStyles}
      className="inline-flex items-center px-2.5 py-0.5 rounded-full text-xs font-semibold border"
    >
      Active
    </span>
  );
};
```
Recommended MCP Servers (mcp-serverlist.com)

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

Tailwind v4 Documentation Fetcher
Retrieves official Tailwind CSS v4 migration guides, `@theme` token references, and `@utility` directive specifications directly from documentation mirrors.
Recommended Agent Skills (askills.dev)

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

Tailwind v4 Upgrade Validator
CLI tool that scans the repository to detect deprecated `tailwind.config.*` files, legacy `@tailwind` directives, and incompatible PostCSS plugin chains.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: Mandating Tailwind CSS v4 CSS-First Theme Directives and Native Color Interpolation

Mandating Tailwind CSS v4 CSS-First Theme Directives and Native Color Interpolation defines an industrial-grade behavioral standard for frontend engineering. Tailwind CSS v4 fully deprecates JavaScript-based configuration (`tailwind.config.js`) in favor of native CSS-first configuration via `@theme` directives and modern CSS variables. Engineering agents must enforce `@import "tailwindcss";`, replace legacy `@tailwind` directives, and map design tokens exclusively through CSS custom properties with native color space interpolation (OKLCH) instead of legacy hex-based opacity workarounds. 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: Persisting tailwind.config.js and legacy @tailwind directives in Tailwind CSS v4 environments 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 DriftPersisting tailwind.config.js and legacy @tailwind directives in Tailwind CSS v4 environmentsCritical
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 NEVER create or reference `tailwind.config.{js,cjs,mjs,ts}` in Tailwind CSS v4 projects.

Engineers MUST NEVER create or reference `tailwind.config.{js,cjs,mjs,ts}` 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.
2

Engineers MUST replace legacy `@tailwind base

Engineers MUST replace legacy `@tailwind base; @tailwind components; @tailwind utilities;` directives with a single `@import "tailwindcss";` entrypoint.

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

Engineers MUST configure theme tokens, breakpoints, typography, and color scales directly in CSS using the `@theme` block (or `@theme inline` / `@theme default`).

Engineers MUST configure theme tokens, breakpoints, typography, and color scales directly in CSS using the `@theme` block (or `@theme inline` / `@theme default`).

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

Design token colors in `@theme` MUST be defined using modern perceptual color spaces (preferably `oklch(...)`) to support seamless opacity modifications and high dynamic range displays.

Design token colors in `@theme` MUST be defined using modern perceptual color spaces (preferably `oklch(...)`) to support seamless opacity modifications and high dynamic range displays.

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

Dynamic color adjustments and variable-driven opacity MUST leverage native CSS `color-mix()` syntax instead of legacy string interpolation or manual opacity utility hacks.

Dynamic color adjustments and variable-driven opacity MUST leverage native CSS `color-mix()` syntax instead of legacy string interpolation or manual opacity utility hacks.

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.
6

Custom arbitrary values referencing theme variables MUST reference CSS custom properties directly via `var(--*)` syntax matching the `@theme` token definitions.

Custom arbitrary values referencing theme variables MUST reference CSS custom properties directly via `var(--*)` syntax matching the `@theme` token definitions.

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.
7

Custom plugins MUST be configured via CSS functional directives (`@utility`, `@variant`) rather than JavaScript `plugins` arrays.

Custom plugins MUST be configured via CSS functional directives (`@utility`, `@variant`) rather than JavaScript `plugins` arrays.

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 Mandating Tailwind CSS v4 CSS-First Theme Directives and Native Color Interpolation critical for AI coding assistants?

Tailwind CSS v4 fully deprecates JavaScript-based configuration (`tailwind.config.js`) in favor of native CSS-first configuration via `@theme` directives and modern CSS variables. Engineering agents must enforce `@import "tailwindcss";`, replace legacy `@tailwind` directives, and map design tokens exclusively through CSS custom properties with native color space interpolation (OKLCH) instead of legacy hex-based opacity workarounds. 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 (Persisting tailwind.config.js and legacy @tailwind directives in Tailwind CSS v4 environments) 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

Mandating