tdd-enforcement
Red-Green-Refactor TDD methodology with mandatory failing tests, minimal implementation, quality refactoring, and 80% coverage gating.
What this skill does
# TDD Enforcement ## Overview Strict test-driven development enforcement adapted from the Everything Claude Code methodology. Mandates the Red-Green-Refactor cycle with evidence-based verification at each phase. ## TDD Process ### 1. RED Phase - Write Failing Tests - Write tests that define expected behavior - Tests MUST fail (exit code 1) - Use CI=true or --run flag, never watch mode - Apply timeout guards (60s) to prevent hanging - Record exit code as evidence ### 2. GREEN Phase - Minimal Implementation - Write the minimal code to make tests pass - Do NOT add features not covered by tests - Do NOT optimize prematurely - Tests MUST pass (exit code 0) - Record exit code as evidence ### 3. REFACTOR Phase - Quality Improvement - Apply SOLID principles and clean code patterns - Improve naming, reduce coupling - Remove duplication - Run tests after EACH refactoring step - Tests MUST remain passing (exit code 0) ### 4. Coverage Gate - Measure coverage: statements, branches, functions, lines - Minimum 80% overall coverage required - Iterate: write additional tests for gaps until threshold met - Maximum 3 convergence iterations ## Rules - Never skip the RED phase - Never accept GREEN without exit code 0 - Never use watch mode in CI - Always record evidence (exit codes, coverage numbers) - Enforce 80% coverage threshold ## When to Use - All code implementation tasks - Feature development - Bug fixes (write regression test first) ## Agents Used - `tdd-guide` (primary consumer) - `code-reviewer` (validates test quality)
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.