CursorSQLDatabase

SQL Cursor Rules

Cursor rules for SQL: query optimization, indexing strategy, safe migrations, and database security best practices.

.cursorrules
- Always use parameterized queries; never concatenate user input into SQL strings
- Add indexes on foreign keys and columns used in WHERE, JOIN, ORDER BY clauses
- Use EXPLAIN ANALYZE to validate query performance before shipping
- Prefer CTEs (WITH) over nested subqueries for readability
- Use transactions for multi-step mutations; include rollback logic
- Add NOT NULL constraints and defaults at the database level
- Use RETURNING clause to avoid extra SELECT after INSERT/UPDATE
- Write backward-compatible migrations; never drop columns in the same deploy

How to use with Cursor

Create a `.cursorrules` file in your project root and paste these rules. Cursor reads this automatically on every AI interaction.

#sql#database#indexes#cursor#coding-rules

Related Rules