Browse 182,092 skills across 14 categories.
Comprehensive testing workflow: TDD cycle, test suggestions, generation, and property-based testing.
Red-green test-first workflow for behavior with a clear, user-confirmed seam. Use when: user asks for TDD/test-first/red...
Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, w...
Use tests to define behavior, implement minimally, then verify the resulting change.
Implement one acceptance criterion through a verified red, green, and refactor cycle using the project’s test tools.
Use when implementing features or fixing bugs test-first, when user mentions "red-green-refactor", when test discipline...
Test-driven development — crear tests antes del código de producción
The test-first gate. Routed to by /feature (after the spec is approved), /fix, and /refactor before any implementation c...
Test-driven development for substantive feature, bug-fix, and behavior-changing work. Use automatically when implementin...
Use only when the user explicitly asks for TDD, a failing test, or a regression test, OR when the bug has an obvious che...
Test-Driven Development workflow - write tests first, then implementation
Test-Driven Development patterns and red-green-refactor workflow. Auto-triggers when writing tests first, implementing T...
Test-driven development with red-green-refactor and behavior-focused tests. Use when the user explicitly wants test-firs...
测试驱动开发(红绿循环)— 来自 superpowers 体系。本 skill 是桥接层,先写失败测试再写实现,完整纪律见 <SUPERPOWERS_SKILL_ROOT>/tdd/。
Fire when creating or modifying test files. Enforces write-test-first discipline and correct framework selection per pro...
Test-first development. Use when the user or repository explicitly requires TDD.
Test-Driven Development workflow'u için kullan. "/tdd" komutuyla veya "test yaz", "tdd ile yap" ifadesi geçtiğinde devre...
Test-Driven Development (TDD) skill for Red-Green-Refactor cycle. Use when implementing features with tests first, minim...
Test-Driven Development enforcement skill - write tests first, always
Test-driven development workflow
Implement a feature test-first with strict red-green-refactor
Invoked helper skill for strict red-green-refactor implementation, usually delegated from /execute or bug-fix work shape...
Use when the user wants test-driven development, asks to write tests first, or requests red-green-refactor discipline fo...
AI DevKit · Test-driven development — write a failing test before writing production code. Use when implementing new fun...
Use before writing any implementation code — enforces RED-GREEN-REFACTOR cycle.
Enforce test-driven development workflow. Scaffold interfaces → write FAILING tests → implement minimal code → refactor....
Test-driven development. Use when the user explicitly wants test-first work, red-green-refactor, or asks to use TDD.
TDD フローで機能を実装する。 ロジック・ユーティリティ・リポジトリ層など、テストで品質を担保すべき実装に使用する。 UI のみの変更には /implement を使うこと。
Red/Green TDD protocol — write a failing test first, implement the minimum to pass, then refactor. Use for any new featu...
Run one RED→GREEN cycle (test-author then implementer) for a single named task, outside of a full /implement batch. Use...
Strict test-driven development for behavior changes. Requires verified RED before production code, minimal GREEN, and re...
Test-Driven Development methodology for writing tests before code. Use when developing new features, fixing bugs with te...
TDD methodology guidance for writing tests and implementing code. Use when writing tests, implementing features, or refa...
ShatterLess Technical Design Document — the repo's engineering law. Read for any code change. Obey it over generic Godot...
Implement features using Test-Driven Development (TDD) with Red-Green-Refactor cycle.
测试驱动开发。当用户想以测试先行构建功能或修复 bug、提到 "red-green-refactor"，或想要集成测试时使用。
Interactive guide for Detroit School TDD. Use whenever the user asks to write or modify code - new feature, bug fix, deb...
Use when implementing features or fixing bugs — write the test first, watch it fail, write minimal code to pass. Ensures...
Test-driven development for ASP.NET Core and EF Core with xUnit. Use when building a feature or fixing a bug test-first,...
This skill should be used when writing unit tests, TDD test cases, test coverage analysis, or test-driven development fo...
Test-driven development with red-green-refactor loop. Use when: user wants to build features or fix bugs using TDD, ment...
Start TDD workflow for a feature
Guide Test-Driven Development workflow for FastLED. Use when implementing new features or fixing bugs with a test-first...
Enforces Test-Driven Development (Red-Green-Refactor) for rigorous code quality.
Canon TDD for humans and AI agents. Use for production code changes by writing tests first, proving RED, implementing mi...
Test-Driven Development with Arcanean philosophy - write tests first, fail intentionally, implement minimally, refactor...
Workflow Phase 6 — TDD coordinator. Decides the scenario recipe and the implementation contract in main context, writes...
Use when writing production code that needs tests - new features, bug fixes, refactoring. Enforces RED-GREEN-REFACTOR cy...
Use when writing production code that needs tests -- new features, bug fixes, refactoring. Enforces RED-GREEN-REFACTOR b...
Detroit-style BDD開発フロー。シナリオテストをメインに据え、振る舞い駆動でテストを設計する。
Test-driven development — write failing test first, then implement (red-green-refactor)
Practice test-driven development for new features and bug fixes.
Runs test-driven development with a red-green-refactor loop. Use when the user wants to build features or fix bugs using...
This skill should be used when the user wants to implement features or fix bugs using test-driven development. Enforces...
Red-green-refactor TDD loop for a single behavior. Writes a failing test first, runs it to confirm red, implements minim...
Discipline skill — TDD red-green-refactor cycle. Use when implementing any feature or bugfix, before writing implementat...
Use when implementing any feature or bugfix, before writing implementation code. Each Scenario in Specs becomes a test c...
Use when implementing or fixing production code with tests.
Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, menti...
Test-driven development: red-green-refactor, integration tests. Use to build features or fix bugs test-first.
Use when implementing any feature, bug fix or behaviour change, before writing production code, or when the user mention...
Develop features or fix bugs test-first using red-green-refactor. Use when the user asks for TDD, test-first work, or a...
a workflow for practicing Test-Driven Development (TDD)
RED-GREEN-REFACTOR cycle enforcement for test-driven development.
Use for explicit TDD or when Roblox logic has a cheap deterministic Luau regression target that can fail before the fix.
Use when the user wants test-driven development, asks to write tests first, or mentions TDD.
Strict test-driven development workflow. Use when implementing any feature, bug fix, or code change. Follows RED → GREEN...
Apply risk-based test-driven development to bugs, domain logic, state transitions, parsers, contracts, migrations, and b...
Implement behavior through a focused red-green-refactor loop. Triggers on "tdd", "测试驱动开发".
Test-driven development - write failing test first, then minimal code. Use before implementing any feature or bugfix.
Run a red-green-refactor TDD workflow — generate failing tests first, implement to green, then check coverage gaps. Usag...
Use when TDD is requested or a bug has a cheap, direct regression target.
테스트 주도 개발(TDD) 강제 워크플로우. Red-Green-Refactor 사이클을 따르며, 테스트를 먼저 작성한 후 구현합니다. Use when the user wants test-first developmen...
Run red-green-refactor in vertical slices, emphasizing behavior-first tests and harness quality gates.
Test-driven development workflows for Kagenti - CI, HyperShift, and Kind
GitHub IssueからTDD（Test-Driven Development）サイクルを実行し、テストと実装を段階的に作成。アプリケーションコードの実装にTDDを適用する際に使用。
Test-Driven Development enforcer. Red→Green→Refactor cycle with no production code without a failing test first. Use for...
Use when implementing features or bug fixes test-first.
Write the failing test before the code that satisfies it, for new behaviour and for bug fixes, and stop when the test pa...
The red → green loop for any stack: seams, what a good test is, and the anti-patterns to refuse. Use when building featu...
Apply the incremental red-green-refactor method when implementing behavior test-first. Use when building a behavior slic...
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor"...
Strict Test-Driven Development workflow (Red-Green-Refactor) with configurable human-in-the-loop checkpoints. Invoke whe...
Test-driven development: what a good test is, where its seam goes, the anti-patterns, and the rules of the red-green loo...
Test-Driven Development patterns for GSD
Test-driven development with a red-green-clean loop, running mix credo on the whole project at the end of every vertical...
Test-Driven Development discipline — red/green/refactor cycles for designing code from tests outward.
TDD 오케스트레이터 — 대상 클래스(FQCN)의 템플릿 문서·테스트 클래스를 생성하고 tdd-plan→tdd-rgb 워크플로우를 안내. "TDD 시작", "TDD로 새 클래스 만들자", "테스트 주도로 시작", "...
Use when implementing any feature, bugfix, refactor, or behavior change, before writing implementation code. Enforce tes...
Test-Driven Development methodology
PROACTIVELY enforce Test-Driven Development when implementing features or fixing bugs. Ensures tests are written BEFORE...
Guides test-driven development — decompose a feature or bug fix into behaviors, then cycle through Red (failing test) →...
Use when asked to develop a fix or feature test-first, plan a multi-step TDD build, or work red-to-green in slices. Writ...
Use when developing a fix or feature test-first, plan a TDD build, or work red-to-green in slices. Not for hardening: us...
Use test-driven development to build behavior or fix bugs test-first, at agreed public seams, with independent expectati...
Test-driven development — the red → green loop and the rules that make its tests worth keeping. Use when the user wants...
Test-first at pre-agreed seams — one test, one implementation, tracer-bullet red/green; independent expected values; sub...