Nuxt 4 Nitro Server Engine, Shared Directory, and SSR State Isolation | AgentRules.org

Rules Stacks Clients Auditor Pruner Self-Heal RFCs Benchmark CLI CI/CD Authors Submit

This specification is maintained by the AgentRules Working Group. Have enhancements or want to claim maintainership?Submit Specification →

frontendcritical PriorityID: nuxt4-nitro-shared-ssr-boundary-standard

Nuxt 4 Nitro Server Engine, Shared Directory, and SSR State Isolation

Enforce strict execution boundary separation across Nuxt 4 app/, server/, and shared/ directories while eradicating cross-request state pollution in Nitro v2 server engines and Vue SSR. Mandates request-bound event contexts in Nitro routes and useState/Pinia per-request lifecycle encapsulation in the app layer.

Prohibited Anti-Pattern: Mutating Module-Scoped State in Nitro Handlers and Violating App/Server/Shared Directory Isolation

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Nuxt 4 Nitro Server Engine, Shared Directory, and SSR State Isolation - Enforce strict execution boundary separation across Nuxt 4 app/, server/, and shared/ directories while eradicating cross-request state pollution in Nitro v2 server engines and Vue SSR. Mandates request-bound event contexts in Nitro routes and useState/Pinia per-request lifecycle encapsulation in the app layer.
globs: app/**/*.{ts,vue}, server/**/*.{ts,js}, shared/**/*.{ts,js}, nuxt.config.ts
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/nuxt4-nitro-shared-ssr-boundary-standard"
---

# Nuxt 4 Nitro Server Engine, Shared Directory, and SSR State Isolation

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Mutating Module-Scoped State in Nitro Handlers and Violating App/Server/Shared Directory Isolation

## System Constraints
You are a Principal Software Architect enforcing architectural integrity for Nuxt 4 and Nitro v2. You must enforce strict directory isolation (app/ for Vue client/SSR, server/ for Nitro routes and middleware, and shared/ for isomorphic contracts and pure utils). Prevent Cross-Request State Pollution (CRSP) by prohibiting module-scoped mutable state in Nitro handlers and Nuxt SSR composables.

## Strict Guidelines
- Engineers MUST ALWAYS house Vue components, pages, composables, and client plugins within the `app/` directory pursuant to Nuxt 4 structure.
- Engineers MUST ALWAYS isolate universal business logic, validation schemas, and pure TypeScript contracts in the root `shared/` directory, free of Nitro server-only runtime imports or DOM-dependent APIs.
- Engineers MUST NOT declare mutable module-level state (e.g., `let cache = {}`, `let currentUser`) in Nitro event handlers (`server/api/**`) or root-level server middleware.
- Engineers MUST use `event.context` in Nitro to attach and access per-request metadata, authenticated identities, and transactional caches.
- Engineers MUST NOT declare `ref()`, `reactive()`, or plain mutable state outside the scope of composables or setup functions in SSR-evaluated client code (`app/`).
- Engineers MUST initialize SSR-safe reactive state using Nuxt's `useState<T>(key, init)` to guarantee per-request hydration isolation without leaking state between concurrent user requests.
- Engineers MUST NEVER import server-only runtime secrets (`process.env`, `useRuntimeConfig().databaseSecret`) or Node-only packages into `shared/` or `app/`.
- Nitro route handlers MUST parse incoming data safely using `readValidatedBody` or `getValidatedQuery` combined with standard shared schemas (e.g., Zod or ArkType).

## Bad vs Good Implementations
### Nitro Server Route: Cross-Request State Pollution vs. Request Context Binding

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Declaring `currentUserSession` in the Nitro module scope retains state between different incoming HTTP requests. Under concurrent traffic, Request B can read or overwrite Request A's authenticated identity, leading to severe data leakage and CVE-level security vulnerabilities.
```typescript
// server/api/profile.ts
import { defineEventHandler } from 'h3';

// CRITICAL BUG: Module-scoped state shared across ALL concurrent SSR requests
let currentUserSession: { userId: string } | null = null;

export default defineEventHandler(async (event) => {
  const token = getHeader(event, 'authorization');
  if (token) {
    // Mutates shared memory; subsequent concurrent requests see this user!
    currentUserSession = await verifyAuthToken(token);
  }
  
  return { user: currentUserSession };
});
```

#### Production Standard (Correct)
> **Standard**: All request data is either returned directly or bound to `event.context`. When the HTTP response finishes, `event` is reclaimed by the V8 garbage collector, preventing cross-request pollution.
```typescript
// server/api/profile.ts
import { defineEventHandler, createError, getHeader } from 'h3';
import { verifyAuthToken } from '../utils/auth';
import type { UserProfile } from '~~/shared/types/user';

export default defineEventHandler(async (event): Promise<{ user: UserProfile }> => {
  const token = getHeader(event, 'authorization');
  if (!token) {
    throw createError({ statusCode: 401, statusMessage: 'Unauthorized' });
  }

  // Request-scoped storage: isolated strictly to this single event lifecycle
  const user = await verifyAuthToken(token);
  event.context.user = user;

  return { user: event.context.user };
});
```

### Nuxt 4 Composables: Global Singleton vs. SSR-Safe useState Hydration

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Creating a `ref` outside the exported composable function in a Nuxt SSR environment creates a single module instance shared across all inbound client sessions, causing shopping carts to bleed across distinct users during server rendering.
```typescript
// app/composables/useUserCart.ts
import { ref } from 'vue';
import type { CartItem } from '~~/shared/types/cart';

// CRITICAL BUG: Module-level ref evaluated once at server process startup
const cart = ref<CartItem[]>([]);

export const useUserCart = () => {
  const addItem = (item: CartItem) => {
    cart.value.push(item);
  };
  return { cart, addItem };
};
```

#### Production Standard (Correct)
> **Standard**: Using `useState` registers a unique state key tied to the active NuxtApp request context. It serializes properly during SSR hydration into Nuxt payload without bleeding into other concurrent requests.
```typescript
// app/composables/useUserCart.ts
import { useState } from '#imports';
import type { CartItem } from '~~/shared/types/cart';

export const useUserCart = () => {
  // Safe: Scoped per NuxtApp instance and serialized uniquely across hydration boundaries
  const cart = useState<CartItem[]>('user-cart-state', () => []);

  const addItem = (item: CartItem) => {
    cart.value = [...cart.value, item];
  };

  return {
    cart: readonly(cart),
    addItem
  };
};
```

Recommended MCP Servers (mcp-serverlist.com)

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

Vue Nitro AST Inspector MCP

Static analysis MCP to detect module-level mutable variables in Nitro route files and Nuxt composables.

Recommended Agent Skills (askills.dev)

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

Nuxt Module Boundary Checker

Linting skill enforcing directory isolation and SSR-safe variable lifetimes in Nuxt 4 and Nitro projects.

Architectural Specification & Invariant Rationale

Architectural Invariant Design: Nuxt 4 Nitro Server Engine, Shared Directory, and SSR State Isolation

Nuxt 4 Nitro Server Engine, Shared Directory, and SSR State Isolation defines an industrial-grade behavioral standard for frontend engineering. Enforce strict execution boundary separation across Nuxt 4 app/, server/, and shared/ directories while eradicating cross-request state pollution in Nitro v2 server engines and Vue SSR. Mandates request-bound event contexts in Nitro routes and useState/Pinia per-request lifecycle encapsulation in the app layer. 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: Mutating Module-Scoped State in Nitro Handlers and Violating App/Server/Shared Directory Isolation 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 Mode	AI Symptom (The Anti-Pattern)	Severity	Production Impact & Remedy
AI Hallucination & Deprecation Drift	Mutating Module-Scoped State in Nitro Handlers and Violating App/Server/Shared Directory Isolation	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 Inconsistency	AI 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 house Vue components, pages, composables, and client plugins within the `app/` directory pursuant to Nuxt 4 structure.

Engineers MUST ALWAYS house Vue components, pages, composables, and client plugins within the `app/` directory pursuant to Nuxt 4 structure.

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 ALWAYS isolate universal business logic, validation schemas, and pure TypeScript contracts in the root `shared/` directory, free of Nitro server-only runtime imports or DOM-dependent APIs.

Engineers MUST ALWAYS isolate universal business logic, validation schemas, and pure TypeScript contracts in the root `shared/` directory, free of Nitro server-only runtime imports or DOM-dependent APIs.

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 NOT declare mutable module-level state (e.g., `let cache = {}`, `let currentUser`) in Nitro event handlers (`server/api/**`) or root-level server middleware.

Engineers MUST NOT declare mutable module-level state (e.g., `let cache = {}`, `let currentUser`) in Nitro event handlers (`server/api/**`) or root-level server middleware.

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 use `event.context` in Nitro to attach and access per-request metadata, authenticated identities, and transactional caches.

Engineers MUST use `event.context` in Nitro to attach and access per-request metadata, authenticated identities, and transactional caches.

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 MUST NOT declare `ref()`, `reactive()`, or plain mutable state outside the scope of composables or setup functions in SSR-evaluated client code (`app/`).

Engineers MUST NOT declare `ref()`, `reactive()`, or plain mutable state outside the scope of composables or setup functions in SSR-evaluated client code (`app/`).

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 initialize SSR-safe reactive state using Nuxt's `useState<T>(key, init)` to guarantee per-request hydration isolation without leaking state between concurrent user requests.

Engineers MUST initialize SSR-safe reactive state using Nuxt's `useState<T>(key, init)` to guarantee per-request hydration isolation without leaking state between concurrent user requests.

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.

7

Engineers MUST NEVER import server-only runtime secrets (`process.env`, `useRuntimeConfig().databaseSecret`) or Node-only packages into `shared/` or `app/`.

Engineers MUST NEVER import server-only runtime secrets (`process.env`, `useRuntimeConfig().databaseSecret`) or Node-only packages into `shared/` or `app/`.

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.

8

Nitro route handlers MUST parse incoming data safely using `readValidatedBody` or `getValidatedQuery` combined with standard shared schemas (e.g., Zod or ArkType).

Nitro route handlers MUST parse incoming data safely using `readValidatedBody` or `getValidatedQuery` combined with standard shared schemas (e.g., Zod or ArkType).

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 Nuxt 4 Nitro Server Engine, Shared Directory, and SSR State Isolation critical for AI coding assistants?

Enforce strict execution boundary separation across Nuxt 4 app/, server/, and shared/ directories while eradicating cross-request state pollution in Nitro v2 server engines and Vue SSR. Mandates request-bound event contexts in Nitro routes and useState/Pinia per-request lifecycle encapsulation in the app layer. 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 (Mutating Module-Scoped State in Nitro Handlers and Violating App/Server/Shared Directory Isolation) 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 →

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.

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.

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

Nuxt