write-scenario
Write BDD scenarios in Gherkin format (Given/When/Then) in pure business language. Use when creating acceptance tests, user story scenarios, or stakeholder-readable specifications.
আপনার এজেন্টের জন্য উপযুক্ত সক্ষমতা খুঁজে নিন।
Write BDD scenarios in Gherkin format (Given/When/Then) in pure business language. Use when creating acceptance tests, user story scenarios, or stakeholder-readable specifications.
Table-driven tests, mocking strategies, and comprehensive testing patterns. Use when writing tests.
Write failing test first, then minimal code to pass (RED-GREEN-REFACTOR cycle). WHEN: MUST use when implementing new features, fixing bugs, refactoring. Invoke with "/test-driven-development" or "use TDD". Always write test BEFORE implementation code. WHEN NOT: Throwaway prototypes, generated code, configuration files, debugging root cause (use systematic-debugging first).
REST integration testing patterns with JUnit 5, Mockito, RestAssured. Use when writing integration tests that mock external dependencies, use Testcontainers/H2 for databases, and test endpoints with raw JSON bodies.
Use when writing or reviewing tests - covers test philosophy, condition-based waiting, mocking strategy, and test isolation
Generates failing tests that reproduce reported bugs in FanHub. Use when a bug report comes in and you need to create a test that demonstrates the issue before fixing it. Follows FanHub's testing patterns and data integrity rules.
Maintain and extend prompt-injection defenses. Use when adding new user-input surfaces, changing prompt templates, or when a new injection pattern is observed; run the security regression suite and add a minimal new test case.
Write strategic tests following best practices including minimal tests during development, focus on core user flows only, defer edge case testing until later, test behavior not implementation, use clear descriptive test names, mock external dependencies, and maintain fast execution times. Use this skill when deciding which tests to write during feature development, determining appropriate test coverage levels, writing tests for critical user flows, choosing between unit and integration tests, implementing test mocking strategies, or balancing test coverage with development velocity. This skill applies when working on test files and determining testing strategy for features.
Use when implementing any feature, bugfix, or code change. Invoke BEFORE writing implementation code. The Iron Law - no production code without a failing test first.
Run end-to-end browser tests using Playwright MCP. Use when testing web applications, validating user journeys, checking UI interactions, or when the user mentions E2E tests, browser automation, or Playwright.
Guide for testing password generator functionality. Use when creating or running unit tests for password generation, validation, or strength checking.
Playwright E2E testing setup and configuration. Use when setting up end-to-end tests.
Run integration tests validating cross-component requirements and system behavior. Executes BDD scenarios, API tests, and end-to-end tests. Use to validate integrated system or as pre-deployment quality gate.
Executa testes end-to-end em aplicacoes React locais (Vite) usando Playwright. Permite validar formularios, capturar logs e inspecionar UI.
Use when automating browsers, testing pages, or taking screenshots
Browser automation using Vercel's agent-browser CLI. Use when you need to interact with web pages, fill forms, take screenshots, or scrape data. Alternative to Playwright MCP - uses Bash commands with ref-based element selection. Triggers on "browse website", "fill form", "click button", "take screenshot", "scrape page", "web automation".
Standard procedure for running pytest tests in the airline-discount-ml project with proper Python environment configuration.
Use when creating new skills, editing existing skills, or verifying skills work before deployment - applies TDD to process documentation by testing with subagents before writing, iterating until bulletproof against rationalization
Tests web applications with Playwright including E2E tests, locators, assertions, and visual testing. Use when writing end-to-end tests, testing across browsers, automating user flows, or debugging test failures. Triggers: "playwright", "e2e tests", "end-to-end testing", "cross-browser testing", "automated tests", "ui tests", "visual testing".
Optimize Playwright E2E tests by removing anti-patterns, implementing smart waits, enabling test sharding, and improving reliability.