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.
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.
# 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.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.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.
# 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.
---
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.
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.
pnpm install, pnpm dev, pnpm build, pnpm test, pnpm vitest run path/to/file.test.ts, pnpm lint, pnpm tsc --noEmit, pnpm prettier --write ..app/, prisma/schema.prisma, prisma/migrations/, lib/db.ts, lib/data/.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.
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.
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.
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.
lib/db.ts; never call new PrismaClient() anywhere else (it exhausts connections in dev and serverless).lib/data/ and Server Actions call Prisma. Components receive plain data, never the client.prisma/schema.prisma, then run pnpm prisma migrate dev --name <change> and commit the generated migration folder.prisma migrate reset or prisma db push against any database other than your local one.select; do not return whole rows that include password hashes or tokens.prisma.$transaction.Want different commands or rules? Load this preset into the generator, change anything, and download your own set.
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.
All presets are on the stacks page.
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.
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.
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.
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.
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.
F12, or Cmd+Option+I on a Mac, and select the Network tab.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.