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-ppr-dynamic-io-shell-isolation

Next.js 15 PPR Dynamic IO Shell Isolation Standard

Enforces strict architectural boundaries between static prerendered HTML shells and asynchronous streaming promises under Next.js 15 Partial Prerendering (PPR) and Dynamic IO. Prevents synchronous resolution of dynamic operations—such as cookies(), headers(), searchParams, or uncached I/O—outside of explicit Suspense boundaries, eliminating cascading prerender deoptimizations and build-time dynamic bailouts.

Prohibited Anti-Pattern: Leaking Dynamic Server Execution into Root Shell Contexts via Un-Suspended Async Operations

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Next.js 15 PPR Dynamic IO Shell Isolation Standard - Enforces strict architectural boundaries between static prerendered HTML shells and asynchronous streaming promises under Next.js 15 Partial Prerendering (PPR) and Dynamic IO. Prevents synchronous resolution of dynamic operations—such as cookies(), headers(), searchParams, or uncached I/O—outside of explicit Suspense boundaries, eliminating cascading prerender deoptimizations and build-time dynamic bailouts.
globs: src/app/**/*.{ts,tsx}, app/**/*.{ts,tsx}
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/nextjs15-ppr-dynamic-io-shell-isolation"
---

# Next.js 15 PPR Dynamic IO Shell Isolation Standard

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Leaking Dynamic Server Execution into Root Shell Contexts via Un-Suspended Async Operations

## System Constraints
You are a Principal Software Architect enforcing Next.js 15 Partial Prerendering (PPR) and Dynamic IO Shell Isolation. You must mandate strict separation between static shells generated at build time and dynamic streaming regions resolved at request time. Reject any pattern where cookies(), headers(), dynamic route parameters, or uncached I/O are awaited outside of explicit <Suspense> boundaries in PPR-enabled routes.

## Strict Guidelines
- Engineers MUST ALWAYS isolate dynamic data operations (e.g., cookies(), headers(), connection(), uncached fetch, or database calls) inside discrete async Server Components wrapped with a <Suspense> boundary.
- Engineers MUST NOT await dynamic request APIs (cookies(), headers(), searchParams) directly within root Layout or Page component bodies.
- Layouts MUST remain 100% static shells containing shared navigation, structural wrappers, and skeleton placeholders to guarantee zero-latency TTFB.
- Dynamic leaf components MUST encapsulate their own data resolution or accept unawaited dynamic promises passed down to React 19 use() hooks inside Suspense boundaries.
- Code SHOULD leverage the 'use cache' directive alongside revalidation tags for cacheable dynamic fragments, ensuring only strictly personalized or unpredictable data triggers dynamic streaming.
- Components NEVER execute top-level synchronous access to asynchronous dynamic parameters introduced in Next.js 15 (e.g., params and searchParams must be awaited within dynamic boundaries).

## Bad vs Good Implementations
### Dynamic Cart & User Shell Demarcation in PPR

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Awaiting cookies() and fetchUserCart() at the top-level Page component halts static prerendering during 'next build'. The static hero banner and layout are blocked from emitting an instant prerendered HTML shell, collapsing the PPR execution model into legacy blocking dynamic SSR.
```typescript
// app/dashboard/page.tsx
import { cookies } from 'next/headers';
import { fetchUserCart } from '@/lib/db';

export const experimental_ppr = true;

// ANTI-PATTERN: Awaiting dynamic data at page root deoptimizes the entire static shell.
export default async function DashboardPage() {
  const cookieStore = await cookies();
  const sessionId = cookieStore.get('session_id')?.value;
  const cart = await fetchUserCart(sessionId); // Cascading dynamic bailout: whole page becomes dynamic SSR

  return (
    <main className="dashboard-container">
      <header className="hero-banner">
        <h1>Welcome to the Marketplace</h1>
        <p>Instant static marketing content.</p>
      </header>
      <section className="cart-summary">
        <h2>Your Cart ({cart.items.length})</h2>
      </section>
    </main>
  );
}
```

#### Production Standard (Correct)
> **Standard**: DashboardPage remains synchronous and static, allowing Next.js to prerender and immediately flush the static layout and hero banner. Dynamic cart retrieval is deferred to a streaming component encapsulated inside a <Suspense> boundary with a deterministic fallback.
```typescript
// app/dashboard/page.tsx
import { Suspense } from 'react';
import { cookies } from 'next/headers';
import { fetchUserCart } from '@/lib/db';
import { CartSkeleton } from '@/components/skeletons';

export const experimental_ppr = true;

// Isolated dynamic leaf component
async function DynamicCartSection() {
  const cookieStore = await cookies();
  const sessionId = cookieStore.get('session_id')?.value;
  const cart = await fetchUserCart(sessionId);

  return (
    <section className="cart-summary">
      <h2>Your Cart ({cart.items.length})</h2>
    </section>
  );
}

// PRODUCTION FIX: Root page acts as a deterministic static shell.
export default function DashboardPage() {
  return (
    <main className="dashboard-container">
      <header className="hero-banner">
        <h1>Welcome to the Marketplace</h1>
        <p>Instant static marketing content.</p>
      </header>
      <Suspense fallback={<CartSkeleton />}>
        <DynamicCartSection />
      </Suspense>
    </main>
  );
}
```
Recommended MCP Servers (mcp-serverlist.com)

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

Next.js Build & Runtime Diagnostic Server
Inspects static build manifests, analyzes prerender trace dumps, and flags dynamic IO leaks across App Router routes.
Recommended Agent Skills (askills.dev)

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

Next.js PPR Prerender Audit CLI
Runs static generation checks during CI to identify routes failing PPR shell prerendering due to un-Suspended dynamic calls.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: Next.js 15 PPR Dynamic IO Shell Isolation Standard

Next.js 15 PPR Dynamic IO Shell Isolation Standard defines an industrial-grade behavioral standard for frontend engineering. Enforces strict architectural boundaries between static prerendered HTML shells and asynchronous streaming promises under Next.js 15 Partial Prerendering (PPR) and Dynamic IO. Prevents synchronous resolution of dynamic operations—such as cookies(), headers(), searchParams, or uncached I/O—outside of explicit Suspense boundaries, eliminating cascading prerender deoptimizations and build-time dynamic bailouts. 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: Leaking Dynamic Server Execution into Root Shell Contexts via Un-Suspended Async Operations 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 DriftLeaking Dynamic Server Execution into Root Shell Contexts via Un-Suspended Async OperationsCritical
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 operations (e.g., cookies(), headers(), connection(), uncached fetch, or database calls) inside discrete async Server Components wrapped with a <Suspense> boundary.

Engineers MUST ALWAYS isolate dynamic data operations (e.g., cookies(), headers(), connection(), uncached fetch, or database calls) inside discrete async Server Components wrapped with a <Suspense> 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 request APIs (cookies(), headers(), searchParams) directly within root Layout or Page component bodies.

Engineers MUST NOT await dynamic request APIs (cookies(), headers(), searchParams) directly within root Layout or Page component bodies.

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

Layouts MUST remain 100% static shells containing shared navigation, structural wrappers, and skeleton placeholders to guarantee zero-latency TTFB.

Layouts MUST remain 100% static shells containing shared navigation, structural wrappers, and skeleton placeholders to guarantee zero-latency TTFB.

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

Dynamic leaf components MUST encapsulate their own data resolution or accept unawaited dynamic promises passed down to React 19 use() hooks inside Suspense boundaries.

Dynamic leaf components MUST encapsulate their own data resolution or accept unawaited dynamic promises passed down to React 19 use() hooks inside Suspense boundaries.

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

Code SHOULD leverage the 'use cache' directive alongside revalidation tags for cacheable dynamic fragments, ensuring only strictly personalized or unpredictable data triggers dynamic streaming.

Code SHOULD leverage the 'use cache' directive alongside revalidation tags for cacheable dynamic fragments, ensuring only strictly personalized or unpredictable data triggers dynamic streaming.

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 execute top-level synchronous access to asynchronous dynamic parameters introduced in Next.js 15 (e.g., params and searchParams must be awaited within dynamic boundaries).

Components NEVER execute top-level synchronous access to asynchronous dynamic parameters introduced in Next.js 15 (e.g., params and searchParams must be awaited within dynamic boundaries).

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 PPR Dynamic IO Shell Isolation Standard critical for AI coding assistants?

Enforces strict architectural boundaries between static prerendered HTML shells and asynchronous streaming promises under Next.js 15 Partial Prerendering (PPR) and Dynamic IO. Prevents synchronous resolution of dynamic operations—such as cookies(), headers(), searchParams, or uncached I/O—outside of explicit Suspense boundaries, eliminating cascading prerender deoptimizations and build-time dynamic bailouts. 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 (Leaking Dynamic Server Execution into Root Shell Contexts via Un-Suspended Async Operations) 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