Best use case
vitest is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Vitest configuration, mocking, coverage, snapshot testing, and performance.
Teams using vitest should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/vitest/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How vitest Compares
| Feature / Agent | vitest | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Vitest configuration, mocking, coverage, snapshot testing, and performance.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Vitest Skill
Expert assistance for unit and integration testing with Vitest.
## Capabilities
- Configure Vitest for projects
- Write unit and integration tests
- Implement mocking strategies
- Configure coverage reporting
- Optimize test performance
## Test Patterns
```typescript
import { describe, it, expect, vi, beforeEach } from 'vitest';
import { render, screen } from '@testing-library/react';
import { UserService } from './user.service';
describe('UserService', () => {
const mockDb = { user: { findMany: vi.fn() } };
beforeEach(() => {
vi.clearAllMocks();
});
it('should fetch users', async () => {
mockDb.user.findMany.mockResolvedValue([{ id: '1', name: 'John' }]);
const service = new UserService(mockDb);
const users = await service.findAll();
expect(users).toHaveLength(1);
expect(mockDb.user.findMany).toHaveBeenCalledOnce();
});
});
```
## Configuration
```typescript
// vitest.config.ts
export default defineConfig({
test: {
globals: true,
environment: 'jsdom',
coverage: {
provider: 'v8',
reporter: ['text', 'html'],
},
},
});
```
## Target Processes
- unit-testing
- react-testing
- tdd-developmentRelated Skills
process-builder
Scaffold new babysitter process definitions following SDK patterns, proper structure, and best practices. Guides the 3-phase workflow from research to implementation.
babysitter
Orchestrate via @babysitter. Use this skill when asked to babysit a run, orchestrate a process or whenever it is called explicitly. (babysit, babysitter, orchestrate, orchestrate a run, workflow, etc.)
yolo
Run Babysitter autonomously with minimal manual interruption.
user-install
Install the user-level Babysitter Codex setup.
team-install
Install the team-pinned Babysitter Codex workspace setup.
retrospect
Summarize or retrospect on a completed Babysitter run.
resume
Resume an existing Babysitter run from Codex.
project-install
Install the Babysitter Codex workspace integration into the current project.
plan
Plan a Babysitter workflow without executing the run.
observe
Observe, inspect, or monitor a Babysitter run.
model
Inspect or change Babysitter model-routing policy by phase.
issue
Run an issue-centric Babysitter workflow.