Spring Boot Unit 테스트 작성. JUnit5+Mockito, domain 패키지별 구조, entity는 common/entity, service는 {domain}/service. 네이밍 test_{대상}_{시나리오}_{예상결과}. Entity 직접 반환 금지 (DTO만). Fail Fast - 모든 필드/타입/예외 엄격 검증, 예상외 결과는 실패 처리.
Use when testing Nango syncs locally - runs dry-run command with proper parameters for integration testing without affecting production data
Tests Phylax Credible Layer assertions with CredibleTest, fuzzing, and backtesting. Use when writing or reviewing assertion tests.
Ruby 3.4+ best practices with RSpec 4, RuboCop 2, Bundler, and Rails
End-to-end verification for the site-visit (Step 7) flow. Use when you need to reproduce or validate that the system reaches the site-visit prompt/options and can proceed to confirmation, either via deterministic backend-only traces (manual_ux_scenario_I/H) or via browser UI checks (Playwright/MCP).
テストコードを作成する際に使用します。ユニットテスト、統合テスト、エンドツーエンドテストなど、あらゆる種類のテストコードを生成するためにこのスキルを利用してください。
从需求文档（文字、图片、PDF、DOCX）生成结构化的功能测试用例。遵循 15 字段规范，输出 Excel 文件，支持正向/异常场景、边界值、安全性测试。
Ensure backend build readiness for Espresso Engineered. Use when backend code/config changes are made or when a feature/task is wrapping up to suggest running `npm run build:backend` (and tests only if requested).
This is the guideline to follow when writing unit tests. Refer to this content when writing unit tests.
Standards de tests exhaustifs pour les bounded contexts DDD (Domain, Application, Integration). À utiliser lors de l'écriture de tests backend, tests unitaires, tests d'intégration, ou quand l'utilisateur mentionne "test", "TDD", "coverage", "unit test", "integration test", "test domain", "test handler".
Playwright MCPを使用してブラウザ操作を記録し、E2Eテストコードを自動生成します。テスト駆動開発やリグレッションテストの作成に使用します。
Complete browser automation with Playwright. Auto-detects dev servers, writes clean test scripts to /tmp. Test pages, fill forms, take screenshots, check responsive design, validate UX, test login flows, check links, automate any browser task. Use when user wants to test websites, automate browser interactions, validate web functionality, or perform any browser-based testing.
Strategies for exploring and testing tightly-coupled BitZero code. Use when code seems untestable, has singleton dependencies, or you need to understand complex game logic before writing tests.
Generates test cases, creates mocks, identifies edge cases, analyzes coverage gaps, and supports property-based, mutation, and contract testing. Use when writing tests, improving coverage, detecting flaky tests, or implementing advanced testing strategies. Triggers: "write tests", "add tests", "test coverage", "property-based testing", "mutation testing", "contract testing", "flaky tests", "test generation".
Manually verify code changes work as expected. Use after implementing a feature or bug fix, after making visual/UI changes, after modifying API endpoints, or before considering work "done". All functional changes must be manually verified, even small changes. This is in addition to automated tests.
Designs unit, integration and end-to-end testing strategies and implements tests for code changes.
Implement comprehensive testing strategies with pytest, fixtures, mocking, and test-driven development. Use when writing Python tests, setting up test suites, or implementing testing best practices.
TDD Red Phase expert. Activate when: - Starting new feature development with TDD - User mentions "write test first", "failing test", "red phase" - Need to design test cases before implementation - Questions about test structure, assertions, test naming Auto-triggers on: test design, test-first development, TDD start
Use when writing pytest tests, creating fixtures, mocking dependencies, or testing async code - provides patterns that verify actual behavior with proper fixtures and parametrization; prevents testing mocks instead of code (plugin:python@dot-claude)
Unified QA verification for both web UI and CLI work. Use when tasks require QA evidence, test execution, or verification checklists.
Adds visual capabilities to the agent using Playwright MCP with Script Execution support.
