Write Angular unit tests with ng-mocks (MockBuilder / MockRender / ngMocks) instead of raw TestBed. Use whenever creating or editing any `*.spec.ts` file in this Nx workspace โ components, services, pipes, directives, guards, resolvers, interceptors, NgRx effects, or any Angular construct. Triggers on: "write a test for", "add a spec", "unit test this", "cover X with tests", "fix this failing test", editing any existing spec file, or any mention of Jest, Jasmine, TestBed, MockBuilder, MockRender, ngMocks. This skill is the default for authoring tests in this project โ use it even when the user doesn't explicitly say "ng-mocks", because the house style requires ng-mocks over hand-rolled TestBed setup.
Apply test-naming conventions, AAA structure, and readability rules when writing or reviewing any *.spec.ts file. Use whenever naming describe/it blocks, structuring test bodies, deciding what to assert, or reviewing tests for clarity. Triggers on: "write a test for", "add a spec", "name this test", "review my test", "is this test readable", editing any *.spec.ts, or any question about test structure, naming, or what to assert.