Nestjs Modular Monolith

This one's for when you're building a NestJS backend that needs to stay maintainable as it grows beyond basic CRUD. It guides you through setting up bounded contexts, Clean Architecture layers, and event-driven module communication so you get microservices-style boundaries without the operational overhead. The workflow is consultative, it asks about your stack preferences (Fastify vs Express, Prisma vs TypeORM, whether you actually need CQRS) before generating code, which is refreshing. Best part is the state isolation enforcement and the explicit principle that modules shouldn't share database tables. If you're building a simple API with ten endpoints, skip this. But if you're architecting something that might need to break apart later, the structured approach to module boundaries will save you from a future rewrite.

Install to Claude Code

npx -y skills add tech-leads-club/agent-skills --skill nestjs-modular-monolith --agent claude-code