Claude Skill

vitest

Imported from paulrberg/agent-skills/skills/vitest.

LLM Mart · 0 points · 1 views 0 listing impressions 0 install-command copies
Download PaulRBerg-agent-skills-skills_vitest-c9e5a34.zip · 5 KB

Install

skills CLI npx skills add https://github.com/PaulRBerg/agent-skills/tree/main/skills/vitest
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install paulrberg-agent-skills@llmmart
Git git clone https://github.com/PaulRBerg/agent-skills.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole paulrberg/agent-skills collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Vitest

Repository configuration, projects, setup, imports/globals, environments, aliases, test placement, and cleanup own the test contract. Inspect them and nearby tests before adding generic patterns. Do not add globals, jsdom, coverage, new setup, or browser mode by default.

Workflow

Define the behavior or regression. Test its observable public result. Mock system boundaries rather than the behavior under test. Follow local fixture and cleanup ownership. In Effect repositories, use established @effect/vitest conventions such as it.effect, Layers, and TestClock rather than generic replacements. For a bug fix, reproduce the failure before relying on a passing result when practical.

Read patterns for component, async, fixture, snapshot, tag, or browser questions. Read mocking for module, timer, spy, or global boundaries. Read configuration for projects, migration, coverage, or reporter selection. Read troubleshooting for hangs, discovery, resolution, or flaky state.

For test changes, run the narrowest established command for the changed behavior, then the affected package suite only when shared setup or contracts changed. Use nlx vitest run only when no project recipe or script exists. Reuse passing results until new edits, failures, or unresolved concerns justify another run.

Completion requires a meaningful passing focused test under repository configuration and concise command/result evidence for test changes. A read-only explanation instead requires supporting configuration or API evidence. Do not add or run tests merely to satisfy the change workflow. When red-before-green evidence exists, use ### 🧪 Regression covered. Otherwise, use ### 🧪 Tests verified for executed tests.

Files (agent-skills)
  • agents
    • openai.yaml 42 B
      Loading…
  • references
    • configuration.md 4.3 KB
      Loading…
    • mocking.md 1.7 KB
      Loading…
    • testing-patterns.md 1.2 KB
      Loading…
    • troubleshooting.md 1.3 KB
      Loading…
  • SKILL.md 2 KB
    ---
    name: vitest
    description:
      "Use for Vitest in TypeScript projects (Node, bun, React/Next.js, Effect): write, run, or debug unit/component tests,
      mocks, testing utilities, and coverage."
    ---
    
    # Vitest
    
    Repository configuration, projects, setup, imports/globals, environments, aliases, test placement, and cleanup own the
    test contract. Inspect them and nearby tests before adding generic patterns. Do not add globals, jsdom, coverage, new
    setup, or browser mode by default.
    
    ## Workflow
    
    Define the behavior or regression. Test its observable public result. Mock system boundaries rather than the behavior
    under test. Follow local fixture and cleanup ownership. In Effect repositories, use established `@effect/vitest`
    conventions such as `it.effect`, Layers, and TestClock rather than generic replacements. For a bug fix, reproduce the
    failure before relying on a passing result when practical.
    
    Read [patterns](references/testing-patterns.md) for component, async, fixture, snapshot, tag, or browser questions. Read
    [mocking](references/mocking.md) for module, timer, spy, or global boundaries. Read
    [configuration](references/configuration.md) for projects, migration, coverage, or reporter selection. Read
    [troubleshooting](references/troubleshooting.md) for hangs, discovery, resolution, or flaky state.
    
    For test changes, run the narrowest established command for the changed behavior, then the affected package suite only
    when shared setup or contracts changed. Use `nlx vitest run` only when no project recipe or script exists. Reuse passing
    results until new edits, failures, or unresolved concerns justify another run.
    
    Completion requires a meaningful passing focused test under repository configuration and concise command/result evidence
    for test changes. A read-only explanation instead requires supporting configuration or API evidence. Do not add or run
    tests merely to satisfy the change workflow. When red-before-green evidence exists, use `### 🧪 Regression covered`.
    Otherwise, use `### 🧪 Tests verified` for executed tests.
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.