coverage-loop
Iteratively improve test coverage until target is reached. Use when: improve coverage, test coverage, coverage target, baldrick coverage. Triggers on: coverage, test coverage, coverage loop.
Iteratively improve test coverage until target is reached. Use when: improve coverage, test coverage, coverage target, baldrick coverage. Triggers on: coverage, test coverage, coverage loop.
Generates complete, runnable RSpec tests for Rails models, services, controllers, and background jobs following project conventions. Use when new code is created without corresponding tests, when refactoring existing code, or when explicitly asked to add test coverage.
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