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-fallback-boundary-invariant

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

Enforces strict isolation of dynamic Server Components inside explicit React Suspense boundaries when Partial Prerendering (PPR) is enabled. Calling runtime dynamic APIs (cookies, headers, searchParams, un-cached data queries) outside a Suspense boundary de-optimizes the entire prerendered shell into blocking dynamic SSR, introducing waterfall cascades and hydration mismatches.

Prohibited Anti-Pattern: Leaking Dynamic Request Contexts into Prerendered Shell Layouts Without Suspense Isolation

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Next.js 15 Partial Prerendering (PPR) Fallback Boundary Invariant - Enforces strict isolation of dynamic Server Components inside explicit React Suspense boundaries when Partial Prerendering (PPR) is enabled. Calling runtime dynamic APIs (cookies, headers, searchParams, un-cached data queries) outside a Suspense boundary de-optimizes the entire prerendered shell into blocking dynamic SSR, introducing waterfall cascades and hydration mismatches.
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-fallback-boundary-invariant"
---

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

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Leaking Dynamic Request Contexts into Prerendered Shell Layouts Without Suspense Isolation

## System Constraints
You are a Principal Software Architect enforcing Next.js 15 Partial Prerendering (PPR) invariants. You must prevent dynamic request cascades and static shell de-optimizations by mandating that all dynamic APIs (cookies, headers, connection, dynamic fetches, un-cached database reads, dynamic searchParams) are isolated behind deterministic Suspense boundaries with non-null, layout-stable fallbacks.

## Strict Guidelines
- Engineers MUST ALWAYS isolate components accessing dynamic runtime APIs (e.g., `cookies()`, `headers()`, `searchParams`, `connection()`) within an explicit `<Suspense fallback={<StaticFallback />}>` boundary.
- Engineers MUST NOT access dynamic functions directly in root layouts, static shell wrappers, or top-level page components configured with `export const experimental_ppr = true`.
- Components acting as dynamic boundaries MUST define layout-stable fallbacks matching the exact dimensional box and visual structure of the resolved component to prevent Cumulative Layout Shift (CLS) and hydration mismatch.
- Code SHOULD pass dynamic parameters down via Promises when leveraging React 19 / Next.js 15 async APIs, resolving them inside the dynamic leaf components using `use()` or async/await within the boundary.
- Services MUST differentiate between static pre-computable data (which remains outside Suspense) and personalized/per-request data (which MUST be deferred inside Suspense).

## Bad vs Good Implementations
### Dynamic Cart & User Context in Static Page Shell

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Invoking `await cookies()` at the root of the page component forces the entire route to bail out of prerendering at build time. The static shell (including ProductGrid) is converted into a blocking runtime dynamic response.
```typescript
import { cookies } from 'next/headers';
import { Header } from '@/components/Header';
import { ProductGrid } from '@/components/ProductGrid';

export const experimental_ppr = true;

// ANTI-PATTERN: Awaiting cookies() directly in the page body de-optimizes
// the entire static shell. PPR cannot prerender the ProductGrid statically
// because execution halts at the top-level cookie resolution.
export default async function StorePage() {
  const cookieStore = await cookies();
  const cartId = cookieStore.get('cart_id')?.value;
  const cartData = cartId ? await fetchCart(cartId) : null;

  return (
    <main className="container mx-auto p-4">
      <Header cartCount={cartData?.itemCount ?? 0} />
      <ProductGrid />
    </main>
  );
}
```

#### Production Standard (Correct)
> **Standard**: The dynamic `cookies()` call is encapsulated inside `DynamicCartBadge` and wrapped with a structural `<Suspense fallback={<HeaderCartSkeleton />}>`. Next.js 15 prerenders the static shell (HeaderShell and ProductGrid) instantly, streaming the dynamic badge on request.
```typescript
import { Suspense } from 'react';
import { cookies } from 'next/headers';
import { HeaderShell, HeaderCartSkeleton } from '@/components/Header';
import { ProductGrid } from '@/components/ProductGrid';

export const experimental_ppr = true;

async function DynamicCartBadge() {
  const cookieStore = await cookies();
  const cartId = cookieStore.get('cart_id')?.value;
  const cartData = cartId ? await fetchCart(cartId) : null;

  return <span className="badge">{cartData?.itemCount ?? 0}</span>;
}

// PRODUCTION FIX: The page shell and ProductGrid remain 100% static.
// Dynamic per-user data is isolated behind a Suspense boundary with
// a structural fallback matching target dimensions.
export default function StorePage() {
  return (
    <main className="container mx-auto p-4">
      <HeaderShell>
        <Suspense fallback={<HeaderCartSkeleton />}>
          <DynamicCartBadge />
        </Suspense>
      </HeaderShell>
      <ProductGrid />
    </main>
  );
}
```
Recommended MCP Servers (mcp-serverlist.com)

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

Next.js DevTools MCP
Inspects route segment configurations, PPR manifests, and dynamic bailing traces during compilation.
Recommended Agent Skills (askills.dev)

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

Next.js Build Route Trace Analyzer
Verifies prerender manifests and static/dynamic route segment emission during CI/CD builds.
Architectural Specification & Invariant Rationale

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

Next.js 15 Partial Prerendering (PPR) Fallback Boundary Invariant defines an industrial-grade behavioral standard for frontend engineering. Enforces strict isolation of dynamic Server Components inside explicit React Suspense boundaries when Partial Prerendering (PPR) is enabled. Calling runtime dynamic APIs (cookies, headers, searchParams, un-cached data queries) outside a Suspense boundary de-optimizes the entire prerendered shell into blocking dynamic SSR, introducing waterfall cascades and hydration mismatches. 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 Request Contexts into Prerendered Shell Layouts Without Suspense Isolation 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 Request Contexts into Prerendered Shell Layouts Without Suspense IsolationCritical
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 components accessing dynamic runtime APIs (e.g., `cookies()`, `headers()`, `searchParams`, `connection()`) within an explicit `<Suspense fallback={<StaticFallback />}>` boundary.

Engineers MUST ALWAYS isolate components accessing dynamic runtime APIs (e.g., `cookies()`, `headers()`, `searchParams`, `connection()`) within an explicit `<Suspense fallback={<StaticFallback />}>` 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 dynamic functions directly in root layouts, static shell wrappers, or top-level page components configured with `export const experimental_ppr = true`.

Engineers MUST NOT access dynamic functions directly in root layouts, static shell wrappers, 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 acting as dynamic boundaries MUST define layout-stable fallbacks matching the exact dimensional box and visual structure of the resolved component to prevent Cumulative Layout Shift (CLS) and hydration mismatch.

Components acting as dynamic boundaries MUST define layout-stable fallbacks matching the exact dimensional box and visual structure of the resolved component to prevent Cumulative Layout Shift (CLS) and hydration mismatch.

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 pass dynamic parameters down via Promises when leveraging React 19 / Next.js 15 async APIs, resolving them inside the dynamic leaf components using `use()` or async/await within the boundary.

Code SHOULD pass dynamic parameters down via Promises when leveraging React 19 / Next.js 15 async APIs, resolving them inside the dynamic leaf components using `use()` or async/await within the 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

Services MUST differentiate between static pre-computable data (which remains outside Suspense) and personalized/per-request data (which MUST be deferred inside Suspense).

Services MUST differentiate between static pre-computable data (which remains outside Suspense) and personalized/per-request data (which MUST be deferred inside 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.
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) Fallback Boundary Invariant critical for AI coding assistants?

Enforces strict isolation of dynamic Server Components inside explicit React Suspense boundaries when Partial Prerendering (PPR) is enabled. Calling runtime dynamic APIs (cookies, headers, searchParams, un-cached data queries) outside a Suspense boundary de-optimizes the entire prerendered shell into blocking dynamic SSR, introducing waterfall cascades and hydration mismatches. 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 Request Contexts into Prerendered Shell Layouts Without Suspense Isolation) 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