What problem does it solve? Building a consistent NestJS backend in a modulith monorepo requires enforcing module boundaries, tenant-aware data access, security controls, and testing discipline. This Skill encodes those architectural decisions so backend work stays aligned with the repository baseline instead of drifting into circular imports, unvalidated endpoints, or off-baseline ORMs. ## Core Features & Use Cases - Modulith boundary enforcement: Rules for module-per-feature structure, no cross-module table access, no circular imports, and typed interfaces or domain events for internal integration. - Data and security standards: TypeORM with versioned reversible migrations, PostgreSQL schema-per-tenant resolution, RS256 JWT configuration, DTO validation, and explicit authorization guards. - Testing and API contracts: Jest unit tests, Supertest integration tests, OpenAPI updates when HTTP contracts change, and an implementation checklist for every change. - Use Case: When adding a new customers module with a REST endpoint, apply this Skill to place providers in the correct boundary, validate payloads, wire RS256 authentication, update OpenAPI, and add Supertest coverage for unauthorized requests. ## Quick Start Ask the AI to create a new NestJS module with a controller, service, TypeORM entity, and integration tests following the repo's modulith and multi-tenant conventions.