nestjs-personal-conventions
NestJS Personal Conventions
Overview
REQUIRED SUB-SKILL: Invoke nestjs-best-practices first — it covers generic NestJS architecture, DI, and security. This skill is a personal layer on top of it: four opinionated conventions this developer applies to every NestJS project, closing gaps generic best-practice guidance leaves open (it doesn't mandate a repository layer, doesn't say DTOs must implement shared interfaces, and doesn't prescribe a shape for external HTTP integrations).
Baseline testing (an agent asked to add a DB lookup + outbound webhook call, no skill loaded) reproducibly violates all four: it calls the ORM client directly from a service, writes a DTO with no shared-interface contract, and bundles the outbound HTTP call into an ad-hoc service instead of a dedicated one. None of this is exotic knowledge — it just isn't default NestJS style, so it has to be stated explicitly.