database-patterns

Standardize ORM setup, migrations, seeders, and transactions for Node.js relational databases.

3|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/mauriciodelrio/delriodev-skills --skill database-patterns-mauriciodelrio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: database-patterns
Source: https://github.com/mauriciodelrio/delriodev-skills/tree/main/es-skills/software/backend/database-patterns
Command: npx skills add https://github.com/mauriciodelrio/delriodev-skills --skill database-patterns-mauriciodelrio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Este Skill facilita la implementación de patrones de acceso a datos en el backend Node.js, articulando la configuración de ORM (Prisma, Drizzle, TypeORM), migraciones, seeders, transacciones, pooling, N+1 y consultas eficientes.

Core Features & Use Cases

  • Configuración y patrones de ORM (Prisma, Drizzle, TypeORM) para proyectos Node.js.
  • Gestión de migraciones y seeders con prácticas seguras y reproducibles.
  • Soporte para transacciones, pooling de conexiones, arreglos de N+1 y soft deletes, con ejemplos de uso eficiente de consultas.

Quick Start

Configura y aplica inmediatamente un patrón de acceso a datos en tu proyecto Node.js usando el ORM recomendado y ejemplos de migraciones.

Frequently Asked Questions about database-patterns

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure ORM migrations and seeders in a Node.js backend?

ORM migrations and seeders in Node.js are configured by standardizing setup patterns across relational databases, ensuring safe and reproducible migration practices alongside consistent seeding rules for immediate data access implementation.

What's the best way to manage transactions and connection pooling in Node.js?

Transactions and connection pooling in Node.js are managed by applying standardized transactional workflows and pooling configurations across backend services using relational databases, ensuring consistent data access and efficient query execution.

How do I fix N+1 query problems and implement soft deletes with an ORM?

Fixing N+1 query problems and implementing soft deletes involves applying specific data access patterns in Node.js that standardize efficient query usage and safe record removal across ORM setups like Prisma, Drizzle, or TypeORM.

Does this approach support setting up Prisma, Drizzle, and TypeORM in Node.js projects?

Yes, the data access patterns support ORM selection and setup for Prisma, Drizzle, and TypeORM in Node.js projects, standardizing configuration and usage to ensure consistent backend data access workflows.

When do I need standardized data access patterns for Node.js relational databases?

Standardized data access patterns for Node.js relational databases are needed when backend services require consistent migrations, transactional workflows, connection pooling, and performance optimizations like N+1 fixes across multiple projects.