Test Writing Workflow
iOfficeAI/AionUi
Sets the test-writing workflow for the repository: risk-first scenario lists, behavior-focused Vitest tests, a full run before each commit and a coverage target.
Comprehensive vitest testing patterns covering test structure, AAA pattern, parameterized tests, assertions, mocking, test doubles, error handling, async testing, and performance optimization.
$ npx skills add PageAI-Pro/ralph-loop --skill vitest-best-practices -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install PageAI-Pro/ralph-loop vitest-best-practices --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/PageAI-Pro/ralph-loop.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agent/skills/vitest-best-practices .claude/skills/vitest-best-practices && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "vitest-best-practices" agent skill from https://github.com/PageAI-Pro/ralph-loop/tree/main/.agent/skills/vitest-best-practices into .claude/skills/vitest-best-practices/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vitest-best-practices", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/PageAI-Pro/ralph-loop/tree/main/.agent/skills/vitest-best-practicesType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add PageAI-Pro/ralph-loop --skill vitest-best-practices -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install PageAI-Pro/ralph-loop vitest-best-practices --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PageAI-Pro/ralph-loop.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agent/skills/vitest-best-practices .agents/skills/vitest-best-practices && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "vitest-best-practices" agent skill from https://github.com/PageAI-Pro/ralph-loop/tree/main/.agent/skills/vitest-best-practices into .agents/skills/vitest-best-practices/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vitest-best-practices", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add PageAI-Pro/ralph-loop --skill vitest-best-practices -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install PageAI-Pro/ralph-loop vitest-best-practices --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PageAI-Pro/ralph-loop.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agent/skills/vitest-best-practices .cursor/skills/vitest-best-practices && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "vitest-best-practices" agent skill from https://github.com/PageAI-Pro/ralph-loop/tree/main/.agent/skills/vitest-best-practices into .cursor/skills/vitest-best-practices/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vitest-best-practices", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/PageAI-Pro/ralph-loop.git --path .agent/skills/vitest-best-practices--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add PageAI-Pro/ralph-loop --skill vitest-best-practices -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install PageAI-Pro/ralph-loop vitest-best-practices --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PageAI-Pro/ralph-loop.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agent/skills/vitest-best-practices .gemini/skills/vitest-best-practices && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "vitest-best-practices" agent skill from https://github.com/PageAI-Pro/ralph-loop/tree/main/.agent/skills/vitest-best-practices into .gemini/skills/vitest-best-practices/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vitest-best-practices", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install PageAI-Pro/ralph-loop vitest-best-practicesInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add PageAI-Pro/ralph-loop --skill vitest-best-practices -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/PageAI-Pro/ralph-loop.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agent/skills/vitest-best-practices .github/skills/vitest-best-practices && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "vitest-best-practices" agent skill from https://github.com/PageAI-Pro/ralph-loop/tree/main/.agent/skills/vitest-best-practices into .github/skills/vitest-best-practices/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vitest-best-practices", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add PageAI-Pro/ralph-loop --skill vitest-best-practices -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install PageAI-Pro/ralph-loop vitest-best-practices --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PageAI-Pro/ralph-loop.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agent/skills/vitest-best-practices .opencode/skills/vitest-best-practices && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "vitest-best-practices" agent skill from https://github.com/PageAI-Pro/ralph-loop/tree/main/.agent/skills/vitest-best-practices into .opencode/skills/vitest-best-practices/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vitest-best-practices", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
vitest-best-practicesComprehensive vitest testing patterns covering test structure, AAA pattern, parameterized tests, assertions, mocking, test doubles, error handling, async testing, and performance optimization.
Vitest Best Practices is an agent skill from PageAI-Pro/ralph-loop. Comprehensive vitest testing patterns covering test structure, AAA pattern, parameterized tests, assertions, mocking, test doubles, error handling, async testing, and performance optimization. Use when writing, reviewing, or refactoring vitest tests, or when user mentions vitest, testing, TDD, test coverage, mocking, assertions, or test files (.test.ts, .spec.ts).
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 12 other files, including reference files (for example `AGENTS.md`, `references/aaa-pattern.md` and `references/assertions.md`). Compatibility notes: Requires vitest testing framework
It sits in Testing & QA, covering Unit testing. It works with Vitest. The repository describes itself as: A long-running AI agent loop. Ralph automates software development tasks by iteratively working through a task list until completion. The licence is MIT.
3 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit eba65eb. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md (its code samples are typescript).
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Requires vitest testing framework
From compatibility in the SKILL.md frontmatter.
Vitest Best Practices loads about 1.2k tokens when it runs, and up to ~26k if it reads all its reference files. Until then it costs about 98 tokens; SKILL.md has 426 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from PageAI-Pro/ralph-loop at commit eba65eb, republished under its MIT licence (© PageAI-Pro). 426 words, ~1,220 tokens.
.claude/skills/vitest-best-practices/SKILL.md (or your agent's skills folder). This skill also uses 11 other files; get the full folder from GitHub.Use this skill when you encounter any of these scenarios:
*.test.ts, *.spec.ts, or similar test filesvitest (describe, it, expect, vi)beforeEach, afterEach, beforeAll, afterAll)vi.mock(), vi.spyOn(), vi.fn()expect(...).toEqual(), .toBe(), .toThrow(), etc.)This skill provides comprehensive guidance on:
it.each() for testing variationstoEqual, toStrictEqual, toThrow)This skill uses a progressive disclosure structure to minimize context usage:
Read AGENTS.md for a concise overview of all rules with one-line summaries.
When you identify a relevant optimization, load the corresponding reference file for detailed implementation guidance:
Core Patterns:
Advanced Topics:
Each reference file contains:
This skill helps you transform unclear tests into clear, maintainable ones:
Before (unclear):
test('product test', () => {
const p = new ProductService().add({name: 'Widget'});
expect(p.status).toBe('pendingApproval');
});After (optimized with this skill):
describe('ProductService', () => {
describe('Add new product', () => {
it('should have status "pending approval" when no price is specified', () => {
// Arrange
const productService = new ProductService();
// Act
const newProduct = productService.add({name: 'Widget'});
// Assert
expect(newProduct.status).toEqual('pendingApproval');
});
});
});toEqual over toBe, toStrictEqual when needed© PageAI-Pro, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 11 other files (references) in .agent/skills/vitest-best-practices of PageAI-Pro/ralph-loop.
Open the folder on GitHubat commit eba65eb
Vitest Best Practices next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Vitest Best Practices this skillPageAI-Pro/ralph-loop | 315 | — | ~1.2k | Automated safety check: Pass | MIT | |
| Test Writing WorkflowiOfficeAI/AionUi | 33k | 1 repos | ~1.2k | Automated safety check: Pass | Apache-2.0 | |
| Vitestsupabase/supabase | 111k | 12 repos | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Test GuardamElnagdy/guard-skills | 1.3k | 2 repos | ~2.1k | Automated safety check: Pass | MIT | |
| Adding LLM MCP ToolsTriliumNext/Trilium | 38k | — | ~2.5k | Automated safety check: Pass | AGPL-3.0 | |
| Concept Page Test Writerleonardomso/33-js-concepts | 67k | — | ~5.5k | Automated safety check: Pass | MIT |
iOfficeAI/AionUi
Sets the test-writing workflow for the repository: risk-first scenario lists, behavior-focused Vitest tests, a full run before each commit and a coverage target.
supabase/supabase
Vitest API and config reference (Jest-compatible) — mocking with vi., spies, fake timers, coverage configuration, fixtures, snapshots, and test filtering.
amElnagdy/guard-skills
Reviews newly written or edited tests against nine rules that cut test bloat, such as mock-heavy checks and near-duplicate cases, before they are committed.
TriliumNext/Trilium
A skill your agent uses when adding, changing, or reviewing an LLM/MCP tool in Trilium (the defineTools definitions under packages/trilium-core/src/services/llm/tools/ —…
leonardomso/33-js-concepts
Generates Vitest tests for every runnable code example on a JavaScript concept documentation page, following a four-phase extraction and conversion process.
archestra-ai/archestra
A skill your agent uses for test selection and quality across backend, frontend, and e2e; load its backend reference for Vitest projects, mocking, DB fixtures, and performance.
PageAI-Pro/ralph-loop
Refactor high-complexity React components in frontend. An agent skill from PageAI-Pro/ralph-loop.
PageAI-Pro/ralph-loop
Playwright E2E testing patterns. An agent skill from PageAI-Pro/ralph-loop.
PageAI-Pro/ralph-loop
Guides creation of comprehensive Product Requirement Documents (PRDs) for software projects through structured questioning and validation, then generates implementation task lists in JSON format.
Works with
Categories
Comprehensive vitest testing patterns covering test structure, AAA pattern, parameterized tests, assertions, mocking, test doubles, error handling, async testing, and performance optimization. Vitest Best Practices is an agent skill from PageAI-Pro/ralph-loop. Comprehensive vitest testing patterns covering test structure, AAA pattern, parameterized tests, assertions, mocking, test doubles, error handling, async testing, and performance optimization.
Vitest Best Practices fits situations like: refactoring vitest tests; user mentions vitest; test files (.test.ts.
Run `npx skills add PageAI-Pro/ralph-loop --skill vitest-best-practices -a claude-code`. Or copy the skill folder (.agent/skills/vitest-best-practices in PageAI-Pro/ralph-loop) into .claude/skills/vitest-best-practices in your project. Claude Code loads it when a task matches its description.
Run `npx skills add PageAI-Pro/ralph-loop --skill vitest-best-practices -a codex`. Or copy the skill folder (.agent/skills/vitest-best-practices in PageAI-Pro/ralph-loop) into .agents/skills/vitest-best-practices in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add PageAI-Pro/ralph-loop --skill vitest-best-practices -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/vitest-best-practices, .gemini/skills/vitest-best-practices, .github/skills/vitest-best-practices and .opencode/skills/vitest-best-practices in your project.
SKILL.md names no scripts, command-line tools or credentials: Vitest Best Practices is instructions for the agent only. Compatibility (from SKILL.md): Requires vitest testing framework.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Vitest Best Practices is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.2k tokens (SKILL.md is roughly 4.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 25k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Vitest Best Practices: Test Writing Workflow (iOfficeAI/AionUi, 33k stars), Vitest (supabase/supabase, 111k stars), Test Guard (amElnagdy/guard-skills, 1.3k stars) and Adding LLM MCP Tools (TriliumNext/Trilium, 38k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
PageAI-Pro (a GitHub organization) maintains it in PageAI-Pro/ralph-loop, which has 315 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on August 31, 2026.
Source: PageAI-Pro/ralph-loop on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.