559 个 · 按相关度排序
Create a technical design document before implementation by answering questions about the problem, scope, architecture, risks, and delivery plan. The skill adjusts sections to project size and covers security, testing, monitoring, and recovery where relevant.
中文简介正在准备中。当前显示英语简介。
Write Jest unit tests for component behavior and user interactions. Includes reusable test data builders, mock replacements for dependencies, and test-driven development, where a failing test guides implementation before the code is cleaned up.
中文简介正在准备中。当前显示英语简介。
Build features or fix bugs through test-driven development: write one failing test, add enough code to pass, then refactor. Focuses on observable behavior through public interfaces, helping tests remain useful when internal code changes.
中文简介正在准备中。当前显示英语简介。
Work with AI as a coding partner, choosing who writes code and who guides the work. Supports role switching, test generation, ongoing code review, debugging, and step-by-step explanations for learning.
中文简介正在准备中。当前显示英语简介。
Organize software development from requirements and architecture through testing, review, and deployment. Use specialized agent roles, shared memory, and test-driven development, where tests are written before code, to coordinate work across the project.
中文简介正在准备中。当前显示英语简介。
Master TDD orchestrator specializing in red-green-refactor discipline, multi-agent workflow coordination, and comprehensive test-driven development practices. Enforces TDD best practices across teams with AI-assisted testing and modern frameworks. Use PROACTIVELY for TDD implementation and governance.
中文简介正在准备中。当前显示原文说明。
Test-driven development for substantive feature, bug-fix, and behavior-changing work. Use automatically when implementing features, fixing bugs, or changing behavior (red → green → refactor). Also use when the user mentions TDD, /tdd, /TDD, or red-green-refactor. Do not use for documentation-only, formatting-only, exact generated-mirror, or provenance-only changes.
中文简介正在准备中。当前显示原文说明。
Use when implementing features or writing code. TDD enforcement is opt-in via --tdd / MEOWKIT_TDD=1. Provides code patterns, skill loading, and coding standards.
中文简介正在准备中。当前显示原文说明。
git diff 기준 변경 파일을 자동 탐지해 Composed Method 지향 Tidying Process를 TDD 사이클 없이 독립 실행. 완료 후 선택 기법 제안. "변경 파일 정리", "tidying만", "방금 바꾼 코드 정돈", "tidy first", "/tdd-tidy" 요청 시 사용. 단, 다른 클래스로 로직을 옮기는 구조 변경은 /system-wide-refactoring이 적합. /tdd-tidy [commit-ref]로 호출.
中文简介正在准备中。当前显示原文说明。
TDD 세션이 끝난 뒤 "어디서 시간·토큰이 많이 들었나"를 단계(Skill)·에이전트별로 집계하고 병목과 model/effort 조정안을 보고한다. 세션 transcript를 읽는 사후 분석이며 코드를 바꾸지 않는다. "이번 TDD 세션 병목 분석", "토큰 어디에 썼어", "어느 단계가 느렸어", "모델 조정 제안", "/tdd-profile" 요청 시 사용.
中文简介正在准备中。当前显示原文说明。
テストは存在するがアサーションが実質何も検証しておらず、実装が壊れても落ちない（常に PASS する）構造を diff-time で検出する。Check 1 missing assertion（テスト本体にアサーションが無い）、Check 2 tautological assertion（定数同士・入力自身・mock の戻り値自身を assert し SUT に依存しない）、Check 3 nonexistent expected literal（assertDontSee / assertNotContains 等の期待文字列が対象ファイルに実在しない）、Check 4 stale expected value（同一 diff で対象の出力が変わったのに期待値が据え置き）、Check 5 unscoped expectation（汎用的な属性・クラスを応答全体に対して assert し対象要素にスコープされていない）、Check 6 swallowed failure（例外の握り潰しや到達しない位置のアサーションで判定が成立しない）、の 6 Check を対象とする report-only。テストの有無は test-existence、未テスト経路の量は coverage-gap、非決定性は flaky-test、命名は test-naming、JS/TS の un-awaited resolves / rejects は vitest-mock-isolation、tdd-ledger artifact ベースの RED/GREEN 検証は plangate-tdd-evidence、.only / .skip / xit / @ts-ignore と空の catch は heuristic-review.mjs の決定論検出器へ委譲する
中文简介正在准备中。当前显示原文说明。
テスト駆動開発（TDD）の0spec-1red-2green-3blueサイクルを実施します。対話でテスト対象を絞り込み、コンテキスト消費を最小化します。
中文简介正在准备中。当前显示原文说明。
features.json を読み込み、pending な機能を1件ずつ tdd-guide エージェント（内部で tdd-cycle を使用）で実装するスキル。 Context anxiety（トークン上限接近による焦り）と Context rot（情報劣化）を防ぐため、 機能単位のループ・状態管理・implementation-notes.md への記録を担う。 builder エージェントが実装フェーズを開始するときは必ずこのスキルを呼ぶ。
中文简介正在准备中。当前显示原文说明。
Master TDD orchestrator specializing in red-green-refactor discipline, multi-agent workflow coordination, and comprehensive test-driven development practices. Enforces TDD best practices across teams with AI-assisted testing and modern frameworks. Use PROACTIVELY for TDD implementation and governance.
中文简介正在准备中。当前显示原文说明。
通过先写测试，为Quarkus 3.x LTS服务添加功能、修复故障或重构，验证API、事件及异步处理，并检查测试覆盖率。
为Kotlin代码先编写测试，使用Kotest和MockK验证行为与依赖交互，涵盖异步测试、生成输入的属性测试及Kover覆盖率检查。
根据变更规模，为功能开发、缺陷修复等工作选择调研、规划、测试和审查阶段。这套相关技能共用的流程包含计划审批和提交前确认。
将尚未实现的新功能从调研、规划推进到测试先行的开发、审查和提交。各阶段交由对应的ECC智能体负责，并在计划批准和提交前暂停确认。
从测试开始实现 Laravel 功能，使用 PHPUnit 或 Pest 验证模型、API、身份认证和权限，模拟外部服务，并通过覆盖率了解测试执行了哪些代码。
按先写测试的流程开发Go代码，支持多组用例、HTTP响应验证、性能基准测试、自动生成输入的模糊测试，以及查看测试执行范围的覆盖率检查。
通过先写测试再实现功能的流程，验证Django模型、页面和API，涵盖测试数据生成、外部服务模拟及代码覆盖率，帮助确认功能行为与测试范围。
Automatically repair source code against a failing test while preserving the test itself. Set a spending limit and attempt count, then receive verification results and usage costs based on rerunning the test command.
中文简介正在准备中。当前显示英语简介。
Develop features through a test-first workflow using mocks, or stand-ins for dependencies. Write a failing behavior test, implement the minimum code, refactor, and record observed results from final target and regression tests.
中文简介正在准备中。当前显示英语简介。
Follow Conductor's development plans using test-driven development: write a failing test, implement the change, then improve the code. Manage phase verification, progress updates, and focused git commits as tasks move toward completion.
中文简介正在准备中。当前显示英语简介。