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-855

Next.js 15 Partial Prerendering Dynamic Hole Isolation and Layout Stability

Enforces deterministic boundaries between static prerendered HTML shells and dynamic asynchronous streaming segments under Next.js 15 Partial Prerendering (PPR). Guarantees dynamic data fetching functions execute strictly within explicitly bounded React Suspense boundaries equipped with dimension-locked fallbacks to eliminate cascading layout shifts (CLS) and TTFB regression over multiplexed HTTP/3 connections.

Prohibited Anti-Pattern: Dynamic Scope Creep Causing Static Shell De-opt and Cascading Layout Shifts

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Next.js 15 Partial Prerendering Dynamic Hole Isolation and Layout Stability - Enforces deterministic boundaries between static prerendered HTML shells and dynamic asynchronous streaming segments under Next.js 15 Partial Prerendering (PPR). Guarantees dynamic data fetching functions execute strictly within explicitly bounded React Suspense boundaries equipped with dimension-locked fallbacks to eliminate cascading layout shifts (CLS) and TTFB regression over multiplexed HTTP/3 connections.
globs: app/**/{page,layout,loading,template}.{ts,tsx}, src/app/**/{page,layout,loading,template}.{ts,tsx}, components/**/*.{ts,tsx}, src/components/**/*.{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-855"
---

# Next.js 15 Partial Prerendering Dynamic Hole Isolation and Layout Stability

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Dynamic Scope Creep Causing Static Shell De-opt and Cascading Layout Shifts

## System Constraints
You are a Principal Software Architect enforcing Next.js 15 Partial Prerendering (PPR) dynamic hole isolation invariants. Dynamic execution contexts (e.g., cookies(), headers(), searchParams, non-cached fetch) MUST NOT leak into parent component execution paths, and all dynamic holes MUST be wrapped in explicit Suspense boundaries with matching dimensional fallback skeletons to prevent CLS under HTTP/3 streaming multiplexing.

## Strict Guidelines
- Engineers MUST ALWAYS isolate dynamic API consumption (such as `cookies()`, `headers()`, and runtime data fetches) inside dedicated child Server Components isolated by `<Suspense>` boundaries.
- Engineers MUST NOT access dynamic functions (`cookies()`, `headers()`, runtime `searchParams`) directly at the root level of a layout or page if that shell is intended to prerender statically.
- Components acting as dynamic fallback skeletons MUST declare explicit CSS containment, width, height, or aspect-ratio constraints identical to the hydrated dynamic component to prevent Cumulative Layout Shift (CLS).
- Services MUST declare experimental PPR flags (`export const experimental_ppr = true;` or `'incremental'`) only when sub-trees cleanly separate static shell rendering from dynamic holes.
- Engineers MUST NEVER interleave dynamic I/O awaits inside the same asynchronous frame as static layout elements, as this collapses PPR streaming back into dynamic SSR TTFB latencies.

## Bad vs Good Implementations
### Dynamic Hole Isolation with Geometrically Stable Suspense Skeletons

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Calling `cookies()` directly in the root page component taints the entire compilation unit as dynamic. The static shell cannot be prerendered at build time or served from the edge cache, negating Next.js 15 Partial Prerendering and forcing TTFB to block on network fetches.
```typescript
import { cookies } from 'next/headers';

export const experimental_ppr = true;

// ANTI-PATTERN: Direct invocation of dynamic functions in page root de-opts static shell
export default async function UserDashboardPage() {
  const cookieStore = await cookies();
  const token = cookieStore.get('auth_token')?.value;
  const response = await fetch(`https://api.internal/profile`, {
    headers: { Authorization: `Bearer ${token}` },
    cache: 'no-store'
  });
  const profile = await response.json();

  return (
    <main className="dashboard-container">
      <header className="static-header">
        <h1>Dashboard Shell</h1>
      </header>
      {/* Dynamic and static rendering collapsed; entire page blocks on dynamic I/O */}
      <section className="profile-panel">
        <h2>Welcome, {profile.name}</h2>
      </section>
    </main>
  );
}
```

#### Production Standard (Correct)
> **Standard**: The dynamic context (`cookies()`) and dynamic data fetch are fully encapsulated in `DynamicUserProfile`. The page component immediately emits the prerendered static shell, streaming the dynamic hole over HTTP/3 into an exact-dimension fallback skeleton that eliminates layout shifts.
```typescript
import { Suspense } from 'react';
import { cookies } from 'next/headers';

export const experimental_ppr = true;

// Static Shell prerendered to static HTML at build time
export default function UserDashboardPage() {
  return (
    <main className="dashboard-container">
      <header className="static-header">
        <h1>Dashboard Shell</h1>
      </header>
      {/* Dynamic Hole isolated; fallback enforces exact box model constraints */}
      <Suspense fallback={<ProfileSkeleton />}>
        <DynamicUserProfile />
      </Suspense>
    </main>
  );
}

// Isolated Dynamic Stream Hole
async function DynamicUserProfile() {
  const cookieStore = await cookies();
  const token = cookieStore.get('auth_token')?.value;
  const response = await fetch(`https://api.internal/profile`, {
    headers: { Authorization: `Bearer ${token}` },
    cache: 'no-store'
  });
  const profile = await response.json();

  return (
    <section className="profile-panel h-24 w-full contain-layout">
      <h2>Welcome, {profile.name}</h2>
    </section>
  );
}

// Dimensionally matched skeleton preventing CLS under HTTP/3 chunk arrival
function ProfileSkeleton() {
  return (
    <div 
      aria-busy="true" 
      aria-live="polite" 
      className="profile-panel h-24 w-full animate-pulse bg-gray-200 contain-layout"
    />
  );
}
```
Recommended MCP Servers (mcp-serverlist.com)

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

Next.js Build & Performance Analyzer MCP
Inspects static vs dynamic segment outputs and flags de-optimized route segments under Next.js 15 builds.
Recommended Agent Skills (askills.dev)

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

Lighthouse CI Layout & Streaming Auditor
Verifies zero CLS violations and monitors Time to First Byte across partially prerendered routes.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: Next.js 15 Partial Prerendering Dynamic Hole Isolation and Layout Stability

Next.js 15 Partial Prerendering Dynamic Hole Isolation and Layout Stability defines an industrial-grade behavioral standard for frontend engineering. Enforces deterministic boundaries between static prerendered HTML shells and dynamic asynchronous streaming segments under Next.js 15 Partial Prerendering (PPR). Guarantees dynamic data fetching functions execute strictly within explicitly bounded React Suspense boundaries equipped with dimension-locked fallbacks to eliminate cascading layout shifts (CLS) and TTFB regression over multiplexed HTTP/3 connections. 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 Scope Creep Causing Static Shell De-opt and Cascading Layout Shifts 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 Scope Creep Causing Static Shell De-opt and Cascading Layout ShiftsCritical
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 consumption (such as `cookies()`, `headers()`, and runtime data fetches) inside dedicated child Server Components isolated by `<Suspense>` boundaries.

Engineers MUST ALWAYS isolate dynamic API consumption (such as `cookies()`, `headers()`, and runtime data fetches) inside dedicated child Server Components isolated by `<Suspense>` boundaries.

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 (`cookies()`, `headers()`, runtime `searchParams`) directly at the root level of a layout or page if that shell is intended to prerender statically.

Engineers MUST NOT access dynamic functions (`cookies()`, `headers()`, runtime `searchParams`) directly at the root level of a layout or page if that shell is intended to prerender statically.

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 fallback skeletons MUST declare explicit CSS containment, width, height, or aspect-ratio constraints identical to the hydrated dynamic component to prevent Cumulative Layout Shift (CLS).

Components acting as dynamic fallback skeletons MUST declare explicit CSS containment, width, height, or aspect-ratio constraints identical to the hydrated dynamic 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.
4

Services MUST declare experimental PPR flags (`export const experimental_ppr = true

Services MUST declare experimental PPR flags (`export const experimental_ppr = true;` or `'incremental'`) only when sub-trees cleanly separate static shell rendering from dynamic holes.

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 interleave dynamic I/O awaits inside the same asynchronous frame as static layout elements, as this collapses PPR streaming back into dynamic SSR TTFB latencies.

Engineers MUST NEVER interleave dynamic I/O awaits inside the same asynchronous frame as static layout elements, as this collapses PPR streaming back into dynamic SSR TTFB latencies.

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 Dynamic Hole Isolation and Layout Stability critical for AI coding assistants?

Enforces deterministic boundaries between static prerendered HTML shells and dynamic asynchronous streaming segments under Next.js 15 Partial Prerendering (PPR). Guarantees dynamic data fetching functions execute strictly within explicitly bounded React Suspense boundaries equipped with dimension-locked fallbacks to eliminate cascading layout shifts (CLS) and TTFB regression over multiplexed HTTP/3 connections. 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 Scope Creep Causing Static Shell De-opt and Cascading Layout Shifts) 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