Agent skill
NestJS Database
Data access patterns, Scaling, Migrations, and ORM selection.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/database-hoangnguyen0403-agent-skills-standar
Metadata
Additional technical details for this skill
- labels
-
nestjs database typeorm prisma mongodb
- triggers
-
{ "files": [ "**/*.entity.ts", "prisma/schema.prisma" ], "keywords": [ "TypeOrmModule", "PrismaService", "MongooseModule", "Repository" ] }
SKILL.md
NestJS Database Standards
Priority: P0 (FOUNDATIONAL)
Database integration patterns and ORM standards for NestJS applications.
Selection Strategy
See references/persistence_strategy.md for database selection matrix and scaling patterns (Connection Pooling, Sharding).
Patterns
- Repository Pattern: Isolate database logic.
- TypeORM: Inject
@InjectRepository(Entity). - Prisma: Create a comprehensive
PrismaService.
- TypeORM: Inject
- Abstraction: Services should call Repositories, not raw SQL queries.
Configuration (TypeORM)
- Async Loading: Always use
TypeOrmModule.forRootAsyncto load secrets fromConfigService. - Sync: Set
synchronize: falsein production; use migrations instead.
Migrations
- Never use
synchronize: truein production. - Execution: Run via init container or CD step.
- Zero-Downtime: Use Expand-Contract pattern (Add -> Backfill -> Drop).
- Seeding: Use factories for dev data; only static dicts for prod.
Best Practices
- Pagination: Mandatory. Use limit/offset or cursor-based pagination.
- Indexing: Define indexes in code (decorators/schema) for frequently filtered columns (
where,order by). - Transactions: Use
QueryRunner(TypeORM) or$transaction(Prisma) for all multi-step mutations to ensure atomicity.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?