44 Vitest best practices rules organized by priority, covering async patterns, test setup, mocking, performance, snapshots, and assertions.
Run in your terminal
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
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionvitestExecute the skills CLI command in your project's root directory to begin installation:
Package manager
npx skills add https://github.com/pproenca/dot-skills --skill vitestFetches vitest from pproenca/dot-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate vitest. Access via /vitestin your agent's command palette.
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 environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Package manager
npx skills add https://github.com/pproenca/dot-skills --skill vitestWorks with
4
total installs
4
this week
95
GitHub stars
0
upvotes
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ 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.
pproenca/dot-skills
pproenca/dot-skills
pproenca/dot-skills
pproenca/dot-skills
pproenca/dot-skills
pproenca/dot-skills
We added vitest from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Registry listing for vitest matched our evaluation — installs cleanly and behaves as described in the markdown.
vitest fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Solid pick for teams standardizing on skills: vitest is focused, and the summary matches what you get after install.
vitest reduced setup friction for our internal harness; good balance of opinion and flexibility.
vitest has been reliable in day-to-day use. Documentation quality is above average for community skills.
Registry listing for vitest matched our evaluation — installs cleanly and behaves as described in the markdown.
vitest reduced setup friction for our internal harness; good balance of opinion and flexibility.
vitest has been reliable in day-to-day use. Documentation quality is above average for community skills.
Registry listing for vitest matched our evaluation — installs cleanly and behaves as described in the markdown.
showing 1-10 of 71