testing-strategy
Use when designing test architecture, building API test suites, validating API contracts, setting up component or E2E testing, managing test data, debugging flaky tests, reviewing coverage strategy, or organizing test files. Covers test pyramid, mocking (MSW), frontend (React Testing Library, Playwright), and CI integration.
What this skill does
# Testing Strategy Comprehensive testing guidance for test architecture, coverage strategy, and test design. ## Test Pyramid | Level | Speed | Cost | Confidence | Share | |-------|-------|------|------------|-------| | **Unit** | ~1ms | Low | Narrow | 65-80% | | **Integration** | ~100ms | Medium | Medium | 15-25% | | **Contract** | ~10ms | Low | API shape | Part of unit | | **E2E** | ~1s+ | High | Broad | 5-10% | ## Key Principles - Test behavior, not implementation — test what code does, not how - For behavior changes, write the failing test first and verify it fails for the expected reason - Follow the testing pyramid — more unit tests, fewer E2E - Use meaningful coverage metrics — branch coverage over line coverage - Prevent flaky tests — no arbitrary waits, no test interdependence ## Quick Start Checklist 1. Choose test framework (Vitest recommended for new projects) 2. Design test folder structure mirroring source 3. Write unit tests for pure logic and utilities 4. Add integration tests for API endpoints and data flows 5. Add contract tests against OpenAPI spec (if applicable) 6. Add E2E tests for critical user journeys only 7. Set up CI to run tests on every PR 8. Before completion claims, run `verification-before-completion` and cite the fresh command result ## What NOT to Test - Framework internals (React rendering, Express routing) - Third-party library behavior - Trivial getters/setters with no logic - Implementation details (private methods, internal state) ## References | Reference | Description | |-----------|-------------| | [test-architecture-structure.md](references/test-architecture-structure.md) | Project structures, shared utilities, test configuration | | [test-architecture-isolation.md](references/test-architecture-isolation.md) | Playwright config, database isolation, performance optimization | | [test-design-techniques.md](references/test-design-techniques.md) | Equivalence partitioning, boundary values, decision tables, state transitions | | [test-design-error-and-advanced.md](references/test-design-error-and-advanced.md) | Error handling tests, property-based testing, parameterization, regression | | [frontend-react-testing.md](references/frontend-react-testing.md) | React Testing Library, queries, user events, hooks, forms | | [frontend-vue-a11y-visual.md](references/frontend-vue-a11y-visual.md) | Vue Test Utils, accessibility, visual/Storybook testing, anti-patterns | | [e2e-playwright.md](references/e2e-playwright.md) | Playwright POM, fixtures, auth state, API mocking, visual comparison | | [e2e-cypress-and-stability.md](references/e2e-cypress-and-stability.md) | Cypress patterns, flaky test prevention, test data, debugging | | [mocking-fundamentals.md](references/mocking-fundamentals.md) | Mock decision tree, stubs/mocks/spies/fakes, MSW setup and usage | | [mocking-modules-and-patterns.md](references/mocking-modules-and-patterns.md) | Module mocking, time mocking, anti-patterns, dependency injection | | [coverage-guide.md](references/coverage-guide.md) | Coverage metrics, meaningful thresholds, CI integration | | [api-test-frameworks-setup.md](references/api-test-frameworks-setup.md) | Vitest and Jest setup, configuration, running tests | | [api-test-supertest-and-helpers.md](references/api-test-supertest-and-helpers.md) | Supertest usage, request helpers, custom matchers, snapshots, debugging | | [api-integration-patterns.md](references/api-integration-patterns.md) | CRUD endpoint tests, relationship tests | | [api-auth-patterns.md](references/api-auth-patterns.md) | Login/logout, protected routes, authorization, auth helpers | | [api-e2e-and-edge-cases.md](references/api-e2e-and-edge-cases.md) | Multi-step workflow tests, error responses, edge cases | | [api-test-data-factories.md](references/api-test-data-factories.md) | Factory patterns, builders, fixtures | | [api-test-data-database.md](references/api-test-data-database.md) | Database helpers, cleanup strategies, data generation | | [api-contract-openapi.md](references/api-contract-openapi.md) | OpenAPI/AJV schema validation, contract tests | | [api-contract-zod-advanced.md](references/api-contract-zod-advanced.md) | Zod validation, response shape testing, breaking change detection | | [api-test-ci-pipelines.md](references/api-test-ci-pipelines.md) | CI pipeline strategy, GitHub Actions, parallel execution | | [api-test-ci-environments.md](references/api-test-ci-environments.md) | Environment config, test reporting, database services, E2E environments | | [anti-rationalization.md](references/anti-rationalization.md) | Iron Law, common rationalizations, red flag STOP list for TDD discipline |
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.