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-edge-cache-invariant

Next.js 15 Partial Prerendering (PPR) Edge Cache Invariant Standard

Enforces strict isolation between static prerendered HTML shells and dynamic stream chunks under Next.js 15 Partial Prerendering (PPR). Mandates explicit Suspense boundaries around all dynamic context (cookies, headers, searchParams, and uncached data fetches) to prevent edge cache poisoning and cross-session identity leakage.

Prohibited Anti-Pattern: Dynamic session and auth context escaping Suspense boundaries into statically prerendered edge-cached shells.

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Next.js 15 Partial Prerendering (PPR) Edge Cache Invariant Standard - Enforces strict isolation between static prerendered HTML shells and dynamic stream chunks under Next.js 15 Partial Prerendering (PPR). Mandates explicit Suspense boundaries around all dynamic context (cookies, headers, searchParams, and uncached data fetches) to prevent edge cache poisoning and cross-session identity leakage.
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-edge-cache-invariant"
---

# Next.js 15 Partial Prerendering (PPR) Edge Cache Invariant Standard

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Dynamic session and auth context escaping Suspense boundaries into statically prerendered edge-cached shells.

## System Constraints
You are a Principal Software Architect enforcing the Next.js 15 Partial Prerendering (PPR) Edge Cache Invariant. You must reject any code where dynamic APIs (such as `cookies()`, `headers()`, `searchParams`, or uncached data calls) execute within the top-level prerendered shell instead of strictly inside isolated `<Suspense>` streaming boundaries. Enforce exact isolation to protect CDN edge layers from caching sensitive user state.

## Strict Guidelines
- Engineers MUST ALWAYS isolate every component consuming dynamic APIs (`cookies()`, `headers()`, `searchParams`, or `fetch` with `{ cache: 'no-store' }`) behind an explicit React `<Suspense>` boundary when `experimental_ppr` is enabled.
- Engineers MUST NOT read dynamic request context (e.g., calling `await cookies()` or `await headers()`) in root layouts or parent components that generate the static prerender shell.
- Components rendering user-specific identity, session tokens, or personalized UI MUST NEVER be evaluated during the static generation phase; they must live inside dedicated dynamic subtrees.
- Engineers MUST configure static skeletons and fallbacks inside `<Suspense fallback={...}>` to ensure the edge CDN serves zero personally identifiable information (PII) within the static HTML pre-stream response.
- Services invoking Next.js 15 `connection()` MUST ensure it is called strictly within a streaming dynamic component to cleanly defer execution until client connection time without deoptimizing ancestor shells.
- Code SHOULD verify `export const experimental_ppr = true` routes using automated build-time static generation diagnostics to prevent accidental bailouts into fully dynamic edge compute.

## Bad vs Good Implementations
### Dynamic Request APIs Outside Suspense in PPR Route

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Accessing `cookies()` at the layout root without a Suspense boundary forces the entire layout into the dynamic tier, either breaking the PPR shell generation or inadvertently caching dynamic user markers if edge caching policies are misconfigured.
```typescript
import { cookies } from 'next/headers';
import { CartSummary } from '@/components/cart-summary';

export const experimental_ppr = true;

// Anti-pattern: Root layout/page resolves dynamic cookies directly
// This deopts PPR or leaks dynamic values into edge-cached static shell fragments
export default async function StoreLayout({ children }: { children: React.ReactNode }) {
  const cookieStore = await cookies();
  const userId = cookieStore.get('session_id')?.value;

  return (
    <div className="store-container">
      <header>
        <nav>Navigation</nav>
        {/* VULNERABILITY: User state exposed in un-suspended shell */}
        <div className="user-info">User: {userId ?? 'Guest'}</div>
      </header>
      <main>{children}</main>
    </div>
  );
}
```

#### Production Standard (Correct)
> **Standard**: The layout remains purely static, allowing the edge CDN to instantly return the prerendered HTML shell with `UserInfoSkeleton`. The `UserProfile` Server Component executes strictly inside the streaming dynamic chunk, ensuring zero session leakage across edge cache boundaries.
```typescript
import { Suspense } from 'react';
import { cookies } from 'next/headers';
import { UserInfoSkeleton } from '@/components/skeletons';

export const experimental_ppr = true;

async function UserProfile() {
  const cookieStore = await cookies();
  const userId = cookieStore.get('session_id')?.value;
  return <div className="user-info">User: {userId ?? 'Guest'}</div>;
}

// Invariant compliant: Static shell remains fully cacheable at edge CDN
export default function StoreLayout({ children }: { children: React.ReactNode }) {
  return (
    <div className="store-container">
      <header>
        <nav>Navigation</nav>
        {/* Dynamic hole correctly isolated by Suspense */}
        <Suspense fallback={<UserInfoSkeleton />}>
          <UserProfile />
        </Suspense>
      </header>
      <main>{children}</main>
    </div>
  );
}
```
Recommended MCP Servers (mcp-serverlist.com)

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

Next.js Runtime Inspector MCP
Inspects static analysis traces and App Router PPR route manifests to detect boundary leaks.
Recommended Agent Skills (askills.dev)

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

Next.js PPR Static Shell Audit
CLI utility to verify static and dynamic boundary demarcations during the Next.js compilation phase.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: Next.js 15 Partial Prerendering (PPR) Edge Cache Invariant Standard

Next.js 15 Partial Prerendering (PPR) Edge Cache Invariant Standard defines an industrial-grade behavioral standard for frontend engineering. Enforces strict isolation between static prerendered HTML shells and dynamic stream chunks under Next.js 15 Partial Prerendering (PPR). Mandates explicit Suspense boundaries around all dynamic context (cookies, headers, searchParams, and uncached data fetches) to prevent edge cache poisoning and cross-session identity leakage. 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 session and auth context escaping Suspense boundaries into statically prerendered edge-cached shells. 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 session and auth context escaping Suspense boundaries into statically prerendered edge-cached shells.Critical
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 every component consuming dynamic APIs (`cookies()`, `headers()`, `searchParams`, or `fetch` with `{ cache

Engineers MUST ALWAYS isolate every component consuming dynamic APIs (`cookies()`, `headers()`, `searchParams`, or `fetch` with `{ cache: 'no-store' }`) behind an explicit React `<Suspense>` boundary when `experimental_ppr` is enabled.

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 read dynamic request context (e.g., calling `await cookies()` or `await headers()`) in root layouts or parent components that generate the static prerender shell.

Engineers MUST NOT read dynamic request context (e.g., calling `await cookies()` or `await headers()`) in root layouts or parent components that generate the static prerender shell.

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 rendering user-specific identity, session tokens, or personalized UI MUST NEVER be evaluated during the static generation phase

Components rendering user-specific identity, session tokens, or personalized UI MUST NEVER be evaluated during the static generation phase; they must live inside dedicated dynamic subtrees.

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

Engineers MUST configure static skeletons and fallbacks inside `<Suspense fallback={...}>` to ensure the edge CDN serves zero personally identifiable information (PII) within the static HTML pre-stream response.

Engineers MUST configure static skeletons and fallbacks inside `<Suspense fallback={...}>` to ensure the edge CDN serves zero personally identifiable information (PII) within the static HTML pre-stream response.

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 invoking Next.js 15 `connection()` MUST ensure it is called strictly within a streaming dynamic component to cleanly defer execution until client connection time without deoptimizing ancestor shells.

Services invoking Next.js 15 `connection()` MUST ensure it is called strictly within a streaming dynamic component to cleanly defer execution until client connection time without deoptimizing ancestor shells.

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

Code SHOULD verify `export const experimental_ppr = true` routes using automated build-time static generation diagnostics to prevent accidental bailouts into fully dynamic edge compute.

Code SHOULD verify `export const experimental_ppr = true` routes using automated build-time static generation diagnostics to prevent accidental bailouts into fully dynamic edge compute.

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) Edge Cache Invariant Standard critical for AI coding assistants?

Enforces strict isolation between static prerendered HTML shells and dynamic stream chunks under Next.js 15 Partial Prerendering (PPR). Mandates explicit Suspense boundaries around all dynamic context (cookies, headers, searchParams, and uncached data fetches) to prevent edge cache poisoning and cross-session identity leakage. 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 session and auth context escaping Suspense boundaries into statically prerendered edge-cached shells.) 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