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: css-modern-container

Modern CSS Grid, Subgrid & Container Queries Standard

Responsive layout architecture: CSS container queries (@container), subgrid alignment, clamp() fluid typography, and zero hardcoded fixed-pixel breakpoints.

Prohibited Anti-Pattern: AI uses fixed pixel widths that break mobile viewports, or writes dozens of rigid media queries.

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Modern CSS Grid, Subgrid & Container Queries Standard - Responsive layout architecture: CSS container queries (@container), subgrid alignment, clamp() fluid typography, and zero hardcoded fixed-pixel breakpoints.
globs: **/*.css, **/*.module.css
alwaysApply: false
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/css-modern-container"
---

# Modern CSS Grid, Subgrid & Container Queries Standard

> **Severity**: MEDIUM | **Category**: frontend
> **Anti-Pattern Warning**: AI uses fixed pixel widths that break mobile viewports, or writes dozens of rigid media queries.

## System Constraints
You are a CSS layouts and responsiveness expert. Build adaptable components with CSS Container Queries (@container) and grid subgrid. Use clamp() for fluid typography. Never assign fixed pixel widths to content containers.

## Strict Guidelines
- Use container-type: inline-size on wrapper cards so child components respond to parent width rather than viewport.
- Use subgrid for child cards to align headers and footers across rows cleanly.
- Use clamp(min, val, max) for fluid fonts without step-function media query jumps.

## Bad vs Good Implementations
### Container Queries for Component Adaptability

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Viewport queries break when a component is embedded inside a narrow column or modal on desktop.
```css
/* Anti-pattern: Rigid viewport media query */
.card {
  width: 100%;
}
@media (min-width: 1024px) {
  .card-layout { display: flex; } /* Breaks if card is placed inside a 300px sidebar! */
}
```

#### Production Standard (Correct)
> **Standard**: Card adapts its layout based on its immediate container width, regardless of where it appears in the page hierarchy.
```css
/* Production Standard: Container Queries */
.card-wrapper {
  container-type: inline-size;
  container-name: card;
}

.card-layout {
  display: grid;
  grid-template-columns: 1fr;
  gap: 1rem;
}

@container card (min-width: 480px) {
  .card-layout {
    grid-template-columns: 120px 1fr;
  }
}
```
Recommended MCP Servers (mcp-serverlist.com)

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

CSS Inspector MCP
Validate layout responsiveness and overflow boundaries.
Recommended Agent Skills (askills.dev)

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

Container Query Builder
Generate responsive container query layouts.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: Modern CSS Grid, Subgrid & Container Queries Standard

Modern CSS Grid, Subgrid & Container Queries Standard defines an industrial-grade behavioral standard for frontend engineering. Responsive layout architecture: CSS container queries (@container), subgrid alignment, clamp() fluid typography, and zero hardcoded fixed-pixel breakpoints. 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 uses fixed pixel widths that break mobile viewports, or writes dozens of rigid media queries. 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 uses fixed pixel widths that break mobile viewports, or writes dozens of rigid media queries.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

Use container-type

Use container-type: inline-size on wrapper cards so child components respond to parent width rather than viewport.

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

Use subgrid for child cards to align headers and footers across rows cleanly.

Use subgrid for child cards to align headers and footers across rows cleanly.

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

Use clamp(min, val, max) for fluid fonts without step-function media query jumps.

Use clamp(min, val, max) for fluid fonts without step-function media query jumps.

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 Modern CSS Grid, Subgrid & Container Queries Standard critical for AI coding assistants?

Responsive layout architecture: CSS container queries (@container), subgrid alignment, clamp() fluid typography, and zero hardcoded fixed-pixel breakpoints. 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 uses fixed pixel widths that break mobile viewports, or writes dozens of rigid media queries.) 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

Modern