tdd

Test-first development is implemented by enforcing a strict RED → GREEN → REFACTOR cycle, requiring a failing test before any code implementation, followed by minimal code to pass, and then refactoring without breaking tests.

The RED → GREEN → REFACTOR cycle is a TDD practice where you write a failing unit test, implement minimal code to make it pass, and then refactor the implementation while ensuring the tests continue to pass.

Test-driven development works with testing-heavy stacks like React with Jest or Vitest, Python with pytest, Rails with RSpec, and Go with the testing package, ensuring minimal code implementation and maintainable refactoring.

The best way to start TDD for integration tests is to begin the cycle by writing a failing test for your feature, ensuring you only write implementation code after the test fails.

You should avoid strict test-driven development when working in environments without testing frameworks, as this practice requires a failing test before implementation and relies on test-heavy stacks like Jest, pytest, RSpec, or Go testing.

Yes, the tdd Skill implements Test-Driven Development practices that ensure you can refactor code without breaking tests by maintaining the RED → GREEN → REFACTOR cycle throughout your coding workflow.