What problem does it solve? Writing consistent, high-coverage unit tests for NestJS code is repetitive and error-prone: developers often skip failure paths, forget to reset mocks, or produce fragile tests tied to real implementations. This Skill standardizes spec file creation with TestingModule isolation, typed mocks, and the AAA pattern. ## Core Features & Use Cases - Structured spec generation: Creates *.spec.ts files next to the code under test using an official template with TestingModule, jest-mock-extended typed mocks, and Arrange-Act-Assert structure. - Result pattern validation: Tests both isSuccess and isFailure paths, and verifies controllers map errors to HttpException. - Coverage enforcement: Runs focused coverage with pnpm test -- <spec> --coverage and requires a minimum of 85% on lines and branches. - Use Case: After implementing a new NestJS service, ask the agent to write its unit tests; it writes the spec directly to disk and reports only test signatures and coverage metrics in chat. ## Quick Start Write unit tests with coverage for the demand service in src/modules/demands/domain/services/demand.service.ts.