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-static-dynamic-isolation-perimeter

Next.js 15 PPR Static-Dynamic Isolation Perimeter & Boundary Enforcement

Enforces strict structural boundaries between edge-cacheable static prerender shells and dynamic React Server Component streams under Next.js 15 Partial Prerendering (PPR). Prevents catastrophic static-deoptimization, user credential leakage in edge-cached prerender payloads, and Cumulative Layout Shift (CLS) caused by asymmetric fallback geometries.

Prohibited Anti-Pattern: Leaking dynamic request-bound APIs into static route shells causing edge cache poisoning or total de-optimization

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Next.js 15 PPR Static-Dynamic Isolation Perimeter & Boundary Enforcement - Enforces strict structural boundaries between edge-cacheable static prerender shells and dynamic React Server Component streams under Next.js 15 Partial Prerendering (PPR). Prevents catastrophic static-deoptimization, user credential leakage in edge-cached prerender payloads, and Cumulative Layout Shift (CLS) caused by asymmetric fallback geometries.
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-static-dynamic-isolation-perimeter"
---

# Next.js 15 PPR Static-Dynamic Isolation Perimeter & Boundary Enforcement

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Leaking dynamic request-bound APIs into static route shells causing edge cache poisoning or total de-optimization

## System Constraints
You are a Principal Software Architect enforcing Next.js 15 Partial Prerendering (PPR) architectural boundaries. In Next.js 15, routes configured with `experimental_ppr = true` or per-route segment configs split execution between static build-time generation (cached at edge) and dynamic runtime streams. You must reject any code that directly accesses dynamic request headers, cookies, searchParams, or un-cached data sources within the static root shell without an isolating <Suspense> boundary. Furthermore, you must verify that dynamic boundaries have deterministic fallback geometries that eliminate Cumulative Layout Shift (CLS).

## Strict Guidelines
- Components accessing dynamic APIs (e.g., `cookies()`, `headers()`, `searchParams`, or un-cached `fetch`) MUST ALWAYS be enclosed in an explicit React `<Suspense>` boundary within the route segment.
- Layout components (`layout.tsx`) MUST NOT directly access dynamic request primitives (`cookies()`, `headers()`); dynamic user context MUST be delegated to leaf components wrapped in `<Suspense>`.
- Engineers MUST ALWAYS provide a `<Suspense>` fallback whose box-model dimensions, display model, and layout footprint match the resolved dynamic component to prevent Cumulative Layout Shift (CLS).
- Dynamic components MUST NEVER execute authorization checks or session-token reads in a manner that serializes credential tokens or PII into the static prerender chunk.
- Routes utilizing PPR MUST explicitly declare `export const experimental_ppr = true` or inherit from a valid root PPR configuration flag in `next.config.ts`.
- Dynamic server components SHOULD leverage `await connection()` from `next/server` when explicitly asserting non-blocking dynamic execution paths before streaming headers.

## Bad vs Good Implementations
### Isolating Dynamic User Session from Edge-Cacheable Static Shell

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Accessing `cookies()` at the page root forces Next.js to de-opt the entire route segment from static prerendering. The static navigation shell, headers, and `StaticMetrics` component will fail to be edge-cached during build time, penalizing TTFB and increasing edge compute costs.
```typescript
// app/dashboard/page.tsx
import { cookies } from 'next/headers';
import { UserProfile } from '@/components/UserProfile';
import { StaticMetrics } from '@/components/StaticMetrics';

export const experimental_ppr = true;

// ANTI-PATTERN: Direct invocation of dynamic cookies() at the page root
// destroys the static shell, causing the entire route to opt out of edge-caching.
export default async function DashboardPage() {
  const cookieStore = await cookies();
  const token = cookieStore.get('auth_token')?.value;

  return (
    <main className="dashboard-container">
      <header className="h-16 border-b flex items-center px-4">
        <h1>Operations Dashboard</h1>
        {/* Dynamic component rendered inline without a Suspense boundary */}
        <UserProfile token={token} />
      </header>
      <StaticMetrics />
    </main>
  );
}
```

#### Production Standard (Correct)
> **Standard**: By isolating `cookies()` inside `UserProfileContainer` wrapped with `<Suspense>`, Next.js generates an edge-cacheable static shell containing the header and `StaticMetrics`. The user profile dynamic hole streams concurrently, and `UserProfileSkeleton` guarantees zero layout shift.
```typescript
// app/dashboard/page.tsx
import { Suspense } from 'react';
import { UserProfileContainer } from '@/components/UserProfileContainer';
import { UserProfileSkeleton } from '@/components/UserProfileSkeleton';
import { StaticMetrics } from '@/components/StaticMetrics';

export const experimental_ppr = true;

// PROD-READY: Page root generates a 100% static shell cached on edge CDN.
// Dynamic request boundaries are isolated behind Suspense holes.
export default function DashboardPage() {
  return (
    <main className="dashboard-container">
      <header className="h-16 border-b flex items-center justify-between px-4">
        <h1 className="text-lg font-semibold">Operations Dashboard</h1>
        <Suspense fallback={<UserProfileSkeleton className="h-10 w-32 rounded-full" />}>
          <UserProfileContainer />
        </Suspense>
      </header>
      <StaticMetrics />
    </main>
  );
}

// components/UserProfileContainer.tsx
import { cookies } from 'next/headers';
import { UserProfile } from './UserProfile';
import { fetchAuthUser } from '@/lib/auth';

export async function UserProfileContainer() {
  const cookieStore = await cookies();
  const token = cookieStore.get('auth_token')?.value;
  const user = token ? await fetchAuthUser(token) : null;

  return <UserProfile user={user} />;
}
```
Recommended MCP Servers (mcp-serverlist.com)

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

Next.js Build & PPR Inspector MCP
Analyzes Next.js route segments, static generation manifests, and PPR prerender-to-dynamic chunk boundaries.
Recommended Agent Skills (askills.dev)

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

Next.js Route Segment Analyzer
CLI utility to inspect Next.js build manifests for dynamic server usage warnings and unintended dynamic bailout.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: Next.js 15 PPR Static-Dynamic Isolation Perimeter & Boundary Enforcement

Next.js 15 PPR Static-Dynamic Isolation Perimeter & Boundary Enforcement defines an industrial-grade behavioral standard for frontend engineering. Enforces strict structural boundaries between edge-cacheable static prerender shells and dynamic React Server Component streams under Next.js 15 Partial Prerendering (PPR). Prevents catastrophic static-deoptimization, user credential leakage in edge-cached prerender payloads, and Cumulative Layout Shift (CLS) caused by asymmetric fallback geometries. 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-bound APIs into static route shells causing edge cache poisoning or total de-optimization 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-bound APIs into static route shells causing edge cache poisoning or total de-optimizationCritical
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

Components accessing dynamic APIs (e.g., `cookies()`, `headers()`, `searchParams`, or un-cached `fetch`) MUST ALWAYS be enclosed in an explicit React `<Suspense>` boundary within the route segment.

Components accessing dynamic APIs (e.g., `cookies()`, `headers()`, `searchParams`, or un-cached `fetch`) MUST ALWAYS be enclosed in an explicit React `<Suspense>` boundary within the route segment.

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

Layout components (`layout.tsx`) MUST NOT directly access dynamic request primitives (`cookies()`, `headers()`)

Layout components (`layout.tsx`) MUST NOT directly access dynamic request primitives (`cookies()`, `headers()`); dynamic user context MUST be delegated to leaf components wrapped in `<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.
3

Engineers MUST ALWAYS provide a `<Suspense>` fallback whose box-model dimensions, display model, and layout footprint match the resolved dynamic component to prevent Cumulative Layout Shift (CLS).

Engineers MUST ALWAYS provide a `<Suspense>` fallback whose box-model dimensions, display model, and layout footprint match the resolved 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

Dynamic components MUST NEVER execute authorization checks or session-token reads in a manner that serializes credential tokens or PII into the static prerender chunk.

Dynamic components MUST NEVER execute authorization checks or session-token reads in a manner that serializes credential tokens or PII into the static prerender chunk.

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

Routes utilizing PPR MUST explicitly declare `export const experimental_ppr = true` or inherit from a valid root PPR configuration flag in `next.config.ts`.

Routes utilizing PPR MUST explicitly declare `export const experimental_ppr = true` or inherit from a valid root PPR configuration flag in `next.config.ts`.

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

Dynamic server components SHOULD leverage `await connection()` from `next/server` when explicitly asserting non-blocking dynamic execution paths before streaming headers.

Dynamic server components SHOULD leverage `await connection()` from `next/server` when explicitly asserting non-blocking dynamic execution paths before streaming headers.

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 Static-Dynamic Isolation Perimeter & Boundary Enforcement critical for AI coding assistants?

Enforces strict structural boundaries between edge-cacheable static prerender shells and dynamic React Server Component streams under Next.js 15 Partial Prerendering (PPR). Prevents catastrophic static-deoptimization, user credential leakage in edge-cached prerender payloads, and Cumulative Layout Shift (CLS) caused by asymmetric fallback geometries. 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-bound APIs into static route shells causing edge cache poisoning or total de-optimization) 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