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

package/.skills/worktree-cleanup/SKILL.md

@@ -0,0 +1,294 @@
+---
+name: worktree-cleanup
+description: Clean up merged worktrees by verifying PR/issue status, consolidating settings, removing stale worktrees. Use after merging features. Keywords: git, worktree, cleanup, maintenance, branches
+license: MIT
+compatibility: Requires Claude Code with MCP servers (Context7, GitHub), Python 3.9+ for hooks, pnpm 10.11.0+
+metadata:
+  version: "3.0.0"
+  category: "git"
+  tags: ['git', 'worktree', 'cleanup', 'maintenance']
+  author: "Hustle Together"
+allowed-tools: WebSearch WebFetch mcp__context7 mcp__github AskUserQuestion Read Write Edit Bash TodoWrite
+---
+
+---
+description: Clean up merged worktrees by verifying PR/issue status, consolidating settings, and removing stale worktrees
+argument-hint: (no arguments)
+---
+
+# Worktree Cleanup
+
+## General Guidelines
+
+### Output Style
+
+- **Never explicitly mention TDD** in code, comments, commits, PRs, or issues
+- Write natural, descriptive code without meta-commentary about the development process
+- The code should speak for itself - TDD is the process, not the product
+
+Clean up merged worktrees by finding the oldest merged branch, consolidating settings, and removing stale worktrees.
+
+Additional info: $ARGUMENTS
+
+<current_state>
+Current branch: !git branch --show-current`
+Current worktrees: !git worktree list`
+</current_state>
+
+<execution_steps>
+<step_0>
+  <description>Validate MCP dependencies</description>
+  <check_github_mcp>
+    <requirement>GitHub MCP server must be configured</requirement>
+    <fallback>If unavailable, use `gh` CLI commands</fallback>
+    <validation>
+      - Try listing available MCP resources
+      - If GitHub MCP not found, switch to CLI fallback
+      - Inform user about MCP configuration if needed
+    </validation>
+  </check_github_mcp>
+  <error_handling>
+    If MCP validation fails:
+    - Show clear error message
+    - Provide setup instructions
+    - Fallback to CLI if possible
+  </error_handling>
+  <purpose>Ensure required MCP dependencies are available before proceeding</purpose>
+</step_0>
+
+  <step_1>
+    <description>Verify we're in main branch</description>
+    <check_command>git branch --show-current</check_command>
+    <required_branch>main</required_branch>
+    <error_if_not_main>Exit with error message: "This command must be run from the main branch"</error_if_not_main>
+    <purpose>Ensure we're consolidating to the main worktree</purpose>
+  </step_1>
+
+  <step_2>
+    <description>Get list of all worktrees</description>
+    <command>git worktree list --porcelain</command>
+    <parse_output>Extract worktree paths and branch names</parse_output>
+    <exclude_main>Filter out the main worktree from cleanup candidates</exclude_main>
+    <purpose>Identify all worktrees that could potentially be cleaned up</purpose>
+  </step_2>
+
+  <step_3>
+    <description>Find oldest worktree by directory age</description>
+    <get_worktree_ages>
+      <command_macos>git worktree list | grep -v "main" | awk '{print $1}' | while read path; do /usr/bin/stat -f "%Sm|%N" -t "%Y-%m-%d %H:%M:%S" "$path" 2>/dev/null; done | sort</command_macos>
+      <command_linux>git worktree list | grep -v "main" | awk '{print $1}' | xargs stat -c "%y|%n" | sort</command_linux>
+      <purpose>List all worktrees sorted by directory modification time (oldest first)</purpose>
+      <note>Use full path /usr/bin/stat on macOS, regular stat on Linux.</note>
+    </get_worktree_ages>
+    <filter_recent>
+      <exclude_new>For worktrees created within the last 24 hours, let user know that this worktree might not be worth cleaning</exclude_new>
+      <get_current_time>date +"%Y-%m-%d %H:%M"</get_current_time>
+    </filter_recent>
+    <select_oldest>
+      <extract_branch_name>Parse branch name from oldest worktree path</extract_branch_name>
+      <important_note>DO NOT use "git branch --merged" to check merge status - it's unreliable</important_note>
+      <proceed_to_pr_check>Move directly to step 4 to verify PR merge status instead</proceed_to_pr_check>
+    </select_oldest>
+    <purpose>Identify oldest worktree candidate - actual merge verification happens via GitHub PR in next step</purpose>
+  </step_3>
+
+  <step_4>
+    <description>Verify GitHub PR merge status (primary merge verification)</description>
+    <determine_repo>
+      <check_remote>git remote get-url origin</check_remote>
+      <parse_repo>Extract owner/repo from GitHub URL</parse_repo>
+      <fallback>Use project repository from git remote (owner/repo format)</fallback>
+    </determine_repo>
+    <search_pr>
+      <tool>mcp__github__search_pull_requests</tool>
+      <query>repo:owner/repo head:{branch_name} base:main</query>
+      <purpose>Find PR for this branch targeting main</purpose>
+      <important>This is the PRIMARY way to verify if a branch was merged - NOT git commands</important>
+    </search_pr>
+    <verify_pr_merged>
+      <if_pr_found>
+        <get_pr_details>Use mcp__github__pull_request_read to get full PR info</get_pr_details>
+        <confirm_merged>Verify PR state is "closed" AND merged_at is not null AND base is "main"</confirm_merged>
+        <extract_issue_number>Look for issue references in PR title/body (e.g., #14533, owner/repo#14533)</extract_issue_number>
+        <if_merged>Proceed with cleanup - this branch was definitively merged to main</if_merged>
+        <if_not_merged>
+          <skip_worktree>This worktree is NOT merged - continue to next oldest worktree</skip_worktree>
+          <repeat_from_step_3>Go back and find the next oldest worktree to check</repeat_from_step_3>
+        </if_not_merged>
+      </if_pr_found>
+      <if_no_pr>
+        <skip_worktree>No PR found - this branch was likely never submitted for review</skip_worktree>
+        <continue_to_next>Continue checking next oldest worktree</continue_to_next>
+      </if_no_pr>
+    </verify_pr_merged>
+    <purpose>Use GitHub PR status as the authoritative source for merge verification instead of unreliable git commands</purpose>
+  </step_4>
+
+  <step_4_5>
+    <description>Check and close related GitHub issue</description>
+    <if_issue_found>
+      <get_issue_details>
+        <tool>mcp__github__issue_read</tool>
+        <method>get</method>
+        <extract_repo>From issue reference (main-repo vs cross-repo)</extract_repo>
+      </get_issue_details>
+      <check_issue_state>
+        <if_open>
+          <ask_close>Ask user: "Related issue #{number} is still open. Should I close it? (y/N)"</ask_close>
+          <if_yes_close>
+            <add_closing_comment>
+              <tool>mcp__github__add_issue_comment</tool>
+              <body_template>Closing this issue as branch {branch_name} was merged to main on {merge_date} via PR #{pr_number}.</body_template>
+              <get_merge_date>Extract merge date from PR details</get_merge_date>
+              <get_pr_number>Use PR number from search results</get_pr_number>
+            </add_closing_comment>
+            <close_issue>
+              <tool>mcp__github__issue_write</tool>
+              <method>update</method>
+              <state>closed</state>
+              <state_reason>completed</state_reason>
+            </close_issue>
+          </if_yes_close>
+        </if_open>
+        <if_closed>Inform user issue is already closed</if_closed>
+      </check_issue_state>
+    </if_issue_found>
+    <if_no_issue>Continue without issue management</if_no_issue>
+    <purpose>Ensure proper issue lifecycle management</purpose>
+  </step_4_5>
+
+  <step_5>
+    <description>Check if worktree is locked</description>
+    <check_command>git worktree list --porcelain | grep -A5 "worktree {path}" | grep "locked"</check_command>
+    <if_locked>
+      <unlock_command>git worktree unlock {path}</unlock_command>
+      <notify_user>Inform user that worktree was unlocked</notify_user>
+    </if_locked>
+    <purpose>Unlock worktree if it was locked for tracking purposes</purpose>
+  </step_5>
+
+  <step_6>
+    <description>Analyze Claude settings differences</description>
+    <read_main_settings>.claude/settings.local.json</read_main_settings>
+    <read_worktree_settings>{worktree_path}/.claude/settings.local.json</read_worktree_settings>
+    <compare_allow_lists>
+      <extract_main_allows>Extract "allow" array from main settings</extract_main_allows>
+      <extract_worktree_allows>Extract "allow" array from worktree settings</extract_worktree_allows>
+      <find_differences>Identify entries in worktree that are not in main</find_differences>
+    </compare_allow_lists>
+    <filter_suggestions>
+      <include_filesystem>Read permissions for filesystem paths</include_filesystem>
+      <exclude_intrusive>Exclude bash commands, write permissions, etc.</exclude_intrusive>
+      <focus_user_specific>Include only user-specific, non-disruptive entries</focus_user_specific>
+    </filter_suggestions>
+    <purpose>Identify useful settings to consolidate before cleanup</purpose>
+  </step_6>
+
+  <step_7>
+    <description>Suggest settings consolidation</description>
+    <if_differences_found>
+      <display_suggestions>Show filtered differences to user</display_suggestions>
+      <ask_confirmation>Ask user which entries to add to main settings</ask_confirmation>
+      <apply_changes>Update main .claude/settings.local.json with selected entries</apply_changes>
+    </if_differences_found>
+    <if_no_differences>Inform user no settings need consolidation</if_no_differences>
+    <purpose>Preserve useful development settings before removing worktree</purpose>
+  </step_7>
+
+  <step_8>
+    <description>Final cleanup confirmation</description>
+    <summary>
+      <display_worktree>Show worktree path and branch name</display_worktree>
+      <show_pr_status>Show merged PR details if found</show_pr_status>
+      <show_issue_status>Show related issue status if found</show_issue_status>
+      <show_last_activity>Display directory creation/modification date</show_last_activity>
+    </summary>
+    <safety_checks>
+      <check_uncommitted>git status --porcelain in worktree directory</check_uncommitted>
+      <warn_if_dirty>Alert user if uncommitted changes exist</warn_if_dirty>
+    </safety_checks>
+    <ask_deletion>Ask user confirmation: "Delete this worktree? (y/N)"</ask_deletion>
+    <purpose>Final safety check before irreversible deletion</purpose>
+  </step_8>
+
+  <step_9>
+    <description>Delete worktree</description>
+    <if_confirmed>
+      <remove_worktree>git worktree remove {path} --force</remove_worktree>
+      <cleanup_branch>git branch -d {branch_name}</cleanup_branch>
+      <success_message>Inform user worktree was successfully removed</success_message>
+      <next_steps>Suggest running command again to find next candidate</next_steps>
+    </if_confirmed>
+    <if_declined>Exit gracefully with no changes</if_declined>
+    <purpose>Perform the actual cleanup and guide user for next iteration</purpose>
+  </step_9>
+</execution_steps>
+
+<important_notes>
+
+- Uses GitHub PR merge status as the ONLY reliable way to verify if a branch was merged
+- DOES NOT use "git branch --merged" command as it's unreliable for merge verification
+- Only processes branches with PRs that were definitively merged to main
+- Skips worktrees without merged PRs and continues to next oldest candidate
+- Checks and optionally closes related GitHub issues
+- Prioritizes oldest worktrees by directory age first for systematic cleanup
+- Warns about very recent worktrees (created within 24 hours) to avoid cleaning active work
+- Preserves useful development settings before deletion
+- Requires explicit confirmation before any destructive actions
+- Handles locked worktrees automatically
+- Processes one worktree at a time to maintain control
+- Must be run from main branch for safety
+- Works with standard GitHub repository URLs (owner/repo format)
+</important_notes>
+
+
+## 🛡 Project Rules (Injected into every command)
+
+1. **NO BROKEN BUILDS:**
+   - Run `pnpm test` before every `/commit`
+   - Ensure all tests pass
+   - Fix any type errors immediately
+
+2. **API DEVELOPMENT:**
+   - All new APIs MUST have Zod request/response schemas
+   - All APIs MUST be documented in both:
+     - OpenAPI spec ([src/lib/openapi/](src/lib/openapi/))
+     - API test manifest ([src/app/api-test/api-tests-manifest.json](src/app/api-test/api-tests-manifest.json))
+   - Test ALL parameters and edge cases
+   - Include code examples and real-world outputs
+
+3. **TDD WORKFLOW:**
+   - ALWAYS use /red → /green → /refactor cycle
+   - NEVER write implementation without failing test first
+   - Use /cycle for feature development
+   - Use characterization tests for refactoring
+
+4. **API KEY MANAGEMENT:**
+   - Support three loading methods:
+     - Server environment variables
+     - NEXT_PUBLIC_ variables (client-side)
+     - Custom headers (X-OpenAI-Key, X-Anthropic-Key, etc.)
+   - Never hardcode API keys
+   - Always validate key availability before use
+
+5. **COMPREHENSIVE TESTING:**
+   - When researching APIs, read actual implementation code
+   - Discover ALL possible parameters (not just documented ones)
+   - Test with various parameter combinations
+   - Document custom headers, query params, request/response schemas
+   - Include validation rules and testing notes
+
+6. **NO UI BLOAT:**
+   - This is an API project with minimal frontend
+   - Only keep necessary test/documentation interfaces
+   - Delete unused components immediately
+   - No unnecessary UI libraries or features
+
+7. **DOCUMENTATION:**
+   - If you change an API, you MUST update:
+     - OpenAPI spec
+     - api-tests-manifest.json
+     - Code examples
+     - Testing notes
+   - Document expected behavior and edge cases
+   - Include real-world output examples

package/CHANGELOG.md

@@ -0,0 +1,97 @@
+# Changelog
+
+All notable changes to `@hustle-together/api-dev-tools` will be documented in this file.
+
+## [3.10.0] - 2025-12-12
+
+### Added
+- **UI Page Mode** - Full `/hustle-ui-create-page` workflow with dedicated documentation
+  - Page types: landing, dashboard, form, list, detail, auth
+  - Playwright E2E test generation (15+ test cases)
+  - Data schema validation before implementation
+- **Page-Specific Hooks**
+  - `check-api-routes.py` - Verifies required API routes exist before page implementation
+  - `enforce-page-components.py` - Checks registry for reusable components
+  - `enforce-page-data-schema.py` - Validates API response types defined
+  - `enforce-a11y-audit.py` - Triggers WCAG audit after TDD Green phase
+- **Combine Workflow Validation**
+  - 2+ API selection enforcement
+  - Registry verification for source APIs
+  - Flow type validation (sequential, parallel, conditional)
+  - Orchestration examples in manifest generation
+- **Brand Color Validation** in `enforce-brand-guide.py`
+  - Extracts allowed colors from BRAND_GUIDE.md
+  - Validates hex colors, Tailwind classes, CSS variables
+  - Notifies on non-brand color usage
+- **UI Showcase Auto-Population** in `update-ui-showcase.py`
+  - Generates `data.json` from registry automatically
+  - Component and page metadata extraction
+
+### Changed
+- **State Template** (`api-dev-state.json`)
+  - Added `workflow` field: api-create, combine-api, ui-create-component, ui-create-page
+  - Added `combine_config` section for orchestration settings
+  - Added `ui_config` section for component/page settings
+- **Session Startup** (`session-startup.py`)
+  - Workflow-specific context injection
+  - Combine: source APIs, flow type, error strategy
+  - UI: brand guide status, component/page type, a11y level
+- **Manifest Generation** (`generate-manifest-entry.py`)
+  - Orchestration examples for combined endpoints
+  - Flow diagrams and error handling examples
+  - Version updated to 3.10.0
+
+### Fixed
+- Phase numbering now correctly uses 1-13 (was 0-12 in some files)
+- Workflow type detection in api-workflow-check.py for all workflow types
+
+## [3.9.2] - 2025-12-10
+
+### Added
+- Animated Hero Header with 3D perspective grid
+- Dev Tools landing page at `/dev-tools`
+- Multi-endpoint selector for APIs with sub-endpoints
+- Audio playback for TTS/voice API responses
+- CLI flags: `--with-sandpack`, `--with-storybook`, `--with-playwright`
+
+### Changed
+- Updated BRAND_GUIDE.md with complete Hustle brand
+- Enhanced showcase components with dark mode support
+- Boxy 90s styling with 2px borders
+
+## [3.9.0] - 2025-12-08
+
+### Added
+- `/hustle-ui-create` command for UI components/pages
+- Brand guide integration with time to update
+- ShadCN component detection in Phase 5
+- 4-step verification (desktop/tablet/mobile + brand + tests + memory)
+- UI Showcase auto-generation at `/ui-showcase`
+
+## [3.8.0] - 2025-12-05
+
+### Added
+- `/hustle-combine` command for API orchestration
+- Registry.json central tracking
+- Combined entry support in update-registry.py
+- Orchestration flow types: sequential, parallel, conditional
+
+## [3.7.0] - 2025-12-01
+
+### Added
+- Multi-API state support (endpoints object)
+- Research cache freshness tracking (7-day threshold)
+- Comprehensive manifest generation with 50+ test cases
+- Session logging in api-sessions/
+
+## [3.6.7] - 2025-11-28
+
+### Added
+- Phase 13 completion output with curl examples
+- Scope coverage report
+- Research cache location in output
+- Gap fixes for file tracking and verification
+
+---
+
+Note: v3.x is the final major version. All future updates will be v3.x.y releases.

package/README.md

@@ -1,8 +1,23 @@
-# Hustle Development Tools for Claude Code v3.10.0
+# API Development Tools v3.11.0
 
-**Interview-driven, research-first API and UI development with 100% phase enforcement**
+**Interview-driven, research-first API development with 13-phase TDD workflow**
 
-## Quick Start
+[![Agent Skills](https://img.shields.io/badge/Agent_Skills-Compatible-blue)](https://agentskills.io)
+[![Cross-Platform](https://img.shields.io/badge/Cross--Platform-Claude%20%7C%20VS%20Code%20%7C%20Cursor-green)](https://github.com/hustle-together/api-dev-tools)
+[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
+
+> Now with **23 Agent Skills** for cross-platform compatibility across Claude Code, VS Code, Cursor, ChatGPT, and GitHub Copilot
+
+## ⚡ Quick Start
+
+### Via Claude Code Plugin (Recommended)
+
+```bash
+/plugin marketplace add hustle-together/api-dev-tools
+/plugin install api-dev-tools
+```
+
+### Via NPM
 
 ```bash
 npx @hustle-together/api-dev-tools --scope=project
@@ -20,25 +35,51 @@ npx @hustle-together/api-dev-tools --with-sandpack --with-storybook
 ```
 
 **What Gets Installed:**
-- 11 Hustle slash commands (API + UI + Page + Combine)
-- 38 enforcement hooks (Python scripts)
-- Multi-element state tracking (`api-dev-state.json`)
-- **Central registry** (`registry.json`) - tracks all APIs, components, pages
-- **Brand guide** (`BRAND_GUIDE.md`) - default branding template
-- **Showcase pages** - `/dev-tools`, `/api-showcase`, `/ui-showcase`
-- **Component/Page templates** - Storybook stories, Playwright E2E tests
-- Research cache with 7-day freshness (`research/`)
-- Session logging (`api-sessions/`)
-- MCP server integrations (Context7, GitHub)
+- **23 Agent Skills** (cross-platform compatible)
+- **18 Enforcement Hooks** (Python scripts for Claude Code)
+- **State Tracking** (`.claude/api-dev-state.json`)
+- **Research Cache** (`.claude/research/` with 7-day freshness)
+- **MCP Server Integration** (Context7 for docs, GitHub for PRs)
 
 **Start Your First Workflow:**
 ```bash
-/hustle-api-create my-endpoint     # For APIs
-/hustle-ui-create                  # For UI components
-/hustle-ui-create-page             # For Next.js pages (NEW in v3.10)
-/hustle-combine                    # For API orchestration
+/api-create my-endpoint      # Complete 13-phase API workflow
+/red                         # Write failing test
+/green                       # Minimal implementation
+/refactor                    # Clean up code
+/commit                      # Semantic commit
+/pr                          # Create pull request
 ```
 
+## 🎉 What's New in v3.11.0
+
+### Agent Skills Migration 🎯
+
+**We've migrated to the [Agent Skills open standard](https://agentskills.io)!**
+
+#### Cross-Platform Compatibility
+- ✅ **Claude Code**: Full support with hooks and enforcement
+- ✅ **VS Code**: Works with GitHub Copilot (manual hook setup)
+- ✅ **Cursor**: Skills available (manual hook setup)
+- ✅ **ChatGPT**: Skills available (no hooks)
+- ✅ **Any Agent Skills-compatible platform**
+
+#### What Changed
+- **23 Skills**: All commands converted to `SKILL.md` format with YAML frontmatter
+- **Plugin Marketplace**: One-command installation via `/plugin install`
+- **Backward Compatible**: Original `.claude/commands/` still works
+- **Enhanced Discovery**: Rich metadata and keywords for better skill selection
+- **Automated Setup**: Installation script handles hooks and settings
+
+#### Distribution
+- **GitHub**: [hustle-together/api-dev-tools](https://github.com/hustle-together/api-dev-tools)
+- **NPM**: [@hustle-together/api-dev-tools](https://npmjs.com/package/@hustle-together/api-dev-tools)
+- **SkillsMP**: Coming soon
+
+See [`.skills/README.md`](./.skills/README.md) for complete skills documentation.
+
+---
+
 ## What's New in v3.10.0
 
 ### UI Page Mode Complete
@@ -175,7 +216,7 @@ During Phase 3, Claude prompts: *"NOW is the time to update your brand guide!"*
 - `update-ui-showcase.py` - Auto-update UI Showcase registry
 - `update-api-showcase.py` - Auto-update API Showcase registry
 
-## What's in v3.8.0
+## What's New in v3.8.0
 
 ### `/hustle-combine` Command
 Combine existing APIs from the registry into orchestration endpoints:
@@ -4125,7 +4166,7 @@ const researchCache = `.claude/research/${endpoint}/CURRENT.md`;
 When you install with `npx @hustle-together/api-dev-tools --scope=project`, the following files are created in your project's `.claude/` directory:
 
 ```
-@hustle-together/api-dev-tools v3.7.0
+@hustle-together/api-dev-tools v3.10.0
 │
 ├── bin/
 │   └── cli.js                              # NPX installer
@@ -4221,7 +4262,7 @@ When you install with `npx @hustle-together/api-dev-tools --scope=project`, the
 │   ├── extract-parameters.ts               # Extract Zod params
 │   └── collect-test-results.ts             # Run tests → results
 │
-└── package.json                            # v3.9.2
+└── package.json                            # v3.10.0
 ```
 
 ### Files Installed to Your Project
@@ -4870,6 +4911,9 @@ When `/hustle-ui-create` runs, it uses these templates as starting points, custo
 
 ---
 
+<details>
+<summary>📜 Older Version History (v3.6.0 - v3.7.0)</summary>
+
 ## What's New in v3.7.0
 
 ### Hustle Branding
@@ -4994,6 +5038,8 @@ Upgraded hooks:
 
 Every phase requires an "exit confirmation" question and affirmative user response before advancing. Prevents Claude from self-answering questions.
 
+</details>
+
 ---
 
 ## All Hooks Reference (34 Hooks)

package/bin/cli.js

@@ -365,16 +365,17 @@ function main() {
                     fs.existsSync(path.join(targetDir, 'next.config.mjs')) ||
                     fs.existsSync(path.join(targetDir, 'next.config.ts'));
 
+  // Detect App Router structure (used by Test UI and Showcase Pages)
+  const appDir = fs.existsSync(path.join(targetDir, 'src', 'app'))
+    ? path.join(targetDir, 'src', 'app')
+    : fs.existsSync(path.join(targetDir, 'app'))
+      ? path.join(targetDir, 'app')
+      : null;
+
   if (!hasNextJs) {
     log('   ⚠️  Next.js not detected - skipping Test UI installation', 'yellow');
     log('   💡 Test UI requires Next.js App Router', 'yellow');
   } else if (fs.existsSync(testUiSourceDir)) {
-    // Detect App Router structure
-    const appDir = fs.existsSync(path.join(targetDir, 'src', 'app'))
-      ? path.join(targetDir, 'src', 'app')
-      : fs.existsSync(path.join(targetDir, 'app'))
-        ? path.join(targetDir, 'app')
-        : null;
 
     if (!appDir) {
       log('   ⚠️  App Router not detected - skipping Test UI installation', 'yellow');

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@hustle-together/api-dev-tools",
-  "version": "3.10.0",
-  "description": "Interview-driven, research-first API and UI development workflow with continuous verification loops for Claude Code",
+  "version": "3.11.1",
+  "description": "Interview-driven, research-first API development toolkit with 13-phase TDD workflow, enforcement hooks, and 23 Agent Skills for cross-platform AI agents",
   "main": "bin/cli.js",
   "bin": {
     "api-dev-tools": "./bin/cli.js"
@@ -12,8 +12,12 @@
     "hooks/",
     "scripts/",
     "templates/",
+    ".claude/",
+    ".claude-plugin/",
+    ".skills/",
     "README.md",
-    "LICENSE"
+    "LICENSE",
+    "CHANGELOG.md"
   ],
   "scripts": {
     "test": "node bin/cli.js --scope=project"
@@ -21,20 +25,20 @@
   "keywords": [
     "claude",
     "claude-code",
+    "agent-skills",
     "api-development",
-    "ui-development",
-    "components",
-    "storybook",
-    "playwright",
     "tdd",
     "test-driven-development",
     "interview-driven",
+    "research-first",
+    "verification",
+    "hooks",
+    "mcp",
     "api-testing",
-    "api-orchestration",
-    "combine",
     "documentation",
     "workflow",
-    "automation"
+    "automation",
+    "cross-platform"
   ],
   "author": "Hustle Together",
   "license": "MIT",
@@ -47,6 +51,13 @@
   },
   "homepage": "https://github.com/hustle-together/api-dev-tools#readme",
   "engines": {
-    "node": ">=14.0.0"
+    "node": ">=18.0.0",
+    "pnpm": ">=10.11.0"
+  },
+  "claudeCode": {
+    "marketplace": ".claude-plugin/marketplace.json",
+    "skills": ".skills",
+    "hooks": ".skills/_shared/hooks",
+    "settings": ".skills/_shared/settings.json"
   }
 }