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-boundary-standard-next-js-15-parti-940

Next.js 15 Partial Prerendering (PPR) Dynamic Boundary Standard

Enforces strict structural segregation between static edge cache shells and dynamic streaming Suspense boundaries under Next.js 15 Partial Prerendering (PPR). Prevents dynamic API leakage (such as async cookies, headers, and uncached data fetches) from poisoning static page shells and collapsing entire routes into dynamic runtime execution.

Prohibited Anti-Pattern: Uncontained Dynamic API Access in Static Route Shells Causing Full PPR De-optimization

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Next.js 15 Partial Prerendering (PPR) Dynamic Boundary Standard - Enforces strict structural segregation between static edge cache shells and dynamic streaming Suspense boundaries under Next.js 15 Partial Prerendering (PPR). Prevents dynamic API leakage (such as async cookies, headers, and uncached data fetches) from poisoning static page shells and collapsing entire routes into dynamic runtime execution.
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-boundary-standard-next-js-15-parti-940"
---

# Next.js 15 Partial Prerendering (PPR) Dynamic Boundary Standard

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Uncontained Dynamic API Access in Static Route Shells Causing Full PPR De-optimization

## System Constraints
You are a Principal Software Architect enforcing Next.js 15 Partial Prerendering (PPR) architectural boundaries. In Next.js 15 with PPR enabled, any uncontained access to dynamic request data (such as awaiting `cookies()`, `headers()`, `searchParams`, or executing uncached I/O) outside an explicit React `<Suspense>` boundary immediately de-optimizes the entire page shell, destroying static CDN caching and spiking Time-To-First-Byte (TTFB). You must enforce strict containment of all dynamic execution within isolated async leaf components wrapped by Suspense boundaries with non-null deterministic fallbacks.

## Strict Guidelines
- Engineers MUST ALWAYS isolate dynamic runtime APIs (`cookies()`, `headers()`, `searchParams`, and uncached `fetch`) inside standalone async child server components wrapped in an explicit `<Suspense>` boundary.
- Engineers MUST NOT invoke or await `cookies()`, `headers()`, or `searchParams` in root layouts, page-level root component bodies, or outside of `<Suspense>` boundaries when `experimental_ppr = true` is configured.
- Engineers MUST ALWAYS provide a deterministic, skeleton-based fallback to every `<Suspense>` boundary that wraps a dynamic component to ensure the static shell pre-renders cleanly.
- Components accessing dynamic APIs MUST NOT pass dynamic values down via props from the page root; instead, dynamic components MUST independently resolve their dynamic context within their own Suspense-contained execution subtree.
- Engineers SHOULD leverage Next.js 15 `import { connection } from 'next/server'` when intentionally deferring execution of a component to the dynamic streaming phase.
- Static page layouts MUST NOT depend on dynamic route parameters unless wrapped within a Suspense-isolated boundary or partitioned into static outer shells and dynamic inner slots.

## Bad vs Good Implementations
### Dynamic Header and Cookie Contamination vs Suspense Boundary Encapsulation

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Awaiting cookies() at the page root forces Next.js 15 to abort static shell generation, causing the entire layout and page markup to wait for dynamic server rendering. This increases TTFB and removes edge caching benefits.
```typescript
import { cookies } from 'next/headers';
import { Suspense } from 'react';

export const experimental_ppr = true;

// ANTI-PATTERN: Awaiting cookies() directly in the page component
// de-optimizes the entire route shell into dynamic server-side rendering,
// bypassing the static edge prerender phase completely.
export default async function DashboardPage() {
  const cookieStore = await cookies();
  const token = cookieStore.get('auth_token')?.value;

  return (
    <main className="dashboard-shell">
      <header className="static-nav">
        <h1>Enterprise Dashboard</h1>
      </header>
      <section className="user-content">
        {token ? <p>Welcome authenticated user!</p> : <p>Guest session</p>}
      </section>
    </main>
  );
}
```

#### Production Standard (Correct)
> **Standard**: The main layout and header pre-render statically at the edge. The dynamic cookie check is segregated into an async leaf Server Component wrapped in a Suspense boundary with a skeleton fallback, streaming the personalized content without blocking the initial shell.
```typescript
import { cookies } from 'next/headers';
import { Suspense } from 'react';

export const experimental_ppr = true;

// Isolated dynamic Server Component
async function DynamicUserGreeting() {
  const cookieStore = await cookies();
  const token = cookieStore.get('auth_token')?.value;

  return (
    <div className="user-content">
      {token ? <p>Welcome authenticated user!</p> : <p>Guest session</p>}
    </div>
  );
}

function GreetingSkeleton() {
  return <div className="user-content-skeleton h-6 w-48 animate-pulse bg-gray-200" />;
}

// Page remains fully static at build/ISR time
export default function DashboardPage() {
  return (
    <main className="dashboard-shell">
      <header className="static-nav">
        <h1>Enterprise Dashboard</h1>
      </header>
      <Suspense fallback={<GreetingSkeleton />}>
        <DynamicUserGreeting />
      </Suspense>
    </main>
  );
}
```
Recommended MCP Servers (mcp-serverlist.com)

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

Next.js Build & Runtime Inspector
Validates route segment configurations, PPR manifests, and static prerender artifacts during build analysis.
Recommended Agent Skills (askills.dev)

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

Next.js PPR Static Analyzer
CLI tool that statically parses Next.js App Router ASTs to flag dynamic API invocations outside Suspense trees.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: Next.js 15 Partial Prerendering (PPR) Dynamic Boundary Standard

Next.js 15 Partial Prerendering (PPR) Dynamic Boundary Standard defines an industrial-grade behavioral standard for frontend engineering. Enforces strict structural segregation between static edge cache shells and dynamic streaming Suspense boundaries under Next.js 15 Partial Prerendering (PPR). Prevents dynamic API leakage (such as async cookies, headers, and uncached data fetches) from poisoning static page shells and collapsing entire routes into dynamic runtime execution. 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: Uncontained Dynamic API Access in Static Route Shells Causing Full PPR 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 DriftUncontained Dynamic API Access in Static Route Shells Causing Full PPR 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

Engineers MUST ALWAYS isolate dynamic runtime APIs (`cookies()`, `headers()`, `searchParams`, and uncached `fetch`) inside standalone async child server components wrapped in an explicit `<Suspense>` boundary.

Engineers MUST ALWAYS isolate dynamic runtime APIs (`cookies()`, `headers()`, `searchParams`, and uncached `fetch`) inside standalone async child server components wrapped in an explicit `<Suspense>` 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 invoke or await `cookies()`, `headers()`, or `searchParams` in root layouts, page-level root component bodies, or outside of `<Suspense>` boundaries when `experimental_ppr = true` is configured.

Engineers MUST NOT invoke or await `cookies()`, `headers()`, or `searchParams` in root layouts, page-level root component bodies, or outside of `<Suspense>` boundaries when `experimental_ppr = true` is configured.

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 deterministic, skeleton-based fallback to every `<Suspense>` boundary that wraps a dynamic component to ensure the static shell pre-renders cleanly.

Engineers MUST ALWAYS provide a deterministic, skeleton-based fallback to every `<Suspense>` boundary that wraps a dynamic component to ensure the static shell pre-renders cleanly.

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 accessing dynamic APIs MUST NOT pass dynamic values down via props from the page root

Components accessing dynamic APIs MUST NOT pass dynamic values down via props from the page root; instead, dynamic components MUST independently resolve their dynamic context within their own Suspense-contained execution subtree.

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 SHOULD leverage Next.js 15 `import { connection } from 'next/server'` when intentionally deferring execution of a component to the dynamic streaming phase.

Engineers SHOULD leverage Next.js 15 `import { connection } from 'next/server'` when intentionally deferring execution of a component to the dynamic streaming phase.

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

Static page layouts MUST NOT depend on dynamic route parameters unless wrapped within a Suspense-isolated boundary or partitioned into static outer shells and dynamic inner slots.

Static page layouts MUST NOT depend on dynamic route parameters unless wrapped within a Suspense-isolated boundary or partitioned into static outer shells and dynamic inner slots.

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) Dynamic Boundary Standard critical for AI coding assistants?

Enforces strict structural segregation between static edge cache shells and dynamic streaming Suspense boundaries under Next.js 15 Partial Prerendering (PPR). Prevents dynamic API leakage (such as async cookies, headers, and uncached data fetches) from poisoning static page shells and collapsing entire routes into dynamic runtime execution. 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 (Uncontained Dynamic API Access in Static Route Shells Causing Full PPR 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