One-click install
npx skills add https://github.com/hiromima/collaborative-canvas --skill tdd-workflow-hiromima
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: TDD Workflow
Source: https://github.com/hiromima/collaborative-canvas/tree/main/.claude/skills/tdd-workflow
Command: npx skills add https://github.com/hiromima/collaborative-canvas --skill tdd-workflow-hiromima

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual testing and inconsistent feature implementation often lead to regressions. This skill codifies a repeatable TDD workflow to ensure features are designed with tests first, promoting robust Rust code.

Core Features & Use Cases

  • Red-Green-Refactor cycle for new features, bug fixes, or test additions.
  • Rust-specific patterns and tooling guidance (cargo test, clippy, fmt) to maintain quality.
  • Deterministic workflow that can be integrated into CI to enforce discipline.

Quick Start

Write a failing test for the new feature and then implement just enough code to pass it, keeping the design simple and clean.

Frequently Asked Questions about TDD Workflow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up a TDD workflow for Rust projects to prevent regressions?

A TDD workflow for Rust enforces a deterministic Red-Green-Refactor cycle using cargo test. It ensures features are designed with tests first, promoting robust and maintainable code.

What is the Red-Green-Refactor cycle for Rust feature development?

The Red-Green-Refactor cycle for Rust involves writing a failing test first, implementing just enough code to pass it, and then refactoring. This deterministic process ensures reliable feature development.

How do I integrate cargo test, clippy, and fmt into a deterministic CI workflow?

You integrate cargo test, clippy, and fmt into CI by enforcing them as quality gates within a deterministic TDD workflow. This ensures discipline and maintains code quality during feature development and bug fixes.

Can I use this TDD workflow for bug fixes and test augmentation in existing Rust code?

Yes, the TDD workflow applies to bug fixes and test augmentation in existing Rust code. It enforces a deterministic process with explicit steps and tooling requirements to maintain reliability.

What's the best way to enforce Rust code quality during refactoring?

The best way to enforce Rust code quality during refactoring is following a deterministic TDD workflow. It integrates cargo test, clippy, and formatting guidance as quality gates to maintain robust, clean design.

Does this testing workflow require specific Rust patterns or dependencies to function?

The testing workflow operates within Miyabi Rust patterns and requires no external dependencies. It relies on standard Rust tooling like cargo test, clippy, and fmt to enforce its quality gates.