Skip to content

ever-co/ever-works / .agents/skills/nestjs-best-practices

nestjs-best-practices

Verified

NestJS best practices and architecture patterns for building production-ready applications. This skill should be used when writing, reviewing, or refactoring NestJS code to ensure proper patterns for modules, dependency injection, security, and performance.

FileKindSize
AGENTS.mdmarkdown154.2 KB
README.mdmarkdown4.7 KB
SKILL.mdskill md4.8 KB
rules/_sections.mdmarkdown2.1 KB
rules/_template.mdmarkdown633 B
rules/api-use-dto-serialization.mdmarkdown4.2 KB
rules/api-use-interceptors.mdmarkdown5.4 KB
rules/api-use-pipes.mdmarkdown5.3 KB
rules/api-versioning.mdmarkdown4.7 KB
rules/arch-avoid-circular-deps.mdmarkdown1.9 KB
rules/arch-feature-modules.mdmarkdown2.3 KB
rules/arch-module-sharing.mdmarkdown3.7 KB
rules/arch-single-responsibility.mdmarkdown2.8 KB
rules/arch-use-events.mdmarkdown2.9 KB
rules/arch-use-repository-pattern.mdmarkdown2.7 KB
rules/db-avoid-n-plus-one.mdmarkdown3.8 KB
rules/db-use-migrations.mdmarkdown3.7 KB
rules/db-use-transactions.mdmarkdown3.6 KB
rules/devops-graceful-shutdown.mdmarkdown5.5 KB
rules/devops-use-config-module.mdmarkdown4.2 KB
rules/devops-use-logging.mdmarkdown5.1 KB
rules/di-avoid-service-locator.mdmarkdown2.8 KB
rules/di-interface-segregation.mdmarkdown5.0 KB
rules/di-liskov-substitution.mdmarkdown6.8 KB
rules/di-prefer-constructor-injection.mdmarkdown2.2 KB
rules/di-scope-awareness.mdmarkdown2.5 KB
rules/di-use-interfaces-tokens.mdmarkdown2.5 KB
rules/error-handle-async-errors.mdmarkdown3.4 KB
rules/error-throw-http-exceptions.mdmarkdown3.0 KB
rules/error-use-exception-filters.mdmarkdown3.4 KB
rules/micro-use-health-checks.mdmarkdown6.1 KB
rules/micro-use-patterns.mdmarkdown5.0 KB
rules/micro-use-queues.mdmarkdown5.7 KB
rules/perf-async-hooks.mdmarkdown2.8 KB
rules/perf-lazy-loading.mdmarkdown3.6 KB
rules/perf-optimize-database.mdmarkdown3.0 KB
rules/perf-use-caching.mdmarkdown3.3 KB
rules/security-auth-jwt.mdmarkdown3.8 KB
rules/security-rate-limiting.mdmarkdown3.1 KB
rules/security-sanitize-output.mdmarkdown3.7 KB
rules/security-use-guards.mdmarkdown3.4 KB
rules/security-validate-all-input.mdmarkdown3.2 KB
rules/test-e2e-supertest.mdmarkdown4.4 KB
rules/test-mock-external-services.mdmarkdown4.2 KB
rules/test-use-testing-module.mdmarkdown4.1 KB
scripts/build-agents.tsscript8.1 KB
scripts/build.shscript369 B
scripts/package-lock.jsonmanifest7.7 KB
scripts/package.jsonmanifest410 B

rules/db-use-transactions.md

View on GitHub
---
title: Use Transactions for Multi-Step Operations
impact: HIGH
impactDescription: Ensures data consistency in multi-step operations
tags: database, transactions, typeorm, consistency
---

## Use Transactions for Multi-Step Operations

When multiple database operations must succeed or fail together, wrap them in a transaction. This prevents partial updates that leave your data in an inconsistent state. Use TypeORM's transaction APIs or the DataSource query runner for complex scenarios.

**Incorrect (multiple saves without transaction):**

```typescript
// Multiple saves without transaction
@Injectable()
export class OrdersService {
	async createOrder(userId: string, items: OrderItem[]): Promise<Order> {
		// If any step fails, data is inconsistent
		const order = await this.orderRepo.save({ userId, status: 'pending' });

		for (const item of items) {
			await this.orderItemRepo.save({ orderId: order.id, ...item });
			await this.inventoryRepo.decrement({ productId: item.productId }, 'stock', item.quantity);
		}

		await this.paymentService.charge(order.id);
		// If payment fails, order and inventory are already modified!

		return order;
	}
}
```

**Correct (use DataSource.transaction for automatic rollback):**

```typescript
// Use DataSource.transaction() for automatic rollback
@Injectable()
export class OrdersService {
	constructor(private dataSource: DataSource) {}

	async createOrder(userId: string, items: OrderItem[]): Promise<Order> {
		return this.dataSource.transaction(async (manager) => {
			// All operations use the same transactional manager
			const order = await manager.save(Order, { userId, status: 'pending' });

			for (const item of items) {
				await manager.save(OrderItem, { orderId: order.id, ...item });
				await manager.decrement(Inventory, { productId: item.productId }, 'stock', item.quantity);
			}

			// If this throws, everything rolls back
			await this.paymentService.chargeWithManager(manager, order.id);

			return order;
		});
	}
}

// QueryRunner for manual transaction control
@Injectable()
export class TransferService {
	constructor(private dataSource: DataSource) {}

	async transfer(fromId: string, toId: string, amount: number): Promise<void> {
		const queryRunner = this.dataSource.createQueryRunner();
		await queryRunner.connect();
		await queryRunner.startTransaction();

		try {
			// Debit source account
			await queryRunner.manager.decrement(Account, { id: fromId }, 'balance', amount);

			// Verify sufficient funds
			const source = await queryRunner.manager.findOne(Account, {
				where: { id: fromId }
			});
			if (source.balance < 0) {
				throw new BadRequestException('Insufficient funds');
			}

			// Credit destination account
			await queryRunner.manager.increment(Account, { id: toId }, 'balance', amount);

			// Log the transaction
			await queryRunner.manager.save(TransactionLog, {
				fromId,
				toId,
				amount,
				timestamp: new Date()
			});

			await queryRunner.commitTransaction();
		} catch (error) {
			await queryRunner.rollbackTransaction();
			throw error;
		} finally {
			await queryRunner.release();
		}
	}
}

// Repository method with transaction support
@Injectable()
export class UsersRepository {
	constructor(
		@InjectRepository(User) private repo: Repository<User>,
		private dataSource: DataSource
	) {}

	async createWithProfile(userData: CreateUserDto, profileData: CreateProfileDto): Promise<User> {
		return this.dataSource.transaction(async (manager) => {
			const user = await manager.save(User, userData);
			await manager.save(Profile, { ...profileData, userId: user.id });
			return user;
		});
	}
}
```

Reference: [TypeORM Transactions](https://typeorm.io/transactions)
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall