Fullstack & DB · Cursor
Prisma ORM .cursorignore
A .cursorignore for Prisma ORM that keeps build output, large files and secrets out of Cursor's index (best effort).
- Path
- .cursorignore
- Loads
- Indexing and AI features
- Format
- gitignore syntax
- Used by
- Cursor
What this file tells the agent
This .cursorignore keeps Prisma ORM build output, large data files and environment secrets out of Cursor's index and AI features, so context goes to your source code. It is best effort: commands the agent runs in the terminal can still read ignored files, so keep real secrets out of the repo too.
- Always use `select` to specify required fields; avoid raw `findMany()` fetching unused relations.
- Wrap multi-step dependent writes inside `prisma.$transaction()`.
- Ensure foreign keys and queried filter fields are indexed with `@@index` in schema.prisma.
- Use global singleton PrismaClient to avoid exhausting connection pools in serverless environments.
Install it in one command
- 01
Go to your project root
The file goes at .cursorignore, relative to the root.
- 02
Download the file
Run the command on the right. It downloads this preset and writes the file.
- 03
Make sure it gets used
Cursor applies .cursorignore automatically. Matching files leave the index and AI features, but commands the agent runs in the terminal can still read them.
$ curl -fsSL "https://www.devscratchpad.tech/api/raw/cursorignore/prisma" -o ".cursorignore"
writes .cursorignore
.cursorignore
To write the file from your own code instead, use Read your code or Convert Legacy Rules in the editor above.
More for Prisma ORM
Questions
- How is .cursorignore different from .gitignore?
- .gitignore decides what git tracks. .cursorignore keeps files out of Cursor's codebase index and AI features; Cursor already skips files in .gitignore when it indexes.
- Does .cursorignore reduce wasted context?
- Yes. Ignored files are not indexed or pulled into requests, so build output and large data files do not crowd out your source code.