Lists multiple specific concrete actions: 'unit and integration testing patterns', 'commands', 'mocking (vi.mock)', 'coverage', 'writing .test.ts files', 'configuring the test runner', 'adding coverage thresholds'.

Clearly answers both what ('Vitest unit and integration testing patterns, commands, mocking, and coverage') and when ('Use when writing .test.ts files, configuring the test runner, or adding coverage thresholds') with explicit trigger guidance.

Includes strong natural keywords users would say: 'Vitest', 'unit', 'integration testing', 'mocking', 'vi.mock', 'coverage', '.test.ts', 'test runner', 'coverage thresholds'. These cover common variations of how users would describe testing needs.

Clearly scoped to Vitest specifically, with distinct triggers like 'vi.mock', '.test.ts', and 'Vitest' that distinguish it from other testing frameworks (Jest, Mocha, etc.) or general coding skills.

The content is lean and efficient. It jumps straight into commands, code examples, and configuration without explaining what Vitest is or how testing works conceptually. Every section earns its place with concrete, non-redundant information.

All code examples are fully executable and copy-paste ready — from CLI commands to test structure, mocking patterns, timer mocking, and configuration. Specific imports are shown, and examples cover real patterns (spies, module mocks, fake timers).

The workflow section provides a clear 6-step sequence with explicit validation checkpoints: run tests, fix failures, use verbose reporter to inspect, check coverage against thresholds, add targeted tests if below thresholds, and re-run. The feedback loop (step 4 and step 5) is explicit.

The skill opens with a reference to project-specific configuration in a separate file, keeps the main content well-organized into logical sections (Commands, Test Structure, Mocking, Configuration, Workflow), and avoids monolithic walls of text. References are one level deep and clearly signaled.