testing-strategy — Claude Code skill: testing and setup
This skill designs testing strategies and test plans for a project. Use it when you need test types, coverage goals, or gaps in existing checks.
npx skills add anthropics/knowledge-work-plugins --skill testing-strategy -a claude-codeWhat testing-strategy does
testing-strategy organizes testing by levels: unit tests for focused checks, integration tests for connected parts, and E2E tests for key flows. For API endpoints, it separates business-logic tests, HTTP-layer integration tests, and consumer contract tests. Data pipelines get checks for input validation, transformation correctness, and idempotency.
The skill produces a test plan that names what to test, assigns a test type to each area, sets coverage targets, and gives example cases. It also directs attention to error handling, edge cases, security boundaries, and data integrity. Frontend plans can cover components, interactions, visual regression, and accessibility.
For infrastructure, it includes smoke, chaos, and load testing. It advises skipping trivial getters and setters, framework code, and one-off scripts, so review which parts of the project carry the real testing risk before using its plan.
What it helps with
- design a testing strategy for a component
- split checks across the testing pyramid
- find gaps in existing test coverage
- choose tests for an API, pipeline, or frontend
- cover edge cases and error handling
Example prompts for the agent
- How should we test this API? Separate business-logic, HTTP-layer, and consumer contract tests.
- Write a test plan for this data pipeline with input validation, transformation, and idempotency checks.
- What tests do we need for this frontend, including accessibility and visual regression?
How to install testing-strategy
1Skills CLI (Vercel)
npx skills add anthropics/knowledge-work-plugins --skill testing-strategy -a claude-code2Manually: put the files in place
~/.claude/skills/testing-strategy/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/testing-strategy/
1Skills CLI (Vercel)
npx skills add anthropics/knowledge-work-plugins --skill testing-strategy -a codex2Manually: put the files in place
.agents/skills/testing-strategy/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add anthropics/knowledge-work-plugins --skill testing-strategy -a cursor2Manually: put the files in place
.cursor/skills/testing-strategy/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install anthropics/knowledge-work-plugins testing-strategy2Manually: put the files in place
.github/skills/testing-strategy/SKILL.md1Skills CLI (Vercel)
npx skills add anthropics/knowledge-work-plugins --skill testing-strategy -a gemini-cli2Platform CLI
gemini skills install https://github.com/anthropics/knowledge-work-plugins --path engineering/skills/testing-strategyManually: put the files in place
.devin/skills/testing-strategy/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add anthropics/knowledge-work-plugins --skill testing-strategy -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set133
The whole set →Similar
Questions about testing-strategy
How do I install testing-strategy in Claude Code?
Run npx skills add anthropics/knowledge-work-plugins --skill testing-strategy -a claude-code, run the same command again, then check ~/.claude/skills/testing-strategy/SKILL.md.
What does testing-strategy do?
It designs a testing strategy and test plan, assigns test types to project areas, proposes coverage targets and example cases, and identifies gaps in existing coverage.
Which project areas does it cover?
For APIs, it separates business logic, HTTP-layer, and consumer contract checks. For frontends, it covers components, interactions, visual regression, and accessibility; data pipelines get validation, transformation, and idempotency checks.
Source text
SKILL.md · Apache-2.0
---
name: testing-strategy
description: Design test strategies and test plans. Trigger with "how should we test", "test strategy for", "write tests for", "test plan", "what tests do we need", or when the user needs help with testing approaches, coverage, or test architecture.
---
# Testing Strategy
Design effective testing strategies balancing coverage, speed, and maintenance.
## Testing Pyramid
```
/ E2E \ Few, slow, high confidence
/ Integration \ Some, medium speed
/ Unit Tests \ Many, fast, focused
```
## Strategy by Component Type
- **API endpoints**: Unit tests for business logic, integration tests for HTTP layer, contract tests for consumers
- **Data pipelines**: Input validation, transformation correctness, idempotency tests
- **Frontend**: Component tests, interaction tests, visual regression, accessibility
- **Infrastructure**: Smoke tests, chaos engineering, load tests
## What to Cover
Focus on: business-critical paths, error handling, edge cases, security boundaries, data integrity.
Skip: trivial getters/setters, framework code, one-off scripts.
## Output
Produce a test plan with: what to test, test type for each area, coverage targets, and example test cases. Identify gaps in existing coverage.
© anthropics · Apache-2.0 · anthropics/knowledge-work-plugins