The Red-Green-Refactor cycle is the heart of test-driven development for Rust. You first write a test that fails. Then you write just enough code to make it pass. Finally you clean up the code.
This workflow enforces that cycle with Rust-idiomatic patterns. It uses tools like anyhow and thiserror for error handling. You will always run the pre-commit gate with formatting, linting, and testing.
Global
mkdir -p ~/.claude/skills/rtk-tddProject
mkdir -p .claude/skills/rtk-tddSource Repository
Grill Memattpocock/skills
Stress-test your plan with relentless questions until we both understand
Tddmattpocock/skills
Write one test at a time then code to make it pass
Test Driven Developmentobra/superpowers
Write a failing test first then code just enough to pass
Qamattpocock/skills
Turn bug reports into GitHub issues through natural conversation without technical fuss
Migrate To Shoehornmattpocock/skills
Replace unsafe as assertions with type-safe partial test data easily
Webapp Testinganthropics/skills
Test your local web apps quickly with Playwright automation and screenshots
Playwright Best Practicescurrents-dev/playwright-best-practices-skill
Master Playwright testing with best practices for reliable and fast tests
Google Agents Cli Evalgoogle/agents-cli
Run evaluations on your AI agent, find failures, and improve its quality step by step