@hustle-together/api-dev-tools 3.6.5 → 3.10.0

package/commands/hustle-api-continue.md

@@ -0,0 +1,158 @@
+# API Continue Command
+
+Resume an interrupted API development workflow from where it left off.
+
+## Usage
+```
+/hustle-api-continue [endpoint-name]
+```
+
+## Arguments
+- `endpoint-name` (optional): The endpoint to resume. If not provided, will show available interrupted workflows.
+
+## What This Command Does
+
+1. **Check for Interrupted Workflows**
+   - Read `.claude/api-dev-state.json`
+   - Find endpoints with `status: "in_progress"`
+   - Identify the last completed phase
+
+2. **Restore Context**
+   - Load all interview decisions
+   - Load research cache from `.claude/research/{endpoint}/`
+   - Inject phase-specific context
+
+3. **Resume Workflow**
+   - Set `active_endpoint` to the resumed endpoint
+   - Continue from the interrupted phase
+   - Re-inject any needed context
+
+## Example
+
+```bash
+# List interrupted workflows
+/hustle-api-continue
+
+# Resume specific workflow
+/hustle-api-continue brandfetch
+```
+
+## Output
+
+When resuming, you'll see:
+- Summary of completed phases
+- Current phase to resume
+- Key interview decisions
+- Research cache status
+
+---
+
+## Implementation
+
+When user runs `/hustle-api-continue [endpoint]`:
+
+### Step 1: Load State and Find Workflow
+
+```
+READ .claude/api-dev-state.json
+IF endpoint argument provided:
+  FIND endpoint in state.endpoints
+ELSE:
+  LIST all endpoints with status == "in_progress"
+  ASK user which to resume
+```
+
+### Step 2: Validate Workflow Can Resume
+
+```
+CHECK endpoint exists
+CHECK endpoint.status == "in_progress"
+FIND last completed phase
+IDENTIFY next phase to run
+```
+
+### Step 3: Restore Context
+
+```
+SET state.active_endpoint = endpoint
+LOAD .claude/research/{endpoint}/CURRENT.md if exists
+LOAD .claude/research/{endpoint}/interview.json if exists
+INJECT context into Claude's memory:
+  - Endpoint name and purpose
+  - Completed phases summary
+  - Interview decisions
+  - Research findings
+  - Current phase requirements
+```
+
+### Step 4: Resume
+
+```
+SHOW resume summary to user:
+  ┌────────────────────────────────────────────────────────┐
+  │ RESUMING: {endpoint}                                   │
+  │                                                        │
+  │ Completed: Phase 1-5                                   │
+  │ Resuming at: Phase 6 (Schema Creation)                 │
+  │                                                        │
+  │ Interview Decisions Loaded:                            │
+  │   • format: json                                       │
+  │   • authentication: api_key                            │
+  │   • rate_limiting: yes                                 │
+  │                                                        │
+  │ Research Cache:                                        │
+  │   • .claude/research/{endpoint}/CURRENT.md (fresh)     │
+  │                                                        │
+  │ Continue with Phase 6? [Y/n]                           │
+  └────────────────────────────────────────────────────────┘
+
+IF user confirms:
+  TRIGGER next phase workflow
+```
+
+### Step 5: Clear Interruption State
+
+```
+UPDATE state.endpoints[endpoint].session:
+  interrupted_at = null
+  interrupted_phase = null
+  recovery_checkpoint = null
+SAVE state
+```
+
+---
+
+## Phase Order for Reference
+
+1. Disambiguation
+2. Scope
+3. Initial Research
+4. Interview
+5. Deep Research
+6. Schema Creation
+7. Environment Check
+8. TDD Red
+9. TDD Green
+10. Verify
+11. TDD Refactor
+12. Documentation
+13. Completion
+
+---
+
+## Error Handling
+
+| Error | Resolution |
+|-------|------------|
+| No interrupted workflows | Show message: "No interrupted workflows found. Use /hustle-api-create to start a new one." |
+| Endpoint not found | Show available endpoints and ask user to choose |
+| Research cache stale | Warn user and offer to re-run research phases |
+| State file missing | Error: "No state file found. Use /hustle-api-create to start a new workflow." |
+
+---
+
+## Related Commands
+
+- `/hustle-api-create [endpoint]` - Start new workflow
+- `/hustle-api-status [endpoint]` - Check workflow progress
+- `/hustle-api-sessions --list` - View saved session logs

package/commands/{api-create.md → hustle-api-create.md}

@@ -1,6 +1,6 @@
 # API Create - Comprehensive API Development Workflow v3.0
 
-**Usage:** `/api-create [endpoint-name]`
+**Usage:** `/hustle-api-create [endpoint-name]`
 
 **Purpose:** Orchestrates the complete API development workflow using interview-driven, research-first, test-first methodology with continuous verification loops.
 
@@ -98,10 +98,10 @@ Both conditions must be true for the flag to be set.
 ## Complete Phase Flow
 
 ```
-/api-create [endpoint]
+/hustle-api-create [endpoint]
         │
         ▼
-┌─ PHASE 0: DISAMBIGUATION ─────────────────────────────────┐
+┌─ PHASE 1: DISAMBIGUATION ─────────────────────────────────┐
 │ Search 3-5 variations of the term:                        │
 │   • "[term]"                                              │
 │   • "[term] API"                                          │
@@ -128,7 +128,7 @@ Both conditions must be true for the flag to be set.
 └───────────────────────────────────────────────────────────┘
         │ Clear
         ▼
-┌─ PHASE 1: SCOPE CONFIRMATION ─────────────────────────────┐
+┌─ PHASE 2: SCOPE ──────────────────────────────────────────┐
 │                                                           │
 │ Present your understanding, then:                         │
 │                                                           │
@@ -153,7 +153,7 @@ Both conditions must be true for the flag to be set.
 └───────────────────────────────────────────────────────────┘
         │
         ▼
-┌─ PHASE 2: INITIAL RESEARCH ───────────────────────────────┐
+┌─ PHASE 3: INITIAL RESEARCH ───────────────────────────────┐
 │                                                           │
 │ Execute 2-3 initial searches:                             │
 │   • Context7: "[library/api name]"                        │
@@ -183,7 +183,7 @@ Both conditions must be true for the flag to be set.
 └───────────────────────────────────────────────────────────┘
         │
         ▼
-┌─ PHASE 3: INTERVIEW (Generated FROM Research) ────────────┐
+┌─ PHASE 4: INTERVIEW (Generated FROM Research) ────────────┐
 │                                                           │
 │ For EACH parameter discovered in research, ask ONE        │
 │ question at a time using AskUserQuestion:                 │
@@ -235,7 +235,7 @@ Both conditions must be true for the flag to be set.
 └───────────────────────────────────────────────────────────┘
         │
         ▼
-┌─ PHASE 4: DEEP RESEARCH (Adaptive) ───────────────────────┐
+┌─ PHASE 5: DEEP RESEARCH (Adaptive) ───────────────────────┐
 │                                                           │
 │ Based on interview answers, PROPOSE additional research.  │
 │                                                           │
@@ -260,7 +260,7 @@ Both conditions must be true for the flag to be set.
 └───────────────────────────────────────────────────────────┘
         │
         ▼
-┌─ PHASE 5: SCHEMA DESIGN ──────────────────────────────────┐
+┌─ PHASE 6: SCHEMA ─────────────────────────────────────────┐
 │                                                           │
 │ Create Zod schema from research + interview, then:        │
 │                                                           │
@@ -285,7 +285,7 @@ Both conditions must be true for the flag to be set.
 └───────────────────────────────────────────────────────────┘
         │
         ▼
-┌─ PHASE 6: ENVIRONMENT CHECK ──────────────────────────────┐
+┌─ PHASE 7: ENVIRONMENT ────────────────────────────────────┐
 │                                                           │
 │ Check required API keys, show status table, then:         │
 │                                                           │
@@ -309,7 +309,7 @@ Both conditions must be true for the flag to be set.
 └───────────────────────────────────────────────────────────┘
         │
         ▼
-┌─ PHASE 7: TDD RED (Write Failing Tests) ──────────────────┐
+┌─ PHASE 8: TDD RED (Write Failing Tests) ──────────────────┐
 │                                                           │
 │ Generate test matrix from schema + interview, then:       │
 │                                                           │
@@ -335,7 +335,7 @@ Both conditions must be true for the flag to be set.
 └───────────────────────────────────────────────────────────┘
         │
         ▼
-┌─ PHASE 8: TDD GREEN (Minimal Implementation) ─────────────┐
+┌─ PHASE 9: TDD GREEN (Minimal Implementation) ─────────────┐
 │                                                           │
 │ Write minimal code to pass ALL tests.                     │
 │ Tests derived from schema.                                │
@@ -347,7 +347,7 @@ Both conditions must be true for the flag to be set.
 └───────────────────────────────────────────────────────────┘
         │
         ▼
-┌─ PHASE 9: VERIFY (Re-Research After Green) ───────────────┐
+┌─ PHASE 10: VERIFY (Re-Research After Green) ──────────────┐
 │                                                           │
 │ MANDATORY: Re-read original documentation.                │
 │ Compare implementation to docs, then:                     │
@@ -374,7 +374,7 @@ Both conditions must be true for the flag to be set.
 └───────────────────────────────────────────────────────────┘
         │
         ▼
-┌─ PHASE 10: TDD REFACTOR ──────────────────────────────────┐
+┌─ PHASE 11: TDD REFACTOR ──────────────────────────────────┐
 │                                                           │
 │ Clean up code while tests stay green:                     │
 │   • Extract reusable patterns                             │
@@ -386,7 +386,7 @@ Both conditions must be true for the flag to be set.
 └───────────────────────────────────────────────────────────┘
         │
         ▼
-┌─ PHASE 11: DOCUMENTATION ─────────────────────────────────┐
+┌─ PHASE 12: DOCUMENTATION ─────────────────────────────────┐
 │                                                           │
 │ Update documentation files, then:                         │
 │                                                           │
@@ -411,7 +411,7 @@ Both conditions must be true for the flag to be set.
 └───────────────────────────────────────────────────────────┘
         │
         ▼
-┌─ PHASE 12: COMPLETION ────────────────────────────────────┐
+┌─ PHASE 13: COMPLETION ────────────────────────────────────┐
 │                                                           │
 │ Final verification:                                       │
 │   • All tests passing                                     │
@@ -421,9 +421,29 @@ Both conditions must be true for the flag to be set.
 │   • State file shows all phases complete                  │
 │                                                           │
 │ Run /commit to create semantic commit.                    │
+│                                                           │
+│ API Showcase: http://localhost:3000/api-showcase          │
+│ Your API is now available for interactive testing!       │
 └───────────────────────────────────────────────────────────┘
 ```
 
+### Showcase Redirect
+
+After successful API creation, output:
+
+```
+Your API has been added to the showcase!
+
+View it at: http://localhost:3000/api-showcase
+
+Or run `pnpm dev` and navigate to /api-showcase to:
+  - Test your API interactively
+  - View auto-generated curl examples
+  - See request/response schemas
+```
+
+Registry is automatically updated with the new API entry.
+
 ## State File Tracking
 
 All phases are tracked in `.claude/api-dev-state.json`:

package/commands/{api-env.md → hustle-api-env.md}

@@ -1,6 +1,6 @@
 # API Environment - Check API Keys & Configuration
 
-**Usage:** `/api-env [endpoint-name]`
+**Usage:** `/hustle-api-env [endpoint-name]`
 
 **Purpose:** Quick check for required API keys and environment setup before implementation.
 
@@ -32,9 +32,9 @@ Status: BLOCKED - Cannot proceed without FIRECRAWL_API_KEY
 
 ```bash
 # Before starting implementation
-/api-interview generate-css
-/api-research firecrawl
-/api-env generate-css  ← Check keys
+/hustle-api-interview generate-css
+/hustle-api-research firecrawl
+/hustle-api-env generate-css  ← Check keys
 /red                   ← Start TDD if ready
 ```
 

package/commands/{api-interview.md → hustle-api-interview.md}

@@ -1,6 +1,6 @@
 # API Interview - Research-Driven Dynamic Discovery v3.0
 
-**Usage:** `/api-interview [endpoint-name]`
+**Usage:** `/hustle-api-interview [endpoint-name]`
 
 **Purpose:** Conduct structured interview where questions are GENERATED FROM research findings, not generic templates. Every question is specific to the discovered API capabilities.
 

package/commands/{api-research.md → hustle-api-research.md}

@@ -1,6 +1,6 @@
 # API Research - Adaptive Documentation Discovery v3.0
 
-**Usage:** `/api-research [library-or-service-name]`
+**Usage:** `/hustle-api-research [library-or-service-name]`
 
 **Purpose:** Research external APIs and SDKs using an adaptive, propose-approve flow (not shotgun searches).
 
@@ -302,7 +302,7 @@ All research is tracked in `.claude/api-dev-state.json`:
 
 ### Research with full flow
 ```bash
-/api-research brandfetch
+/hustle-api-research brandfetch
 # → Initial search (2-3 queries)
 # → Present summary, ask to proceed
 # → Interview happens (separate phase)
@@ -324,7 +324,7 @@ All research is tracked in `.claude/api-dev-state.json`:
 
 ## Integration with API Development
 
-- Phase 3 of `/api-create` uses this for initial research
+- Phase 3 of `/hustle-api-create` uses this for initial research
 - Phase 5 uses adaptive proposal flow
 - Phase 10 (Verify) triggers re-research
 - Freshness check prevents stale data

package/commands/hustle-api-sessions.md

@@ -0,0 +1,149 @@
+# API Sessions Command
+
+Browse and export saved session logs from previous API development workflows.
+
+## Usage
+```
+/hustle-api-sessions [options]
+```
+
+## Options
+
+| Option | Description |
+|--------|-------------|
+| `--list` | List all saved sessions |
+| `--view [endpoint]` | View a specific session |
+| `--export [endpoint] [format]` | Export session to PDF/HTML/MD |
+| `--search [term]` | Search across all sessions |
+| `--cleanup` | Remove old sessions (>30 days) |
+
+## Examples
+
+```bash
+# List all sessions
+/hustle-api-sessions --list
+
+# View most recent brandfetch session
+/hustle-api-sessions --view brandfetch
+
+# Export to markdown
+/hustle-api-sessions --export brandfetch md
+
+# Search for "rate limit"
+/hustle-api-sessions --search "rate limit"
+```
+
+## Session Storage Structure
+
+Sessions are stored in `.claude/hustle-api-sessions/`:
+
+```
+.claude/hustle-api-sessions/
+├── brandfetch_2025-12-11_15-30-00/
+│   ├── state-snapshot.json     # State at completion
+│   ├── files-created.txt       # List of files made
+│   ├── summary.md              # Executive summary
+│   └── research-cache/         # Copy of research files
+│       ├── sources.json
+│       ├── interview.json
+│       └── CURRENT.md
+├── elevenlabs_2025-12-11_18-45-00/
+│   └── ...
+└── index.json                  # Session index
+```
+
+## Output Examples
+
+### --list
+
+```
+SAVED SESSIONS
+═══════════════════════════════════════════════════
+
+ # │ Endpoint    │ Date       │ Phases │ Status
+───┼─────────────┼────────────┼────────┼──────────
+ 1 │ brandfetch  │ 2025-12-11 │ 13/13  │ complete
+ 2 │ elevenlabs  │ 2025-12-10 │ 8/13   │ in_progress
+ 3 │ stripe      │ 2025-12-09 │ 13/13  │ complete
+
+Total: 3 sessions
+```
+
+### --view [endpoint]
+
+```
+SESSION: brandfetch
+═══════════════════════════════════════════════════
+
+Date: 2025-12-11 15:30:00
+Status: complete
+Phases: 13/13
+
+Files Created:
+  • src/app/api/v2/brandfetch/route.ts
+  • src/app/api/v2/brandfetch/__tests__/brandfetch.api.test.ts
+  • src/lib/schemas/brandfetch.ts
+
+Interview Decisions:
+  • format: json, svg
+  • authentication: api_key
+  • rate_limiting: yes
+
+Research Sources:
+  • https://docs.brandfetch.com/reference/
+  • https://brandfetch.com/developers/
+
+Session Path: .claude/hustle-api-sessions/brandfetch_2025-12-11_15-30-00/
+```
+
+---
+
+## Implementation
+
+When user runs `/hustle-api-sessions`:
+
+### --list
+
+```
+READ .claude/hustle-api-sessions/index.json
+FOR each session in index:
+  SHOW endpoint, date, phases completed, status
+SORT by date descending
+```
+
+### --view [endpoint]
+
+```
+FIND most recent session for endpoint
+READ summary.md from session folder
+DISPLAY formatted summary
+OFFER to open session folder
+```
+
+### --export [endpoint] [format]
+
+```
+FIND session folder
+LOAD all session files
+FORMAT to requested output (md/html/pdf)
+WRITE to output file
+SHOW output path
+```
+
+### --search [term]
+
+```
+FOR each session folder:
+  SEARCH summary.md for term
+  SEARCH state-snapshot.json for term
+  SEARCH research-cache/* for term
+SHOW matching sessions with context
+```
+
+---
+
+## Related Commands
+
+- `/hustle-api-create [endpoint]` - Start new workflow
+- `/hustle-api-continue [endpoint]` - Resume interrupted workflow
+- `/hustle-api-status [endpoint]` - Check current workflow progress

package/commands/{api-status.md → hustle-api-status.md}

@@ -1,6 +1,6 @@
 # API Status - Track Implementation Progress
 
-**Usage:** `/api-status [endpoint-name]` or `/api-status --all`
+**Usage:** `/hustle-api-status [endpoint-name]` or `/hustle-api-status --all`
 
 **Purpose:** View and update API implementation status, track progress, and manage V2 migration.
 
@@ -123,14 +123,14 @@ Last updated: 2025-12-06
 
 ### View Status
 ```bash
-/api-status generate-css    # Specific endpoint
-/api-status --all           # All endpoints
+/hustle-api-status generate-css    # Specific endpoint
+/hustle-api-status --all           # All endpoints
 ```
 
 ### Update Status
 ```bash
-/api-status generate-css --phase=testing
-/api-status generate-css --complete
+/hustle-api-status generate-css --phase=testing
+/hustle-api-status generate-css --complete
 ```
 
 ## Status Tracking File
@@ -176,32 +176,32 @@ Updates: `/src/v2/docs/v2-api-implementation-status.md`
 
 ### After Interview
 ```bash
-/api-interview generate-css
-/api-status generate-css --phase=interview-complete
+/hustle-api-interview generate-css
+/hustle-api-status generate-css --phase=interview-complete
 ```
 
 ### After Research
 ```bash
-/api-research gemini-flash
-/api-status generate-css --phase=research-complete
+/hustle-api-research gemini-flash
+/hustle-api-status generate-css --phase=research-complete
 ```
 
 ### After TDD Cycle
 ```bash
 /cycle generate CSS with Gemini
-/api-status generate-css --complete
+/hustle-api-status generate-css --complete
 ```
 
 ### Before Commit
 ```bash
 pnpm test:run
-/api-status --all  # Verify all green
+/hustle-api-status --all  # Verify all green
 /commit
 ```
 
 ## Automatic Updates
 
-The `/api-create` command automatically updates status:
+The `/hustle-api-create` command automatically updates status:
 - Interview phase → "Interview Complete"
 - Red phase → "Tests Written"
 - Green phase → "Implementation Complete"
@@ -225,19 +225,19 @@ The `/api-create` command automatically updates status:
 
 ### Coverage Report
 ```bash
-/api-status --coverage
+/hustle-api-status --coverage
 ```
 Shows test coverage for all V2 endpoints.
 
 ### Migration Report
 ```bash
-/api-status --migration
+/hustle-api-status --migration
 ```
 Shows progress from legacy to V2.
 
 ### Blockers Report
 ```bash
-/api-status --blocked
+/hustle-api-status --blocked
 ```
 Shows endpoints blocked by missing keys, dependencies, etc.
 
@@ -252,7 +252,7 @@ Shows endpoints blocked by missing keys, dependencies, etc.
 
 ## Integration Points
 
-- Used by /api-create to track progress
+- Used by /hustle-api-create to track progress
 - Used by /commit to verify readiness
 - Used by team to see what's done
 - Used for planning future work

package/commands/{api-verify.md → hustle-api-verify.md}

@@ -1,6 +1,6 @@
 # API Verify - Implementation Verification (Phase 10) v3.0
 
-**Usage:** `/api-verify [endpoint-name]`
+**Usage:** `/hustle-api-verify [endpoint-name]`
 
 **Purpose:** Manually trigger Phase 10 verification - re-research documentation and compare to implementation to catch memory-based errors.
 
@@ -203,7 +203,7 @@ Phase 8: TDD Red (write tests)
 Phase 9: TDD Green (implementation)
     │
     ▼
-Phase 10: VERIFY ← /api-verify triggers this
+Phase 10: VERIFY ← /hustle-api-verify triggers this
     │
     ├─► Gaps found? → Loop back to Phase 8
     │