আপনার এজেন্টের জন্য উপযুক্ত সক্ষমতা খুঁজে নিন।
Update test binaries (test_stream_generator.rs) to match the latest architecture from main.rs, ensuring they use the same caching, rendering, and pagination patterns. Use when test binaries need to be synchronized with production code.
This skill should be used when the user asks about "Minitest", "Rails testing", "test/", "fixtures", "ActiveSupport::TestCase", "ActionDispatch::IntegrationTest", "system tests", "functional tests", "assert", "assert_equal", "assert_difference", "test_helper", "rails test", or needs guidance on testing Rails applications with the default Minitest framework.
Use when about to claim work is complete, fixed, passing, or done - requires running verification commands and confirming output before making any success claims. Evidence before assertions.
Analyze test failures and suggest fixes for Feature Swarm verification. Use when tests fail during the verification phase to diagnose root cause and determine if automatic recovery is possible.
Subagent-driven task execution with TDD workflow. Dispatches tester subagent (writes failing tests) then implementer subagent (makes tests pass), with batch review.
Plan and design tests with a UX-first approach. Use this skill when: (1) Adding new features that need test coverage, (2) Fixing bugs and need to prevent regression, (3) Reviewing or improving existing test coverage, (4) The test suite failed to catch a production issue. Forces a conversation about what user experience we're protecting before writing any test code.
Writing Playwright E2E tests following project patterns and fixtures. Use when creating new E2E tests, debugging test failures, or setting up test helpers and page objects.
Combines Ralph Wiggum loops with structured feature plans for automated TDD-driven development. Creates phase-based plans with quality gates, then executes each phase using Ralph loops with Beads for persistent state tracking. Includes E2E testing with Playwright agents. Use for automated overnight development, complex feature implementation, or when you want AI to iterate until tests pass.
Docker-based testing with testcontainers. Use when running tests with real databases.
Define comprehensive testing strategies, write tests with proper naming conventions, organize tests by type, and implement mocking strategies. Use when creating tests, refactoring test suites, or improving test coverage.
Optimizes Playwright E2E tests by removing waitForTimeout anti-patterns, implementing smart waits, and enabling test sharding for parallel execution. Use when tests timeout, CI execution exceeds limits, or test reliability issues occur.
Runs tests and explains results. Use when user asks to run tests, check tests, or verify code works.
How tests should be structured, named, and prioritized in this codebase.
Create scenario files for testing migrated Output SDK workflows. Use to set up test inputs in the scenarios/ subfolder.
Validate at every layer data passes through to make bugs impossible
