NEXT.JS + PRISMA AGENTS.MD

A Next.js App Router application that owns its own PostgreSQL database through Prisma. The instructions focus on the parts agents most often get wrong: migrations, the Prisma client lifecycle, and where data access is allowed to happen.

Zero retention: everything you type stays in this browser. Verify it yourself in DevTools.
The Next.js + Prisma filesCustomize in the generator
AGENTS.mdFor Codex, Cursor, Copilot, Jules, Windsurf and more
# AGENTS.md

Project: nextjs-prisma-app. A Next.js App Router app using Prisma ORM with PostgreSQL.

This file is the single source of truth for every coding agent working in this repository. The tool-specific files (CLAUDE.md, GEMINI.md, .github/copilot-instructions.md and .cursor/rules/project.mdc) point here. Edit this file, not those.

## Stack

- Language: TypeScript
- Framework: Next.js (App Router)
- Database: PostgreSQL
- Hosting: Vercel
- Tests: Vitest
- Package manager: pnpm

## Commands

Run these from the repository root.

- Install dependencies: `pnpm install`
- Run locally: `pnpm dev`
- Build: `pnpm build`
- Run all tests: `pnpm test`
- Run one test file: `pnpm vitest run path/to/file.test.ts`
- Lint: `pnpm lint`
- Type-check: `pnpm tsc --noEmit`
- Format: `pnpm prettier --write .`

## Project layout

- `app/`: Routes, layouts and Server Actions
- `prisma/schema.prisma`: The database schema, the single source of truth for models
- `prisma/migrations/`: Generated SQL migrations (committed, never edited after they are applied)
- `lib/db.ts`: The shared Prisma client singleton
- `lib/data/`: Data access functions, the only code that calls Prisma

## Code style

- Indent with 2 spaces. Never tabs.
- TypeScript runs in strict mode. Do not use `any`; use `unknown` and narrow it, or write the real type.
- Match the style and patterns of the surrounding code, even where you would personally choose differently.
- Use named exports. Do not add default exports.
- Prefer small pure functions and immutable data; keep side effects at the edges (handlers, jobs, I/O modules).
- Never swallow an error. Handle it where you can act on it, or rethrow it with context about what failed.
- Commit messages follow Conventional Commits: `feat:`, `fix:`, `refactor:`, `test:`, `docs:`, `chore:`, with an imperative summary under 72 characters.

## Working rules

- Before you say a task is done, run the test, lint and type-check commands above and make sure they pass. If you could not run them, say so.
- Never write secrets, API keys, tokens or passwords into code, tests, fixtures, logs or commits. Read them from environment variables, and never commit `.env` files.
- Ask before creating, editing or running database migrations, and never edit a migration that has already been applied.
- Never run destructive commands (`rm -rf`, `git reset --hard`, `git push --force`, `DROP TABLE`, deleting cloud resources) without explicit approval.
- Do not hand-edit generated files or lockfiles; change the source and regenerate.
- Change only what the task needs. Do not refactor, rename or reformat unrelated code.

## Project-specific notes

- Import the Prisma client only from `lib/db.ts`; never call `new PrismaClient()` anywhere else (it exhausts connections in dev and serverless).
- Only modules in `lib/data/` and Server Actions call Prisma. Components receive plain data, never the client.
- Change the schema in `prisma/schema.prisma`, then run `pnpm prisma migrate dev --name <change>` and commit the generated migration folder.
- Never run `prisma migrate reset` or `prisma db push` against any database other than your local one.
- Select only the fields a page needs with `select`; do not return whole rows that include password hashes or tokens.
- Wrap multi-step writes in `prisma.$transaction`.
- Validate every Server Action input with a schema (zod) before it reaches Prisma.

## Project phase

This project is in active development. Follow the patterns that already exist; consistency beats novelty.
CLAUDE.mdFor Claude Code
# CLAUDE.md

@AGENTS.md

## Claude Code

- The shared project instructions are imported from AGENTS.md on the line above. Edit AGENTS.md, not this file, so every agent stays in sync.
- Put Claude-only preferences below this line. Personal, uncommitted notes belong in CLAUDE.local.md.
GEMINI.mdFor Gemini CLI
# GEMINI.md

@./AGENTS.md

## Gemini CLI

- The shared project instructions are imported from AGENTS.md on the line above. Edit AGENTS.md, not this file.
- Alternative: delete this file and set "context": { "fileName": ["AGENTS.md"] } in .gemini/settings.json so Gemini CLI reads AGENTS.md directly.
.github/copilot-instructions.mdFor GitHub Copilot
# Copilot instructions

Project: nextjs-prisma-app. A Next.js App Router app using Prisma ORM with PostgreSQL.

The full instructions are in AGENTS.md at the repository root. Read it before you change code; if anything here disagrees with it, AGENTS.md wins. The essentials are repeated below for Copilot surfaces that only read this file.

## Stack

- Language: TypeScript
- Framework: Next.js (App Router)
- Database: PostgreSQL
- Hosting: Vercel
- Tests: Vitest
- Package manager: pnpm

## Commands

- Install dependencies: `pnpm install`
- Run locally: `pnpm dev`
- Build: `pnpm build`
- Run all tests: `pnpm test`
- Run one test file: `pnpm vitest run path/to/file.test.ts`
- Lint: `pnpm lint`
- Type-check: `pnpm tsc --noEmit`
- Format: `pnpm prettier --write .`

## Working rules

- Before you say a task is done, run the test, lint and type-check commands above and make sure they pass. If you could not run them, say so.
- Never write secrets, API keys, tokens or passwords into code, tests, fixtures, logs or commits. Read them from environment variables, and never commit `.env` files.
- Ask before creating, editing or running database migrations, and never edit a migration that has already been applied.
- Never run destructive commands (`rm -rf`, `git reset --hard`, `git push --force`, `DROP TABLE`, deleting cloud resources) without explicit approval.
- Do not hand-edit generated files or lockfiles; change the source and regenerate.
- Change only what the task needs. Do not refactor, rename or reformat unrelated code.
.cursor/rules/project.mdcFor Cursor
---
description: Project instructions for every task (mirrors AGENTS.md)
globs:
alwaysApply: true
---

# Project rules

The project instructions live in @AGENTS.md at the repository root, which Cursor loads automatically. They are not repeated here, so they cost context only once. Edit AGENTS.md, not this rule.

Before you change code, check the Commands and Working rules sections of AGENTS.md, and run its test and lint commands before you say a task is done.

Put Cursor-only rules below, or add scoped rules as more .mdc files with `globs` (for example `src/components/**/*.tsx`).

These are the exact files the generator writes for this preset. Change any command or rule in the generator and download your own set.

About the Next.js + Prisma preset

What Is in the Next.js + Prisma AGENTS.md?

The preset describes a a Next.js App Router app using Prisma ORM with PostgreSQL. Its AGENTS.md is 51 non-empty lines with 8 exact commands, 5 key directories, and 7 stack-specific rules on top of the shared working rules.

  • Commands: pnpm install, pnpm dev, pnpm build, pnpm test, pnpm vitest run path/to/file.test.ts, pnpm lint, pnpm tsc --noEmit, pnpm prettier --write ..
  • Layout: app/, prisma/schema.prisma, prisma/migrations/, lib/db.ts, lib/data/.
  • Wrappers: CLAUDE.md and GEMINI.md import AGENTS.md; the Copilot file repeats the essentials; the Cursor rule points to AGENTS.md.

Why These Rules for Next.js + Prisma?

One Prisma client, not many

Next.js hot reload re-evaluates modules, and serverless functions start often. Every stray new PrismaClient() opens its own connection pool, and the database runs out of connections long before traffic is high. Agents create clients casually when writing a quick script or route, so the rule names the one allowed import path.

Migrations are history

Prisma migration folders are a record of what has already run in production. Editing an applied migration makes environments disagree silently. Agents fix a typo in an old migration because it is the shortest path to a passing build; the rule tells them to add a new migration instead.

db push and reset are local tools

Both commands are convenient and both can destroy data. They are fine on a laptop and dangerous on a shared database, and an agent cannot tell which database a connection string points at unless you tell it.

Over-fetching leaks data

Returning whole Prisma rows to a client component serializes every column into the page payload. A select keeps hashes, tokens and internal flags on the server.

Which Stack Rules Does the File Add?

  • Import the Prisma client only from lib/db.ts; never call new PrismaClient() anywhere else (it exhausts connections in dev and serverless).
  • Only modules in lib/data/ and Server Actions call Prisma. Components receive plain data, never the client.
  • Change the schema in prisma/schema.prisma, then run pnpm prisma migrate dev --name <change> and commit the generated migration folder.
  • Never run prisma migrate reset or prisma db push against any database other than your local one.
  • Select only the fields a page needs with select; do not return whole rows that include password hashes or tokens.
  • Wrap multi-step writes in prisma.$transaction.
  • Validate every Server Action input with a schema (zod) before it reaches Prisma.

How Do You Add These Files to a Next.js + Prisma Repository?

  1. Download the zip above. It is laid out exactly as the files go into the repository.
  2. Unzip it at the repository root. AGENTS.md, CLAUDE.md and GEMINI.md go next to your README; the Copilot file goes in .github/ and the Cursor rule in .cursor/rules/.
  3. Open AGENTS.md and check every command against your package scripts or Makefile.
  4. Delete wrappers for tools your team does not use, and any old .cursorrules or .windsurfrules file.
  5. Commit, then run the linter on AGENTS.md whenever you change it.

Want different commands or rules? Load this preset into the generator, change anything, and download your own set.

Which Agents Will Read These Files?

AGENTS.md is read directly by Codex, Cursor, Windsurf, Cline, Zed and Jules, and by GitHub Copilot's cloud agent, code review and CLI. Claude Code reads it through the generated CLAUDE.md, and Gemini CLI through GEMINI.md. See the compatibility table for details, last verified 2026-11-13.

Which Similar Stacks Are in the Library?

All presets are on the stacks page.

Frequently Asked Questions

Does this template work with Drizzle instead of Prisma?

The structure does, but the commands and the client rule are Prisma-specific. Open it in the generator and replace the migration commands and the notes with your Drizzle equivalents.

Why does the file forbid prisma db push?

db push syncs the schema without writing a migration, so production and local history drift apart. It is useful for quick local experiments, which is why the rule only forbids it outside your own machine.

Where should database credentials live?

In environment variables such as DATABASE_URL, set locally in an untracked .env file and in your host dashboard for production. The no-secrets rule tells the agent never to write them into code or commit them.

Are these Next.js + Prisma files free to use?

Yes. Copy them into any project, commercial or not, without attribution. They are a starting point: adjust the commands and rules to match your repository.

How Can You Verify That Nothing Leaves This Browser?

You do not have to take our word for it. Developer tools show every request a page makes, so you can watch this page work and confirm that nothing you type is sent. The check takes under a minute.

  1. Open your browser developer tools with F12, or Cmd+Option+I on a Mac, and select the Network tab.
  2. Reload the page and let it finish. You will see the page's own files, its web fonts, and one anonymous page-view request. Nothing has been typed yet, so none of them can contain your input.
  3. Click the clear icon in the Network tab so that the log is empty.
  4. Switch between the file tabs, copy a file and download the zip.
  5. Look at the Network tab again. It is still empty. Downloads are built in the page as Blob URLs, so even the zip never touches a server. For extra proof, turn on offline mode after the page loads: everything keeps working.

Only the feedback form can add a line to that log, and it sends only the vote and comment you type into it. 2prompt has no server code at all: no API, no model and no database of your files. The production site also sends a Content-Security-Policy header that tells your browser to refuse connections to anywhere except this site, the fonts and the anonymous analytics endpoint.

Was this helpful?