Generate production-ready Prisma Cursor rules for Project Rules (.mdc), AGENTS.md, or legacy .cursorrules. This template encodes stack-specific conventions for projects using Prisma. Type-safe ORM with schema-first design and generated database clients.
The template focuses Cursor AI on concrete Prisma practices instead of generic coding advice. Required sections are always included; optional sections can be enabled when they match your project.
Optional sections: Middleware & Extensions.
The generator turns these sections into Project Rules with frontmatter, AGENTS.md, or a single .cursorrules file depending on the output format you choose.
- Use singular model names (User, not Users).
- Use camelCase for model field names.
- Use @@map and @map for consistent database naming when needed.
- Define explicit relation fields on both sides for bidirectional relations.
- Use enums for fixed sets of values.
- Use @@index and @@unique for performance and data integrity.- Use include for eager loading related records.
- Use select for partial object queries to minimize data transfer.
- Use where with typed filter conditions.
- Use pagination with take, skip, and cursor for large datasets.
- Use transactions ($transaction) for atomic multi-operation writes.
- Use interactive transactions for dependent operations.- Use prisma migrate dev for development migrations.
- Use prisma migrate deploy for production deployments.
- Always review migration SQL before applying in production.
- Use prisma migrate reset for development database resets.
- Use seed files for reproducible test and development data.
- Keep migrations small and focused — one logical change per migration.