Software testing expertise for writing effective tests. Use when writing tests, reviewing test quality, designing test suites, debugging test failures, or implementing TDD. Covers xUnit patterns, test case selection, mocks/fixtures, parametrization, testing stateful systems, BDD, golden/snapshot testing, and LLM output evaluation.
Use for flaky or nondeterministic tests, especially local-vs-CI inconsistencies. Trigger on intermittent failures, race/timing symptoms, retry-only greens, or unexplained skip/xfail markers. Output should isolate reproducible cause, narrowest durable fix, and prevention guidance.
Debug Compact contracts and manage toolchain versions. Covers static vs dynamic errors, reading compiler messages, the --skip-zk dev loop, version synchronization, and common traps.
Universal testing framework (frontend + backend) — a meticulous run of any testing task with evidence discipline. Use when you need to test a feature/form/build/API/service, draft a test plan, run checks, perform exploratory or regression testing, or find defects.
Skill: Testing Strategy & Implementation
## Role
You are a Quality Assurance Architect and Testing Specialist.
## Objective
Design and implement a comprehensive testing strategy that focuses on behavior-driven integration tests
Write, review, and debug tests using Vitest. Use for: unit tests, API route tests, executor/serializer/tool tests, jsdom vs node environment selection, shared __test-utils__ patterns, and mandatory code-to-test sync with executed test runs.
When the user wants to plan, run, or read A/B tests, or asks a judgement call on one: is the result real, can we stop, which version won, is this worth testing at all: sample size, duration, significance, hypotheses, and experiment backlogs. For tracking setup, see analytics. For page-level conversion fixes, see cro.
Write, change, or review Fast Link tests, choose between specs, browser tests, and real app fixtures, or audit and clean up test suites. Use when assessing test value, duplication, reliability, or coverage in this repository.
How DAG nodes prove code changes through public interfaces - red before green for new behavior and bug fixes, preservation checks for refactors, and mocks at system boundaries - loaded through load_skills. A DAG node writes or changes code and has to prove the change with tests, so its prompt lists this skill in load_skills.
What makes a good test, whatever is under test: the principles behind choosing inputs and oracles, judging a suite's adequacy, and planning a test effort. Use for general or overall questions about tests and test plans, flaky tests, or when no single technique fits, or on /testing. For a specific technique use its own skill: unit-tests, black-box, white-box, test-oracle or mutation-testing. For evaluations of agents use agent-evals.
Write tests for E2BGateway. Use when writing unit tests, integration tests, or E2E tests — covers conventions, layer selection, mocks, and race detection.
Plain text files in a repository that tell a coding agent how the project works: commands to run, conventions to follow and things to avoid. CLAUDE.md, AGENTS.md, cursor rules and skills are the common kinds.
CLAUDE.md or AGENTS.md?
CLAUDE.md is read by Claude Code. AGENTS.md is an open format that Codex, Cursor and other agents read. Many projects keep one and point the other at it.
What is a skill?
A folder with a SKILL.md that describes one capability, such as filling PDFs or reviewing code. The agent loads it only when the task calls for it.
Can I search my own team's files too?
Your agents already can, over MCP, limited to the files you're allowed to read. Searching them from this page is coming.