@hustle-together/api-dev-tools 3.11.1 → 3.12.1

package/.skills/api-interview/SKILL.md

@@ -20,6 +20,7 @@ allowed-tools: WebSearch WebFetch mcp__context7 mcp__github AskUserQuestion Read
 ## Key Principle: Questions FROM Research
 
 **OLD WAY (Generic Templates):**
+
 ```
 "Which AI provider should this endpoint support?"
 - OpenAI
@@ -28,6 +29,7 @@ allowed-tools: WebSearch WebFetch mcp__context7 mcp__github AskUserQuestion Read
 ```
 
 **NEW WAY (From Research):**
+
 ```
 Based on research, Brandfetch API has 7 parameters:
 
@@ -53,6 +55,7 @@ Based on research, Brandfetch API has 7 parameters:
 **Interview is BLOCKED until research is done.**
 
 The interview READS from the research findings:
+
 ```
 State file shows:
   research_initial.status = "complete"
@@ -70,6 +73,7 @@ Discovered parameters:
 For each discovered parameter, generate an appropriate question:
 
 #### Required Parameters (Confirmation Only)
+
 ```
 ┌────────────────────────────────────────────────────────────┐
 │ REQUIRED PARAMETERS                                        │
@@ -84,6 +88,7 @@ For each discovered parameter, generate an appropriate question:
 ```
 
 #### Enum Parameters (Multi-Select)
+
 ```
 ┌────────────────────────────────────────────────────────────┐
 │ FORMAT PARAMETER                                           │
@@ -100,6 +105,7 @@ For each discovered parameter, generate an appropriate question:
 ```
 
 #### Continuous Parameters (Test Strategy)
+
 ```
 ┌────────────────────────────────────────────────────────────┐
 │ QUALITY PARAMETER                                          │
@@ -118,6 +124,7 @@ For each discovered parameter, generate an appropriate question:
 ```
 
 #### Boolean Parameters (Enable/Disable)
+
 ```
 ┌────────────────────────────────────────────────────────────┐
 │ INCLUDE_COLORS PARAMETER                                   │
@@ -202,14 +209,14 @@ After interview, propose additional research:
 
 ## Question Types Summary
 
-| Discovered Type | Question Type | Example |
-|----------------|---------------|---------|
-| Required param | Confirmation | "Confirm these are understood?" |
-| Enum param | Multi-select | "Which formats to support?" |
-| Continuous range | Test strategy | "How to test 1-100 range?" |
-| Boolean param | Enable/disable | "Expose this parameter?" |
-| Optional feature | Priority | "Include this feature?" |
-| Error case | Handling strategy | "How to handle rate limits?" |
+| Discovered Type  | Question Type     | Example                         |
+| ---------------- | ----------------- | ------------------------------- |
+| Required param   | Confirmation      | "Confirm these are understood?" |
+| Enum param       | Multi-select      | "Which formats to support?"     |
+| Continuous range | Test strategy     | "How to test 1-100 range?"      |
+| Boolean param    | Enable/disable    | "Expose this parameter?"        |
+| Optional feature | Priority          | "Include this feature?"         |
+| Error case       | Handling strategy | "How to handle rate limits?"    |
 
 ## State Tracking
 
@@ -252,7 +259,7 @@ All decisions are saved to `.claude/api-dev-state.json`:
 
 Creates: `.claude/research/[api-name]/interview.md`
 
-```markdown
+````markdown
 # Interview: [API Name]
 
 **Date:** [current-date]
@@ -261,19 +268,19 @@ Creates: `.claude/research/[api-name]/interview.md`
 
 ## Discovered Parameters
 
-| Parameter | Type | Required | Decision |
-|-----------|------|----------|----------|
-| domain | string | Yes | Always required |
-| format | enum | No | json, svg, png |
-| quality | 1-100 | No | Boundary testing: 1, 50, 100 |
+| Parameter | Type   | Required | Decision                     |
+| --------- | ------ | -------- | ---------------------------- |
+| domain    | string | Yes      | Always required              |
+| format    | enum   | No       | json, svg, png               |
+| quality   | 1-100  | No       | Boundary testing: 1, 50, 100 |
 
 ## Feature Scope
 
-| Feature | Included | Reason |
-|---------|----------|--------|
-| Basic fetch | Yes | Core functionality |
-| Multiple formats | Yes | User selected |
-| Webhooks | No | Deferred to v2 |
+| Feature          | Included | Reason             |
+| ---------------- | -------- | ------------------ |
+| Basic fetch      | Yes      | Core functionality |
+| Multiple formats | Yes      | User selected      |
+| Webhooks         | No       | Deferred to v2     |
 
 ## Test Strategy
 
@@ -290,6 +297,7 @@ Creates: `.claude/research/[api-name]/interview.md`
   "rate_limit_handling": "exponential_backoff"
 }
 ```
+````
 
 ## Deep Research Approved
 
@@ -299,6 +307,7 @@ Creates: `.claude/research/[api-name]/interview.md`
 ## Open Questions
 
 [Any remaining ambiguities]
+
 ```
 
 ## Integration with Hooks
@@ -306,14 +315,17 @@ Creates: `.claude/research/[api-name]/interview.md`
 The `enforce-interview.py` hook injects these decisions when Claude tries to write implementation:
 
 ```
+
 INTERVIEW CONTEXT REMINDER
 
 When implementing, remember user decisions:
+
 - format: ["json", "svg", "png"] (raw excluded)
 - quality: boundary testing (1, 50, 100)
 - rate limits: exponential backoff
 
 Source: .claude/api-dev-state.json
+
 ```
 
 <claude-commands-template>
@@ -342,3 +354,4 @@ Source: .claude/api-dev-state.json
 - Decisions injected during implementation via hook
 - Consistency between interview answers and code enforced
 </claude-commands-template>
+```

package/.skills/api-research/SKILL.md

@@ -22,6 +22,7 @@ allowed-tools: WebSearch WebFetch mcp__context7 mcp__github AskUserQuestion Read
 **NOT shotgun research** - We don't blindly run 20 searches.
 
 **Adaptive flow:**
+
 1. Run 2-3 initial searches
 2. Summarize findings
 3. PROPOSE additional searches based on context
@@ -34,6 +35,7 @@ allowed-tools: WebSearch WebFetch mcp__context7 mcp__github AskUserQuestion Read
 ### Initial Discovery (Automatic)
 
 Run 2-3 targeted searches:
+
 ```
 - Context7: "[library-name]" (if SDK/library)
 - WebSearch: "[name] official documentation"
@@ -41,6 +43,7 @@ Run 2-3 targeted searches:
 ```
 
 Present initial summary:
+
 ```
 ┌────────────────────────────────────────────────────────────┐
 │ INITIAL RESEARCH: [library-name]                           │
@@ -94,6 +97,7 @@ After interview, PROPOSE targeted searches based on user's selections:
 ### Execute Approved Searches
 
 Only run searches that were explicitly approved:
+
 - Track which searches were proposed vs approved vs skipped
 - Log everything to state file for transparency
 
@@ -113,9 +117,7 @@ Only run searches that were explicitly approved:
       "SVG optimization options",
       "batch processing"
     ],
-    "skipped_searches": [
-      "webhook support"
-    ]
+    "skipped_searches": ["webhook support"]
   }
 }
 ```
@@ -154,6 +156,7 @@ Research is cached in `.claude/research/[api-name]/`:
 ```
 
 **Freshness Rule:** If research is >7 days old when referenced:
+
 ```
 ⚠️ Research for "brandfetch" is 15 days old.
 Re-research before using? [Y/n]
@@ -163,7 +166,7 @@ Re-research before using? [Y/n]
 
 Creates: `.claude/research/[library-name]/CURRENT.md`
 
-```markdown
+````markdown
 # Research: [Library/Service Name]
 
 **Date:** [current-date]
@@ -172,6 +175,7 @@ Creates: `.claude/research/[library-name]/CURRENT.md`
 **Freshness:** 0 days (valid for 7 days)
 
 ## 1. Official Documentation Links
+
 - Main docs: [URL]
 - API reference: [URL]
 - GitHub repo: [URL]
@@ -179,72 +183,93 @@ Creates: `.claude/research/[library-name]/CURRENT.md`
 - TypeScript types: [URL]
 
 ## 2. Installation & Setup
+
 ### Installation
+
 ```bash
 [installation command]
 ```
+````
 
 ### Environment Variables
+
 ```env
 [required env vars]
 ```
 
 ### API Key Setup
+
 [How to obtain and configure]
 
 ## 3. Complete Request Schema
+
 ### Required Parameters
-| Parameter | Type | Description | Validation |
-|-----------|------|-------------|------------|
-| [name] | [type] | [desc] | [rules] |
+
+| Parameter | Type   | Description | Validation |
+| --------- | ------ | ----------- | ---------- |
+| [name]    | [type] | [desc]      | [rules]    |
 
 ### Optional Parameters
-| Parameter | Type | Default | Description | Notes |
-|-----------|------|---------|-------------|-------|
-| [name] | [type] | [default] | [desc] | [notes] |
+
+| Parameter | Type   | Default   | Description | Notes   |
+| --------- | ------ | --------- | ----------- | ------- |
+| [name]    | [type] | [default] | [desc]      | [notes] |
 
 ### Continuous Parameters (for test strategy)
-| Parameter | Type | Range | Suggested Test Values |
-|-----------|------|-------|----------------------|
-| quality | number | 1-100 | 1, 50, 100 (boundary) |
-| timeout | number | 1000-30000 | 1000, 15000, 30000 |
+
+| Parameter | Type   | Range      | Suggested Test Values |
+| --------- | ------ | ---------- | --------------------- |
+| quality   | number | 1-100      | 1, 50, 100 (boundary) |
+| timeout   | number | 1000-30000 | 1000, 15000, 30000    |
 
 ## 4. Complete Response Schema
+
 ### Success Response
+
 [TypeScript interface]
 
 ### Error Response
+
 [TypeScript interface with error codes]
 
 ## 5. Features & Capabilities
+
 ### Core Features (Discovered)
+
 - [x] [Feature 1]: [description]
 - [x] [Feature 2]: [description]
 
 ### Features NOT Implemented (Intentional)
+
 - [ ] [Feature]: [reason for exclusion]
 
 ## 6. Limitations & Constraints
+
 - Rate limits: [details]
 - Size limits: [details]
 - Timeout: [details]
 
 ## 7. Testing Considerations
+
 - [ ] Test boundary values for continuous params
 - [ ] Test all enum values
 - [ ] Test error responses
 - [ ] Test rate limiting behavior
 
 ## 8. Research Trail
+
 ### Searches Performed
-| Search | Tool | Found |
-|--------|------|-------|
-| "[name] documentation" | WebSearch | ✓ |
-| "[name]" | Context7 | ✓ |
+
+| Search                 | Tool      | Found |
+| ---------------------- | --------- | ----- |
+| "[name] documentation" | WebSearch | ✓     |
+| "[name]"               | Context7  | ✓     |
 
 ### Proposed but Skipped
+
 - "webhook support" - User declined, not needed
-```
+
+````
 
 ## Research-First Schema Design (MANDATORY)
 
@@ -309,11 +334,12 @@ All research is tracked in `.claude/api-dev-state.json`:
     }
   }
 }
-```
+````
 
 ## Usage Examples
 
 ### Research with full flow
+
 ```bash
 /api-research brandfetch
 # → Initial search (2-3 queries)
@@ -341,4 +367,4 @@ All research is tracked in `.claude/api-dev-state.json`:
 - Phase 5 uses adaptive proposal flow
 - Phase 10 (Verify) triggers re-research
 - Freshness check prevents stale data
-</claude-commands-template>
+  </claude-commands-template>

package/.skills/api-status/SKILL.md

@@ -31,6 +31,7 @@ Path: .claude/api-dev-state.json
 ```
 
 Parse the JSON and display a formatted status report showing:
+
 - Current endpoint being worked on
 - Phase completion status (scope, research, interview, TDD, docs)
 - Sources consulted during research
@@ -73,6 +74,7 @@ VERIFICATION:
 ## What This Shows
 
 ### For Specific Endpoint
+
 ```
 📊 Status: /api/v2/generate-css
 
@@ -100,6 +102,7 @@ Next Steps: None - endpoint complete
 ```
 
 ### For All Endpoints
+
 ```
 📊 V2 API Implementation Status
 
@@ -135,12 +138,14 @@ Last updated: 2025-12-06
 ## Commands
 
 ### View Status
+
 ```bash
 /api-status generate-css    # Specific endpoint
 /api-status --all           # All endpoints
 ```
 
 ### Update Status
+
 ```bash
 /api-status generate-css --phase=testing
 /api-status generate-css --complete
@@ -151,6 +156,7 @@ Last updated: 2025-12-06
 Updates: `/src/v2/docs/v2-api-implementation-status.md`
 
 **Format:**
+
 ```markdown
 # V2 API Implementation Status
 
@@ -161,6 +167,7 @@ Updates: `/src/v2/docs/v2-api-implementation-status.md`
 ## Endpoints
 
 ### ✅ /api/v2/health
+
 - **Status:** Complete
 - **Tests:** 15/15 passing
 - **Coverage:** 100%
@@ -169,6 +176,7 @@ Updates: `/src/v2/docs/v2-api-implementation-status.md`
 - **Purpose:** System health check with dependency validation
 
 ### 🚧 /api/v2/generate-css
+
 - **Status:** In Progress (Testing)
 - **Tests:** 20/33 passing
 - **Coverage:** 85%
@@ -178,6 +186,7 @@ Updates: `/src/v2/docs/v2-api-implementation-status.md`
 - **Next:** Complete remaining tests
 
 ### 📋 /api/v2/generate-html
+
 - **Status:** Planned
 - **Priority:** High
 - **Dependencies:** None
@@ -188,24 +197,28 @@ Updates: `/src/v2/docs/v2-api-implementation-status.md`
 ## Integration with Workflow
 
 ### After Interview
+
 ```bash
 /api-interview generate-css
 /api-status generate-css --phase=interview-complete
 ```
 
 ### After Research
+
 ```bash
 /api-research gemini-flash
 /api-status generate-css --phase=research-complete
 ```
 
 ### After TDD Cycle
+
 ```bash
 /cycle generate CSS with Gemini
 /api-status generate-css --complete
 ```
 
 ### Before Commit
+
 ```bash
 pnpm test:run
 /api-status --all  # Verify all green
@@ -215,6 +228,7 @@ pnpm test:run
 ## Automatic Updates
 
 The `/api-create` command automatically updates status:
+
 - Interview phase → "Interview Complete"
 - Red phase → "Tests Written"
 - Green phase → "Implementation Complete"
@@ -237,21 +251,27 @@ The `/api-create` command automatically updates status:
 ## Reports
 
 ### Coverage Report
+
 ```bash
 /api-status --coverage
 ```
+
 Shows test coverage for all V2 endpoints.
 
 ### Migration Report
+
 ```bash
 /api-status --migration
 ```
+
 Shows progress from legacy to V2.
 
 ### Blockers Report
+
 ```bash
 /api-status --blocked
 ```
+
 Shows endpoints blocked by missing keys, dependencies, etc.
 
 <claude-commands-template>
@@ -269,4 +289,4 @@ Shows endpoints blocked by missing keys, dependencies, etc.
 - Used by /commit to verify readiness
 - Used by team to see what's done
 - Used for planning future work
-</claude-commands-template>
+  </claude-commands-template>

package/.skills/api-verify/SKILL.md

@@ -151,24 +151,24 @@ Creates: `.claude/research/[api-name]/verification.md`
 
 **Date:** [current-date]
 **Implementation File:** src/app/api/v2/[endpoint]/route.ts
-**Test File:** src/app/api/v2/[endpoint]/__tests__/[endpoint].api.test.ts
+**Test File:** src/app/api/v2/[endpoint]/**tests**/[endpoint].api.test.ts
 
 ## Documentation Sources Re-Checked
 
-| Source | URL | Checked |
-|--------|-----|---------|
-| Official docs | [URL] | ✓ |
-| Context7 | [library] | ✓ |
-| Cached research | .claude/research/[api]/CURRENT.md | ✓ |
+| Source          | URL                               | Checked |
+| --------------- | --------------------------------- | ------- |
+| Official docs   | [URL]                             | ✓       |
+| Context7        | [library]                         | ✓       |
+| Cached research | .claude/research/[api]/CURRENT.md | ✓       |
 
 ## Feature Comparison
 
-| Feature | In Docs | Implemented | Status |
-|---------|---------|-------------|--------|
-| domain param | ✓ | ✓ | ✅ Match |
-| format param | 4 options | 3 options | ⚠️ Fixed |
-| size param | ✓ | ✓ | ⚠️ Fixed |
-| webhook | ✓ | ✗ | ℹ️ Intentional |
+| Feature      | In Docs   | Implemented | Status         |
+| ------------ | --------- | ----------- | -------------- |
+| domain param | ✓         | ✓           | ✅ Match       |
+| format param | 4 options | 3 options   | ⚠️ Fixed       |
+| size param   | ✓         | ✓           | ⚠️ Fixed       |
+| webhook      | ✓         | ✗           | ℹ️ Intentional |
 
 ## Gaps Fixed
 
@@ -203,6 +203,7 @@ Creates: `.claude/research/[api-name]/verification.md`
 This command is normally triggered automatically by `verify-after-green.py` hook after tests pass.
 
 Manual invocation is useful when:
+
 - Hook was skipped or didn't trigger
 - Want to re-verify after changes
 - Research is stale and needs refresh
@@ -241,4 +242,4 @@ Phase 10: VERIFY ← /api-verify triggers this
 - Error codes handled?
 - Optional features accounted for?
 - Default values match docs?
-</claude-commands-template>
+  </claude-commands-template>

package/.skills/beepboop/SKILL.md

@@ -12,8 +12,10 @@ allowed-tools: WebSearch WebFetch mcp__context7 mcp__github AskUserQuestion Read
 ---
 
 ---
+
 description: Communicate AI-generated content with transparent attribution
 argument-hint: <task-description>
+
 ---
 
 # AI-Attributed Communication Command
@@ -34,7 +36,7 @@ Arguments: $ARGUMENTS
 
 **IMPORTANT Communication Format:**
 
-1. **Opening**: Begin with "*Beep boop, I am Claude Code 🤖, my user has reviewed and approved the following written by me:*"
+1. **Opening**: Begin with "_Beep boop, I am Claude Code 🤖, my user has reviewed and approved the following written by me:_"
    - Use italics for this line
    - Clearly establishes AI authorship
 
@@ -42,7 +44,7 @@ Arguments: $ARGUMENTS
    - Execute whatever communication task the user requested
    - Write the actual content that accomplishes the user's goal
 
-3. **Closing**: End with "*Beep boop, Claude Code 🤖 out!*"
+3. **Closing**: End with "_Beep boop, Claude Code 🤖 out!_"
    - Use italics for this line
    - Provides clear closure
 
@@ -57,7 +59,6 @@ This command ensures transparency about AI usage while maintaining that the user
 - Responding to feedback with AI-generated explanations
 - Any communication where AI attribution is valuable
 
-
 ## 🛡 Project Rules (Injected into every command)
 
 1. **NO BROKEN BUILDS:**
@@ -82,7 +83,7 @@ This command ensures transparency about AI usage while maintaining that the user
 4. **API KEY MANAGEMENT:**
    - Support three loading methods:
      - Server environment variables
-     - NEXT_PUBLIC_ variables (client-side)
+     - NEXT*PUBLIC* variables (client-side)
      - Custom headers (X-OpenAI-Key, X-Anthropic-Key, etc.)
    - Never hardcode API keys
    - Always validate key availability before use
@@ -107,4 +108,4 @@ This command ensures transparency about AI usage while maintaining that the user
      - Code examples
      - Testing notes
    - Document expected behavior and edge cases
-   - Include real-world output examples
+   - Include real-world output examples

package/.skills/busycommit/SKILL.md

@@ -12,8 +12,10 @@ allowed-tools: WebSearch WebFetch mcp__context7 mcp__github AskUserQuestion Read
 ---
 
 ---
+
 description: Create multiple atomic git commits, one logical change at a time
 argument-hint: [optional-commit-description]
+
 ---
 
 ## General Guidelines
@@ -72,7 +74,6 @@ git add src/user-service.ts
 git commit -m "refactor: extract user lookup to helper"
 ```
 
-
 ## 🛡 Project Rules (Injected into every command)
 
 1. **NO BROKEN BUILDS:**
@@ -97,7 +98,7 @@ git commit -m "refactor: extract user lookup to helper"
 4. **API KEY MANAGEMENT:**
    - Support three loading methods:
      - Server environment variables
-     - NEXT_PUBLIC_ variables (client-side)
+     - NEXT*PUBLIC* variables (client-side)
      - Custom headers (X-OpenAI-Key, X-Anthropic-Key, etc.)
    - Never hardcode API keys
    - Always validate key availability before use
@@ -122,4 +123,4 @@ git commit -m "refactor: extract user lookup to helper"
      - Code examples
      - Testing notes
    - Document expected behavior and edge cases
-   - Include real-world output examples
+   - Include real-world output examples

package/.skills/commit/SKILL.md

@@ -12,8 +12,10 @@ allowed-tools: WebSearch WebFetch mcp__context7 mcp__github AskUserQuestion Read
 ---
 
 ---
+
 description: Create a git commit following project standards
 argument-hint: [optional-commit-description]
+
 ---
 
 ## General Guidelines
@@ -43,7 +45,6 @@ git add <files>
 git commit -m "feat(#123): add validation to user input form"
 ```
 
-
 ## 🛡 Project Rules (Injected into every command)
 
 1. **NO BROKEN BUILDS:**
@@ -68,7 +69,7 @@ git commit -m "feat(#123): add validation to user input form"
 4. **API KEY MANAGEMENT:**
    - Support three loading methods:
      - Server environment variables
-     - NEXT_PUBLIC_ variables (client-side)
+     - NEXT*PUBLIC* variables (client-side)
      - Custom headers (X-OpenAI-Key, X-Anthropic-Key, etc.)
    - Never hardcode API keys
    - Always validate key availability before use
@@ -93,4 +94,4 @@ git commit -m "feat(#123): add validation to user input form"
      - Code examples
      - Testing notes
    - Document expected behavior and edge cases
-   - Include real-world output examples
+   - Include real-world output examples