name: drizzle-orm description: Enforces project Drizzle ORM coding conventions when creating or modifying database queries, schemas, and migrations. This skill ensures consistent patterns for query structure, type safety, permission filtering, pagination, resilience, and database operations.
Drizzle ORM Skill
Purpose
This skill enforces the project Drizzle ORM coding conventions automatically during database query development. It ensures consistent patterns for query structure, type safety, permission filtering, pagination, circuit breaker resilience, and database operations.
Activation
This skill activates when:
- Creating new query files in
src/lib/queries/ - Modifying database schema in
src/lib/db/schema/ - Writing database migrations
- Working with Drizzle query builders
- Implementing permission filtering or soft delete logic
Workflow
- Detect Drizzle ORM work (file imports from
drizzle-ormor path containsqueries/ordb/schema) - Load
references/Drizzle-ORM-Conventions.md - Generate/modify code following all conventions
- Scan for violations of query patterns
- Auto-fix all violations (no permission needed)
- Report fixes applied
Key Patterns
Query Classes
- Extend
BaseQueryclass for all query classes - Use
QueryContextfor database instance and user context - Use
this.getDbInstance(context)for database access - Apply
this.applyPagination(options)for list queries - Use
this.combineFilters()to combine multiple SQL conditions
Context Types
createPublicQueryContext()- public read operations (isPublic = true)createUserQueryContext(userId)- authenticated user operationscreateProtectedQueryContext(requiredUserId)- owner-only operationscreateAdminQueryContext(adminUserId)- admin access to all content
Permission Filtering
- Use
this.buildBaseFilters(isPublicCol, userIdCol, deletedAtCol, context)for permission + soft delete - Import standalone filters from
@/lib/queries/base/permission-filters:buildPermissionFilter()- handles public/user/owner visibilitybuildSoftDeleteFilter()- handles deletedAt filtering (returnsisNull(deletedAt))buildOwnershipFilter()- handles owner-only accesscombineFilters()- combines multiple SQL conditions with AND
Resilience
- Use
this.executeWithRetry(operation, operationName)for circuit breaker + retry logic - Use
this.executeWithRetryDetails(operation, operationName)when you need retry metadata
Return Values
- Single item:
T | null(returnnullfor not found) - List:
Array<T>(return[]for empty) - Count:
number(return0for none) - Boolean check:
boolean(returnfalsefor not found) - Map:
Map<K, V>(returnnew Map()for empty)
Anti-Patterns to Avoid
- Never access
dbdirectly - Always usethis.getDbInstance(context) - Never skip permission filters - Always use
buildBaseFiltersfor user-visible data - Never return undefined - Return
nullfor missing single items - Never use raw strings in queries - Use parameterized queries via Drizzle
- Never skip pagination limits - Always apply
applyPagination - Never hard delete - Use soft delete with
deletedAttimestamp column - Never ignore circuit breaker - Use
executeWithRetryfor external calls
References
references/Drizzle-ORM-Conventions.md- Complete Drizzle ORM conventions