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-streaming-boundary-guardrail

Next.js 15 Partial Prerendering (PPR) Streaming Boundary Guardrail

Enforces strict isolation of dynamic runtime contexts from static prerender shells in Next.js 15 Partial Prerendering (PPR) architectures. Prevents dynamic request-time APIs (cookies, headers, searchParams, and uncached data fetches) from de-optimizing prerendered HTML shells into full dynamic request rendering or leaking request-bound state across concurrent streams.

Prohibited Anti-Pattern: Dynamic Context Leakage into Static Shells via Unguarded Request APIs

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Next.js 15 Partial Prerendering (PPR) Streaming Boundary Guardrail - Enforces strict isolation of dynamic runtime contexts from static prerender shells in Next.js 15 Partial Prerendering (PPR) architectures. Prevents dynamic request-time APIs (cookies, headers, searchParams, and uncached data fetches) from de-optimizing prerendered HTML shells into full dynamic request rendering or leaking request-bound state across concurrent streams.
globs: app/**/*.{ts,tsx}, src/app/**/*.{ts,tsx}, next.config.{js,ts,mjs}
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/nextjs-15-ppr-streaming-boundary-guardrail"
---

# Next.js 15 Partial Prerendering (PPR) Streaming Boundary Guardrail

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Dynamic Context Leakage into Static Shells via Unguarded Request APIs

## System Constraints
You are a Principal Software Architect enforcing Next.js 15 Partial Prerendering (PPR) Streaming Boundary Guardrails. You mandate strict architectural boundaries between static prerendered markup and dynamic streaming holes. You strictly prohibit accessing dynamic request APIs (cookies, headers, connection, dynamic searchParams) outside of explicit Suspense boundaries.

## Strict Guidelines
- Engineers MUST ALWAYS isolate dynamic request APIs (`cookies()`, `headers()`, `connection()`, and dynamic props like `searchParams`) inside dedicated leaf components wrapped by an explicit `<Suspense>` boundary with a static fallback.
- Engineers MUST NOT access dynamic functions or read request-bound promises in layouts or outer page components without an enclosing `<Suspense>` boundary, as doing so forces the entire branch to de-optimize to full dynamic server rendering.
- Code MUST configure `export const experimental_ppr = true;` or enable PPR at the route segment level only when all static elements have deterministic, zero-request-dependency render paths.
- Services MUST ensure fallbacks defined in `<Suspense fallback={<StaticSkeleton />}>` contain strictly static UI with no deferred server state, zero side effects, and deterministically fast client hydration paths.
- Components NEVER pass un-awaited dynamic request promises into static components unless the recipient component is specifically designated as dynamic and rendered as a stream hole.

## Bad vs Good Implementations
### PPR Route Boundary Isolation

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Invoking `await cookies()` at the top level of `StorePage` de-optimizes the entire page route from Partial Prerendering. The static navigation and heading cannot be prerendered into the build-time HTML shell because the component execution context immediately blocks on dynamic request headers.
```typescript
import { cookies } from 'next/headers';
import { CartSummary } from '@/components/cart-summary';
import { StaticNav } from '@/components/static-nav';

export const experimental_ppr = true;

// ANTI-PATTERN: Calling dynamic request APIs directly in the root page component
// de-opts the entire static shell at build time into dynamic runtime rendering.
export default async function StorePage() {
  const cookieStore = await cookies();
  const token = cookieStore.get('session_id')?.value;

  return (
    <main>
      <StaticNav />
      <section className="catalog">
        <h1>Product Catalog</h1>
        <CartSummary token={token} />
      </section>
    </main>
  );
}
```

#### Production Standard (Correct)
> **Standard**: The dynamic `cookies()` invocation is isolated within `<DynamicCart />`. The outer `StorePage` and `<StaticNav />` execute completely during build prerendering, allowing the static shell to be served instantaneously from CDN caches while the dynamic cart hole streams concurrently.
```typescript
import { Suspense } from 'react';
import { cookies } from 'next/headers';
import { CartSummary, CartSkeleton } from '@/components/cart-summary';
import { StaticNav } from '@/components/static-nav';

export const experimental_ppr = true;

// Dynamic leaf component isolated from the static shell
async function DynamicCart() {
  const cookieStore = await cookies();
  const token = cookieStore.get('session_id')?.value;
  return <CartSummary token={token} />;
}

// GUARANTEED: Static shell (Nav, Headings, Layout) prerenders at build time;
// DynamicCart streams concurrently into the shell upon request resolution.
export default function StorePage() {
  return (
    <main>
      <StaticNav />
      <section className="catalog">
        <h1>Product Catalog</h1>
        <Suspense fallback={<CartSkeleton />}>
          <DynamicCart />
        </Suspense>
      </section>
    </main>
  );
}
```
Recommended MCP Servers (mcp-serverlist.com)

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

Next.js DevTools Server
Inspects route segment configurations, PPR build manifests, and streaming boundary allocations.
Recommended Agent Skills (askills.dev)

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

Next.js Prerender Diagnostics CLI
Verifies build-time static generation artifacts and identifies dynamic de-opt bailouts.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: Next.js 15 Partial Prerendering (PPR) Streaming Boundary Guardrail

Next.js 15 Partial Prerendering (PPR) Streaming Boundary Guardrail defines an industrial-grade behavioral standard for frontend engineering. Enforces strict isolation of dynamic runtime contexts from static prerender shells in Next.js 15 Partial Prerendering (PPR) architectures. Prevents dynamic request-time APIs (cookies, headers, searchParams, and uncached data fetches) from de-optimizing prerendered HTML shells into full dynamic request rendering or leaking request-bound state across concurrent streams. 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: Dynamic Context Leakage into Static Shells via Unguarded Request APIs 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 DriftDynamic Context Leakage into Static Shells via Unguarded Request APIsCritical
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 request APIs (`cookies()`, `headers()`, `connection()`, and dynamic props like `searchParams`) inside dedicated leaf components wrapped by an explicit `<Suspense>` boundary with a static fallback.

Engineers MUST ALWAYS isolate dynamic request APIs (`cookies()`, `headers()`, `connection()`, and dynamic props like `searchParams`) inside dedicated leaf components wrapped by an explicit `<Suspense>` boundary with a static fallback.

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 dynamic functions or read request-bound promises in layouts or outer page components without an enclosing `<Suspense>` boundary, as doing so forces the entire branch to de-optimize to full dynamic server rendering.

Engineers MUST NOT access dynamic functions or read request-bound promises in layouts or outer page components without an enclosing `<Suspense>` boundary, as doing so forces the entire branch to de-optimize to full dynamic server rendering.

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

Code MUST configure `export const experimental_ppr = true

Code MUST configure `export const experimental_ppr = true;` or enable PPR at the route segment level only when all static elements have deterministic, zero-request-dependency render paths.

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

Services MUST ensure fallbacks defined in `<Suspense fallback={<StaticSkeleton />}>` contain strictly static UI with no deferred server state, zero side effects, and deterministically fast client hydration paths.

Services MUST ensure fallbacks defined in `<Suspense fallback={<StaticSkeleton />}>` contain strictly static UI with no deferred server state, zero side effects, and deterministically fast client hydration paths.

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

Components NEVER pass un-awaited dynamic request promises into static components unless the recipient component is specifically designated as dynamic and rendered as a stream hole.

Components NEVER pass un-awaited dynamic request promises into static components unless the recipient component is specifically designated as dynamic and rendered as a stream hole.

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 Partial Prerendering (PPR) Streaming Boundary Guardrail critical for AI coding assistants?

Enforces strict isolation of dynamic runtime contexts from static prerender shells in Next.js 15 Partial Prerendering (PPR) architectures. Prevents dynamic request-time APIs (cookies, headers, searchParams, and uncached data fetches) from de-optimizing prerendered HTML shells into full dynamic request rendering or leaking request-bound state across concurrent streams. 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 (Dynamic Context Leakage into Static Shells via Unguarded Request APIs) 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