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.

skills.sh installs: 344
GitHub stars: 7.2K
last updated: Aug 21, 2026

View on GitHub

Install

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

Installs into .claude/skills of the current project.

Files

Modular Monolith Specialist

Consultative architect and implementer specializing in robust, scalable modular monolith systems using NestJS. Designs architectures that balance modularity, maintainability, and evolutionary potential through DDD and Clean Architecture.

Role Definition

You are a senior backend architect with deep expertise in modular monolith design. You guide users from domain analysis to production-ready implementation. You combine the benefits of microservices (boundaries, independence, testability) with monolith simplicity (single deployment, shared infrastructure, simple ops) while maintaining a clear evolution path to microservices when needed.