Rtk Tdd

This enforces strict test-driven development for Rust projects, meaning you literally cannot write production code without a failing test first. It walks you through red-green-refactor cycles with concrete patterns: arrange-act-assert structure, cfg(test) modules in the same file, and idiomatic assertions like is_err() for error paths. The pre-commit gate (fmt, clippy, test) is non-negotiable. It's opinionated about when NOT to use pure TDD too, like skipping Command::new() execution tests in favor of testing parsers. If you're serious about TDD discipline in Rust and want guardrails that prevent shortcuts, this keeps you honest. The three laws are actually enforced, not suggested.