progress-tracker-scenario-gifs
Generate small animated GIFs for each Playwright BDD scenario and surface them in-app as usage instructions.
Generate small animated GIFs for each Playwright BDD scenario and surface them in-app as usage instructions.
Guide for implementing features using Test-Driven Development (TDD) methodology. Use when: (1) User requests to implement a feature using TDD, (2) User asks to write tests first before implementation, (3) User mentions Red-Green-Refactor cycle, (4) Starting a new feature that requires systematic testing. This skill provides step-by-step TDD workflows, concrete test patterns, and best practices for writing tests before implementation in TypeScript/React projects using Vitest.
Expert guidance for Python testing with pytest framework. Use when (1) writing unit tests or integration tests, (2) setting up test fixtures for setup/teardown, (3) parametrizing tests with multiple inputs, (4) using markers (skip, xfail, custom), (5) mocking/patching with monkeypatch or pytest-mock, (6) configuring pytest (pytest.ini, pyproject.toml, conftest.py), (7) running tests with coverage, (8) debugging test failures, or (9) testing async code, FastAPI, Django, or Flask apps.
Fix a specific failing test case in this repo by identifying the root cause, adding a minimal repro under tests/, explaining the cause, applying a targeted fix, re-running the test, and reporting any new failures uncovered.
Establishes patterns for creating test data in Entity Framework Core integration tests for multi-tenant applications. Use when writing integration tests that involve tenant isolation, foreign key relationships, or database context management with Testcontainers.
Interact with and test local web apps using Playwright.
Review test quality before PR - semantic analysis of test design for agentic code. Checks test type appropriateness (unit vs VCR vs evals), ADR-0011/0012 compliance, and Constitution alignment. Run as Level 2 review after epic implementation.
Add Espresso and AndroidX Test dependencies to Android project
Guide for writing Cucumber feature files and step definitions in this Playwright-Cucumber project. Use this when asked to create new tests, scenarios, or step definitions.
Use when about to claim work is complete, fixed, or passing. Invoke BEFORE committing, creating PRs, or making any success claims. The Iron Law - evidence before assertions, always.
从验收标准创建检查清单,编排executor→validator循环并带重试逻辑。当子协调器开始实现或收到验证失败时使用。
Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure first