tdd-workflow
# Test-Driven Development (TDD) Best Practices
What this skill does
# Test-Driven Development (TDD) Best Practices This skill guides rigorous test-first development following the Red-Green-Refactor cycle. ## When to Use Activate when: - Implementing new features - Fixing bugs - Refactoring existing code - Making any code changes ## TDD Core Principles ### Red-Green-Refactor Cycle 1. **Red** - Write tests FIRST before implementation 2. **Green** - Write minimal code to pass tests 3. **Refactor** - Clean up while keeping tests green ### Test Quality Standards **Write Tests First:** - Tests should be minimal and focused on single behaviors - Tests are documentation - they clearly show expected behavior - If you can't easily test it, the design is wrong - refactor for testability **Test Organization:** - Use table-driven tests for multiple inputs/scenarios in Go - Test file naming: `*_test.go` for unit tests, `e2e_test.go` for integration - Always test error cases and edge conditions **Test Types:** - **Unit tests** - Mock external dependencies (network, filesystem, time) - **Integration tests** - Validate real component interactions - **End-to-end tests** - Cover critical user workflows ### Assertion Libraries **Go Testing:** - Use `testify/require` for assertions that should stop test execution - Use `testify/assert` for assertions that should continue test execution ## Design for Testability ✅ **Testable patterns:** - Dependency injection - Interface-based abstractions - Pure functions - Isolated side effects ❌ **Hard to test (redesign):** - Global state - Hidden dependencies - Tight coupling - Side effects mixed with logic ## TDD Workflow 1. Write failing test(s) embodying acceptance criteria 2. Run tests - verify they fail for the right reason 3. Implement minimal code to make tests pass 4. Run tests - verify they all pass 5. Refactor for quality while keeping tests green 6. Repeat ## Quality Gates Before considering work "done": - [ ] All tests pass locally and in CI - [ ] Coverage ≥ 90% lines/branches - [ ] Error cases are tested - [ ] Edge conditions are tested - [ ] Tests document expected behavior clearly
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.