skills/nestjs/nestjs-database/SKILL.md
Implement data access patterns, Scaling, Migrations, and ORM selection in NestJS. Use when implementing TypeORM/Prisma repositories, migrations, or database patterns in NestJS.
npx skillsauth add hoangnguyen0403/agent-skills-standard nestjs-databaseInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
See references/persistence_strategy.md for database selection matrix and scaling patterns (Connection Pooling, Sharding).
@InjectRepository(Entity).PrismaService.TypeOrmModule.forRootAsync to load secrets from ConfigService.synchronize: false in production; use migrations instead.synchronize: true in production..entity.ts) modified, migration MUST generated using pnpm migration:generate.pnpm migration:run in pre-deploy or post-deploy job (e.g., GitHub Actions, GitLab CI). Ensure production environment variables correctly set.typeorm migration:show to get SQL or simply copy up method's SQL into management tool (like Supabase SQL Editor). Always track manual runs in migrations metadata table.where, order by).QueryRunner (TypeORM) or $transaction (Prisma) for all multi-step mutations to ensure atomicity.synchronize: true drops and recreates columns.testing
Infer the requesting operator's technical fluency from message content (never ask directly) and adapt register — business, hybrid, or technical — across SDLC workflow output. Use when starting sdlc, brainstorm-feature, plan-feature, verify-work, publish-notes, or session-report, or whenever a request's phrasing signals a non-technical or cross-stack operator.
documentation
Define transaction boundaries, locking, and consistency guarantees for multi-step writes. Use when designing atomic operations, retries, idempotency, or concurrent write behavior.
development
Design relational or document schemas from access patterns, cardinality, and lifecycle. Use when modeling entities, choosing embed vs normalize, or shaping schema boundaries before implementation.
data-ai
Diagnose database latency with explain plans, index ownership, and query-shape review. Use when a query is slow, an index is missing, or scans and N+1 patterns appear.