Test Driven Development
Write tests first, then code. Enforces TDD with spec, task, or ad-hoc modes.
What You Can Do
You can enforce test-first development across multiple entry points: parse acceptance criteria from spec files and generate test stubs, extract requirements from task files and design test scenarios, or write tests from ad-hoc descriptions. Claude guides you through the complete TDD cycle—RED (failing tests), GREEN (minimal implementation), and REFACTOR (clean code)—while leveraging your existing repository patterns and providing proptest guidance for property-based testing.
Features
spec files with Given/When/Then criteria, task files with requirements, or free-form descriptions
Example Output
From Spec Mode:
/// Spec: authentication.spec.md — Criterion #1
/// Given a user with valid credentials
/// When login is called
/// Then the session token is returned
#[test]
fn authentication_criterion_1_valid_login() {
todo!("Implement: the session token is returned");
}
From Task Mode:
Test scenarios extracted from .code-task.md: normal path (valid input → success), edge case (empty input → validation error), error condition (DB timeout → retry with backoff)
From Description Mode: Prompt: "Add file upload with size validation." → Generated tests: file under limit passes, oversized file rejected, zero-byte file handled
What's Included
- SKILL.md: Complete TDD workflow instruction with three input mode handlers
- Test stub templates: Rust test stubs with Given/When/Then comment structure
- Pattern discovery framework: Guides to identify repository and async patterns in your codebase
- Proptest checklist: Property-based testing strategy guide with shrinking examples
- TDD cycle verification: Compilation and test run commands to confirm RED and GREEN states
Who It's For
- QA engineers — Design comprehensive test scenarios before implementation
- Backend engineers — Enforce test-first Rust development with async/concurrent code
- Test automation engineers — Generate test stubs from specs and requirements in bulk
- DevOps engineers — Write infrastructure tests following TDD discipline
- Team leads — Ensure consistent TDD adoption across codebases
Best For
- Converting acceptance criteria (Given/When/Then) into failing test stubs
- Designing test scenarios from task descriptions with edge cases and error paths
- Property-based testing strategy for exhaustive input validation
- Refactoring existing code with tests written first
- Onboarding new team members into TDD workflows and repository patterns
You might also like
Rapidly analyze production incidents by correlating observability signals—logs, metrics, traces, and events—to identify the true root cause instead of symptoms. You'll reconstruct incident timelines, quantify impact scope, and generate both immediate remediation steps and long-term prevention measures.
Claude analyzes your code diffs and generates standardized commit messages that follow the Conventional Commits specification. The skill automatically determines the correct commit type, scope, and description based on the changes you've made, ensuring your messages are parseable by automation tools while remaining human-readable for code reviewers.
Transform schema and data changes into production-ready migration packages that protect data integrity and minimize downtime. You can handle column additions, renames, type conversions, and backfills using proven patterns like expand-contract and shadow tables. The skill generates explicit rollback scripts, validation checklists, and phased execution plans that keep applications stable throughout the migration.
You can submit your Solidity smart contracts for comprehensive security analysis, vulnerability detection, and gas optimization recommendations. Claude reviews your code against known attack vectors, design patterns, and best practices—identifying reentrancy risks, overflow/underflow issues, access control flaws, and inefficient operations. You receive actionable fix recommendations with explanations of the security implications and gas savings potential.
You can design end-to-end NGS pipelines tailored to your experiment type (WGS, WES, RNA-seq, targeted), troubleshoot pipeline failures by analyzing QC metrics and logs, and optimize performance by fine-tuning parameters and identifying bottlenecks. This skill handles the full workflow from raw sequencing data quality assessment through variant interpretation and annotation.
This skill guides you through designing Kalman filters for your specific state estimation and sensor fusion problems. You'll learn to diagnose filter divergence, tune covariance matrices (Q and R), and validate observability—turning mathematical theory into production-ready filters. The skill provides step-by-step workflows, diagnostic tools, and practical templates for common applications like GPS/IMU fusion, SLAM, and aircraft navigation.
You can rapidly identify root causes of training failures, data pipeline breakdowns, and model serving issues by analyzing logs, metrics, and infrastructure state. Claude examines your system events, resource utilization patterns, and error traces to pinpoint performance bottlenecks, data quality problems, and deployment misconfigurations—then recommends targeted remediation steps.
You can accelerate your entire antenna design workflow—from initial concept to optimized specifications—by leveraging Claude's knowledge of electromagnetic theory, antenna types, and design trade-offs. Claude helps you parameterize designs, identify optimal configurations for your frequency band and application, and prepare detailed briefs for simulation and manufacturing. You'll generate design reviews, impedance-matching solutions, and validation checklists without context-switching to multiple tools.