What problem does it solve? Writing consistent unit tests in a Vitest and Nx workspace is error-prone: tests without scenario ids break spec checks, module mocks hide the database calls they should verify, and libs without a vitest config pass green while running nothing. This Skill encodes the exact layout and rules for unit tests so they are verifiable and consistent. ## Core Features & Use Cases - Standard test layout: One describe per function, explicit vitest imports, Russian behavior-focused it titles prefixed with a scenario id from docs/specs. - Fixture builders: Build test data with Partial<T> factory functions and module-scope shared constants instead of repeated literals. - Procedure testing: Call a Connect procedure's handle method directly with a hand-written database double (e.g. FakePrismaClient) to verify action order, rollback, and idempotence. - Use Case: When creating availability-calendar.logic.spec.ts, load this Skill to structure the describe blocks, build a day() fixture with overrides, and tag each test with its scenario id like SC-BK-19. ## Quick Start Load this Skill before creating or editing any *.spec.ts file under Vitest, then follow its layout for describes, fixtures, and procedure tests.
