react-testing-workflows

react-testing-workflows is a skill for Claude Code from PMDevSolutions/Aurelius. It costs 76 tokens per session (4,963 once invoked), scanned A, original, MIT.

A testing guide for React applications written in TypeScript. It covers small function and hook tests, component tests, browser-based end-to-end tests, Storybook interaction tests, and coverage reporting.

In plain words
What is it for?
Use it to configure Vitest, test React components and custom hooks, create Storybook stories, write Playwright browser tests, and measure coverage.
Why use it?
It gives developers a testing approach for checking isolated code, connected components, and complete user journeys instead of relying on manual checks. It also helps investigate failing tests and set up the required tools.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

Good fit Use it to configure Vitest, test React components and custom hooks, create…

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/pmdevsolutions/aurelius/react-testing-workflows
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add PMDevSolutions/Aurelius --skill react-testing-workflows
Clone the repo
git clone --depth 1 https://github.com/PMDevSolutions/Aurelius

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for react-testing-workflows

README.md
[![agentmods](https://agentmods.dev/badge/skills/pmdevsolutions/aurelius/react-testing-workflows.svg)](https://agentmods.dev/skills/pmdevsolutions/aurelius/react-testing-workflows)
Your own site
<a href="https://agentmods.dev/skills/pmdevsolutions/aurelius/react-testing-workflows"><img src="https://agentmods.dev/badge/skills/pmdevsolutions/aurelius/react-testing-workflows.svg" alt="Measured on agentmods" height="20"></a>
Per session 76 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,963 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00076 $0.04963
Opus 5 $0.00038 $0.02482
Sonnet 5 $0.00015 $0.00993
Haiku 4.5 $0.00008 $0.00496

Measured 2d ago against content hash daac289e35e8, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

react-testing-workflows scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/react-testing-workflows/SKILL.md · 732 lines

How it starts

The opening of the file, as written. The whole thing — 732 lines — stays where its author put it; the contents beside it link to each section on GitHub.

React Testing Workflows

Overview

This skill provides a complete testing strategy for React applications built with TypeScript. It covers every layer of the testing pyramid: unit tests with Vitest, component integration tests with React Testing Library, visual and interaction tests with Storybook, and end-to-end tests with Playwright.

Testing Pyramid Target Ratios:

Layer Proportion Tool Speed
Unit (functions, hooks) 50% Vitest < 5ms each
Integration (components) 30% Vitest + React Testing Library < 50ms each
E2E (full user flows) 15% Playwright < 5s each
Visual (screenshot comparison) 5% Storybook + Chromatic or Playwright Varies

When to Use

Use this skill when:

  • Setting up testing infrastructure for a React project
  • Writing tests for React components or custom hooks
  • Creating Storybook stories with play functions
  • Writing E2E tests with Playwright
  • Configuring test coverage reporting
  • Debugging failing tests

Trigger phrases:

  • "Write tests for this component"
  • "Set up Vitest"
  • "Test this custom hook"
  • "Create a Storybook story"
  • "Write an E2E test"
  • "Check test coverage"
  • "Why is this test failing"

Vitest Configuration

Setup

pnpm add -D vitest @testing-library/react @testing-library/jest-dom @testing-library/user-event jsdom @vitejs/plugin-react

vitest.config.ts

import { defineConfig } from "vitest/config";
import react from "@vitejs/plugin-react";
import path from "path";

export default defineConfig({
  plugins: [react()],
  test: {
    globals: true,
    environment: "jsdom",
    setupFiles: ["./src/test/setup.ts"],
    include: ["src/**/*.{test,spec}.{ts,tsx}"],
    coverage: {
      provider: "v8",
      reporter: ["text", "html", "lcov"],
      include: ["src/**/*.{ts,tsx}"],
      exclude: [
        "src/**/*.test.{ts,tsx}",
        "src/**/*.stories.{ts,tsx}",
        "src/test/**",
        "src/types/**",
        "src/**/*.d.ts",
      ],
      thresholds: {
        branches: 80,
        functions: 80,
        lines: 80,
        statements: 80,
      },
    },
  },
  resolve: {
    alias: {
      "@": path.resolve(__dirname, "./src"),
    },
  },
});

Read the full file on GitHub · 732 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 732 lines · 0 tokens per session scan A daac289e35e8

Subscribe to this mod's changes

react-testing-workflows is a skill published in the GitHub repository PMDevSolutions/Aurelius (8 stars, last pushed 22d ago), licensed MIT. It adds 76 tokens to every session and 4,963 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-04.

Related

Other skills, from other repositories

frontend-testing

Scaffold and advise on frontend testing for production readiness, mapped to the Front-End-Checklist Testing category (13 rules). Defines a testing pyramid (unit, integration, E2E, visual, a11y, cross-browser, real-device, perf-budget, mutation, error-monitoring, coverage, mocking, contract) and emits copy-pasteable…

bestdeejay-design/agent-skills · 243 tokens

create-pi-web-extension

Como criar/extender extensões web no pi com arquitetura determinística, segurança mínima e testes automatizados (smoke + e2e via pi-test-harness).

aretw0/agents-lab · 39 tokens

webapp-testing

Testing strategy and execution for web applications. Covers test pyramid decisions (unit/integration/E2E), framework selection, mocking boundaries, and visual testing with Playwright. Use when deciding what to test, how to test it, and when writing tests.

yves-s/just-ship · 54 tokens

playwright-component-testing

Set up component testing with Playwright using a story gallery — scaffold stories and a gallery dev page driven by the built-in mount fixture, no dedicated component-testing runtime. Use when asked to test React or Vue components in isolation with Playwright, or to migrate off @playwright/experimental-ct-react / -vue.

microsoft/playwright · 69 tokens

tdd-workflow

Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.

affaan-m/ECC · 43 tokens

memstack-development-test-writer

Use this skill when the user says 'write tests', 'add tests', 'test coverage', 'unit tests', 'integration tests', 'component tests', 'mocking', 'edge cases', or needs to generate tests with proper mocking and edge case coverage. Do NOT use for refactoring plans or database migrations.

cwinvestments/memstack · 70 tokens