Discover tools testing skills, compare source repositories and read the instructions for each workflow.
Comprehensive guide for writing and running Terraform tests. Use when creating test files (.tftest.hcl), writing test scenarios with run blocks, validating infrastructure behavior with assertions, mocking provi...
Create minimal POC to validate technical hypotheses. Reuse/call existing code, or write new if needed. Report success or propose alternatives on failure.
Orchestrates full feature implementation using Standard, TDD, or BDD workflows with automated quality gates.
Run tests, check builds, and validate the application works correctly. Use after making changes.
Write Jest tests for React components in this Gatsby project. Use this skill when creating new tests or improving test coverage. Handles Gatsby-specific mocking and Testing Library patterns.
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
Complete testing infrastructure and patterns for the monorepo. Use this skill when writing tests, setting up test configuration, troubleshooting test failures, or working with the CI pipeline. Covers vitest con...
Go Constraints. Errors, Context, testify/require, SQLBoiler, Nx Support.
Use when user says "write tests first", "TDD", "test-driven", "tests before implementation", or when implementing a feature where verification is critical. Creates scratchpad, writes failing tests, then iterate...
Use when reviewing test suites, after test runs pass, or when user asks about test quality
Use when tests are failing, test quality issues were identified, or user wants to fix/improve specific tests
Enforces project E2E testing conventions using Playwright with custom fixtures, Page Object Model, and authentication contexts.
Enforces project React component testing conventions using Testing Library with proper rendering, user interactions, and accessibility testing.
Enforces project integration testing conventions for facades, server actions, and database operations using Testcontainers with real PostgreSQL.
Enforces project test infrastructure conventions for factories, MSW handlers, mock data, Page Objects, and shared test utilities.
Enforces project shared testing conventions for test structure, file naming, description patterns, assertions, and anti-patterns. This base skill is loaded by all test-type specialists.
Enforces project unit testing conventions for pure functions, validation schemas, and utility modules using Vitest with proper isolation and mocking.
Debug and fix complex scripts by isolating side effects, extracting core logic into a controlled environment, validating behavior there, then reintegrating with minimal changes. Use this when scripts lack unit...
Browser automation with Playwright. Use when user asks to automate web interactions, scrape websites, test web applications, fill web forms, take screenshots, or interact with dynamic web content.
Create or update Playwright end-to-end tests for the Product Agents frontend in this repo, especially for settings validation, conversation artifact visibility, research plan approval/rejection, and clarifying-...
Browser automation toolkit using Playwright. Supports interacting with web applications, form filling, capturing screenshots, viewing browser logs, and running automated tests. Use when automating browser tasks...
Use when implementing any feature or bugfix, before writing implementation code. Each Scenario in Specs becomes a test case following RED → GREEN → REFACTOR cycle.
Use after implementation is complete to verify that code matches specifications. Ensures every Requirement is implemented and every Scenario has a corresponding test.
Use after specs are validated to create TDD implementation plan. Each Scenario in Specs becomes a test case in the plan. Combines bite-sized TDD tasks with spec references.
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.