Find the perfect skill

Testing

Automated assistance for test retry configuration, providing best practices and production-ready code for test frameworks.

Testing

Check implemented work against executable spec.yml by validating acceptance criteria coverage and test evidence.

Testing

Independently audits an Angular spec file against project migration guidelines, checking quality and testing rules.

Testing

Legal quality gate for claims management, reviewing facts, evidence, norms from a defendant's perspective, with risk and deadline assessment.

Testing

Expert-level JMeter skill for creating test plans, distributed testing, and analyzing performance results.

Testing

Audit user flows for friction and pain points. Use when reviewing a feature's UX, identifying drop-off risks, or getting actionable improvement recommendations based on industry best practices (Nielsen heuristics, Baymard benchmarks).

Testing

Launch a sub-agent that performs end-to-end verification of the application. It checks builds, linting, type errors, runs unit tests, performs manual UI testing via Playwright, and verifies integration points. Ideal for QA verification before release or after changes to ensure app stability and correctness.

Testing

A convenient wrapper over Flutter golden tests. Automates multi-platform and multi-device golden testing: manages device configurations, themes, localization, fonts, and CI environments.

Testing

Test-Driven Development workflow principles covering the RED-GREEN-REFACTOR cycle. Write tests first, code second for robust software.

Testing

End-to-end parity testing for gochickpeas engine/gql changes using real LDBC data.

Testing

Verifies test quality, coverage, and correctness by ensuring BDD scenarios map 1:1 to tests and that testing rules (≥80% coverage, error handling) are followed. Used during the review phase to confirm the implementation meets acceptance criteria through automated test validation.

Testing

This skill provides best practices for writing and understanding tests in the SonarQube web application. It covers testing philosophy, file naming conventions (unit, integration, snapshots), three testing layers (integration, unit, snapshots), and smart mocks usage. It also includes critical rules like preferring `findBy` over `waitFor` and `toBeInTheDocument` over `toBeVisible`.