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: nextjs15-dynamic-io-ppr-boundaries

Next.js 15 Dynamic IO and PPR Asynchronous Boundary Enforcement

Next.js 15 Dynamic IO with Partial Prerendering (PPR) mandates that dynamic data sources (cookies, headers, searchParams, and uncached dynamic fetches) are quarantined behind strict React Suspense boundaries. Top-level synchronous or layout-level un-suspended dynamic accesses de-opt the static shell, leak contextual request state into shared prerender buffers, and trigger client hydration mismatch panics.

Prohibited Anti-Pattern: Awaiting dynamic request APIs at root page/layout level without Suspense encapsulation, collapsing PPR into SSR

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Next.js 15 Dynamic IO and PPR Asynchronous Boundary Enforcement - Next.js 15 Dynamic IO with Partial Prerendering (PPR) mandates that dynamic data sources (cookies, headers, searchParams, and uncached dynamic fetches) are quarantined behind strict React Suspense boundaries. Top-level synchronous or layout-level un-suspended dynamic accesses de-opt the static shell, leak contextual request state into shared prerender buffers, and trigger client hydration mismatch panics.
globs: app/**/*.{ts,tsx}, src/app/**/*.{ts,tsx}
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/nextjs15-dynamic-io-ppr-boundaries"
---

# Next.js 15 Dynamic IO and PPR Asynchronous Boundary Enforcement

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Awaiting dynamic request APIs at root page/layout level without Suspense encapsulation, collapsing PPR into SSR

## System Constraints
You are a Principal Software Architect enforcing Next.js 15 Dynamic IO and Partial Prerendering (PPR) architectural boundaries. Mandate strict separation between the static prerendered HTML shell and dynamic streaming micro-promises. Prevent any top-level layout de-opt, unauthorized access of request-specific stores within cached scopes, and client hydration mismatches.

## Strict Guidelines
- Engineers MUST ALWAYS isolate dynamic data reads (`cookies()`, `headers()`, `searchParams`, uncached DB calls) inside dedicated leaf Server Components wrapped in a `<Suspense fallback={<Skeleton />}>` boundary.
- Engineers MUST NOT `await` dynamic APIs (`await cookies()`, `await headers()`, or dynamic `params`/`searchParams` promises) at the root level of a layout or static page component, as this de-opts the static prerender shell.
- Components NEVER access request-specific contextual state (such as user session IDs or bearer tokens) inside functions or files annotated with `'use cache'`, preventing cross-tenant data leakage in the shared data cache.
- Code SHOULD pass dynamic streaming promises directly into Client Components using the React 19 `use()` API inside suspended subtrees rather than blocking the Server Component render cycle.
- Services MUST configure fine-grained cache invalidation using `cacheTag()` and `cacheLife()` inside explicit `'use cache'` scopes instead of relying on legacy route segment configs (`export const dynamic = 'force-dynamic'`).
- Components MUST provide deterministic, structurally identical HTML skeletons in Suspense fallbacks that mirror the resolved DOM nodes to eliminate layout shifts and hydration mismatch warnings.

## Bad vs Good Implementations
### Dynamic IO and PPR Suspense Boundary Separation

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Awaiting `cookies()` directly within the root `DashboardPage` forces the entire page tree to resolve at request time. This kills the static prerendered shell benefit of PPR, introduces server-side rendering latency for the entire viewport, and risks hydration stalls.
```typescript
import { cookies } from 'next/headers';
import { Suspense } from 'react';

// ANTI-PATTERN: Awaiting cookies at the top-level Page de-opts the entire
// route from Partial Prerendering. The static shell cannot be generated at build time.
export default async function DashboardPage() {
  const cookieStore = await cookies();
  const token = cookieStore.get('session_token')?.value;
  const user = await fetchUserData(token);

  return (
    <main className="dashboard-container">
      <header className="static-banner">
        <h1>Application Dashboard</h1>
      </header>
      <section className="user-profile">
        <p>Welcome back, {user.name}!</p>
      </section>
    </main>
  );
}

async function fetchUserData(token?: string) {
  const res = await fetch(`https://api.internal/user`, {
    headers: { Authorization: `Bearer ${token}` },
  });
  return res.json();
}
```

#### Production Standard (Correct)
> **Standard**: The page exports a synchronous, statically analyzable outer shell rendered at build time and cached on the edge. The dynamic `cookies()` dependency is strictly isolated inside `<DynamicUserProfile />` wrapped in `<Suspense>`, preserving PPR streaming guarantees and fast time-to-first-byte.
```typescript
import { cookies } from 'next/headers';
import { Suspense } from 'react';

// PRODUCTION INVARIANT: The outer page shell is statically prerenderable.
// Dynamic request context is pushed down into an isolated, Suspended leaf boundary.
export default function DashboardPage() {
  return (
    <main className="dashboard-container">
      <header className="static-banner">
        <h1>Application Dashboard</h1>
      </header>
      <Suspense fallback={<UserProfileSkeleton />}>
        <DynamicUserProfile />
      </Suspense>
    </main>
  );
}

async function DynamicUserProfile() {
  const cookieStore = await cookies();
  const token = cookieStore.get('session_token')?.value;
  
  if (!token) {
    return <p>Please sign in.</p>;
  }

  const user = await fetchUserData(token);
  return (
    <section className="user-profile">
      <p>Welcome back, {user.name}!</p>
    </section>
  );
}

function UserProfileSkeleton() {
  return (
    <section className="user-profile animate-pulse" aria-busy="true">
      <div className="h-4 w-48 bg-slate-200 rounded" />
    </section>
  );
}

async function fetchUserData(token: string) {
  const res = await fetch('https://api.internal/user', {
    headers: { Authorization: `Bearer ${token}` },
    cache: 'no-store',
  });
  return res.json();
}
```
Recommended MCP Servers (mcp-serverlist.com)

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

Next.js Runtime Inspector MCP
Inspects Next.js compilation artifacts and route manifests to detect PPR static shell de-optimizations.
Recommended Agent Skills (askills.dev)

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

Next.js Codemod Dynamic IO Runner
Applies AST codemods to migrate legacy async params and cookies access to React 19 / Next.js 15 Suspense boundaries.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: Next.js 15 Dynamic IO and PPR Asynchronous Boundary Enforcement

Next.js 15 Dynamic IO and PPR Asynchronous Boundary Enforcement defines an industrial-grade behavioral standard for frontend engineering. Next.js 15 Dynamic IO with Partial Prerendering (PPR) mandates that dynamic data sources (cookies, headers, searchParams, and uncached dynamic fetches) are quarantined behind strict React Suspense boundaries. Top-level synchronous or layout-level un-suspended dynamic accesses de-opt the static shell, leak contextual request state into shared prerender buffers, and trigger client hydration mismatch panics. 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: Awaiting dynamic request APIs at root page/layout level without Suspense encapsulation, collapsing PPR into SSR 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 DriftAwaiting dynamic request APIs at root page/layout level without Suspense encapsulation, collapsing PPR into SSRCritical
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 isolate dynamic data reads (`cookies()`, `headers()`, `searchParams`, uncached DB calls) inside dedicated leaf Server Components wrapped in a `<Suspense fallback={<Skeleton />}>` boundary.

Engineers MUST ALWAYS isolate dynamic data reads (`cookies()`, `headers()`, `searchParams`, uncached DB calls) inside dedicated leaf Server Components wrapped in a `<Suspense fallback={<Skeleton />}>` boundary.

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 `await` dynamic APIs (`await cookies()`, `await headers()`, or dynamic `params`/`searchParams` promises) at the root level of a layout or static page component, as this de-opts the static prerender shell.

Engineers MUST NOT `await` dynamic APIs (`await cookies()`, `await headers()`, or dynamic `params`/`searchParams` promises) at the root level of a layout or static page component, as this de-opts the static prerender shell.

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

Components NEVER access request-specific contextual state (such as user session IDs or bearer tokens) inside functions or files annotated with `'use cache'`, preventing cross-tenant data leakage in the shared data cache.

Components NEVER access request-specific contextual state (such as user session IDs or bearer tokens) inside functions or files annotated with `'use cache'`, preventing cross-tenant data leakage in the shared data cache.

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 SHOULD pass dynamic streaming promises directly into Client Components using the React 19 `use()` API inside suspended subtrees rather than blocking the Server Component render cycle.

Code SHOULD pass dynamic streaming promises directly into Client Components using the React 19 `use()` API inside suspended subtrees rather than blocking the Server Component render cycle.

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

Services MUST configure fine-grained cache invalidation using `cacheTag()` and `cacheLife()` inside explicit `'use cache'` scopes instead of relying on legacy route segment configs (`export const dynamic = 'force-dynamic'`).

Services MUST configure fine-grained cache invalidation using `cacheTag()` and `cacheLife()` inside explicit `'use cache'` scopes instead of relying on legacy route segment configs (`export const dynamic = 'force-dynamic'`).

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 MUST provide deterministic, structurally identical HTML skeletons in Suspense fallbacks that mirror the resolved DOM nodes to eliminate layout shifts and hydration mismatch warnings.

Components MUST provide deterministic, structurally identical HTML skeletons in Suspense fallbacks that mirror the resolved DOM nodes to eliminate layout shifts and hydration mismatch warnings.

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 Next.js 15 Dynamic IO and PPR Asynchronous Boundary Enforcement critical for AI coding assistants?

Next.js 15 Dynamic IO with Partial Prerendering (PPR) mandates that dynamic data sources (cookies, headers, searchParams, and uncached dynamic fetches) are quarantined behind strict React Suspense boundaries. Top-level synchronous or layout-level un-suspended dynamic accesses de-opt the static shell, leak contextual request state into shared prerender buffers, and trigger client hydration mismatch panics. 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 (Awaiting dynamic request APIs at root page/layout level without Suspense encapsulation, collapsing PPR into SSR) 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

Next.js