vitest

pproenca/dot-skills · updated May 20, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/pproenca/dot-skills --skill vitest
0 commentsdiscussion
summary

44 Vitest best practices rules organized by priority, covering async patterns, test setup, mocking, performance, snapshots, and assertions.

  • Async patterns and test isolation are marked CRITICAL; covers awaiting assertions, returning promises, fake timers, and proper cleanup between tests
  • Mocking rules address vi.mock hoisting, spyOn vs mock selection, implementation patterns, and type safety
  • Performance optimization includes pool selection, test isolation toggling, happy-dom preferen
skill.md

Vitest Best Practices

Comprehensive performance optimization and best practices guide for Vitest testing framework. Contains 44 rules across 8 categories, prioritized by impact to guide test writing, refactoring, and code review.

When to Apply

Reference these guidelines when:

  • Writing new Vitest tests
  • Debugging flaky or slow tests
  • Setting up test configuration
  • Reviewing test code in PRs
  • Migrating from Jest to Vitest
  • Optimizing CI/CD test performance

Rule Categories by Priority

Priority Category Impact Prefix
1 Async Patterns CRITICAL async-
2 Test Setup & Isolation CRITICAL setup-
3 Mocking Patterns HIGH mock-
4 Performance HIGH perf-
5 Snapshot Testing MEDIUM snap-
6 Environment MEDIUM env-
7 Assertions LOW-MEDIUM assert-
8 Test Organization LOW org-

Quick Reference

1. Async Patterns (CRITICAL)

  • async-await-assertions - Await async assertions to prevent false positives
  • async-return-promises - Return promises from test functions
  • async-fake-timers - Use fake timers for time-dependent code
  • async-waitfor-polling - Use vi.waitFor for async conditions
  • async-concurrent-expect - Use test context expect in concurrent tests
  • async-act-wrapper - Await user events to avoid act warnings
  • async-error-handling - Test async error handling properly

2. Test Setup & Isolation (CRITICAL)

  • setup-beforeeach-cleanup - Clean up state in afterEach hooks
  • setup-restore-mocks - Restore mocks after each test
  • setup-avoid-shared-state - Avoid shared mutable state between tests
  • setup-beforeall-expensive - Use beforeAll for expensive one-time setup
  • setup-reset-modules - Reset modules when testing module state
  • setup-test-factories - Use test factories for complex test data

3. Mocking Patterns (HIGH)

  • mock-vi-mock-hoisting - Understand vi.mock hoisting behavior
  • mock-spyon-vs-mock - Choose vi.spyOn vs vi.mock appropriately
  • mock-implementation-not-value - Use mockImplementation for dynamic mocks
  • mock-msw-network - Use MSW for network request mocking
  • mock-avoid-overmocking - Avoid over-mocking
  • mock-type-safety - Maintain type safety in mocks
  • mock-clear-between-tests - Clear mock state between tests

4. Performance (HIGH)

  • perf-pool-selection - Choose the right pool for performance
  • perf-disable-isolation - Disable test isolation when safe
  • perf-happy-dom - Use happy-dom over jsdom when possible
  • perf-sharding - Use sharding for CI parallelization
  • perf-run-mode-ci - Use run mode in CI environments
  • perf-bail-fast-fail - Use bail for fast failure in CI

5. Snapshot Testing (MEDIUM)

  • snap-inline-over-file - Prefer inline snapshots for small values
  • snap-avoid-large - Avoid large snapshots
  • snap-stable-serialization - Ensure stable snapshot serialization
  • snap-review-updates - Review snapshot updates before committing
  • snap-describe-intent - Name snapshot tests descriptively

6. Environment (MEDIUM)

  • env-per-file-override - Override environment per file when needed
  • env-setup-files - Use setup files for global configuration
  • env-globals-config - Configure globals consistently
  • env-browser-api-mocking - Mock browser APIs not available in test environment

7. Assertions (LOW-MEDIUM)

  • assert-specific-matchers - Use specific matchers over generic ones
  • assert-edge-cases - Test edge cases and boundaries
  • assert-one-assertion-concept - Test one concept per test
  • assert-expect-assertions - Use expect.assertions for async tests
  • assert-toequal-vs-tobe - Choose toBe vs toEqual correctly

8. Test Organization (LOW)

  • org-file-colocation - Colocate test files with source files
  • org-describe-nesting - Use describe blocks for logical grouping
  • org-test-naming - Write descriptive test names
  • org-test-skip-only - Use skip and only appropriately

How to Use

Read individual reference files for detailed explanations and code examples:

Related Skills

  • For TDD methodology, see test-tdd skill
  • For API mocking with MSW, see test-msw skill
  • For TypeScript testing patterns, see typescript skill

Full Compiled Document

For the complete guide with all rules expanded: AGENTS.md

how to use vitest

How to use vitest on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add vitest
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/pproenca/dot-skills --skill vitest

The skills CLI fetches vitest from GitHub repository pproenca/dot-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/vitest

Reload or restart Cursor to activate vitest. Access the skill through slash commands (e.g., /vitest) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

Task Automation & Efficiency

Automate repetitive workflows and reduce manual effort

Example

Generate reports, summarize documents, draft communications

Save 3-5 hours per week on routine tasks

Knowledge Enhancement

Learn new skills, understand complex topics, get expert guidance

Example

Explain concepts, provide examples, suggest learning resources

Accelerate learning and skill development by 2x

Quality Improvement

Enhance output quality through reviews, suggestions, and refinements

Example

Review drafts, suggest improvements, catch errors

Improve work quality by 30-40% with less effort

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client with skill support
  • Clear understanding of task or problem to solve
  • Willingness to iterate and refine outputs

Time Estimate

15-45 minutes depending on use case complexity

Installation Steps

  1. 1.Install skill using provided installation command
  2. 2.Test with simple use case relevant to your work
  3. 3.Evaluate output quality and relevance
  4. 4.Iterate on prompts to improve results
  5. 5.Integrate into regular workflow if valuable

Common Pitfalls

  • Expecting perfect results without iteration
  • Not providing enough context in prompts
  • Using skill for tasks outside its intended scope
  • Accepting outputs without review and validation

Best Practices

✓ Do

  • +Start with clear, specific prompts
  • +Provide relevant context and constraints
  • +Review and refine all outputs before using
  • +Iterate to improve output quality
  • +Document successful prompt patterns

✗ Don't

  • Don't use without understanding skill limitations
  • Don't skip validation of outputs
  • Don't share sensitive information in prompts
  • Don't expect skill to replace human judgment

💡 Pro Tips

  • Be specific about desired format and style
  • Ask for multiple options to choose from
  • Request explanations to understand reasoning
  • Combine AI efficiency with human expertise

When to Use This

✓ Use When

Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.

✗ Avoid When

Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.

Learning Path

  1. 1Familiarize yourself with skill capabilities and limitations
  2. 2Start with low-risk, non-critical tasks
  3. 3Progress to more complex and valuable use cases
  4. 4Build expertise through regular use and experimentation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.671 reviews
  • Kofi Gonzalez· Dec 28, 2024

    We added vitest from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Isabella Ghosh· Dec 16, 2024

    Registry listing for vitest matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Kiara Flores· Dec 12, 2024

    vitest fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Meera Jain· Nov 23, 2024

    Solid pick for teams standardizing on skills: vitest is focused, and the summary matches what you get after install.

  • Nia Jain· Nov 19, 2024

    vitest reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Nia Tandon· Nov 19, 2024

    vitest has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Omar Park· Nov 3, 2024

    Registry listing for vitest matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Chinedu Gill· Oct 22, 2024

    vitest reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Maya Zhang· Oct 14, 2024

    vitest has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Benjamin Robinson· Oct 10, 2024

    Registry listing for vitest matched our evaluation — installs cleanly and behaves as described in the markdown.

showing 1-10 of 71

1 / 8