Use after sumo-qa-deciding-approach picks tdd-scaffold, regression-first, or coverage-first-then-refactor — e.g.
Use when the user asks to plan QA for a story, ticket, or piece of work before coding starts. Identifies named risks anchored in the change shape, then proposes a smallest useful…
Use after sumo-qa-deciding-approach picks strengthen-test-coverage. Mutation-testing follow-up, raise-coverage tasks, killing weak assertions.
Use when: Mau implement fitur/bugfix - Test-Driven Development SEBELUM production code
SurrealKit schema sync, rollout migrations, seeding, and declarative testing for SurrealDB apps. Part of the surreal-skills collection.
Jest-Tests für Storefront-JS-Plugins in Shopware 6: Test-Setup (composer storefront:unit), PluginManager/DOM mocken, Plugin-Methoden testen.
Create, test, and develop swamp extensions — models, vaults, drivers, datastores, and reports. Covers Zod schemas, smoke testing, manifest.yaml, and the quality scorecard.
Playwright E2E testing standards from authoritative docs/explanation/software-engineering/automation-testing/tools/playwright/ documentation
SWI-Prolog-specific tooling, standards, and idioms. Use when working with SWI-Prolog code. Emphasizes relational thinking, steadfastness, DCGs, constraints, and mandatory testing…
Expert guidance on Swift best practices, patterns, and implementation. Use when developers mention: (1) Swift configuration or environment variables, (2) swift-log or logging…
Use when reviewing Swift 5.5+ code containing `await`, `actor`, `Task { }`, `@MainActor`, `@unchecked Sendable`, cancellable timer/deadline handles, or long-lived `for await`…
Guide build, run, manifest, dependency, plugin, resource, Metal-packaging, and Release-versus-Debug work in existing Swift Package Manager repositories.
Guide Swift Testing, XCTest holdouts, xctestplan handoff conditions, async test design, semantic accessibility-test boundaries, test-fixture organization, and package…
Compatibility workflow surface for broad or legacy Swift Package Manager execution requests. Use when older references still point at swift-package-workflow and route the request…
中文优先：用于Swift协议依赖注入测试相关任务，帮助识别、设计、实现或验证对应工作流。English keywords: Protocol-based dependency injection for testable Swift code — mock file system, network, and external APIs using…
Writes and migrates tests using the Swift Testing framework with @Test, @Suite, #expect, #require, confirmation, parameterized tests, test tags, traits, withKnownIssue, XCTest UI…
Reviews Swift Testing code for proper use of #expect/#require, parameterized tests, async testing, and organization.
Expert guidance for Swift Testing: test structure, #expect/#require macros, traits and tags, parameterized tests, test plans, parallel execution, async waiting patterns, and…
Writes, reviews, and improves Swift Testing code using modern APIs and best practices. Use when reading, writing, or reviewing projects that use Swift Testing.
Bidirectional integration validation where two repositories validate each other before release. TRIGGERS - symmetric dogfooding, bidirectional testing, cross-repo validation,…
Monitior technology trends (GitHub, etc.), contextualize them against the user's project, and autonomously verify them through installation and testing.
Match tutorial script blocks to e2e pytest functions and add missing tests
Create comprehensive integration tests for syncable entities in Twenty. Use when writing integration tests for metadata entities, covering validator exceptions, input…
Set up Syncfusion Blazor components — project creation, NuGet packages, service registration, script loading, bUnit testing, and localization & globalization configuration
Use to verify or set up the local Syngen development environment — creates a `.venv` if missing, installs `requirements.txt`, probes runtime imports, and confirms pytest…
Patterns for generating synthetic data for ML training, testing, and privacy. Covers LLM-based generation, tabular synthesis, and quality validation.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase framework (root cause investigation, pattern analysis, hypothesis — from…
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase framework (root cause investigation, pattern analysis, hypothesis — from…
Browser automation via 70 tabz MCP tools. Use when taking screenshots, filling forms, debugging network requests, testing responsive design, or using text-to-speech notifications.
Deep analysis debugging mode for complex issues. Activates methodical investigation protocol with evidence gathering, hypothesis testing, and rigorous verification.
Summarizes, explains, and answers questions about Dave Farley's talk 'Vibe Coding — Is this really the best we can do?', including key arguments, frameworks, and recommendations.
Use when the user asks about Ian Thomas's talk \"AI Native Engineering\" (Meta / Reality Labs / Horizon Experiences) — including questions about Meta's AI4P (AI For Productivity)…
Use to decide where to spend a finite testing budget — prioritize by risk (likelihood × impact), hammering data loss, auth, the core flow, and money first, and right-size the…
Generates structured handoff reports after completing development tasks. Scans changes across 8 dimensions (navigation, documentation, rules, workflows, testing, risks, code…
Implements exactly one planned task from .ai/tasks/ using test-first development, then pauses for human review. Invoke with /task-implementor.
Debug, test, or stabilize Tauri 2 apps, including Rust compile/runtime errors, frontend API mocks, permissions failures, dev/build mismatches, WebDriver, CI checks, logs,…
Create and run tests for The Dreamer's Cave. Use for pytest (backend), vitest (frontend), fixtures, mocking, and coverage.
引导测试驱动开发（TDD）流程：红-绿-重构。 使用时机：TDD 开发、撰写测试先行的代码、学习 TDD。 关键字：TDD, test-driven, red-green-refactor, 测试驱动, 红绿重构。
Test-Driven Development and Behavior-Driven Development as design tools, not just verification. Use when shipping changes that "worked locally" but break in CI, when refactors are…
Fix bugs using red-green-refactor — reproduce the bug as a failing test first, then fix it. Use when fixing bugs to ensure they never regress.
CI-driven TDD workflow - commit, local checks, push, wait for CI, iterate on failures
Guide la pratique du Test-Driven Development pas à pas. Se déclenche avec "TDD", "test driven", "red green refactor", "écrire le test d'abord", "BDD", "behaviour driven" — from…
Use during implementation to enforce TDD - reminds test-first, validates the Red-Green-Refactor cycle, integrates with superpowers:test-driven-development.
Usar siempre antes de implementar código. Ciclo rojo-verde-refactor estricto. Activar cuando el usuario quiera hacer test first, escribir test antes de implementar, seguir el…
Red-green-refactor TDD-cycle for game development. Use when coding game features for Breakout.
Role-aware TDD. NO production code without a failing test first. Tests live alongside the role's typed artifact.
Strict TDD for Domain and Application layers in Clean Architecture TypeScript. Red-Green-Refactor with Vitest. Mocks ports, never hits a database.
Configure TDD enforcement via pre-commit hooks and CI coverage gates. Use when setting up test-first development workflow, adding coverage gates, or enforcing TDD practices.
Red-Green-Refactor TDD methodology with mandatory failing tests, minimal implementation, quality refactoring, and 80% coverage gating.
Erzwingt Test-zuerst-Disziplin und Edge-Case-Abdeckung. Trigger: TDD/Test-Strategie.
Use when implementing new features. Enforces TDD workflow - write tests FIRST, then implementation. Ensures AAA pattern, proper coverage, and quality test design.
Use when you need to prove test results with a signed receipt from yana-rt evidence run — not just text.
TDD-driven evidence workflow for generating authoritative failure/fix proof in PRs.
Runs red/green/refactor loops against acceptance criteria and TEST_STRATEGY. Use when practicing TDD or when tests should lead implementation. Emits TDD_SESSION.
Use when the user has a test-case-tree output and wants runnable Go tests plus stub implementation following Test-Driven Development.
Guide Test-Driven Development workflow for FastLED. Use when implementing new features or fixing bugs with a test-first approach.
Red-green-refactor scaffold for building new features with TDD. Write failing tests first, then implement to pass. Use when building new features test-first.
Use when the user asks to reproduce a bug with a failing test then fix it in a test-driven loop, "TDD fix", "write a red test then make it green", or wants an autonomous red-green…
TDD Green Phase expert. Activate when: - Test is written and failing, need to make it pass - User mentions "make test pass", "green phase", "minimal implementation" - Writing…
Comprehensive Test Driven Development guide for engineering subagents with multi-framework support, coverage analysis, and intelligent test generation — from isihigameKoudai/utils