flow-convert-activities-to-steps
Convert Flow SDK activities.ts to Output SDK steps.ts. Use when migrating activity functions to step definitions with typed parameters.
Find the perfect capability for your agent.
Convert Flow SDK activities.ts to Output SDK steps.ts. Use when migrating activity functions to step definitions with typed parameters.
Test mocking strategies with Vitest. Use when mocking dependencies in tests.
Guide for writing frontend tests including unit tests with Vitest, component tests, and visual/E2E tests with Playwright MCP. Use when creating tests for hooks, components, or pages.
Scaffold API mocking infrastructure using Mountebank and Testcontainers for reliable integration testing.
Runs and writes tests for the Moonbeam parachain including Rust unit tests, TypeScript integration tests, smoke tests, and multi-chain tests. Use when verifying changes, writing tests for new features, debugging test failures, running specific test suites, or creating test fixtures.
Systematically fixes all failing tests in a project by running test commands repeatedly until 100% pass with zero warnings. Use when tests are failing, validation is not passing, or when asked to fix test suites. Works with any testing framework (Jest, Pytest, Go test, etc.) and ensures complete test compliance without skipping or modifying tests.
Compile multiple run findings into a single report with cross-run diffs and stable conclusions.
Open and analyze Playwright HTML test reports. Use when user asks to see test results, check test report, view test output, or analyze test failures.
Create and maintain runnable examples under examples/ for onboarding and smoke testing. Use when adding/changing public APIs, when you need a quick “does it work end-to-end?” script, or when updating examples/README.md to match the current eo-processor API.
Gather examples for the acceptance test; use when we are about to start development of a new feature
Ensure quality through testing, documentation, and security audits. Use when asked to add tests, improve test coverage, update documentation, write docs, security audit, review safety rules, or verify protected paths are not touched.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Guide for refactoring and improving existing test code, step definitions, and page objects. Use this when asked to improve code quality, maintainability, or performance.
Use when about to claim work is complete, fixed, or passing. Requires running verification commands and confirming output before making any success claims. Evidence before assertions, always.
Create minimal POC to validate technical hypotheses. Reuse/call existing code, or write new if needed. Report success or propose alternatives on failure.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Guide for writing pytest unit tests for the airline-discount-ml project. Use when asked to create, run, or debug Python unit tests for models, data access, or agents.
Generates src/App.vue root component with unit test. Creates both App.vue and App.spec.ts files.