Skip to main content

cursor-drizzle

Cursor IDE rules for drizzle

Datos de origen

Repositorio
GrayCodeAI/hawk-community-skills
Última actividad en el origen
27 de mayo de 2026 a las 18:10
Idioma detectado de SKILL.md
inglés
Estrellas
1
Forks
0

Opciones de instalación

De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.

Revisa los archivos de origen

Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.

Mostrando SKILL.md

SKILL.md
Instrucciones de origen · Vista previa de solo lectura
name
cursor-drizzle
description
Cursor IDE rules for drizzle
license
MIT
tags
["cursor","ide-rules"]
domain
engineering
version
1
author
cursorrules-collection
# Drizzle ORM Rules ## Schema - Define all tables in a central schema file (db/schema.ts) - Use the appropriate column types for your database (pgTable, mysqlTable, sqliteTable) - Always define relations explicitly using the relations() function - Add indexes for columns used in WHERE clauses and JOINs ## Queries - Use the query API (db.query.users.findMany()) for complex joins and nested data - Use the CRUD API (db.select().from()) for simple queries - Always use parameterized queries — never interpolate values into SQL strings - Use transactions (db.transaction()) for multi-step operations that must be atomic ## Migrations - Generate migrations with drizzle-kit generate - Review generated SQL before applying — never auto-apply without inspection - Keep migration files in version control - Use drizzle-kit push for development, drizzle-kit migrate for production ## Type Safety - Infer types from schema: type User = typeof users.$inferSelect - Use insert types for write operations: type NewUser = typeof users.$inferInsert - Do not manually define types that duplicate schema definitions ## Anti-patterns - Do not use raw SQL when Drizzle's query builder can express the same query - Do not skip the migration step — always generate and apply migrations for schema changes - Do not mix different database dialects in the same project
Ver en GitHub