Use to audit a web UI for accessibility against WCAG 2.2 AA. Runs axe-core on key pages and components, then performs the manual keyboard, focus, and screen-reader review that automation can't — driving the live app via the Playwright MCP when available — and produces a WCAG-referenced report where every finding names…
Test web UIs for accessibility to WCAG 2.2 AA with axe-core automation plus the manual keyboard, focus, and screen-reader checks automation can't catch. Use when adding a11y assertions to a suite, auditing a page or component, wiring a11y into CI, or reviewing UI for WCAG conformance. Enforces guardrails against…
Use to add or extend API contract tests for a service. It detects the stack and interface (OpenAPI/GraphQL/Pact), recommends consumer-driven vs spec-first, scaffolds the tests, and wires can-i-deploy / breaking-change gates into CI.
Design and implement API contract tests so a provider can't break its consumers. Enforces guardrails against exact-value matching, unversioned pacts, contract tests that are secretly E2E, and deploys that ship without a can-i-deploy gate. Use when adding contract tests, choosing between consumer-driven (Pact) and…
Use to triage a suspected flaky test end to end. It reproduces the non-determinism by rerunning the test many times (and varying order, workers, timezone, and seed), classifies the root cause against the flake taxonomy, then either proposes a minimal root-cause fix or quarantines the test with a required owner…
Detect, quantify, classify, and fix flaky tests — compute flake rate and per-test flake scores, reproduce non-determinism, classify the root cause, and either fix at the root or quarantine with an owner + issue + SLA. Use when tests pass-on-retry, fail intermittently in CI, or someone reaches for retries to make the…
Use to audit and improve how effective a project's Jest unit tests are. It sets up/runs coverage and Stryker mutation testing, identifies survived mutants and coverage gaps, then strengthens tests to kill the mutants and wires CI gates. Give it a module or the whole src to focus on.
Measure and improve the effectiveness of Jest unit tests using code coverage plus mutation testing (Stryker). Enforces guardrails against coverage theater — assertion-free tests, gamed mutation scores, ignored survivors — and gates CI on a mutation break threshold, not just coverage %. Use when asked to "check test…
Use to design and build LLM/RAG/agent evaluation suites in DeepEval that gate a release on output quality. It elicits or derives the golden dataset and the failure mode to guard against, picks the metrics that match it (faithfulness/answer-relevancy for the generator, contextual precision/recall for the retriever…
Author LLM/RAG/agent evaluation suites in DeepEval that prove a feature is correct with gated numbers, not vibes. Use when asked to "eval an LLM", "test a prompt", "measure RAG quality", "check for hallucination", "score answer relevancy", "verify tool calls", or gate a release on model output quality. Ships the…
Use to design and run performance tests that prove a system meets its SLOs under realistic load. It elicits or derives SLOs and a workload model, writes k6 load/stress/soak scripts and Lighthouse budgets with thresholds-as-gates, runs them against a production-like target, and interprets the results against the SLOs …
Design and run performance tests that prove a system meets its SLOs under realistic load — backend load/stress/soak/spike with k6 and frontend web-vitals with Lighthouse. Use when asked to "load test", "check performance", "find our capacity", "set a latency budget", or gate a release on speed and scale. Enforces…
Use to convert existing imperative Playwright tests into BDD with the playwright-bdd runner. It recovers each test's business intent, writes declarative Gherkin .feature files (business language, no clicks/selectors), extracts page objects, wires step definitions to Playwright fixtures, and verifies behavior parity.…
Convert existing imperative Playwright tests into BDD using the playwright-bdd runner — generate Gherkin .feature files and wire step definitions to Playwright fixtures and page objects. Enforces business-language specs (declarative, not click-by-click). Use when asked to "move to BDD/Cucumber", "generate feature…
Use to author or extend Playwright end-to-end tests for a user journey. Give it the flow to cover; it produces Page Object Model specs with stable locators, web-first assertions, fixture-based isolation, and storage-state auth — and can drive a live browser via the Playwright MCP server to inspect the real UI before…
Author and maintain resilient Playwright end-to-end tests using the Page Object Model, fixtures, and stable, user-facing locators. Enforces guardrails against flakiness, brittle selectors, and shared state. Use when writing, reviewing, or debugging Playwright E2E specs, or when wiring E2E tests into CI. See…
Use to create a tailored QA strategy for a team or project. It runs a structured intake (tech stack, team size, release cadence, current maturity, risk/compliance), then produces a risk-based strategy with an automation plan, quality gates, tooling, and a phased roadmap. Enforces guardrails against invented inputs…
Produce a tailored, risk-based QA strategy for a team or project. Use when asked to "create a QA strategy", "assess our testing approach", "build a test plan/roadmap", or decide what and how much to automate. Enforces guardrails against vanity coverage targets, big-bang rewrites, and metrics with no gate. First…
Use to analyze a full-stack application (frontend, backend, middleware) and produce a complete test pyramid strategy — what to test in the FE, what in the BE, what at the middleware/seams, and at which level. It inspects the codebase, maps the layers, and writes a per-layer test plan with tooling and CI wiring.
Analyze a full-stack application (frontend, backend, middleware) and design a complete test pyramid — deciding exactly which tests belong in the FE, which in the BE, which at middleware/seams, and at what level (unit, integration/component, contract, E2E). Use when asked to "design a testing strategy for the whole…
Use to audit a UI/E2E test suite for overuse and recommend which tests should move to the API or unit layer. Scans Playwright, WebdriverIO, and Selenium/WebDriver tests in any language (TS/JS, Python, Java, C#, Ruby), finds data-driven repetition and logic tested through the browser, and writes a per-test migration…
Audit an existing UI/E2E test suite for overuse and recommend which tests to move down to the API (or unit) layer. Works across Playwright, WebdriverIO, and Selenium/WebDriver in any language (TS/JS, Python, Java, C#, Ruby). Enforces guardrails — relocate coverage never delete it, name a specific target endpoint/unit…
Use to set up or repair Playwright visual regression tests for a UI. Give it the views or components to cover; it makes screenshots deterministic (disable animations, freeze the clock, seed data, pin fonts/viewport/device-scale), adds a stabilization fixture, chooses masking and thresholds, establishes container-based…