Write, review, and audit tests for Flutter projects using Clean Architecture + Riverpod. Use when writing unit tests, widget tests, golden tests, reviewing test quality, checking test coverage, creating mocks/spies, or testing Riverpod providers.
Testing the product inside the harness — which tests go in which layer, acceptance tests from each feature's declared behavior, keeping the gate fast, and judging test quality.
Methodology and formats for test-case design and execution across the entire SSDLC. Code tests, logic, processes, specs, constraints. Domain-specific eval patterns: testing/eval_patterns/. Triggers when test cases must be designed or executed (build prepare test-design, fix verify); NOT for ad-hoc manual checks without a test plan.
Skill: Testing
## Description
Write, run, or fix tests for the Blog API using pytest and httpx.
## When to Use
Trigger this skill when the user says:
- "write tests", "add tests
How implementers and fixer test their changes - unit tests for every change, end-to-end tests only when the user asks, the shape of each, setting up a harness, how to run them and output discipline. Preloaded by implementer, parallel-implementer and fixer.
Testing taxonomy: test purposes, levels, verification modes, and doubles. Use when choosing the kind of test, its boundary, or how to observe its subject.
Choose tests for their concrete regression value, avoid low-value coverage, and verify changes by exercising the real built behaviour. Use during implementation, fixes, planning, diagnosis, and code review when choosing verification, adding or changing tests, considering a missing-test finding, or when the user asks to test, check, or verify a change.
Use when about to write, add or change a test in any project — a unit, component, API or E2E test, a regression test for a bug, or tests for a change just made. Preloaded into code-writing agents (implementation and bugfix) so the authoring core is in context before the first test file is written. Fires on "write a test for", "add a regression test", "add tests for this change", "cover this with a test", "write a Playwright spec for". Not for: planning or auditing a suite, choosing which tests to run, fixtures, the E2E environment or the testing profile (/aidex:coverage); the RED-first bug-fix procedure (/aidex:bugfix).
This skill should be used when the user asks to "add an E2E test", "run live E2E", "run mock-LLM tests", "debug Playwright CI", "test the Docker image", or changes tests/e2e, Playwright configs, E2E workflows, artifacts, or test reporting.
Use when asked to test a microsoft/aspire pull request, including CLI, hosting, dashboard, component, template, and VS Code extension changes. Also covers testing PRs that change CI infrastructure — GitHub Actions (workflows, actions, gh-aw agentic workflows, CI scripts under .github/ and eng/) and Azure DevOps pipelines (eng/pipelines, eng/common).
Steady9 mentions in 2 weeks
2 projects use a version of this
6.4k6mo agoReviewMountCreate a free account to mount
Defines mandatory testing practices for features, bug fixes, refactors, endpoints, business rules, integrations, and behavior changes. Use during implementation and before declaring any code task complete.
Use when writing tests, deciding on test coverage, choosing between unit/integration/E2E tests, applying TDD, or reviewing test quality — covers rigor tiers, the Red-Green-Refactor cycle, coverage requirements, and Playwright for UI testing.
测试与覆盖率:单元/集成/功能测试、TDD、回归测试、性质测试(Hypothesis/QuickCheck)、 mock 外部依赖、行覆盖率与 Codecov。Use when the user asks to write tests, raise coverage, or choose a testing approach. 触发于「写测试/提覆盖率/选测试策略」。
How to verify AutoCSS work before it ships, in a zero-dependency architecture. Covers the air-gap test, driving the real app in a browser to observe behavior, verifying CSS-only state/visibility, and the accessibility passes. Test tooling is dev-only and never enters the shipped static shell. Use before committing any nontrivial change, or when asked to confirm something works.
Estratégia e escrita de testes production-grade: pirâmide vs troféu, unit/integration/e2e, o que testar (comportamento, não implementação), test doubles, contract e mutation testing, cobertura útil. Use quando o usuário mencionar: "como testar", "escrever testes", "estratégia de testes", "cobertura", "test plan", "TDD", "mock vs stub", "teste e2e", "teste de integração", "flaky test".
How verification works in THIS repo — the cheapest-to-costliest confidence ladder and the exact commands that work today. Carries: the real test runner + invocation, the offline-safe rule (unit tests need no env/service/network/GPU — stub the boundary), the ML confidence checks (tiny-data smoke: a forward pass + one train step on a 2-sample fixture; determinism; split-leakage; metric sanity), the live/GPU-smoke pattern (skips cleanly when its dependency is down, self-cleans), readiness checks, and environment preconditions. Load BEFORE running or writing a test, verifying a change, or claiming something works. Triggers: run tests, verify, does this work, test this change, pytest, uv run pytest, smoke test, offline test, readiness check, integration test, CI, forward-pass smoke, shape mismatch, determinism test, leakage test, overfit one batch, does the model train, cuda available.
While testing an implemented feature or fix, investigate incidental suspected bugs and file new, unrelated findings in the project's designated GitHub repository. Use during implementation testing, not as a request for a broader bug audit.
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.