tdd-red-green-refactor
Enforce TDD workflow (red → green → refactor). Use for any code change that is testable.
Enforce TDD workflow (red → green → refactor). Use for any code change that is testable.
Replace arbitrary timeouts with condition polling for reliable async tests
Skill para ejecutar y gestionar tests. Incluye patrones de testing, fixtures comunes, y estrategias de debugging de tests fallidos.
Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure first
Write comprehensive tests following project conventions (tiers, patterns, anti-patterns). Use when writing tests, improving test coverage, fixing failing tests, or reviewing test quality.
Orchestrates test execution for the Nomos monorepo following TESTING_GUIDE.md standards. Use this when running tests, debugging test failures, validating coverage, or executing verification checklists from AGENTS.md files.
Enforces test-driven development (TDD) following Kent Beck's methodology. MANDATORY micro-cycle approach - write ONE test, watch it fail, write minimal implementation, refactor, then NEXT test. NEVER write all tests first or implementation first. Use for ANY code writing task.
Generates valid and invalid JSON fixtures for CommandDTO and DecisionDTO based on current contract schemas.
Provides ASSERT/ASSUME macro pattern, .sby file template, and f_past_valid usage. Triggers when adding formal verification or writing assertions.
Creates and optimizes MSW (Mock Service Worker) handlers for Playwright E2E tests, implementing handler caching, fixture management, and AI Gateway mocking patterns. Use when mock setup is slow or test data needs centralization.
TDD(テスト駆動開発)のワークフローをガイドする。 Red → Green → Refactor のサイクルに従って開発を進める。 「TDDで実装」「テスト駆動」などのキーワードで自動適用。
Standard procedure for verifying UI updates and bug fixes using the browser subagent.
技術検証(Tech Spike)ワークフロー。ライブラリ選定やアーキテクチャ判断の前に最小限の実験コードで技術的妥当性を検証。 使用タイミング: (1) 複数の技術選択肢がある場合(ライブラリA vs B) (2) 新しいライブラリ・技術の学習コストが高い場合 (3) パフォーマンス・互換性の懸念がある場合 (4) 既存システムとの統合リスクがある場合 (5) 「技術検証」「ライブラリ調査」「スパイク」リクエスト 使用しない場合: 技術スタック確定済み、既知のパターン、単純なCRUD操作
Unit testing patterns for .NET applications using EF Core In-Memory Provider, AAA structure, test data helpers, and TDD workflows. Use when writing unit tests for Application Services, domain logic, or data access.
Validates API contracts for correctness, compatibility, and compliance. Tests REST APIs against OpenAPI/Swagger specifications. Detects breaking changes between versions, validates runtime responses against schemas, and ensures backward compatibility before deployment.
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.