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-hole-containment

Next.js 15 Partial Prerendering (PPR) Dynamic Hole Boundary Isolation

Enforces strict React Suspense encapsulation and dynamic context isolation for Next.js 15 Partial Prerendering (PPR) routes. Prevents dynamic APIs (cookies, headers, uncached fetches) from escaping leaf boundaries and deoptimizing the pre-rendered static shell into blocking dynamic server rendering.

Prohibited Anti-Pattern: Uncontained Dynamic API Access Deoptimizing Static PPR Shells into Blocking SSR

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Next.js 15 Partial Prerendering (PPR) Dynamic Hole Boundary Isolation - Enforces strict React Suspense encapsulation and dynamic context isolation for Next.js 15 Partial Prerendering (PPR) routes. Prevents dynamic APIs (cookies, headers, uncached fetches) from escaping leaf boundaries and deoptimizing the pre-rendered static shell into blocking dynamic server rendering.
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-ppr-dynamic-hole-containment"
---

# Next.js 15 Partial Prerendering (PPR) Dynamic Hole Boundary Isolation

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Uncontained Dynamic API Access Deoptimizing Static PPR Shells into Blocking SSR

## System Constraints
You are a Principal Engineer enforcing Next.js 15 Partial Prerendering (PPR) Dynamic Hole Containment. Mandate strict boundary isolation around dynamic execution contexts to guarantee static prerender shells stream instantly.

## Strict Guidelines
- Engineers MUST ALWAYS isolate dynamic operations (`cookies()`, `headers()`, uncached `fetch()`, `connection()`, `searchParams`) inside dedicated leaf Server Components wrapped in `<Suspense>`.
- Engineers MUST NOT access dynamic context (`headers()`, `cookies()`, dynamic route params) at the top level of pages or shared layouts.
- Code SHOULD wrap dynamic child components in `<Suspense fallback={<StaticSkeleton />}>` at the closest possible ancestor to maximize the surface area of the static HTML shell.
- Services MUST leverage `React.cache()` to deduplicate identical server-side read operations across multiple dynamic holes occurring in a single request lifecycle.
- Components NEVER execute blocking async calls before rendering invariant UI elements like headers, footers, navigation, or critical hero metadata.
- Route segments opting into PPR MUST export `export const experimental_ppr = true;` or rely on `ppr: 'incremental'` with rigorous static analysis verification.

## Bad vs Good Implementations
### Dynamic Hole Containment in PPR Route

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Accessing `cookies()` and performing an uncached `fetch()` directly inside the route's root component collapses the PPR boundary. The static banner and navigation cannot be prerendered into the initial static shell, forcing the entire response to wait for downstream profile fetch latency before streaming the first byte.
```typescript
// app/dashboard/page.tsx
import { cookies } from 'next/headers';

export const experimental_ppr = true;

// ANTI-PATTERN: Root page awaits dynamic cookies() directly,
// deoptimizing the entire static shell and stalling TTFB on backend I/O.
export default async function DashboardPage() {
  const cookieStore = await cookies();
  const token = cookieStore.get('session_token')?.value;
  
  const res = await fetch('https://api.internal/user/profile', {
    headers: { Authorization: `Bearer ${token}` },
    cache: 'no-store'
  });
  const profile = await res.json();

  return (
    <main className="dashboard-layout">
      <header className="static-banner">
        <h1>Enterprise Dashboard</h1>
        <nav>Static Global Navigation</nav>
      </header>
      <section className="profile-panel">
        <h2>Welcome, {profile.name}</h2>
        <p>Tier: {profile.tier}</p>
      </section>
    </main>
  );
}
```

#### Production Standard (Correct)
> **Standard**: The root `DashboardPage` contains no dynamic invocations, allowing Next.js 15 to pre-render the static layout, banner, and navigation shell at build time. Dynamic cookie access and uncached network requests are strictly confined to `DynamicProfileHole` within a `<Suspense>` boundary, ensuring instant TTFB followed by targeted dynamic streaming.
```typescript
// app/dashboard/page.tsx
import { Suspense } from 'react';
import { cookies } from 'next/headers';
import { ProfileSkeleton } from '@/components/ProfileSkeleton';

export const experimental_ppr = true;

// PRODUCTION INVARIANT: The root page remains completely static.
// Dynamic dependencies are encapsulated into leaf holes wrapped with Suspense.
export default function DashboardPage() {
  return (
    <main className="dashboard-layout">
      <header className="static-banner">
        <h1>Enterprise Dashboard</h1>
        <nav>Static Global Navigation</nav>
      </header>
      <Suspense fallback={<ProfileSkeleton />}>
        <DynamicProfileHole />
      </Suspense>
    </main>
  );
}

async function DynamicProfileHole() {
  const cookieStore = await cookies();
  const token = cookieStore.get('session_token')?.value;

  const res = await fetch('https://api.internal/user/profile', {
    headers: { Authorization: `Bearer ${token}` },
    cache: 'no-store'
  });
  const profile = await res.json();

  return (
    <section className="profile-panel">
      <h2>Welcome, {profile.name}</h2>
      <p>Tier: {profile.tier}</p>
    </section>
  );
}
```
Recommended MCP Servers (mcp-serverlist.com)

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

Next.js Runtime Inspector MCP
Validates dynamic hole boundaries, inspects PPR build traces, and flags uncontained dynamic route execution.
Recommended Agent Skills (askills.dev)

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

Next.js Route Segment Analyzer
CLI tool that statically audits App Router pages to detect accidental route deoptimization and dynamic API leaks.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: Next.js 15 Partial Prerendering (PPR) Dynamic Hole Boundary Isolation

Next.js 15 Partial Prerendering (PPR) Dynamic Hole Boundary Isolation defines an industrial-grade behavioral standard for frontend engineering. Enforces strict React Suspense encapsulation and dynamic context isolation for Next.js 15 Partial Prerendering (PPR) routes. Prevents dynamic APIs (cookies, headers, uncached fetches) from escaping leaf boundaries and deoptimizing the pre-rendered static shell into blocking dynamic server rendering. 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: Uncontained Dynamic API Access Deoptimizing Static PPR Shells into Blocking 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 DriftUncontained Dynamic API Access Deoptimizing Static PPR Shells into Blocking 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 operations (`cookies()`, `headers()`, uncached `fetch()`, `connection()`, `searchParams`) inside dedicated leaf Server Components wrapped in `<Suspense>`.

Engineers MUST ALWAYS isolate dynamic operations (`cookies()`, `headers()`, uncached `fetch()`, `connection()`, `searchParams`) inside dedicated leaf Server Components wrapped in `<Suspense>`.

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 context (`headers()`, `cookies()`, dynamic route params) at the top level of pages or shared layouts.

Engineers MUST NOT access dynamic context (`headers()`, `cookies()`, dynamic route params) at the top level of pages or shared layouts.

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 SHOULD wrap dynamic child components in `<Suspense fallback={<StaticSkeleton />}>` at the closest possible ancestor to maximize the surface area of the static HTML shell.

Code SHOULD wrap dynamic child components in `<Suspense fallback={<StaticSkeleton />}>` at the closest possible ancestor to maximize the surface area of the static HTML 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.
4

Services MUST leverage `React.cache()` to deduplicate identical server-side read operations across multiple dynamic holes occurring in a single request lifecycle.

Services MUST leverage `React.cache()` to deduplicate identical server-side read operations across multiple dynamic holes occurring in a single request lifecycle.

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 execute blocking async calls before rendering invariant UI elements like headers, footers, navigation, or critical hero metadata.

Components NEVER execute blocking async calls before rendering invariant UI elements like headers, footers, navigation, or critical hero metadata.

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

Route segments opting into PPR MUST export `export const experimental_ppr = true

Route segments opting into PPR MUST export `export const experimental_ppr = true;` or rely on `ppr: 'incremental'` with rigorous static analysis verification.

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) Dynamic Hole Boundary Isolation critical for AI coding assistants?

Enforces strict React Suspense encapsulation and dynamic context isolation for Next.js 15 Partial Prerendering (PPR) routes. Prevents dynamic APIs (cookies, headers, uncached fetches) from escaping leaf boundaries and deoptimizing the pre-rendered static shell into blocking dynamic server rendering. 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 (Uncontained Dynamic API Access Deoptimizing Static PPR Shells into Blocking 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