Vitest Testing logo

Vitest Testing

Community
ryoppippi
vitest-testing

Write or review Vitest tests with clear behaviour-focused assertions, appropriate globals/imports, file snapshots for terminal output, and readable fixture setup. Use when adding tests, fixing Vitest failures, or improving TypeScript test quality.

Overview

Publisherryoppippi
Repositorydotfiles
Skill namevitest-testing
Stars
263
Forks
5
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by ryoppippi on GitHub. Read the source before you install it.

Installation

Install the Vitest Testing AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/ryoppippi/dotfiles.git /tmp/dotfiles
mkdir -p .claude/skills
cp -r /tmp/dotfiles/agents/skills/vitest-testing .claude/skills/vitest-testing
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Vitest Testing in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Vitest Testing on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Vitest Testing is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Vitest Testing

Use the tdd skill when the task is a logic change or bug fix that should start with a failing test. This skill covers Vitest-specific test shape and review rules.

Setup

  • Check vitest.config.* before assuming globals are enabled.
  • If globals are enabled, use describe, it, expect, vi, beforeEach, and assert directly without importing them.
  • If globals are not enabled, import only the Vitest APIs used by the file.
  • Avoid await import() and other dynamic imports in tests unless the behaviour under test is dynamic loading.
  • Use vi.stubEnv() instead of mutating process.env directly.

Readability

  • Test one behaviour per it.
  • Name tests after observable behaviour, not implementation details.
  • Avoid try/catch for expected failures. Use expect(...).toThrow(), await expect(...).rejects, or explicit Result failure assertions.
  • Avoid if branches inside test bodies. Split behaviours into separate tests or use it.each for table-driven cases.
  • KISS > DRY: do not over-DRY tests. Keep repeated setup inline when it makes the behaviour easier to read.
  • Keep assertions in the test unless a helper name is clearer than the assertion it hides.
  • Use assert to make preconditions explicit and narrow nullable values instead of using non-null assertions.

Output Tests

  • Prefer JSON assertions for structured behaviour.
  • Use file snapshots with toMatchFileSnapshot for human-readable CLI/table output so layout changes are reviewable.
  • For responsive terminal output, capture or set the terminal width used by the command.

Examples

Expected failure:

ts
it('rejects invalid config', async () => {
	await expect(loadConfig('bad.json')).rejects.toThrow(Error);
});

Table-driven case:

ts
it.each([
	['daily', '2026-05-16'],
	['monthly', '2026-05'],
])('groups %s rows by period', (reportType, expectedPeriod) => {
	const rows = groupUsage(reportType, usage);

	expect(rows[0]?.period).toBe(expectedPeriod);
});

Narrowing with assert:

ts
it('returns the first row', () => {
	const rows = getRows();
	const firstRow = rows[0];
	assert.isDefined(firstRow, 'expected at least one row');

	expect(firstRow.id).toBe('row-1');
});

Frequently asked questions

What does the Vitest Testing AI skill do?

Write or review Vitest tests with clear behaviour-focused assertions, appropriate globals/imports, file snapshots for terminal output, and readable fixture setup. Use when adding tests, fixing Vitest failures, or improving TypeScript test quality.

Why use Vitest Testing on TypingMind?

Because you install it once and use it with any model. Vitest Testing is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Vitest Testing in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/ryoppippi/dotfiles/tree/main/agents/skills/vitest-testing. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Vitest Testing?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Vitest Testing?

As many as you like. As long as a model supports skills, you can use Vitest Testing with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Vitest Testing AI skill free?

Yes. It is published on GitHub by ryoppippi under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇