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

Tailwind CSS v4 CSS-First Theme Directives and Dynamic Interpolation Guardrail

Enforces modern Tailwind CSS v4 CSS-first configuration via pure @theme and @theme inline blocks, deprecating legacy tailwind.config.js/ts abstractions. Mandates native CSS custom properties with color-mix() runtime opacity interpolation instead of legacy RGB channel workarounds. Ensures token declarations follow v4 standard namespace conventions and CSS variable resolution across the build pipeline.

Prohibited Anti-Pattern: Persisting legacy tailwind.config.js architecture and RGB-tuple opacity hacks in Tailwind CSS v4 environments

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Tailwind CSS v4 CSS-First Theme Directives and Dynamic Interpolation Guardrail - Enforces modern Tailwind CSS v4 CSS-first configuration via pure @theme and @theme inline blocks, deprecating legacy tailwind.config.js/ts abstractions. Mandates native CSS custom properties with color-mix() runtime opacity interpolation instead of legacy RGB channel workarounds. Ensures token declarations follow v4 standard namespace conventions and CSS variable resolution across the build pipeline.
globs: src/**/*.{css,postcss,ts,tsx,js,jsx}, app/**/*.{css,postcss,ts,tsx,js,jsx}, styles/**/*.{css,postcss}
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/tailwind-v4-css-first-theme-directives"
---

# Tailwind CSS v4 CSS-First Theme Directives and Dynamic Interpolation Guardrail

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Persisting legacy tailwind.config.js architecture and RGB-tuple opacity hacks in Tailwind CSS v4 environments

## System Constraints
You are a Principal Engineer enforcing Tailwind CSS v4 CSS-First Theme Directives. Mandate absolute elimination of legacy tailwind.config.js or tailwind.config.ts configuration patterns in favor of modern @theme CSS directives. Reject outdated CSS variable RGB-triplet interpolation hacks in favor of native CSS color-mix() semantics and first-class custom property theme extensions. Prevent redundant @tailwind base/components/utilities directives and enforce @import 'tailwindcss' entry points with declarative @theme overrides.

## Strict Guidelines
- Engineers MUST ALWAYS declare design tokens and theme extensions inside pure CSS using '@theme' or '@theme inline' directives rather than creating or maintaining 'tailwind.config.js' or 'tailwind.config.ts'.
- Engineers MUST NOT define colors as raw space-separated RGB/HSL channel values (e.g., '--color-primary: 255 115 0') for alpha blending; Tailwind v4 natively supports high-gamut formats (OKLCH, Display P3, Hex) and handles dynamic opacity automatically via native CSS 'color-mix()'.
- Engineers MUST replace deprecated '@tailwind base;', '@tailwind components;', and '@tailwind utilities;' directives with modern '@import "tailwindcss";'.
- Code MUST map custom CSS variables using Tailwind v4 standard theme namespaces (e.g., '--color-*', '--font-*', '--spacing-*', '--radius-*') directly inside '@theme' blocks.
- Components NEVER construct dynamic arbitrary CSS color classes with manual alpha channel syntax like 'bg-[rgba(var(--primary-color),0.5)]'; use standard utility classes with native alpha modifier syntax such as 'bg-primary/50'.

## Bad vs Good Implementations
### Migrating Legacy tailwind.config.js Theme Configuration to v4 @theme CSS Directives

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Tailwind v4 deprecates tailwind.config.js and the three-layer @tailwind directives in favor of a single @import 'tailwindcss' engine. Storing color channels as space-separated numbers forces brittle runtime substitutions and breaks modern color spaces like OKLCH.
```css
/* globals.css - DEPRECATED v3 ARCHITECTURE */
@tailwind base;
@tailwind components;
@tailwind utilities;

:root {
  /* Anti-pattern: Storing raw channel triplets to support opacity hacks */
  --brand-primary-rgb: 99 102 241;
}

/* tailwind.config.js - ANTI-PATTERN IN v4 */
// module.exports = {
//   theme: {
//     extend: {
//       colors: {
//         brand: 'rgb(var(--brand-primary-rgb) / <alpha-value>)',
//       },
//     },
//   },
// };
```

#### Production Standard (Correct)
> **Standard**: Tailwind v4 imports the entire framework via @import 'tailwindcss' and processes custom design tokens directly inside the CSS AST via @theme directives. Colors defined in OKLCH automatically support utility opacity modifiers (e.g., bg-brand-500/50) using modern CSS color-mix() under the hood.
```css
/* src/styles/globals.css - MODERN v4 CSS-FIRST DIRECTIVES */
@import "tailwindcss";

@theme {
  /* Modern OKLCH color scale with native token namespace */
  --color-brand-50: oklch(0.97 0.014 254.604);
  --color-brand-500: oklch(0.62 0.214 259.815);
  --color-brand-900: oklch(0.32 0.134 262.188);

  /* Typography and geometry token namespaces */
  --font-display: 'Inter Variable', sans-serif;
  --radius-card: 0.75rem;
}

/* Alpha blending works out of the box via color-mix(): class='bg-brand-500/50' */
```

### Component Consumption of v4 Dynamic Theme Variables

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Manually invoking arbitrary variable syntax and rgba wrappers completely bypasses Tailwind's optimization pipeline, bloats generated CSS, and causes runtime rendering inconsistencies.
```typescript
import React from 'react';

// Anti-pattern: Manual CSS variable references and arbitrary alpha calculations
export const PromoBadge = ({ label }: { label: string }) => {
  return (
    <span 
      className="px-3 py-1 text-xs font-semibold rounded-[var(--radius-card)] bg-[rgba(var(--brand-primary-rgb),0.15)] text-[rgb(var(--brand-primary-rgb))]"
    >
      {label}
    </span>
  );
};
```

#### Production Standard (Correct)
> **Standard**: Because '--radius-card' and '--color-brand-*' were registered inside the @theme block, Tailwind v4 automatically exposes standard utility classes ('rounded-card', 'bg-brand-500/15', 'text-brand-900') with built-in color-mix() alpha compositing.
```typescript
import React from 'react';

// Production Invariant: Direct utility mapping using @theme tokens and native alpha modifiers
export const PromoBadge = ({ label }: { label: string }) => {
  return (
    <span className="px-3 py-1 text-xs font-semibold rounded-card bg-brand-500/15 text-brand-900 dark:text-brand-50">
      {label}
    </span>
  );
};
```
Recommended MCP Servers (mcp-serverlist.com)

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

PostCSS AST Inspector MCP
Inspects and validates CSS AST trees to ensure @theme directives and color-mix functions compile accurately across Tailwind v4 build pipelines.
Recommended Agent Skills (askills.dev)

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

Tailwind v4 Migration Skill
CLI automation tool for transforming legacy tailwind.config.js files into pure CSS @theme blocks and verifying color-mix compatibility.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: Tailwind CSS v4 CSS-First Theme Directives and Dynamic Interpolation Guardrail

Tailwind CSS v4 CSS-First Theme Directives and Dynamic Interpolation Guardrail defines an industrial-grade behavioral standard for frontend engineering. Enforces modern Tailwind CSS v4 CSS-first configuration via pure @theme and @theme inline blocks, deprecating legacy tailwind.config.js/ts abstractions. Mandates native CSS custom properties with color-mix() runtime opacity interpolation instead of legacy RGB channel workarounds. Ensures token declarations follow v4 standard namespace conventions and CSS variable resolution across the build pipeline. 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 legacy tailwind.config.js architecture and RGB-tuple opacity hacks 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 legacy tailwind.config.js architecture and RGB-tuple opacity hacks 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 ALWAYS declare design tokens and theme extensions inside pure CSS using '@theme' or '@theme inline' directives rather than creating or maintaining 'tailwind.config.js' or 'tailwind.config.ts'.

Engineers MUST ALWAYS declare design tokens and theme extensions inside pure CSS using '@theme' or '@theme inline' directives rather than creating or maintaining 'tailwind.config.js' or 'tailwind.config.ts'.

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 define colors as raw space-separated RGB/HSL channel values (e.g., '--color-primary

Engineers MUST NOT define colors as raw space-separated RGB/HSL channel values (e.g., '--color-primary: 255 115 0') for alpha blending; Tailwind v4 natively supports high-gamut formats (OKLCH, Display P3, Hex) and handles dynamic opacity automatically via native 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.
3

Engineers MUST replace deprecated '@tailwind base

Engineers MUST replace deprecated '@tailwind base;', '@tailwind components;', and '@tailwind utilities;' directives with modern '@import "tailwindcss";'.

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

Code MUST map custom CSS variables using Tailwind v4 standard theme namespaces (e.g., '--color-*', '--font-*', '--spacing-*', '--radius-*') directly inside '@theme' blocks.

Code MUST map custom CSS variables using Tailwind v4 standard theme namespaces (e.g., '--color-*', '--font-*', '--spacing-*', '--radius-*') directly inside '@theme' blocks.

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 construct dynamic arbitrary CSS color classes with manual alpha channel syntax like 'bg-[rgba(var(--primary-color),0.5)]'

Components NEVER construct dynamic arbitrary CSS color classes with manual alpha channel syntax like 'bg-[rgba(var(--primary-color),0.5)]'; use standard utility classes with native alpha modifier syntax such as 'bg-primary/50'.

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 and Dynamic Interpolation Guardrail critical for AI coding assistants?

Enforces modern Tailwind CSS v4 CSS-first configuration via pure @theme and @theme inline blocks, deprecating legacy tailwind.config.js/ts abstractions. Mandates native CSS custom properties with color-mix() runtime opacity interpolation instead of legacy RGB channel workarounds. Ensures token declarations follow v4 standard namespace conventions and CSS variable resolution across the build pipeline. 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 legacy tailwind.config.js architecture and RGB-tuple opacity hacks 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

Tailwind