test-driven-development
Enforces TDD discipline - write tests first, then implement
What this skill does
# Test-Driven Development Skill
Auto-activates to enforce TDD discipline during implementation.
## When to Use
Activate when:
- User starts implementing feature
- User invokes `/tdd:start`
- User mentions "test" or "TDD"
- Integrated from Stage B workflow
## The Iron Law of TDD
**RED → GREEN → REFACTOR**
Never write production code without a failing test first.
## Process
### RED: Write Failing Test
```
1. Write test describing desired behavior
2. Run test
3. MUST fail (if passes, test is bad)
4. Confirm failure message makes sense
```
**Block implementation until test fails.**
### GREEN: Make It Pass
```
1. Write MINIMUM code to pass
2. No refactoring yet
3. No "future-proofing"
4. Quick and dirty is OK
5. Run test - must pass
```
**Block refactoring until test passes.**
### REFACTOR: Improve Code
```
1. Now improve code quality
2. Extract methods
3. Rename for clarity
4. Optimize if needed
5. Run tests after EACH change
6. All tests must stay green
```
**Block next feature until refactoring done.**
## Enforcement
**If user tries to implement before test:**
```
⛔ STOP: No Test Written Yet
TDD requires test-first development.
Please write a failing test before implementing.
Example:
test('feature does X', () => {
expect(feature()).toBe(expected);
});
```
**If user tries to refactor during GREEN:**
```
⛔ STOP: Test Not Passing Yet
Refactoring comes AFTER test passes.
Current phase: GREEN (make it pass)
Next phase: REFACTOR (improve code)
Focus on making the test pass first.
```
## Integration with workflow plugin
When called from Stage B:
- Test cases already generated
- Use those as starting RED tests
- Cycle through each test case
- Mark complete when all pass
This skill enforces discipline so TDD actually happens.
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.