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: nextjs-15-ppr-dynamic-stream-isolation-standard

Next.js 15 PPR Dynamic Stream Isolation & Static Shell Preservation

Enforces strict isolation of dynamic runtime operations (cookies, headers, searchParams, and uncached fetches) inside React Suspense boundaries for Next.js 15 Partial Prerendering (PPR). Prevents accidental de-optimization of static edge-prerendered shells into full server-rendered waterfall executions.

Prohibited Anti-Pattern: Leaking Dynamic Contexts Outside Suspense Boundaries Causing Complete Route De-optimization

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Next.js 15 PPR Dynamic Stream Isolation & Static Shell Preservation - Enforces strict isolation of dynamic runtime operations (cookies, headers, searchParams, and uncached fetches) inside React Suspense boundaries for Next.js 15 Partial Prerendering (PPR). Prevents accidental de-optimization of static edge-prerendered shells into full server-rendered waterfall executions.
globs: src/app/**/*.{ts,tsx}, app/**/*.{ts,tsx}
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/nextjs-15-ppr-dynamic-stream-isolation-standard"
---

# Next.js 15 PPR Dynamic Stream Isolation & Static Shell Preservation

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Leaking Dynamic Contexts Outside Suspense Boundaries Causing Complete Route De-optimization

## System Constraints
You are a Principal Software Architect enforcing Next.js 15 Partial Prerendering (PPR) Dynamic Stream Isolation. You must ensure that layouts and page roots generate pristine static shells while dynamic server components are strictly compartmentalized within explicit Suspense boundaries. Any invocation of dynamic APIs (cookies, headers, searchParams, uncached data fetches) outside a Suspense boundary constitutes an architectural failure and must be rejected.

## Strict Guidelines
- Engineers MUST ALWAYS isolate dynamic API invocations (`cookies()`, `headers()`, `searchParams`) inside leaf React Server Components wrapped with an explicit `<Suspense fallback={<Skeleton />}>` boundary.
- Engineers MUST NOT access `cookies()`, `headers()`, or uncached downstream data at the root of a layout or page if that route enables Partial Prerendering (`export const experimental_ppr = true`).
- Engineers MUST use the `await connection()` API in Next.js 15 to explicitly defer execution of dynamic streams when dynamic context is consumed in streaming components.
- Root page components SHOULD immediately return static layout markup and edge-cacheable UI shells rather than resolving dynamic promises at the page function boundary.
- Suspense boundaries MUST have deterministic, layout-shift-free fallback skeletons matching the exact dimensions of the streamed component.
- Components NEVER await dynamic data dependencies at the top-level of parent containers that enclose unrelated static content.

## Bad vs Good Implementations
### Bailing out static route shell vs. Suspense-isolated dynamic stream

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Reading dynamic cookies and awaiting an uncached dynamic fetch directly in the page body forces Next.js to discard the static prerender shell entirely, de-opting the route into traditional full-page SSR and causing a time-to-first-byte (TTFB) waterfall.
```typescript
import { cookies } from 'next/headers';

export const experimental_ppr = true;

// VIOLATION: Accessing cookies at page component top-level bails entire page out of static prerendering
export default async function DashboardPage() {
  const cookieStore = await cookies();
  const token = cookieStore.get('auth_token');
  const data = await fetch(`https://api.internal/user-metrics`, {
    headers: { Authorization: `Bearer ${token?.value}` },
  }).then((res) => res.json());

  return (
    <main className="dashboard-container">
      <header className="static-header">
        <h1>Executive Dashboard</h1>
        <p>Global Analytics Overview</p>
      </header>
      <section className="metrics-grid">
        <div>Active Sessions: {data.sessions}</div>
        <div>Conversion Rate: {data.rate}%</div>
      </section>
    </main>
  );
}
```

#### Production Standard (Correct)
> **Standard**: The page component returns immediately as an edge-cacheable static shell. Dynamic execution is isolated inside `DynamicMetricsStream` wrapped within `<Suspense>`, using `await connection()` and deferred dynamic APIs to stream user-specific data without stalling TTFB.
```typescript
import { Suspense } from 'react';
import { cookies } from 'next/headers';
import { connection } from 'next/server';

export const experimental_ppr = true;

async function DynamicMetricsStream() {
  // Explicitly defer to dynamic execution context inside Suspense
  await connection();
  const cookieStore = await cookies();
  const token = cookieStore.get('auth_token');
  
  const data = await fetch(`https://api.internal/user-metrics`, {
    headers: { Authorization: `Bearer ${token?.value}` },
    cache: 'no-store',
  }).then((res) => res.json());

  return (
    <section className="metrics-grid">
      <div>Active Sessions: {data.sessions}</div>
      <div>Conversion Rate: {data.rate}%</div>
    </section>
  );
}

function MetricsSkeleton() {
  return (
    <div className="metrics-grid skeleton-pulse" aria-busy="true">
      <div className="h-12 w-full bg-slate-200 rounded" />
      <div className="h-12 w-full bg-slate-200 rounded" />
    </div>
  );
}

export default function DashboardPage() {
  // COMPLIANT: Static shell prerenders instantly at build/edge time
  return (
    <main className="dashboard-container">
      <header className="static-header">
        <h1>Executive Dashboard</h1>
        <p>Global Analytics Overview</p>
      </header>
      <Suspense fallback={<MetricsSkeleton />}>
        <DynamicMetricsStream />
      </Suspense>
    </main>
  );
}
```
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 build manifests and PPR routing boundaries to verify static shell generation and dynamic hole allocations.
Recommended Agent Skills (askills.dev)

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

Next.js Build & Prerender Validator
Executes next build --dry-run validation to verify that PPR routes generate static circle symbols rather than dynamic lambdas.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: Next.js 15 PPR Dynamic Stream Isolation & Static Shell Preservation

Next.js 15 PPR Dynamic Stream Isolation & Static Shell Preservation defines an industrial-grade behavioral standard for frontend engineering. Enforces strict isolation of dynamic runtime operations (cookies, headers, searchParams, and uncached fetches) inside React Suspense boundaries for Next.js 15 Partial Prerendering (PPR). Prevents accidental de-optimization of static edge-prerendered shells into full server-rendered waterfall executions. 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 Contexts Outside Suspense Boundaries Causing Complete Route De-optimization 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 Contexts Outside Suspense Boundaries Causing Complete Route De-optimizationCritical
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 API invocations (`cookies()`, `headers()`, `searchParams`) inside leaf React Server Components wrapped with an explicit `<Suspense fallback={<Skeleton />}>` boundary.

Engineers MUST ALWAYS isolate dynamic API invocations (`cookies()`, `headers()`, `searchParams`) inside leaf React Server Components wrapped with an explicit `<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 access `cookies()`, `headers()`, or uncached downstream data at the root of a layout or page if that route enables Partial Prerendering (`export const experimental_ppr = true`).

Engineers MUST NOT access `cookies()`, `headers()`, or uncached downstream data at the root of a layout or page if that route enables Partial Prerendering (`export const experimental_ppr = true`).

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 use the `await connection()` API in Next.js 15 to explicitly defer execution of dynamic streams when dynamic context is consumed in streaming components.

Engineers MUST use the `await connection()` API in Next.js 15 to explicitly defer execution of dynamic streams when dynamic context is consumed in streaming components.

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

Root page components SHOULD immediately return static layout markup and edge-cacheable UI shells rather than resolving dynamic promises at the page function boundary.

Root page components SHOULD immediately return static layout markup and edge-cacheable UI shells rather than resolving dynamic promises at the page function 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.
5

Suspense boundaries MUST have deterministic, layout-shift-free fallback skeletons matching the exact dimensions of the streamed component.

Suspense boundaries MUST have deterministic, layout-shift-free fallback skeletons matching the exact dimensions of the streamed component.

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 await dynamic data dependencies at the top-level of parent containers that enclose unrelated static content.

Components NEVER await dynamic data dependencies at the top-level of parent containers that enclose unrelated static content.

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 Stream Isolation & Static Shell Preservation critical for AI coding assistants?

Enforces strict isolation of dynamic runtime operations (cookies, headers, searchParams, and uncached fetches) inside React Suspense boundaries for Next.js 15 Partial Prerendering (PPR). Prevents accidental de-optimization of static edge-prerendered shells into full server-rendered waterfall executions. 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 Contexts Outside Suspense Boundaries Causing Complete Route De-optimization) 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