AgentRules.org
RulesStacksClientsAuditorPrunerSelf-HealRFCsBenchmarkCLICI/CDAuthorsSubmit
This specification is maintained by the AgentRules Working Group. Have enhancements or want to claim maintainership?Submit Specification →
backendcritical PriorityID: nodejs-prisma-optimization

Node.js & Prisma ORM Anti-N+1 Query Optimization

Guardrails for Prisma ORM: prevent N+1 query loops using include/select relations, use prisma.$transaction for batching, and maintain singleton PrismaClient instance.

Prohibited Anti-Pattern: AI queries the database inside a for-loop (N+1 query trap) or creates a new PrismaClient() on every request.

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Node.js & Prisma ORM Anti-N+1 Query Optimization - Guardrails for Prisma ORM: prevent N+1 query loops using include/select relations, use prisma.$transaction for batching, and maintain singleton PrismaClient instance.
globs: src/**/*.{ts,js}, prisma/**/*.prisma
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/nodejs-prisma-optimization"
---

# Node.js & Prisma ORM Anti-N+1 Query Optimization

> **Severity**: CRITICAL | **Category**: backend
> **Anti-Pattern Warning**: AI queries the database inside a for-loop (N+1 query trap) or creates a new PrismaClient() on every request.

## System Constraints
You are a database performance expert working with Prisma ORM and Node.js/TypeScript. Never execute database queries inside loops. Use relation queries (include / select) or batching. Reuse a global PrismaClient singleton to avoid exhausting connection pools.

## Strict Guidelines
- Maintain a single PrismaClient instance (singleton pattern) to prevent database connection leaks.
- Never query prisma inside an array map() or for() loop; use include or where: { id: { in: ids } }.
- Use select to fetch only required fields; avoid fetching entire records with large text/blobs.
- Wrap multi-table mutations inside prisma.$transaction().

## Bad vs Good Implementations
### Eliminating N+1 Queries with Relation Include

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Loops generate individual queries per item, overwhelming the database connection pool.
```typescript
// Anti-pattern: N+1 queries executing inside loop
const users = await prisma.user.findMany();
const usersWithPosts = await Promise.all(
  users.map(async (u) => {
    // Fires 1 query per user! 100 users = 101 database roundtrips!
    const posts = await prisma.post.findMany({ where: { authorId: u.id } });
    return { ...u, posts };
  })
);
```

#### Production Standard (Correct)
> **Standard**: Fetches users and their related posts in a single optimized query with field selection.
```typescript
// Production Standard: Single JOIN query using include
const usersWithPosts = await prisma.user.findMany({
  select: {
    id: true,
    name: true,
    email: true,
    posts: {
      select: {
        id: true,
        title: true,
        createdAt: true,
      },
      take: 5,
    },
  },
});
```
Recommended MCP Servers (mcp-serverlist.com)

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

PostgreSQL Database MCP
Inspect database schema, run EXPLAIN ANALYZE, and audit index usage.
Recommended Agent Skills (askills.dev)

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

Prisma Schema Validator
Validate Prisma relations, indexes, and connection pool configurations.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: Node.js & Prisma ORM Anti-N+1 Query Optimization

Node.js & Prisma ORM Anti-N+1 Query Optimization defines an industrial-grade behavioral standard for backend engineering. Guardrails for Prisma ORM: prevent N+1 query loops using include/select relations, use prisma.$transaction for batching, and maintain singleton PrismaClient instance. 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: AI queries the database inside a for-loop (N+1 query trap) or creates a new PrismaClient() on every request. 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 DriftAI queries the database inside a for-loop (N+1 query trap) or creates a new PrismaClient() on every request.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

Maintain a single PrismaClient instance (singleton pattern) to prevent database connection leaks.

Maintain a single PrismaClient instance (singleton pattern) to prevent database connection leaks.

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

Never query prisma inside an array map() or for() loop

Never query prisma inside an array map() or for() loop; use include or where: { id: { in: ids } }.

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

Use select to fetch only required fields

Use select to fetch only required fields; avoid fetching entire records with large text/blobs.

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

Wrap multi-table mutations inside prisma.$transaction().

Wrap multi-table mutations inside prisma.$transaction().

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 Node.js & Prisma ORM Anti-N+1 Query Optimization critical for AI coding assistants?

Guardrails for Prisma ORM: prevent N+1 query loops using include/select relations, use prisma.$transaction for batching, and maintain singleton PrismaClient instance. 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 (AI queries the database inside a for-loop (N+1 query trap) or creates a new PrismaClient() on every request.) 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 BACKEND Rules

View all rules →
backend
42

Fastify 5 Schema Compilers & Encapsulation Production Standard

Fastify relies on lexical encapsulation contexts to sandbox decorators, hooks, and compiled validation/serialization schemas without memory leaks or cross-tenant bleed. In Fastify 5, misuse of global compilers or failing to encapsulate plugin boundaries causes compiled `fast-json-stringify` serializers and Ajv validators to either crash on duplicate IDs, leak private data across sibling scopes, or bypass JIT compilation optimizations. Production services must enforce strict encapsulation hierarchies and type-safe schema compilation across every routing subtree.

backend
68

Bun Embedded SQLite WAL Mode & Transaction Synchronization Standard

Production database standard for bun:sqlite. Mandates enabling Write-Ahead Logging (PRAGMA journal_mode = WAL), busy timeouts, and using db.transaction() for atomic operations without lock starvation.

backend
68

Drizzle ORM Batch API & Interactive Transaction Isolation Standard

Production database standard for Drizzle ORM (PostgreSQL & MySQL). Mandates using db.batch() over HTTP drivers to prevent round-trip waterfalls, explicit db.transaction() with serializable/read-committed isolation, and strictly avoids unawaited query promises.

1 Rule in Stack

Node.js