Skill UI

This comprehensive guide assists developers in adopting Test-Driven Development (TDD) practices. It covers generating unit tests for various languages (Python, JS, Java), analyzing test coverage gaps across multiple frameworks (Jest, Pytest, JUnit), and guiding the iterative Red-Green-Refactor workflow. Use this guide when generating stubs, improving test coverage, or adhering to spec-first development methodologies.

Comprehensive TDD workflow guidance covering the Red/Green/Refactor rhythm, Arrange-Act-Assert test structure, Jest/Vitest, pytest, and Go patterns, coverage rules, mocking advice, and anti-pattern warnings to keep teams disciplined across languages.

This expert skill acts as a master orchestrator for Test-Driven Development (TDD), guiding users through the complete Red-Green-Refactor cycle. It specializes in coordinating complex, multi-agent testing workflows, integrating modern practices like BDD, ATDD, and AI-assisted test generation. Use it to ensure robust, highly maintainable, and thoroughly tested software systems across diverse technological stacks and complex development pipelines.

A detailed, multi-phase workflow that strictly enforces the Test-Driven Development (TDD) discipline using the Red-Green-Refactor cycle. This guide covers the entire software development lifecycle, from test specification and architecture design to minimal implementation, rigorous refactoring, and comprehensive integration testing. It mandates high code and test coverage (e.g., 80% line coverage) to ensure robust, maintainable, and high-quality production code.

This skill guides developers through the 'Green' phase of Test-Driven Development (TDD). It focuses on implementing the absolute minimum code required to satisfy failing tests, allowing the system to pass tests quickly. It is ideal for initial scaffolding and proving functionality, delaying complex design decisions until the refactoring phase.

Guides developers through strict test-driven development: write failing tests first, iterate red-green-refactor, and keep tests passing before refactoring to ensure reliable features.

A comprehensive guide to writing reliable and maintainable tests for Kotlin projects. This skill covers modern testing patterns using Kotest for various spec styles (FunSpec, BehaviorSpec), MockK for dependency mocking, and enforces TDD principles (RED/GREEN/REFACTOR). Learn how to implement unit tests, property-based testing, and ensure high code coverage with Kover.

A comprehensive guide to writing robust and maintainable tests in Rust. It covers various advanced testing patterns, including Unit, Integration, Async, and Property-Based testing. Learn how to apply the TDD (Test-Driven Development) cycle (RED-GREEN-REFACTOR) to enhance code reliability and ensure high code coverage.

Summarizes the Test-Driven Development workflow with RED/GREEN/REFACTOR phases, the AAA pattern, prioritization cues, anti-patterns, and AI-augmented agent roles to guide implementation.

A software development methodology where tests are written before implementation code. It follows the red-green-refactor loop to ensure code quality and reliability. Ideal for bug fixing, new feature implementation, and maintaining existing functionality. Helps prove code correctness and reduces technical debt.

This guide implements the Red-Green-Refactor cycle, the core methodology of Test-Driven Development (TDD). It teaches developers to first write a failing test (RED), then implement the minimum required code to make the test pass (GREEN), and finally improve the structure and clarity of the code without changing its behavior (REFACTOR). Use this guide when mastering TDD, ensuring robust unit test coverage, or following best practices for writing resilient software.

Test-Driven Development (TDD) is a development methodology that emphasizes writing failing tests first, followed by writing minimal code to pass them (Red -> Green), and finally refactoring the code (Refactor). This approach ensures that code is always verified against its intended public behavior, making the system robust, maintainable, and resilient to internal changes. It teaches developers to focus on 'what' the system does, rather than 'how' it does it.