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-suspense-streaming-invariant

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

Enforces strict boundary encapsulation between static CDN pre-rendered shells and dynamic React Server Components (RSC) micro-streams. Prevents dynamic request accessors (headers, cookies, searchParams, uncached fetch calls) from leaking into root execution contexts, which collapses the static prerender shell into full dynamic SSR and introduces cascading client-side waterfalls.

Prohibited Anti-Pattern: Dynamic Accessor Leakage in Outer Layouts and Top-Level Shells Collapsing PPR

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Next.js 15 Partial Prerendering (PPR) Boundary Isolation Invariant - Enforces strict boundary encapsulation between static CDN pre-rendered shells and dynamic React Server Components (RSC) micro-streams. Prevents dynamic request accessors (headers, cookies, searchParams, uncached fetch calls) from leaking into root execution contexts, which collapses the static prerender shell into full dynamic SSR and introduces cascading client-side waterfalls.
globs: app/**/*.{ts,tsx}, src/app/**/*.{ts,tsx}
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/nextjs-15-ppr-suspense-streaming-invariant"
---

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

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Dynamic Accessor Leakage in Outer Layouts and Top-Level Shells Collapsing PPR

## System Constraints
You are a Principal Engineer enforcing Next.js 15 Partial Prerendering (PPR) Suspense Streaming Invariants. Your objective is to guarantee strict mechanical isolation between static CDN shells and dynamic RSC micro-streams. Reject any dynamic runtime evaluations (such as cookies(), headers(), searchParams, or uncached database/fetch calls) executed outside explicit <Suspense> boundaries. Ensure all fallbacks mirror the layout metrics of the dynamic micro-stream to prevent layout shifts and streaming de-optimizations.

## Strict Guidelines
- Engineers MUST ALWAYS isolate dynamic API invocations (e.g., cookies(), headers(), connection(), searchParams) within dedicated leaf Server Components wrapped in a <Suspense> boundary.
- Engineers MUST NOT call dynamic runtime functions (e.g., cookies(), headers()) directly within root layouts, segment layouts, or top-level page components intended for static prerendering.
- Components NEVER accept promises for dynamic segment data at the layout level unless explicit deferred resolution is wrapped within a child <Suspense> stream.
- Code SHOULD provide deterministic, layout-stable skeleton fallbacks in Suspense boundaries that match the exact computed dimensions of the streamed component to prevent Cumulative Layout Shift (CLS).
- Services MUST configure export const experimental_ppr = true at route segment configs where micro-streaming is intended, guaranteeing that static pre-renders resolve at build time without dynamic bailout warnings.

## Bad vs Good Implementations
### Dynamic Header and Cookie Access De-optimizing Static Shell

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Calling `await cookies()` at the top-level Page component turns the entire route segment dynamic. Next.js 15 PPR cannot pre-generate the static CDN shell (including StaticNav and outer grid markup) because dynamic execution happens before any HTML can be emitted.
```typescript
// app/dashboard/page.tsx
import { cookies } from 'next/headers';
import { UserMetrics } from '@/components/user-metrics';
import { StaticNav } from '@/components/static-nav';

export const experimental_ppr = true;

// ANTI-PATTERN: Top-level async page evaluates dynamic cookies,
// collapsing the entire route into runtime SSR and destroying the CDN shell.
export default async function DashboardPage() {
  const cookieStore = await cookies();
  const token = cookieStore.get('auth-token')?.value;

  return (
    <main className="dashboard-container">
      <StaticNav />
      <div className="content-grid">
        <UserMetrics authToken={token} />
      </div>
    </main>
  );
}
```

#### Production Standard (Correct)
> **Standard**: The Page component remains synchronous and static, allowing Next.js 15 to prerender the outer layout shell and serve it immediately from the edge/CDN. Dynamic cookie access is confined inside `DynamicMetricsStream`, which evaluates asynchronously within an explicit `Suspense` boundary and streams to the client via chunked transfer.
```typescript
// app/dashboard/page.tsx
import { Suspense } from 'react';
import { cookies } from 'next/headers';
import { StaticNav } from '@/components/static-nav';
import { MetricsSkeleton } from '@/components/skeletons';

export const experimental_ppr = true;

// Isolated dynamic leaf server component
async function DynamicMetricsStream() {
  const cookieStore = await cookies();
  const token = cookieStore.get('auth-token')?.value;
  
  // Dynamic runtime data fetch isolated inside the stream
  const data = await fetch(`https://api.internal/metrics`, {
    headers: { Authorization: `Bearer ${token}` },
    cache: 'no-store'
  }).then((res) => res.json());

  return <section className="metrics-display">{data.metricValue}</section>;
}

// Pure static shell generated at build time; dynamic leaf streamed over HTTP chunked transfer
export default function DashboardPage() {
  return (
    <main className="dashboard-container">
      <StaticNav />
      <div className="content-grid">
        <Suspense fallback={<MetricsSkeleton />}>
          <DynamicMetricsStream />
        </Suspense>
      </div>
    </main>
  );
}
```
Recommended MCP Servers (mcp-serverlist.com)

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

Next.js Build & Streaming Inspector
Inspects Next.js route manifest and streaming outputs to verify static prerender boundaries and detect dynamic bailouts.
Recommended Agent Skills (askills.dev)

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

Next.js PPR CLI Validator
Runs Next.js build trace analysis to detect unhandled Dynamic Server Usage errors and uncontained RSC accessors.
Architectural Specification & Invariant Rationale

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

Next.js 15 Partial Prerendering (PPR) Boundary Isolation Invariant defines an industrial-grade behavioral standard for frontend engineering. Enforces strict boundary encapsulation between static CDN pre-rendered shells and dynamic React Server Components (RSC) micro-streams. Prevents dynamic request accessors (headers, cookies, searchParams, uncached fetch calls) from leaking into root execution contexts, which collapses the static prerender shell into full dynamic SSR and introduces cascading client-side waterfalls. 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 Accessor Leakage in Outer Layouts and Top-Level Shells Collapsing PPR 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 Accessor Leakage in Outer Layouts and Top-Level Shells Collapsing PPRCritical
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 (e.g., cookies(), headers(), connection(), searchParams) within dedicated leaf Server Components wrapped in a <Suspense> boundary.

Engineers MUST ALWAYS isolate dynamic API invocations (e.g., cookies(), headers(), connection(), searchParams) within dedicated leaf Server Components wrapped in 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 call dynamic runtime functions (e.g., cookies(), headers()) directly within root layouts, segment layouts, or top-level page components intended for static prerendering.

Engineers MUST NOT call dynamic runtime functions (e.g., cookies(), headers()) directly within root layouts, segment layouts, or top-level page components intended for static prerendering.

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 NEVER accept promises for dynamic segment data at the layout level unless explicit deferred resolution is wrapped within a child <Suspense> stream.

Components NEVER accept promises for dynamic segment data at the layout level unless explicit deferred resolution is wrapped within a child <Suspense> stream.

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

Code SHOULD provide deterministic, layout-stable skeleton fallbacks in Suspense boundaries that match the exact computed dimensions of the streamed component to prevent Cumulative Layout Shift (CLS).

Code SHOULD provide deterministic, layout-stable skeleton fallbacks in Suspense boundaries that match the exact computed dimensions of the streamed component to prevent Cumulative Layout Shift (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

Services MUST configure export const experimental_ppr = true at route segment configs where micro-streaming is intended, guaranteeing that static pre-renders resolve at build time without dynamic bailout warnings.

Services MUST configure export const experimental_ppr = true at route segment configs where micro-streaming is intended, guaranteeing that static pre-renders resolve at build time without dynamic bailout warnings.

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 Invariant critical for AI coding assistants?

Enforces strict boundary encapsulation between static CDN pre-rendered shells and dynamic React Server Components (RSC) micro-streams. Prevents dynamic request accessors (headers, cookies, searchParams, uncached fetch calls) from leaking into root execution contexts, which collapses the static prerender shell into full dynamic SSR and introduces cascading client-side waterfalls. 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 Accessor Leakage in Outer Layouts and Top-Level Shells Collapsing PPR) 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