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-dynamic-hole-isolation-next-js-15-parti-864

Next.js 15 PPR Dynamic Hole Boundary Isolation & Static Shell Preservation

Enforces strict isolation of runtime dynamic I/O (cookies, headers, uncached data) inside localized React Suspense boundaries under Next.js 15 Partial Prerendering (PPR). Guarantees an immutable static document shell emitted at build time for sub-50ms edge TTFB while streaming dynamic holes concurrently without execution waterfalls.

Prohibited Anti-Pattern: Dynamic API Hoisting De-optimizing Static Shells into Blocking Dynamic SSR

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Next.js 15 PPR Dynamic Hole Boundary Isolation & Static Shell Preservation - Enforces strict isolation of runtime dynamic I/O (cookies, headers, uncached data) inside localized React Suspense boundaries under Next.js 15 Partial Prerendering (PPR). Guarantees an immutable static document shell emitted at build time for sub-50ms edge TTFB while streaming dynamic holes concurrently without execution 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-dynamic-hole-isolation-next-js-15-parti-864"
---

# Next.js 15 PPR Dynamic Hole Boundary Isolation & Static Shell Preservation

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Dynamic API Hoisting De-optimizing Static Shells into Blocking Dynamic SSR

## System Constraints
You are a Principal Software Architect enforcing deterministic Next.js 15 Partial Prerendering (PPR) dynamic hole boundaries. You must reject any code where dynamic APIs (such as cookies(), headers(), dynamic params, searchParams, or uncached database/fetch calls) are executed outside of an explicit React Suspense boundary or hoisted to page/layout roots. Ensure the static shell is completely deterministic, pre-renderable at build time, and delivers instant (<50ms) edge TTFB.

## Strict Guidelines
- Engineers MUST ALWAYS isolate dynamic I/O operations (cookies(), headers(), searchParams, connection(), and uncached fetches) strictly inside dedicated, leaf-level Server Components wrapped in a <Suspense> boundary.
- Engineers MUST NOT call dynamic APIs (cookies(), headers()) or perform dynamic fetching in layouts, page root components, or static navigation components.
- Components acting as dynamic holes MUST provide deterministic, layout-stable static fallbacks in their <Suspense> boundaries to eliminate cumulative layout shift (CLS) during streaming hydration.
- Services and data fetchers MUST execute concurrently inside independent dynamic holes rather than chaining sequential promises across nested server boundaries to prevent server-side streaming waterfalls.
- Engineers MUST declare 'export const experimental_ppr = true' at the segment route level when targeting incremental or full PPR deployment.

## Bad vs Good Implementations
### Dynamic Cart & Feed Boundary Isolation vs Root Dynamic De-optimization

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Accessing cookies() and awaiting an uncached dynamic fetch directly in the Page component forces the Next.js runtime to bail out of prerendering the static shell. The static navigation and hero banner are delayed until the backend fetch resolves, destroying the sub-50ms TTFB guarantee.
```typescript
// app/dashboard/page.tsx
import { cookies } from 'next/headers';
import { CartSummary } from '@/components/cart-summary';
import { StaticNav } from '@/components/static-nav';

export const experimental_ppr = true;

// ANTI-PATTERN: Accessing dynamic APIs at the page root scope de-optimizes
// the entire document shell into blocking dynamic SSR, collapsing TTFB.
export default async function DashboardPage() {
  const cookieStore = await cookies();
  const token = cookieStore.get('auth-token')?.value;
  const cartData = await fetch(`https://api.internal/cart`, {
    headers: { Authorization: `Bearer ${token}` },
    cache: 'no-store'
  }).then(res => res.json());

  return (
    <main className="dashboard-container">
      <StaticNav />
      <header className="hero-banner">Welcome Back</header>
      <CartSummary data={cartData} />
    </main>
  );
}
```

#### Production Standard (Correct)
> **Standard**: The Page component contains no dynamic dependencies, allowing Next.js 15 PPR to generate an immutable static HTML shell served instantly from the CDN edge. The dynamic hole reads cookies and streams in via HTTP chunked transfer inside its Suspense boundary without blocking static shell TTFB.
```typescript
// app/dashboard/page.tsx
import { Suspense } from 'react';
import { StaticNav } from '@/components/static-nav';
import { CartSummaryHole, CartSummarySkeleton } from '@/components/cart-summary-hole';

export const experimental_ppr = true;

// PRODUCTION FIX: The page shell is completely static and pre-rendered at build time.
// Dynamic data fetching is pushed down to an isolated leaf Server Component behind Suspense.
export default function DashboardPage() {
  return (
    <main className="dashboard-container">
      <StaticNav />
      <header className="hero-banner">Welcome Back</header>
      <Suspense fallback={<CartSummarySkeleton />}>
        <CartSummaryHole />
      </Suspense>
    </main>
  );
}

// components/cart-summary-hole.tsx
import { cookies } from 'next/headers';

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

  return <div className="cart-summary-content">Items: {data.itemCount}</div>;
}

export function CartSummarySkeleton() {
  return <div className="cart-skeleton h-12 w-48 animate-pulse bg-slate-200" />;
}
```
Recommended MCP Servers (mcp-serverlist.com)

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

Next.js Build Trace Analyzer
Inspects Next.js compilation manifests to detect unintended dynamic bailouts and dynamic boundary leaks.
Recommended Agent Skills (askills.dev)

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

Next.js Bundle & PPR Validator
CLI tool to simulate PPR static shell generation and flag dynamic bailouts before deployment.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: Next.js 15 PPR Dynamic Hole Boundary Isolation & Static Shell Preservation

Next.js 15 PPR Dynamic Hole Boundary Isolation & Static Shell Preservation defines an industrial-grade behavioral standard for frontend engineering. Enforces strict isolation of runtime dynamic I/O (cookies, headers, uncached data) inside localized React Suspense boundaries under Next.js 15 Partial Prerendering (PPR). Guarantees an immutable static document shell emitted at build time for sub-50ms edge TTFB while streaming dynamic holes concurrently without execution 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 API Hoisting De-optimizing Static Shells into Blocking Dynamic 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 DriftDynamic API Hoisting De-optimizing Static Shells into Blocking Dynamic 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 I/O operations (cookies(), headers(), searchParams, connection(), and uncached fetches) strictly inside dedicated, leaf-level Server Components wrapped in a <Suspense> boundary.

Engineers MUST ALWAYS isolate dynamic I/O operations (cookies(), headers(), searchParams, connection(), and uncached fetches) strictly inside dedicated, leaf-level 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 APIs (cookies(), headers()) or perform dynamic fetching in layouts, page root components, or static navigation components.

Engineers MUST NOT call dynamic APIs (cookies(), headers()) or perform dynamic fetching in layouts, page root components, or static navigation components.

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 holes MUST provide deterministic, layout-stable static fallbacks in their <Suspense> boundaries to eliminate cumulative layout shift (CLS) during streaming hydration.

Components acting as dynamic holes MUST provide deterministic, layout-stable static fallbacks in their <Suspense> boundaries to eliminate cumulative layout shift (CLS) during streaming hydration.

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 and data fetchers MUST execute concurrently inside independent dynamic holes rather than chaining sequential promises across nested server boundaries to prevent server-side streaming waterfalls.

Services and data fetchers MUST execute concurrently inside independent dynamic holes rather than chaining sequential promises across nested server boundaries to prevent server-side streaming waterfalls.

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 declare 'export const experimental_ppr = true' at the segment route level when targeting incremental or full PPR deployment.

Engineers MUST declare 'export const experimental_ppr = true' at the segment route level when targeting incremental or full PPR deployment.

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 PPR Dynamic Hole Boundary Isolation & Static Shell Preservation critical for AI coding assistants?

Enforces strict isolation of runtime dynamic I/O (cookies, headers, uncached data) inside localized React Suspense boundaries under Next.js 15 Partial Prerendering (PPR). Guarantees an immutable static document shell emitted at build time for sub-50ms edge TTFB while streaming dynamic holes concurrently without execution 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 API Hoisting De-optimizing Static Shells into Blocking Dynamic 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