Plans and interprets A/B copy tests to maximize conversion. Activate when the user asks what to test in copy, how to structure an A/B test, how to interpret test results, which metrics to track, how to scale copy that works, or any data-driven copy optimization.
Validate and choose proportionate test proof for tests, CI, coverage, evals, and closeout evidence: map changed files to repo-native commands, place checks at commit, push, and pull-request gates, classify pass/fail/blocked ownership, and preserve trace/regression artifacts. Use when users ask what tests or gates to run, how to design coverage, why validation failed, or what proof supports a claim.
Test user-facing UI with TDD, component tests, a11y checks, and critical-path coverage. Use when writing or fixing UI tests, verifying loading/error/empty states, or when the user mentions test/TDD/coverage/regresi — including natural language, not only /test-ui.
Write tests for E2BGateway. Use when writing unit tests, integration tests, or E2E tests — covers conventions, layer selection, mocks, and race detection.
Write tests for code. Use when: (1) user asks to write, add, or improve tests; (2) after implementing non-trivial features—propose which tests would add value before writing; (3) user asks to verify a bugfix with a regression test; (4) user wants to understand what tests a change needs.
Design or review testing strategy, test portfolios, and test quality. Use for unit/integration/contract/E2E choices, flaky or brittle tests, mocks and test doubles, BDD review, legacy-code testing, production QA, and testing LLM or AI-generated systems. Also covers TCRDD / TCR (test && commit || revert, red-green-refactor, baby steps, commit on green, revert on failure, approval-gated TDD) and HTTP API smoke tests (smoke test, critical path test, CI gate, Hurl, .hurl files, curl smoke test).
Keep developer test commands identical to Jenkins, and raise real test coverage with tests that exercise actual behavior — because Jenkins and SonarQube gate on presence and a coverage number, not on whether a test is meaningful.
React Testing Library 및 Vitest 기반 테스팅 모범 관례. 다음 상황에서 사용: (1) .test.tsx, .test.ts, .spec.tsx, .spec.ts 파일 작업 시, (2) 컴포넌트 테스트 작성 또는 리팩토링 시, (3) 'test', 'testing', 'vitest', 'RTL', 'getByRole', 'userEvent', 'waitFor', 'expect' 키워드 포함 작업 시, (4) 비동기 로직 또는 사용자 상호작용 테스트 작성 시
Testing stage. Prefer writing test CASES — unit tests, or scripted e2e cases — that exercise code and commands, rather than having the agent manually pilot the UI. Avoid loops where the agent drives Playwright and eyeballs screenshots to judge correctness: its visual judgment is unreliable and screenshots are expensive. Use when verifying a change. Leave visual/UX judgment to a human.
Use when the user writes or runs tests, sets up the Test Runner, needs Edit Mode or Play Mode tests, test assembly definitions, mocks, or async tests, or runs tests in CI. Covers Unity Test Framework, NUnit assertions, UnityTest coroutines, async Task tests, and test asmdef setup.
A folder with a SKILL.md file: a name, a description of when to use it, and instructions. Claude loads a skill only when the task matches its description.
How do I use one I find here?
Copy the folder into your project's .claude/skills/ directory, or into your own skills folder to use it everywhere.
What do the warnings mean?
We read each file for commands that read secrets, delete things or pipe downloads into a shell, and say so before you copy it. No warning is not a promise that a file is safe.
Which skills worked for people?
Open a skill to see its discussion. Reports from people and their agents are coming.