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
You'll develop systematic approaches to injectable formulation design, from API selection through sterilization strategy. Claude helps you troubleshoot failed batches by analyzing root causes, recommends regulatory pathways (505(b)(2), ANDA, NDA), and provides science-backed solutions for stability, compatibility, and manufacturability challenges.
This skill helps you systematically assess integration needs across your systems, design architecture patterns that scale with your organization, and identify technical and operational risks before implementation. You'll receive architecture recommendations aligned to your business constraints, clear integration roadmaps, and risk mitigation strategies that reduce deployment surprises. Get structured decision records suitable for architecture review boards and engineering teams.
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.
You can transform raw text into structured, labeled datasets for machine learning, analysis, and research. This skill performs named entity recognition, sentiment classification, part-of-speech tagging, and dependency parsing—generating consistent, validated annotations at scale. Use it to prepare corpora, extract entities, classify documents, or perform linguistic analysis without manual annotation.
This skill helps you systematically analyze service mesh architectures, identify inter-service communication failures, and design optimal routing and security policies. You'll receive step-by-step troubleshooting guidance tailored to your mesh platform (Istio, Linkerd, Consul), configuration validation reports, and architectural recommendations that reduce latency, improve observability, and tighten security posture.
This skill automates the creation of production-ready deployment validation checklists, infrastructure-as-code templates, and incident response runbooks tailored to your ML stack. You get comprehensive pre-deployment checks covering model validation, data pipeline integrity, infrastructure readiness, and monitoring setup—all customized for your specific models and cloud provider. The skill generates executable runbooks that teams can follow during incidents, including rollback procedures, failover strategies, and diagnostic commands.
Build scalable internal developer platform architectures that reduce cognitive load and standardize workflows for your development organization. Document golden paths that guide developers through common tasks like onboarding, deployment, and troubleshooting. Map platform capabilities, integrations, and service topology to align with your engineering scale and technical strategy.
Rapidly analyze firmware logs and diagnose hardware issues that cause device failures, connectivity problems, and performance degradation. You'll identify root causes from stack traces, crash dumps, and sensor data, then generate specific optimization recommendations. This skill transforms raw device logs into actionable debugging plans that reduce time-to-resolution from hours to minutes.