আপনার এজেন্টের জন্য উপযুক্ত সক্ষমতা খুঁজে নিন।
Implement Advent of Code solutions using Test-Driven Development. Generates test cases from puzzle examples, writes failing tests first, implements solutions incrementally, and iterates until all tests pass. Use when solving AoC puzzles, implementing solutions with TDD, or when user mentions test-driven development or writing tests.
Executes Unity tests and checks coverage. MUST use proactively after implementing features, fixing bugs, or modifying Domain/Application layer code. Also triggers on "test", "テスト".
Follow TDD cycle (RED-GREEN-REFACTOR) writing failing tests first, covering edge cases and error states, using explicit fixtures, and maintaining fast test suites with coverage gates. Use this skill when writing unit tests, integration tests, contract tests, or any test code in test files. Applies to test directories, spec files, test runners (Jest, Vitest, pytest), mocking strategies, regression prevention, and ensuring statement/branch coverage thresholds that block merges when dropped.
Run, debug, and structure tests for this Go project (unit + integration), including generation prerequisites. Use when changing domain logic, repositories, HTTP handlers, or migrations.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Develop, test, and maintain the Paracle framework codebase. Use when implementing features, fixing bugs, writing tests, or refactoring framework code.
Write the test first, watch it fail, write minimal code to pass
Generates test files following TDD patterns with Given-When-Then structure. Use when creating tests for domain logic, API endpoints, or repositories.
Playwrightによるブラウザ自動化スキル。Webテスト、フォーム入力、スクリーンショット、レスポンシブ検証に対応。
Executes implementation tasks using Test-Driven Development, prevents code duplication through anti-duplication checks, and maintains quality through continuous testing. Use when implementing features from tasks.md, during the /implement phase, or when the user requests TDD-based implementation. (project)
Write focused tests for core user flows and critical paths using Pest framework, with minimal tests during development and strategic coverage at completion points. Use this skill when creating or editing test files in tests/Feature/ or tests/Unit/ directories, when writing Pest tests with descriptive names, when testing critical user workflows and business logic, when mocking external dependencies, when implementing fast unit tests, when testing behavior rather than implementation details, or when deciding what needs test coverage at feature completion.
VST3 plugin testing patterns and practices. Use when writing tests, debugging test failures, adding new test cases, when tests don't appear after changes, or when working with DSP algorithms that need verification. Covers build verification, DSP testing strategies, artifact detection, spectral analysis, Catch2 patterns, and VST3 validation.
This skill should be used when the user mentions "flaky tests", "race condition", "timing issues", "wait for", "test sometimes fails", or when tests have inconsistent pass/fail behavior. Replaces arbitrary timeouts with condition polling.
Implement minimal code to make failing tests pass (GREEN phase of TDD). Write just enough code to pass tests, no more. Use after red-phase when tests are failing.
Generate comprehensive unit tests for iOS RxSwift project files (ViewModels, UseCases, Services). Creates complete test files with nested mocks, RxTest patterns, session error handling, and memory leak tests. Use when "generate unit tests", "write tests for", "create unit tests", "add tests for", or analyzing Swift files in PayooMerchant project.
Helper for creating timestamped feature directories. Use when creating new feature specs.
Implement new features following BDD/TDD workflow. Use when building new features, implementing user stories, or adding functionality.
Run tests with Jest, Vitest, or Playwright, fix failing tests, and generate missing test coverage. Use when user says "run tests", "test this", "fix failing tests", "write tests", or when tests need to be executed or created.
