nestjs-clean-hex-cqrs-api-playbook

To structure a NestJS API with Clean Architecture and Hexagonal patterns, you separate API logic from business rules using Ports and Adapters. This skill guides layering from controllers to persistence adapters, enforcing token-based dependency injection within an Nx monorepo.

Preventing architectural drift in a large NestJS Nx monorepo requires enforcing strict module boundaries and standardized workflows. This skill provides a step-by-step playbook mandating CQRS-lite separation, port-based dependency injection, and DomainError usage to maintain consistency.

Adding an endpoint following CQRS-lite involves mapping the HTTP contract in libs/api, implementing the QueryService or UseCase, wiring ports via tokens, and adding a persistence adapter. This ensures API logic remains strictly separate from core business rules.

Yes, this NestJS Clean Architecture playbook supports Prisma 6.x. It codifies specific Prisma 6.x persistence rules and ensures alignment with the Prisma schema while mandating the use of DomainError for handling errors across the persistence adapters.

Token-based dependency injection in NestJS Hexagonal Architecture enforces strict module boundaries by decoupling port interfaces from concrete adapter implementations. This prevents architectural drift and ensures API logic remains separate from business rules and persistence concerns.

You need CQRS-lite in a NestJS API project when separating query services from use cases to maintain strict architectural boundaries. It helps scale large Nx monorepos by ensuring API logic and business rules remain isolated across controller and persistence layers.