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-production-standard

Tailwind CSS v4 CSS-First Declarative Theme and Color Architecture Guardrails

Tailwind CSS v4 replaces JavaScript-based configurations with native CSS-first declarations via `@theme` directives and standard CSS custom properties. Enforcing this invariant prevents silent build regressions, eliminates obsolete CSS opacity-channel string hacks, and unlocks native CSS color gamut interpolation (OKLCH) via dynamic `color-mix()`. Projects migrating to or initialized with v4 must strictly maintain styling configuration inside CSS boundary layers.

Prohibited Anti-Pattern: Retaining legacy tailwind.config.js files, obsolete RGB tuple opacity workarounds, and deprecated PostCSS plugin pipelines in Tailwind CSS v4 builds.

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Tailwind CSS v4 CSS-First Declarative Theme and Color Architecture Guardrails - Tailwind CSS v4 replaces JavaScript-based configurations with native CSS-first declarations via `@theme` directives and standard CSS custom properties. Enforcing this invariant prevents silent build regressions, eliminates obsolete CSS opacity-channel string hacks, and unlocks native CSS color gamut interpolation (OKLCH) via dynamic `color-mix()`. Projects migrating to or initialized with v4 must strictly maintain styling configuration inside CSS boundary layers.
globs: **/*.css, src/**/*.{ts,tsx}, app/**/*.{ts,tsx}, vite.config.{ts,js}
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/tailwind-v4-css-first-theme-production-standard"
---

# Tailwind CSS v4 CSS-First Declarative Theme and Color Architecture Guardrails

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Retaining legacy tailwind.config.js files, obsolete RGB tuple opacity workarounds, and deprecated PostCSS plugin pipelines in Tailwind CSS v4 builds.

## System Constraints
You are a Principal Software Architect enforcing Tailwind CSS v4 architectural standards. You must reject any creation or maintenance of `tailwind.config.js` or `tailwind.config.ts`. Enforce the `@import "tailwindcss";` entrypoint, configure design tokens strictly via `@theme` CSS blocks, and mandate modern CSS color spaces (such as OKLCH) leveraging native `color-mix()` alpha-channel evaluation. Flag any deprecated utility classes, obsolete PostCSS configurations, and legacy RGB channel variables.

## Strict Guidelines
- Engineers MUST configure all theme tokens within CSS stylesheets using `@theme` or `@theme inline` blocks rather than creating a `tailwind.config.{js,ts,mjs,cjs}` file.
- Engineers MUST import Tailwind v4 using standard `@import "tailwindcss";` at the root stylesheet rather than legacy `@tailwind base; @tailwind components; @tailwind utilities;` directives.
- Engineers MUST declare color variables using valid CSS color formats (preferably `oklch(...)` or hex/P3) and MUST NOT define space-delimited raw RGB/HSL channel numbers for opacity substitution.
- Engineers MUST use modern opacity syntax (`bg-brand/50`) which Tailwind v4 maps directly to CSS `color-mix(in oklab, var(--color-brand) 50%, transparent)` natively.
- Build toolchains MUST migrate from legacy `postcss-import` and PostCSS `tailwindcss` plugin packages to dedicated bundler plugins such as `@tailwindcss/vite` or `@tailwindcss/postcss` v4.
- Components NEVER use legacy class names deprecated or renamed in v4 (e.g., use `shadow-xs` instead of `shadow-sm`, `shadow-sm` instead of default shadow, `inset-shadow-*` instead of obsolete custom shadow workarounds).
- Engineers MUST namespace theme token variables systematically (e.g., `--color-*`, `--font-*`, `--spacing-*`, `--breakpoint-*`, `--ease-*`) to ensure Tailwind auto-generates corresponding utility classes.

## Bad vs Good Implementations
### Theme Token Configuration: Legacy JS Config vs. Modern CSS-First @theme Block

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Tailwind v4 deprecates `tailwind.config.js` entirely. Relying on raw RGB channel strings to support opacity prevents utilizing modern wide-gamut OKLCH/Display P3 color spaces and breaks v4's CSS engine parser.
```css
/* ❌ BAD: Legacy tailwind.config.js pattern and RGB opacity hack in CSS */
:root {
  --primary-rgb: 99, 102, 241; /* Obsolete string trick */
}

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

#### Production Standard (Correct)
> **Standard**: Tailwind v4 automatically discovers `--color-brand-primary` within the `@theme` block, synthesizes utilities like `bg-brand-primary`, `text-brand-primary`, and supports automatic dynamic alpha modifier parsing using `color-mix()` without JS configuration files.
```css
/* ✅ GOOD: Native CSS-First Tailwind v4 entrypoint with @theme token block */
@import "tailwindcss";

@theme {
  --color-brand-primary: oklch(0.62 0.24 264.5);
  --color-brand-surface: oklch(0.98 0.01 264.5);
  --font-sans: 'Inter Variable', system-ui, sans-serif;
  --spacing-18: 4.5rem;
  --ease-fluid: cubic-bezier(0.3, 0, 0, 1);
}
```

### Vite Toolchain and Component Consumption

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Legacy CSS arbitrary RGB opacity hacks and deprecated utilities like `text-opacity-*` are anti-patterns in Tailwind v4. The component relies on obsolete v3 configuration practices.
```typescript
// ❌ BAD: Attempting to invoke theme() via obsolete postcss setup or manual opacity tricks
// vite.config.ts importing legacy postcss runner
export const BadHeroCard = () => {
  return (
    // Anti-pattern: reliance on old opacity hack and deprecated v3 utilities
    <div className="bg-[rgb(var(--primary-rgb)/0.8)] shadow-sm text-opacity-80">
      <h1 className="font-[Inter] text-primary">Legacy Config Consumer</h1>
    </div>
  );
};
```

#### Production Standard (Correct)
> **Standard**: The component uses v4 native class names and slash opacity modifiers (`bg-brand-primary/80`) which compile down cleanly using standard `color-mix()` while sourcing token variables declared directly in the stylesheet.
```typescript
// ✅ GOOD: Modern Tailwind v4 Vite plugin setup and declarative utility usage
// vite.config.ts uses: import tailwindcss from '@tailwindcss/vite'; plugins: [tailwindcss()]

export const HeroCard = () => {
  return (
    // In Tailwind v4, opacity uses modern color-mix automatically: bg-brand-primary/80
    // Theme fonts and new shadow scale (shadow-xs/shadow-sm) resolve directly from @theme
    <div className="bg-brand-primary/80 shadow-xs border border-brand-surface/20 rounded-xl p-6">
      <h1 className="font-sans text-brand-surface font-semibold">
        Tailwind v4 Declarative Token Consumer
      </h1>
    </div>
  );
};
```
Recommended MCP Servers (mcp-serverlist.com)

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

CSS AST Analyzer MCP
Inspects project CSS tokens, validates @theme declarations, and flags obsolete PostCSS and Tailwind v3 configuration files.
Recommended Agent Skills (askills.dev)

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

Tailwind v4 Migration & Audit Skill
Runs automated audit commands to detect legacy tailwind.config.* files, obsolete utilities, and migrates configs to modern @theme CSS directives.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: Tailwind CSS v4 CSS-First Declarative Theme and Color Architecture Guardrails

Tailwind CSS v4 CSS-First Declarative Theme and Color Architecture Guardrails defines an industrial-grade behavioral standard for frontend engineering. Tailwind CSS v4 replaces JavaScript-based configurations with native CSS-first declarations via `@theme` directives and standard CSS custom properties. Enforcing this invariant prevents silent build regressions, eliminates obsolete CSS opacity-channel string hacks, and unlocks native CSS color gamut interpolation (OKLCH) via dynamic `color-mix()`. Projects migrating to or initialized with v4 must strictly maintain styling configuration inside CSS boundary layers. 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: Retaining legacy tailwind.config.js files, obsolete RGB tuple opacity workarounds, and deprecated PostCSS plugin pipelines in Tailwind CSS v4 builds. 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 DriftRetaining legacy tailwind.config.js files, obsolete RGB tuple opacity workarounds, and deprecated PostCSS plugin pipelines in Tailwind CSS v4 builds.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 configure all theme tokens within CSS stylesheets using `@theme` or `@theme inline` blocks rather than creating a `tailwind.config.{js,ts,mjs,cjs}` file.

Engineers MUST configure all theme tokens within CSS stylesheets using `@theme` or `@theme inline` blocks rather than creating a `tailwind.config.{js,ts,mjs,cjs}` file.

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 import Tailwind v4 using standard `@import "tailwindcss"

Engineers MUST import Tailwind v4 using standard `@import "tailwindcss";` at the root stylesheet rather than legacy `@tailwind base; @tailwind components; @tailwind utilities;` directives.

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 declare color variables using valid CSS color formats (preferably `oklch(...)` or hex/P3) and MUST NOT define space-delimited raw RGB/HSL channel numbers for opacity substitution.

Engineers MUST declare color variables using valid CSS color formats (preferably `oklch(...)` or hex/P3) and MUST NOT define space-delimited raw RGB/HSL channel numbers for opacity substitution.

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

Engineers MUST use modern opacity syntax (`bg-brand/50`) which Tailwind v4 maps directly to CSS `color-mix(in oklab, var(--color-brand) 50%, transparent)` natively.

Engineers MUST use modern opacity syntax (`bg-brand/50`) which Tailwind v4 maps directly to CSS `color-mix(in oklab, var(--color-brand) 50%, transparent)` natively.

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

Build toolchains MUST migrate from legacy `postcss-import` and PostCSS `tailwindcss` plugin packages to dedicated bundler plugins such as `@tailwindcss/vite` or `@tailwindcss/postcss` v4.

Build toolchains MUST migrate from legacy `postcss-import` and PostCSS `tailwindcss` plugin packages to dedicated bundler plugins such as `@tailwindcss/vite` or `@tailwindcss/postcss` v4.

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

Components NEVER use legacy class names deprecated or renamed in v4 (e.g., use `shadow-xs` instead of `shadow-sm`, `shadow-sm` instead of default shadow, `inset-shadow-*` instead of obsolete custom shadow workarounds).

Components NEVER use legacy class names deprecated or renamed in v4 (e.g., use `shadow-xs` instead of `shadow-sm`, `shadow-sm` instead of default shadow, `inset-shadow-*` instead of obsolete custom shadow workarounds).

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

Engineers MUST namespace theme token variables systematically (e.g., `--color-*`, `--font-*`, `--spacing-*`, `--breakpoint-*`, `--ease-*`) to ensure Tailwind auto-generates corresponding utility classes.

Engineers MUST namespace theme token variables systematically (e.g., `--color-*`, `--font-*`, `--spacing-*`, `--breakpoint-*`, `--ease-*`) to ensure Tailwind auto-generates corresponding 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.
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 Declarative Theme and Color Architecture Guardrails critical for AI coding assistants?

Tailwind CSS v4 replaces JavaScript-based configurations with native CSS-first declarations via `@theme` directives and standard CSS custom properties. Enforcing this invariant prevents silent build regressions, eliminates obsolete CSS opacity-channel string hacks, and unlocks native CSS color gamut interpolation (OKLCH) via dynamic `color-mix()`. Projects migrating to or initialized with v4 must strictly maintain styling configuration inside CSS boundary layers. 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 (Retaining legacy tailwind.config.js files, obsolete RGB tuple opacity workarounds, and deprecated PostCSS plugin pipelines in Tailwind CSS v4 builds.) 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