AgentRules.org
RulesStacksClientsAuditorPrunerSelf-HealRFCsBenchmarkCLICI/CDAuthorsSubmit
This specification is maintained by the AgentRules Working Group. Have enhancements or want to claim maintainership?Submit Specification →
frontendmedium PriorityID: tailwind-v4-container-fluid

Tailwind CSS v4 Container Queries & Fluid Typography System

Modern modular styling with Tailwind CSS v4 container queries (@container) and CSS clamp() fluid scales. Forbids fixed viewport breakpoints on nested components, eliminates brittle @apply statements, and enforces pure CSS theme variables.

Prohibited Anti-Pattern: AI binds nested card components to viewport breakpoints (md: flex), breaking responsive layouts inside sidebars.

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Tailwind CSS v4 Container Queries & Fluid Typography System - Modern modular styling with Tailwind CSS v4 container queries (@container) and CSS clamp() fluid scales. Forbids fixed viewport breakpoints on nested components, eliminates brittle @apply statements, and enforces pure CSS theme variables.
globs: **/*.tsx, **/*.jsx, src/**/*.css
alwaysApply: false
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/tailwind-v4-container-fluid"
---

# Tailwind CSS v4 Container Queries & Fluid Typography System

> **Severity**: MEDIUM | **Category**: frontend
> **Anti-Pattern Warning**: AI binds nested card components to viewport breakpoints (md: flex), breaking responsive layouts inside sidebars.

## System Constraints
You are a CSS architecture and design systems expert. In Tailwind CSS v4, avoid coupling reusable components to viewport breakpoints (sm:, md:, lg:). Use parent '@container' wrappers and child '@sm:', '@md:', '@lg:' container queries so components respond to their actual parent container width.

## Strict Guidelines
- Mark responsive component wrapper elements with '@container' and style children using container query utilities ('@md:flex-row', '@sm:hidden').
- Define fluid typography in '@theme' using modern CSS clamp() scales instead of switching text sizes across dozens of media breakpoints.
- Never use '@apply' in CSS files; write direct utilities in JSX or compose them using tailwind-merge (clsx/cn).
- Use CSS native variables with the new '@theme' directive instead of deprecated tailwind.config.js theme.extend.

## Bad vs Good Implementations
### Container Queries (@container) vs Brittle Viewport Media Queries

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: When inserted into a narrow layout column, the card assumes desktop width and overflows horizontally.
```tsx
// ANTI-PATTERN: Viewport-bound card breaks when placed inside a 300px sidebar!
export function UserProfileCard({ user }: { user: User }) {
  return (
    // Even if parent is narrow, on a 1440px desktop screen 'md:flex' triggers!
    <div className="flex flex-col md:flex-row items-center gap-4 p-4 border">
      <img src={user.avatar} className="w-16 h-16 rounded-full" />
      <div className="md:text-left text-center">
        <h3>{user.name}</h3>
        <p>{user.bio}</p>
      </div>
    </div>
  );
}
```

#### Production Standard (Correct)
> **Standard**: Card gracefully stacks vertically when placed in sidebars and switches to side-by-side layout only when its immediate container has sufficient width.
```tsx
// PRODUCTION STANDARD: Parent @container with child @md: container query
export function UserProfileCard({ user }: { user: User }) {
  return (
    // Container context: Adapts based on actual component box width!
    <div className="@container w-full">
      <div className="flex flex-col @md:flex-row items-center gap-4 p-4 rounded-xl border border-slate-200 bg-white shadow-sm">
        <img src={user.avatar} className="h-14 w-14 shrink-0 rounded-full object-cover" />
        <div className="text-center @md:text-left min-w-0 flex-1">
          <h3 className="text-sm font-semibold text-slate-900 truncate">{user.name}</h3>
          <p className="text-xs text-slate-500 line-clamp-2">{user.bio}</p>
        </div>
      </div>
    </div>
  );
}
```

### Fluid Typography via CSS clamp() in Tailwind v4 @theme

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Requires jumpy layout shifts at breakpoint thresholds and bloated CSS declarations.
```css
/* ANTI-PATTERN: Switching font size at 5 different viewport breakpoints */
.hero-title {
  font-size: 1.5rem;
}
@media (min-width: 640px) { .hero-title { font-size: 2rem; } }
@media (min-width: 1024px) { .hero-title { font-size: 3rem; } }
```

#### Production Standard (Correct)
> **Standard**: Dynamically scales typography smoothly between minimum and maximum bounds across any display resolution.
```css
/* PRODUCTION STANDARD: Continuous smooth fluid typography scale */
@theme {
  --font-fluid-hero: clamp(1.75rem, 1.25rem + 2.5vw, 3.5rem);
  --font-fluid-sub: clamp(1rem, 0.9rem + 0.5vw, 1.25rem);
}
```
Recommended MCP Servers (mcp-serverlist.com)

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

Tailwind v4 CSS Inspector
Inspect container query dimensions and compute effective fluid CSS values.
Recommended Agent Skills (askills.dev)

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

Tailwind v4 Container Query Generator
Convert viewport breakpoint layouts into modular @container query components.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: Tailwind CSS v4 Container Queries & Fluid Typography System

Tailwind CSS v4 Container Queries & Fluid Typography System defines an industrial-grade behavioral standard for frontend engineering. Modern modular styling with Tailwind CSS v4 container queries (@container) and CSS clamp() fluid scales. Forbids fixed viewport breakpoints on nested components, eliminates brittle @apply statements, and enforces pure CSS theme variables. 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: AI binds nested card components to viewport breakpoints (md: flex), breaking responsive layouts inside sidebars. 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 DriftAI binds nested card components to viewport breakpoints (md: flex), breaking responsive layouts inside sidebars.High
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

Mark responsive component wrapper elements with '@container' and style children using container query utilities ('@md

Mark responsive component wrapper elements with '@container' and style children using container query utilities ('@md:flex-row', '@sm:hidden').

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

Define fluid typography in '@theme' using modern CSS clamp() scales instead of switching text sizes across dozens of media breakpoints.

Define fluid typography in '@theme' using modern CSS clamp() scales instead of switching text sizes across dozens of media breakpoints.

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

Never use '@apply' in CSS files

Never use '@apply' in CSS files; write direct utilities in JSX or compose them using tailwind-merge (clsx/cn).

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

Use CSS native variables with the new '@theme' directive instead of deprecated tailwind.config.js theme.extend.

Use CSS native variables with the new '@theme' directive instead of deprecated tailwind.config.js theme.extend.

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 Container Queries & Fluid Typography System critical for AI coding assistants?

Modern modular styling with Tailwind CSS v4 container queries (@container) and CSS clamp() fluid scales. Forbids fixed viewport breakpoints on nested components, eliminates brittle @apply statements, and enforces pure CSS theme variables. 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 (AI binds nested card components to viewport breakpoints (md: flex), breaking responsive layouts inside sidebars.) 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