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: next15-ppr-shell-stream-hydration-invariant

Next.js 15 Partial Prerendering (PPR) Shell-Stream Hydration Invariant

Enforces strict isolation of dynamic runtime access (cookies, headers, uncached data) behind explicit Suspense boundaries in Next.js 15 Partial Prerendering (PPR). Prevents static shell de-optimization, delayed Time-to-First-Byte (TTFB), and client-side hydration thrashing caused by mismatched skeleton geometries under network jitter.

Prohibited Anti-Pattern: Leaking Dynamic Request Data into Route Shells and Unbounded Fallback Skeletons

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Next.js 15 Partial Prerendering (PPR) Shell-Stream Hydration Invariant - Enforces strict isolation of dynamic runtime access (cookies, headers, uncached data) behind explicit Suspense boundaries in Next.js 15 Partial Prerendering (PPR). Prevents static shell de-optimization, delayed Time-to-First-Byte (TTFB), and client-side hydration thrashing caused by mismatched skeleton geometries under network jitter.
globs: app/**/*.{ts,tsx}, src/app/**/*.{ts,tsx}
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/next15-ppr-shell-stream-hydration-invariant"
---

# Next.js 15 Partial Prerendering (PPR) Shell-Stream Hydration Invariant

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Leaking Dynamic Request Data into Route Shells and Unbounded Fallback Skeletons

## System Constraints
You are a Principal Software Architect enforcing Next.js 15 Partial Prerendering (PPR) Shell-Stream Hydration Invariants. You must ensure that static shells remain completely decoupled from dynamic runtime context, preventing route-level de-optimization and client hydration tearing.

## Strict Guidelines
- Engineers MUST ALWAYS isolate dynamic data calls (`cookies()`, `headers()`, `searchParams`, uncached fetches, `connection()`) inside leaf Server Components wrapped in an explicit `<Suspense fallback={<StaticSkeleton />}>` boundary.
- Engineers MUST NOT access dynamic functions (`cookies()`, `headers()`) in layout components or at the root of a page component configured with `experimental_ppr = true`.
- Components NEVER render non-deterministic fallbacks; Suspense fallbacks MUST precisely mirror the box model dimensions (height, width, display grid/flex properties) of the resolved content to prevent Cumulative Layout Shift (CLS) and DOM thrashing during hydration.
- Code SHOULD explicitly export `export const experimental_ppr = true;` on routes utilizing Partial Prerendering to trigger compile-time validation.
- Services MUST utilize React 19 `use()` or async Server Components exclusively inside Suspense boundaries when resolving dynamic request-time promises.
- Engineers MUST NOT place interactive Client Components (`'use client'`) directly as the Suspense wrapper when receiving dynamic server streams without stabilizing keys to avoid client-side DOM reconciliation errors under packet jitter.

## Bad vs Good Implementations
### Dynamic Data Leak vs. Isolated PPR Suspense Stream

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Calling cookies() in the top-level Page component de-opts the entire route out of Partial Prerendering. The static navigation and layout cannot be served instantly from the edge cache, delaying TTFB until server-side cookie resolution completes.
```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: Calling cookies() at the page root destroys the static shell.
// Next.js de-optimizes the entire page to dynamic SSR, blocking TTFB
// and causing hydration thrashing on slow connections.
export default async function DashboardPage() {
  const cookieStore = await cookies();
  const token = cookieStore.get('auth-token')?.value;
  
  return (
    <main className="dashboard-container">
      <StaticNav />
      <section className="metrics-grid">
        {/* Non-isolated dynamic fetch without fallback dimensions */}
        <UserMetrics token={token} />
      </section>
    </main>
  );
}
```

#### Production Standard (Correct)
> **Standard**: The page root contains zero dynamic access, enabling the edge to stream the static shell and MetricsSkeleton instantly. Dynamic context (cookies, no-store fetch) is confined to DynamicMetricsStream inside Suspense, avoiding shell de-optimization and hydration thrashing.
```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/metrics-skeleton';

export const experimental_ppr = true;

// GUARANTEED STATIC SHELL: Instant edge TTFB
export default function DashboardPage() {
  return (
    <main className="dashboard-container">
      <StaticNav />
      <section className="metrics-grid">
        {/* Suspense isolates dynamic stream; fallback prevents CLS/thrashing */}
        <Suspense fallback={<MetricsSkeleton />}>
          <DynamicMetricsStream />
        </Suspense>
      </section>
    </main>
  );
}

// Dynamic leaf server component safely isolates runtime request context
async function DynamicMetricsStream() {
  const cookieStore = await cookies();
  const token = cookieStore.get('auth-token')?.value;
  
  const res = await fetch('https://api.internal/metrics', {
    headers: { Authorization: `Bearer ${token}` },
    cache: 'no-store'
  });
  const data = await res.json();

  return <div className="metrics-card-resolved">{data.value}</div>;
}
```
Recommended MCP Servers (mcp-serverlist.com)

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

Next.js Architecture Inspector
Validates static shell generation and dynamic bailout paths during Next.js build compilation.
Recommended Agent Skills (askills.dev)

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

Next.js Build & PPR Profiler
Analyzes App Router route-segment configurations to verify PPR prerendered shell indicators (○) and dynamic holes (◐).
Architectural Specification & Invariant Rationale

Architectural Invariant Design: Next.js 15 Partial Prerendering (PPR) Shell-Stream Hydration Invariant

Next.js 15 Partial Prerendering (PPR) Shell-Stream Hydration Invariant defines an industrial-grade behavioral standard for frontend engineering. Enforces strict isolation of dynamic runtime access (cookies, headers, uncached data) behind explicit Suspense boundaries in Next.js 15 Partial Prerendering (PPR). Prevents static shell de-optimization, delayed Time-to-First-Byte (TTFB), and client-side hydration thrashing caused by mismatched skeleton geometries under network jitter. 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 Data into Route Shells and Unbounded Fallback Skeletons 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 Data into Route Shells and Unbounded Fallback SkeletonsCritical
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 data calls (`cookies()`, `headers()`, `searchParams`, uncached fetches, `connection()`) inside leaf Server Components wrapped in an explicit `<Suspense fallback={<StaticSkeleton />}>` boundary.

Engineers MUST ALWAYS isolate dynamic data calls (`cookies()`, `headers()`, `searchParams`, uncached fetches, `connection()`) inside leaf Server Components wrapped in an explicit `<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 dynamic functions (`cookies()`, `headers()`) in layout components or at the root of a page component configured with `experimental_ppr = true`.

Engineers MUST NOT access dynamic functions (`cookies()`, `headers()`) in layout components or at the root of a page component configured with `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 NEVER render non-deterministic fallbacks

Components NEVER render non-deterministic fallbacks; Suspense fallbacks MUST precisely mirror the box model dimensions (height, width, display grid/flex properties) of the resolved content to prevent Cumulative Layout Shift (CLS) and DOM thrashing during 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

Code SHOULD explicitly export `export const experimental_ppr = true

Code SHOULD explicitly export `export const experimental_ppr = true;` on routes utilizing Partial Prerendering to trigger compile-time validation.

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 utilize React 19 `use()` or async Server Components exclusively inside Suspense boundaries when resolving dynamic request-time promises.

Services MUST utilize React 19 `use()` or async Server Components exclusively inside Suspense boundaries when resolving dynamic request-time promises.

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

Engineers MUST NOT place interactive Client Components (`'use client'`) directly as the Suspense wrapper when receiving dynamic server streams without stabilizing keys to avoid client-side DOM reconciliation errors under packet jitter.

Engineers MUST NOT place interactive Client Components (`'use client'`) directly as the Suspense wrapper when receiving dynamic server streams without stabilizing keys to avoid client-side DOM reconciliation errors under packet jitter.

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) Shell-Stream Hydration Invariant critical for AI coding assistants?

Enforces strict isolation of dynamic runtime access (cookies, headers, uncached data) behind explicit Suspense boundaries in Next.js 15 Partial Prerendering (PPR). Prevents static shell de-optimization, delayed Time-to-First-Byte (TTFB), and client-side hydration thrashing caused by mismatched skeleton geometries under network jitter. 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 Data into Route Shells and Unbounded Fallback Skeletons) 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