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-io-leakage-guardrail

Next.js 15 Partial Prerendering Dynamic I/O Leakage Guardrail

Enforces strict isolation between static pre-rendered CDN shells and dynamic request-time boundaries under Next.js 15 Partial Prerendering (PPR) and Dynamic I/O. Prevents silent inclusion of personalized data into shared cache artifacts by requiring runtime storage access (headers, cookies, searchParams, uncached I/O) to be contained within explicit Suspense boundaries and async dynamic contracts.

Prohibited Anti-Pattern: Leaking Request-Scoped State into Static Prerendered Shells via Unbounded Dynamic Access

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Next.js 15 Partial Prerendering Dynamic I/O Leakage Guardrail - Enforces strict isolation between static pre-rendered CDN shells and dynamic request-time boundaries under Next.js 15 Partial Prerendering (PPR) and Dynamic I/O. Prevents silent inclusion of personalized data into shared cache artifacts by requiring runtime storage access (headers, cookies, searchParams, uncached I/O) to be contained within explicit Suspense boundaries and async dynamic contracts.
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-io-leakage-guardrail"
---

# Next.js 15 Partial Prerendering Dynamic I/O Leakage Guardrail

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Leaking Request-Scoped State into Static Prerendered Shells via Unbounded Dynamic Access

## System Constraints
You are a Principal Engineer enforcing Next.js 15 Partial Prerendering (PPR) and Dynamic I/O architecture invariants. Under PPR with `experimental.dynamicIO` enabled, accessing dynamic data (cookies, headers, un-tagged fetches, uncached DB queries, searchParams) halts prerendering and forces dynamic evaluation. You must mandate that all dynamic operations are isolated inside React Suspense boundaries or explicitly encapsulated behind cached async storage boundaries to prevent de-optimizing the entire page shell or catastrophically baking user-specific PII/tokens into static edge-cached HTML shells.

## Strict Guidelines
- Engineers MUST ALWAYS isolate dynamic runtime data access (cookies, headers, searchParams) inside `<Suspense fallback={<Fallback />}>` boundaries to preserve the static outer shell during PPR build compilation.
- Engineers MUST NOT access dynamic APIs (`cookies()`, `headers()`) directly within root or outer page layouts unless the entire route segment is explicitly opted into runtime rendering via `export const dynamic = 'force-dynamic'`.
- Code MUST wrap async database calls and third-party fetches that produce static or cacheable output with `unstable_cache` or the `'use cache'` directive (when Dynamic I/O is enabled) to prevent unconstrained dynamic execution from opting out the build tree.
- Components NEVER read searchParams directly in static shell wrappers; dynamic route parameters must be extracted via async props or accessed downstream within client/server leaves wrapped in Suspense.
- Services MUST declare cache revalidation tags using `revalidateTag` or lifecycle parameters rather than relying on full-route on-demand dynamic de-optimizations.

## Bad vs Good Implementations
### Unbounded Cookie Access Bakes or Bails Prerender Shell vs. Suspense-Enclosed Dynamic Boundary

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Awaiting cookies() directly in the page-level component forces the entire route out of Partial Prerendering, disabling the static shell and invalidating edge-cached delivery. In some misconfigured compiler paths without dynamicIO warnings, this riskily persists default or leaked user data into pre-generated edge shells.
```typescript
// app/dashboard/page.tsx
import { cookies } from 'next/headers';
import { Suspense } from 'react';

// ANTI-PATTERN: Direct invocation of dynamic cookies() at root page level
// collapses the entire Partial Prerendering boundary into dynamic rendering,
// or leaks fallback-empty dynamic state into CDN-cached HTML shells.
export default async function DashboardPage() {
  const cookieStore = await cookies();
  const sessionToken = cookieStore.get('session_id')?.value;
  const user = await fetchUserProfile(sessionToken);

  return (
    <main className="dashboard-container">
      <header className="shell-header">
        <h1>Enterprise Portal</h1>
      </header>
      <section className="user-metrics">
        <h2>Welcome back, {user.name}</h2>
        <p>Tenant: {user.tenantId}</p>
      </section>
    </main>
  );
}

async function fetchUserProfile(token?: string) {
  return { name: token ? 'Alice' : 'Anonymous', tenantId: 'corp-1' };
}
```

#### Production Standard (Correct)
> **Standard**: The layout and top-level page component remain strictly static and prerenderable at build time. Dynamic runtime storage access (`cookies()`) is isolated inside the `<Suspense>` boundary, streaming dynamic content at request time while preserving the CDN-cacheable static shell.
```typescript
// app/dashboard/page.tsx
import { cookies } from 'next/headers';
import { Suspense } from 'react';

export const experimental_ppr = true;

// Static Page Shell: Instantly delivered from CDN edge
export default function DashboardPage() {
  return (
    <main className="dashboard-container">
      <header className="shell-header">
        <h1>Enterprise Portal</h1>
      </header>
      <Suspense fallback={<MetricsSkeleton />}>
        <DynamicUserMetrics />
      </Suspense>
    </main>
  );
}

// Dynamic Leaf: Isolated dynamic I/O evaluation streamed via HTTP chunking
async function DynamicUserMetrics() {
  const cookieStore = await cookies();
  const sessionToken = cookieStore.get('session_id')?.value;
  const user = await fetchUserProfile(sessionToken);

  return (
    <section className="user-metrics">
      <h2>Welcome back, {user.name}</h2>
      <p>Tenant: {user.tenantId}</p>
    </section>
  );
}

function MetricsSkeleton() {
  return <div className="animate-pulse h-24 bg-gray-100 rounded" />;
}

async function fetchUserProfile(token?: string) {
  return { name: token ? 'Alice' : 'Anonymous', tenantId: 'corp-1' };
}
```
Recommended MCP Servers (mcp-serverlist.com)

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

Next.js Documentation & Compiler MCP
Validates API signatures and experimental PPR/Dynamic I/O flags against official Next.js 15 canary/stable runtime specifications.
Recommended Agent Skills (askills.dev)

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

Next.js Production Build Analyzer
Runs production Next.js builds with PPR debugging enabled (`next build --debug`) to verify static shell generation and dynamic chunk boundaries.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: Next.js 15 Partial Prerendering Dynamic I/O Leakage Guardrail

Next.js 15 Partial Prerendering Dynamic I/O Leakage Guardrail defines an industrial-grade behavioral standard for frontend engineering. Enforces strict isolation between static pre-rendered CDN shells and dynamic request-time boundaries under Next.js 15 Partial Prerendering (PPR) and Dynamic I/O. Prevents silent inclusion of personalized data into shared cache artifacts by requiring runtime storage access (headers, cookies, searchParams, uncached I/O) to be contained within explicit Suspense boundaries and async dynamic contracts. 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 Request-Scoped State into Static Prerendered Shells via Unbounded Dynamic Access 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 Request-Scoped State into Static Prerendered Shells via Unbounded Dynamic AccessCritical
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 runtime data access (cookies, headers, searchParams) inside `<Suspense fallback={<Fallback />}>` boundaries to preserve the static outer shell during PPR build compilation.

Engineers MUST ALWAYS isolate dynamic runtime data access (cookies, headers, searchParams) inside `<Suspense fallback={<Fallback />}>` boundaries to preserve the static outer shell during PPR build compilation.

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 APIs (`cookies()`, `headers()`) directly within root or outer page layouts unless the entire route segment is explicitly opted into runtime rendering via `export const dynamic = 'force-dynamic'`.

Engineers MUST NOT access dynamic APIs (`cookies()`, `headers()`) directly within root or outer page layouts unless the entire route segment is explicitly opted into runtime rendering via `export const dynamic = 'force-dynamic'`.

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

Code MUST wrap async database calls and third-party fetches that produce static or cacheable output with `unstable_cache` or the `'use cache'` directive (when Dynamic I/O is enabled) to prevent unconstrained dynamic execution from opting out the build tree.

Code MUST wrap async database calls and third-party fetches that produce static or cacheable output with `unstable_cache` or the `'use cache'` directive (when Dynamic I/O is enabled) to prevent unconstrained dynamic execution from opting out the build tree.

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

Components NEVER read searchParams directly in static shell wrappers

Components NEVER read searchParams directly in static shell wrappers; dynamic route parameters must be extracted via async props or accessed downstream within client/server leaves 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.
5

Services MUST declare cache revalidation tags using `revalidateTag` or lifecycle parameters rather than relying on full-route on-demand dynamic de-optimizations.

Services MUST declare cache revalidation tags using `revalidateTag` or lifecycle parameters rather than relying on full-route on-demand dynamic de-optimizations.

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 I/O Leakage Guardrail critical for AI coding assistants?

Enforces strict isolation between static pre-rendered CDN shells and dynamic request-time boundaries under Next.js 15 Partial Prerendering (PPR) and Dynamic I/O. Prevents silent inclusion of personalized data into shared cache artifacts by requiring runtime storage access (headers, cookies, searchParams, uncached I/O) to be contained within explicit Suspense boundaries and async dynamic contracts. 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 Request-Scoped State into Static Prerendered Shells via Unbounded Dynamic Access) 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