database

Database guidelines focused on Prisma and Supabase. Prisma is a tool for working with databases from application code, while Supabase provides a hosted database and related services such as authentication and storage.

In plain words
What is it for?
Use it when designing or changing Prisma models, migrations, queries, or Supabase projects. It covers relationships, indexes, transactions, pagination, authentication, storage, and row-level security policies.
Why use it?
It helps avoid poorly designed tables, unsafe permissions, incomplete migrations, inefficient queries, and mishandled sensitive data. It brings schema design, access control, backups, and query behavior into one set of checks.

Cursor rule for Cursor

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add rules/mitas/cursor-rules/database
Clone the repo
git clone --depth 1 https://github.com/mitas/cursor-rules

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 406 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 97% copy Near-identical to another mod in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00406
Opus 5 $0.00000 $0.00203
Sonnet 5 $0.00000 $0.00081
Haiku 4.5 $0.00000 $0.00041

Measured yesterday against content hash a569f9a311b1, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

database scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

97% identical to database — 7 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.cursor/rules/database.mdc · 86 lines

What it actually says

Database Best Practices

Prisma Setup

  • Use proper schema design
  • Implement proper migrations
  • Use proper relation definitions
  • Configure proper connection
  • Implement proper seeding
  • Use proper client setup

Prisma Models

  • Use proper model naming
  • Implement proper relations
  • Use proper field types
  • Define proper indexes
  • Implement proper constraints
  • Use proper enums

Prisma Queries

  • Use proper query optimization
  • Implement proper filtering
  • Use proper relations loading
  • Handle transactions properly
  • Implement proper pagination
  • Use proper aggregations

Supabase Setup

  • Configure proper project setup
  • Implement proper authentication
  • Use proper database setup
  • Configure proper storage
  • Implement proper policies
  • Use proper client setup

Supabase Security

  • Implement proper RLS policies
  • Use proper authentication
  • Configure proper permissions
  • Handle sensitive data properly
  • Implement proper backups
  • Use proper encryption

Supabase Queries

  • Use proper query optimization
  • Implement proper filtering
  • Use proper joins
  • Handle real-time properly
  • Implement proper pagination
  • Use proper functions

Database Design

  • Use proper normalization
  • Implement proper indexing
  • Use proper constraints
  • Define proper relations
  • Implement proper cascades
  • Use proper data types

Performance

  • Use proper connection pooling
  • Implement proper caching
  • Use proper query optimization
  • Handle N+1 queries properly
  • Implement proper batching
  • Monitor performance metrics

Security

  • Use proper authentication
  • Implement proper authorization
  • Handle sensitive data properly
  • Use proper encryption
  • Implement proper backups
  • Monitor security issues

Best Practices

  • Follow database conventions
  • Use proper migrations
  • Implement proper versioning
  • Handle errors properly
  • Document schema properly
  • Monitor database health
Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 86 lines · 0 tokens per session scan A a569f9a311b1

Subscribe to this mod's changes

database is a cursor rule published in the GitHub repository mitas/cursor-rules (2 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 406 tokens. A static security scan graded it A with 0 findings. It is 97% identical to database, differing in 7 lines, and is treated as a copy.