tdd
The `/tdd` command enforces test-driven development by scaffolding interfaces, generating failing tests before implementation, then writing minimal code to pass those tests while maintaining 80%+ code coverage. Use it when building new features, functions, components, or fixing bugs to ensure code quality through the red-green-refactor cycle.
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/Galaxy-Dawn/claude-scholar/HEAD/commands/tdd.md -o ~/.claude/commands/tdd.mdtdd.md
# TDD Command
This command enforces a test-driven development methodology directly.
## What This Command Does
1. **Scaffold Interfaces** - Define types/interfaces first
2. **Generate Tests First** - Write failing tests (RED)
3. **Implement Minimal Code** - Write just enough to pass (GREEN)
4. **Refactor** - Improve code while keeping tests green (REFACTOR)
5. **Verify Coverage** - Ensure 80%+ test coverage
## When to Use
Use `/tdd` when:
- Implementing new features
- Adding new functions/components
- Fixing bugs (write test that reproduces bug first)
- Refactoring existing code
- Building critical business logic
## How It Works
This command should:
1. **Define interfaces** for inputs/outputs
2. **Write tests that will FAIL** (because code doesn't exist yet)
3. **Run tests** and verify they fail for the right reason
4. **Write minimal implementation** to make tests pass
5. **Run tests** and verify they pass
6. **Refactor** code while keeping tests green
7. **Check coverage** and add more tests if below 80%
## TDD Cycle
```
RED → GREEN → REFACTOR → REPEAT
RED: Write a failing test
GREEN: Write minimal code to pass
REFACTOR: Improve code, keep tests passing
REPEAT: Next feature/scenario
```
## Example Usage
```
User: /tdd I need a function to calculate market liquidity score
Assistant:
# TDD Session: Market Liquidity Score Calculator
## Step 1: Define Interface (SCAFFOLD)
```python
# lib/liquidity.py
from dataclasses import dataclass
from datetime import datetime
from typing import NotRequired
@dataclass
class MarketData:
totalVolume: float
bidAskSpread: float
activeTraders: int
lastTradeTime: datetime
def calculateLiquidityScore(market: MarketData) -> float:
# TODO: Implementation
raise NotImplementedError('Not implemented')
```
## Step 2: Write Failing Test (RED)
```python
# tests/test_liquidity.py
import pytest
from lib.liquidity import calculateLiquidityScore, MarketData
from datetime import datetime
def test_liquid_market_high_score():
"""Test that liquid market gets high score."""
market = MarketData(
totalVolume=100000,
bidAskSpread=0.01,
activeTraders=500,
lastTradeTime=datetime.now()
)
score = calculateLiquidityScore(market)
assert 80 < score <= 100
def test_illiquid_market_low_score():
"""Test that illiquid market gets low score."""
market = MarketData(
totalVolume=100,
bidAskSpread=0.5,
activeTraders=2,
lastTradeTime=datetime.fromtimestamp(datetime.now().timestamp() - 86400) # 1 day ago
)
score = calculateLiquidityScore(market)
assert 0 <= score < 30
def test_zero_volume_edge_case():
"""Test that zero volume returns score of 0."""
market = MarketData(
totalVolume=0,
bidAskSpread=0,
activeTraders=0,
lastTradeTime=datetime.now()
)
score = calculateLiquidityScore(market)
assert score == 0
```
## Step 3: Run Tests - Verify FAIL
```bash
pytest tests/test_liquidity.py -v
FAILED test_liquidity.py::test_liquid_market_high_score
NotImplementedError: Not implemented
1 test failed, 0 passed
```
✅ Tests fail as expected. Ready to implement.
## Step 4: Implement Minimal Code (GREEN)
```python
# lib/liquidity.py
def calculateLiquidityScore(market: MarketData) -> float:
# Handle zero volume edge case
if market.totalVolume == 0:
return 0.0
# Calculate component scores (0-100 scale)
volumeScore = min(market.totalVolume / 1000, 100)
spreadScore = max(100 - (market.bidAskSpread * 1000), 0)
traderScore = min(market.activeTraders / 10, 100)
# Recent activity bonus
hoursSinceLastTrade = (datetime.now().timestamp() - market.lastTradeTime.timestamp()) / 3600
recencyScore = max(100 - (hoursSinceLastTrade * 10), 0)
# Weighted average
score = (
volumeScore * 0.4 +
spreadScore * 0.3 +
traderScore * 0.2 +
recencyScore * 0.1
)
return max(0, min(score, 100)) # Clamp to 0-100
```
## Step 5: Run Tests - Verify PASS
```bash
pytest tests/test_liquidity.py -v
PASSED test_liquidity.py::test_liquid_market_high_score
PASSED test_liquidity.py::test_illiquid_market_low_score
PASSED test_liquidity.py::test_zero_volume_edge_case
3 tests passed
```
✅ All tests passing!
## Step 6: Refactor (IMPROVE)
```python
# lib/liquidity.py - Refactored with constants and better readability
from dataclasses import dataclass
WEIGHTS = {
'VOLUME': 0.4,
'SPREAD': 0.3,
'TRADERS': 0.2,
'RECENCY': 0.1,
}
SCALE_FACTORS = {
'VOLUME': 1000,
'SPREAD': 1000,
'TRADERS': 10,
'RECENCY_PENALTY': 10,
}
def clamp(value: float, min_val: float, max_val: float) -> float:
"""Clamp value between min and max."""
return max(min(value, max_val), min_val)
def calculateLiquidityScore(market: MarketData) -> float:
if market.totalVolume == 0:
return 0.0
volumeScore = min(market.totalVolume / SCALE_FACTORS['VOLUME'], 100)
spreadScore = clamp(100 - (market.bidAskSpread * SCALE_FACTORS['SPREAD']), 0, 100)
traderScore = min(market.activeTraders / SCALE_FACTORS['TRADERS'], 100)
hoursSinceLastTrade = (datetime.now().timestamp() - market.lastTradeTime.timestamp()) / 3600
recencyScore = clamp(100 - (hoursSinceLastTrade * SCALE_FACTORS['RECENCY_PENALTY']), 0, 100)
weightedScore = (
volumeScore * WEIGHTS['VOLUME'] +
spreadScore * WEIGHTS['SPREAD'] +
traderScore * WEIGHTS['TRADERS'] +
recencyScore * WEIGHTS['RECENCY']
)
return clamp(weightedScore, 0, 100)
```
## Step 7: Verify Tests Still Pass
```bash
pytest tests/test_liquidity.py -v
PASSED test_liquidity.py::test_liquid_market_high_score
PASSED test_liquidity.py::test_illiquid_market_low_score
PASSED test_liquidity.py::test_zero_volume_edge_case
3 tests passed
```
✅ Refactoring complete, tests still passing!
## Step 8: Check Coverage
```bash
pytest --cov=lib --cov-rUse when creating or configuring Claude Code agents and their frontmatter.
Run a blocker-first post-experiment workflow: validate evidence, produce strict statistical analysis when possible, and generate a decision-oriented results report only when the analysis bundle is sufficient. Uses results-analysis + results-report as a gated two-stage workflow.
Use only when creating new registrable ML components that require Factory or Registry patterns.
This skill should be used when the user asks to "debug this", "fix this error", "investigate this bug", "troubleshoot this issue", "find the problem", "something is broken", "this isn't working", "why is this failing", or reports errors/exceptions/bugs. Provides systematic debugging workflow and common error patterns.
This skill provides reference guidance for citation verification in academic writing. Use when the user asks about "citation verification best practices", "how to verify references", "preventing fake citations", or needs guidance on citation accuracy. This skill supports ml-paper-writing by providing detailed verification principles and common error patterns.
This skill should be used when the user asks to review a diff or pull request, write review comments, audit code quality, establish review standards, or improve how a team performs code review.
Expert code review specialist. Proactively reviews code for quality, security, and maintainability. Use immediately after writing or modifying code. MUST BE USED for all code changes.
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.