tdd
This skill should be used when implementing any feature or bugfix, before writing implementation code. Also when fixing a bug without a regression test, or when tempted to 'write tests after'.
What this skill does
# Test-Driven Development Write the test first. Watch it fail. Write minimal code to pass. Refactor. ## The Rule No production code without a failing test first. If the test didn't fail, it doesn't prove anything. If you didn't watch the test fail, you don't know if it tests the right thing. **Exceptions:** Throwaway prototypes, generated code, config files. Ask if unsure. ## Red-Green-Refactor ### RED: Write Failing Test One test, one behavior, clear name. Use real code — mocks only when unavoidable. ``` Run the test. Confirm it fails because the feature is missing (not a typo or import error). ``` Test passes immediately? It's testing existing behavior. Fix the test. ### GREEN: Minimal Code Write the simplest code that makes the test pass. Don't add features, don't refactor, don't "improve" beyond what the test requires. ``` Run the test. Confirm it passes. Confirm other tests still pass. ``` ### REFACTOR: Clean Up After green only. Remove duplication, improve names, extract helpers. Keep tests green. Don't add behavior. ### Repeat Next failing test for next behavior. ## Why Order Matters Tests written after code pass immediately. Passing immediately proves nothing — the test might verify the wrong thing, test implementation instead of behavior, or miss edge cases. Test-first forces edge case discovery before implementing. "I'll write tests after" and "tests after achieve the same goals" are the most common rationalizations. They don't. Tests-after answer "what does this do?" Tests-first answer "what should this do?" ## Wrote Code First? Delete it. Start over with a test. - Don't keep it as "reference" - Don't "adapt" it while writing tests - Don't look at it - Delete means delete Implement fresh from tests. Manual testing does not satisfy TDD. ## Bug Fix Pattern 1. Write failing test reproducing the bug 2. Watch it fail (confirms test catches the bug) 3. Fix the bug 4. Watch it pass 5. Revert fix, confirm test fails again (proves the test, not the fix, is what changed) 6. Restore fix ## When Stuck | Problem | Signal | |---------|--------| | Don't know how to test | Write the assertion first. The API you wish existed. | | Test too complicated | Design too complicated. Simplify the interface. | | Must mock everything | Code too coupled. Inject dependencies. | | Test setup is huge | Extract helpers. Still complex? Simplify design. | ## Testing Anti-Patterns - Don't test mock behavior instead of real behavior. If the test only verifies that a mock was called, it proves nothing about the actual code. - Don't add test-only methods to production classes. If you need special access for testing, the design needs work. - Don't mock dependencies you don't understand. If you can't explain what the real dependency does, mocking it means guessing at behavior. ## Stop Signs If you catch yourself doing any of these, stop and restart with TDD: - Writing production code before the test - Test passes on first run (testing existing behavior, not new) - Rationalizing "just this once" or "this is different" - "I already manually tested it" - Keeping pre-written code as "reference"
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.