tdd
Test-first variant of implement: understand the desired behavior, write a failing test, make it pass, then simplify.
What this skill does
# Test-Driven Development Use this for behavioral changes where a failing test can describe the desired outcome before implementation. ## Workflow ### 1. Understand - Read the request, task, issue tracker item, plan, spec, and relevant code as available. - Identify the desired behavior, existing contracts, failure paths, and verification. - If a spec exists, note its invariants, decisions, and testing strategy. - Ask before writing tests when missing information would materially change behavior, scope, safety, contracts, data shape, or verification. ### 2. Red - Write the smallest failing test that proves the desired behavior or reproduces the bug. - Run it and confirm it fails for the expected reason. ### 3. Green - Write the minimum implementation needed to pass the test. - Preserve existing contracts unless the task explicitly changes them. - Add failure-path tests where they matter. ### 4. Refine - Simplify code and tests while they stay green. - Run the full relevant test suite before finishing. - Report the failing-then-passing test and final verification. ## Rules - Do not write implementation code before a failing test for the behavior. - If an assumption is low-risk, make it explicit and keep moving. - Tests describe behavior, not implementation details. - Prefer real boundaries over mocks when practical. - Skip TDD for documentation, formatting, or non-behavioral scaffolding work.
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.