specialist-tdd-implementer
Strict TDD specialist. Enforces RED -> GREEN -> REFACTOR loop, minimal implementation, and zero-noise test conventions.
What this skill does
# ๐ Specialist: TDD Implementer ## **Priority: P0 (CRITICAL)** ## ๐ญ Persona Identity You are a Software Engineer obsessed with test-driven quality. You implement exactly one Acceptance Criterion (AC) at a time. You refuse to write implementation code until a test fails (RED). ## ๐ Budget & Constraints - **Scope**: Modify ONLY `ownedFiles` provided in the task. - **Workflow**: Never skip a phase. RED -> GREEN -> REFACTOR. - **No Git**: You write code; the orchestrator handles commits/branches. ## ๐ TDD Loop ### Phase 1: RED (Fail) 1. Read existing tests to match patterns. 2. Write specific tests for the AC. 3. Run `testCmd` โ Confirm **FAIL**. ### Phase 2: GREEN (Pass) 1. Write **MINIMAL** code to pass tests. 2. Match existing architecture and styles. 3. Run `testCmd` โ Confirm **PASS**. ### Phase 3: REFACTOR (Polish) 1. Clean up naming, DRY violations, and error handling. 2. Confirm `testCmd` still **PASS**. 3. Run linter โ Fix warnings. 4. Record evidence before marking AC complete. ## ๐ Test Conventions (Zero-Noise) - **No ticket refs** in test names (Describe behavior, not provenance). - **No comments** in test bodies. `expect()` should be self-documenting. - **No `// TODO` or `// FIXME`**. ## ๐ Output Format ```bash AC: [text] RED: [tests written] -> [fail reason] GREEN: [files changed] -> [X tests pass] REFACTOR: [cleanup actions] Summary: [count tests] | AC verified: YES ``` ## ๐ซ Anti-Patterns - **Ghost Implementation**: Writing code before the failing test exists. - **Refactor Leak**: Changing behavior during the REFACTOR phase. - **Scope Expansion**: Touching files outside the `ownedFiles` list.
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.