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-boundary-isolation-contract

Next.js 15 Partial Prerendering (PPR) Boundary Isolation Contract

Enforces strict isolation between static pre-rendered HTML shells and dynamic React 19 streaming slots within Next.js 15 PPR architectures. Prevents accidental dynamic context leakage that causes entire page trees to de-optimize to dynamic SSR and trigger cascading hydration bailouts under high concurrency. Mandates explicit React Suspense boundaries around all dynamic I/O primitives including headers(), cookies(), and uncached fetch invocations.

Prohibited Anti-Pattern: Dynamic Hook Leakage Inducing Full-Route Static Shell Bailout

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Next.js 15 Partial Prerendering (PPR) Boundary Isolation Contract - Enforces strict isolation between static pre-rendered HTML shells and dynamic React 19 streaming slots within Next.js 15 PPR architectures. Prevents accidental dynamic context leakage that causes entire page trees to de-optimize to dynamic SSR and trigger cascading hydration bailouts under high concurrency. Mandates explicit React Suspense boundaries around all dynamic I/O primitives including headers(), cookies(), and uncached fetch invocations.
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-boundary-isolation-contract"
---

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

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Dynamic Hook Leakage Inducing Full-Route Static Shell Bailout

## System Constraints
You are a Principal Frontend Architect enforcing Next.js 15 Partial Prerendering (PPR) boundary contracts. Your mission is to ensure zero dynamic data access escapes explicit React Suspense boundaries, guaranteeing that edge CDN static shells are maximally preserved and streamed slots fail independently without cascading hydration bailouts.

## Strict Guidelines
- Engineers MUST ALWAYS wrap any Server Component accessing dynamic I/O (e.g., `cookies()`, `headers()`, `searchParams`, or dynamic data fetches) in a standalone `<Suspense fallback={<StaticSkeleton />}>` boundary.
- Engineers MUST NOT access `cookies()`, `headers()`, or `searchParams` in layout components or top-level page components configured with `export const experimental_ppr = true`.
- Components accessing dynamic context MUST be pushed to the lowest possible leaf node in the React component tree to maximize the static shell surface area.
- Every dynamic streaming component MUST declare a deterministic, statically renderable fallback skeleton that strictly matches the dimensions of the final resolved payload to eliminate layout shifts (CLS).
- Engineers MUST NEVER pass unresolved dynamic promises from page-level props directly into static component trees without an immediate Suspense boundary wrapping the consuming component.
- Data fetching inside static shells MUST explicitly configure `{ cache: 'force-cache' }` or utilize `unstable_cache` to prevent silent downgrades to runtime dynamic rendering.

## Bad vs Good Implementations
### Dynamic Data Access Inside Page Component vs Suspended Dynamic Leaf Component

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Accessing `cookies()` at the page root forces Next.js 15 PPR to de-optimize the entire route. The edge server cannot pre-render and cache the static shell (`<header className="static-banner">`), nullifying the performance and concurrency advantages of Partial Prerendering.
```typescript
// app/dashboard/page.tsx
import { cookies } from 'next/headers';
import { UserMetrics } from '@/components/UserMetrics';

export const experimental_ppr = true;

// ANTI-PATTERN: Accessing cookies() directly in the page root de-opts the entire
// page out of the static pre-rendered shell into dynamic runtime SSR.
export default async function DashboardPage() {
  const cookieStore = await cookies();
  const token = cookieStore.get('auth-token')?.value;
  
  return (
    <main className="dashboard-container">
      <header className="static-banner">
        <h1>Executive Dashboard</h1>
      </header>
      <section className="content">
        <UserMetrics authToken={token} />
      </section>
    </main>
  );
}
```

#### Production Standard (Correct)
> **Standard**: The route root remains fully static and can be rendered at build time and cached instantly at the edge CDN. Dynamic execution begins exclusively inside `DynamicUserMetrics`, which is deferred and streamed over HTTP without stalling the initial layout delivery or triggering hydration bailouts.
```typescript
// app/dashboard/page.tsx
import { Suspense } from 'react';
import { DynamicUserMetrics, MetricsSkeleton } from '@/components/UserMetrics';

export const experimental_ppr = true;

// PRODUCTION INVARIANT: The page component is completely static.
// Dynamic I/O is isolated strictly within DynamicUserMetrics under Suspense.
export default function DashboardPage() {
  return (
    <main className="dashboard-container">
      <header className="static-banner">
        <h1>Executive Dashboard</h1>
      </header>
      <section className="content">
        <Suspense fallback={<MetricsSkeleton />}>
          <DynamicUserMetrics />
        </Suspense>
      </section>
    </main>
  );
}

// components/UserMetrics.tsx
import { cookies } from 'next/headers';

export async function DynamicUserMetrics() {
  const cookieStore = await cookies();
  const token = cookieStore.get('auth-token')?.value;
  const data = await fetch('https://api.internal/metrics', {
    headers: { Authorization: `Bearer ${token}` },
    cache: 'no-store'
  }).then(res => res.json());

  return <div>Active Users: {data.count}</div>;
}

export function MetricsSkeleton() {
  return <div className="h-6 w-32 animate-pulse bg-slate-800 rounded" />;
}
```
Recommended MCP Servers (mcp-serverlist.com)

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

Next.js Build & PPR Inspector
MCP server designed to parse Next.js build outputs, detecting unisolated dynamic primitives and PPR route de-optimizations.
Recommended Agent Skills (askills.dev)

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

Next.js PPR Static Analyzer
CLI tool that statically traverses the Next.js App Router AST to verify all dynamic I/O occurs behind explicit Suspense boundaries.
Architectural Specification & Invariant Rationale

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

Next.js 15 Partial Prerendering (PPR) Boundary Isolation Contract defines an industrial-grade behavioral standard for frontend engineering. Enforces strict isolation between static pre-rendered HTML shells and dynamic React 19 streaming slots within Next.js 15 PPR architectures. Prevents accidental dynamic context leakage that causes entire page trees to de-optimize to dynamic SSR and trigger cascading hydration bailouts under high concurrency. Mandates explicit React Suspense boundaries around all dynamic I/O primitives including headers(), cookies(), and uncached fetch invocations. 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 Hook Leakage Inducing Full-Route Static Shell Bailout 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 Hook Leakage Inducing Full-Route Static Shell BailoutCritical
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 wrap any Server Component accessing dynamic I/O (e.g., `cookies()`, `headers()`, `searchParams`, or dynamic data fetches) in a standalone `<Suspense fallback={<StaticSkeleton />}>` boundary.

Engineers MUST ALWAYS wrap any Server Component accessing dynamic I/O (e.g., `cookies()`, `headers()`, `searchParams`, or dynamic data fetches) in a standalone `<Suspense fallback={<StaticSkeleton />}>` 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 `searchParams` in layout components or top-level page components configured with `export const experimental_ppr = true`.

Engineers MUST NOT access `cookies()`, `headers()`, or `searchParams` in layout components or top-level page components configured with `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

Components accessing dynamic context MUST be pushed to the lowest possible leaf node in the React component tree to maximize the static shell surface area.

Components accessing dynamic context MUST be pushed to the lowest possible leaf node in the React component tree to maximize the static shell surface area.

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

Every dynamic streaming component MUST declare a deterministic, statically renderable fallback skeleton that strictly matches the dimensions of the final resolved payload to eliminate layout shifts (CLS).

Every dynamic streaming component MUST declare a deterministic, statically renderable fallback skeleton that strictly matches the dimensions of the final resolved payload to eliminate layout shifts (CLS).

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

Engineers MUST NEVER pass unresolved dynamic promises from page-level props directly into static component trees without an immediate Suspense boundary wrapping the consuming component.

Engineers MUST NEVER pass unresolved dynamic promises from page-level props directly into static component trees without an immediate Suspense boundary wrapping the consuming 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

Data fetching inside static shells MUST explicitly configure `{ cache

Data fetching inside static shells MUST explicitly configure `{ cache: 'force-cache' }` or utilize `unstable_cache` to prevent silent downgrades to runtime dynamic 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.
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) Boundary Isolation Contract critical for AI coding assistants?

Enforces strict isolation between static pre-rendered HTML shells and dynamic React 19 streaming slots within Next.js 15 PPR architectures. Prevents accidental dynamic context leakage that causes entire page trees to de-optimize to dynamic SSR and trigger cascading hydration bailouts under high concurrency. Mandates explicit React Suspense boundaries around all dynamic I/O primitives including headers(), cookies(), and uncached fetch invocations. 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 Hook Leakage Inducing Full-Route Static Shell Bailout) 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