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

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

@@ -12,8 +12,10 @@ allowed-tools: WebSearch WebFetch mcp__context7 mcp__github AskUserQuestion Read
 ---
 
 ---
+
 description: Clean up merged worktrees by verifying PR/issue status, consolidating settings, and removing stale worktrees
 argument-hint: (no arguments)
+
 ---
 
 # Worktree Cleanup
@@ -37,191 +39,186 @@ Current worktrees: !git worktree list`
 
 <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>
+<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>
+<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>
@@ -239,8 +236,7 @@ Current worktrees: !git worktree list`
 - 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>
-
+  </important_notes>
 
 ## 🛡 Project Rules (Injected into every command)
 
@@ -266,7 +262,7 @@ Current worktrees: !git worktree list`
 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
@@ -291,4 +287,4 @@ Current worktrees: !git worktree list`
      - Code examples
      - Testing notes
    - Document expected behavior and edge cases
-   - Include real-world output examples
+   - Include real-world output examples

package/CHANGELOG.md

@@ -1,97 +1,115 @@
 # 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
+All notable changes to this project will be documented in this file.
+
+## [1.0.1] - 2025-12-28
 
 ### 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
+- **Stop hook false positive blocking**: Fixed bug where `api-workflow-check.py` incorrectly blocked Q&A sessions when no workflow was active. The hook now correctly checks for both `None` and `"not_started"` phase statuses.
+
+---
+
+## [1.0.0] - 2025-12-28
+
+### Initial Release
+
+Interview-driven, research-first API development toolkit with 14-phase TDD workflow.
+
+### Core Features
+
+**Four Main Workflows:**
+
+- `/api-create [endpoint]` - Complete 14-phase API endpoint development
+- `/hustle-ui-create [name]` - Component development with Storybook
+- `/hustle-ui-create-page [name]` - Page development with Playwright E2E
+- `/hustle-combine [type]` - Orchestrate multiple existing APIs
+
+**14-Phase Workflow:**
+
+1. Disambiguation - Clarify ambiguous terms
+2. Scope - Confirm understanding
+3. Initial Research - Context7 + WebSearch (with async parallel subagents)
+4. Interview - Questions FROM research findings
+5. Deep Research - Adaptive searches based on answers
+6. Schema - Zod schema from research + interview
+7. Environment - Verify API keys exist
+8. TDD Red - Write failing tests
+9. TDD Green - Minimal implementation to pass
+10. Verify - Re-research and compare to implementation
+11. Code Review - Greptile AI-powered review (catches issues early)
+12. TDD Refactor - Fix review issues + clean up code
+13. Documentation - Update manifests, cache research
+14. Completion - Final commit and PR
+
+**23 Enforcement Hooks:**
+
+- SessionStart: State context injection
+- UserPromptSubmit: Research requirement detection
+- PreToolUse: Block writes until phases complete
+- PostToolUse: Auto-format, token tracking, notifications, code review
+- Stop: Block if workflow incomplete
+
+**Greptile AI Code Review (Phase 11):**
+
+- Runs BEFORE refactoring so issues can be fixed
+- Bug detection with full codebase context
+- Security vulnerability scanning (OWASP top 10)
+- Performance issue identification
+- Returns actionable issues with file:line references
+- Requires: GREPTILE_API_KEY + GITHUB_TOKEN
+
+**Async Parallel Research:**
+
+- Spawn multiple research subagents in parallel
+- Use Ctrl+B to background agents
+- Use /tasks to monitor progress
+- 3x faster research with parallel Context7 + WebSearch
+
+**7 Subagents:**
+
+- `parallel-researcher` (Haiku) - Parallel documentation scraping
+- `research-validator` (Haiku) - Find all endpoints and webhooks
+- `docs-generator` (Haiku) - TypeDoc generation
+- `schema-generator` (Sonnet) - Zod schema creation
+- `test-writer` (Sonnet) - Comprehensive test generation
+- `implementation-reviewer` (Sonnet) - Compare code to docs
+- `code-reviewer` (Sonnet) - Security and performance review
 
-### 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`
+**NTFY Push Notifications:**
 
-### Changed
-- Updated BRAND_GUIDE.md with complete Hustle brand
-- Enhanced showcase components with dark mode support
-- Boxy 90s styling with 2px borders
+- Phase completion updates
+- Input needed alerts (interview questions)
+- Token usage per phase
+- `/ntfy-setup` and `/ntfy-test` commands
 
-## [3.9.0] - 2025-12-08
+**Component Type System:**
 
-### 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`
+- Basic components (single-purpose, few props)
+- Complex components (multi-part, user flows)
+- AI suggests type, user confirms via hook
 
-## [3.8.0] - 2025-12-05
+**CLI Installer:**
 
-### Added
-- `/hustle-combine` command for API orchestration
-- Registry.json central tracking
-- Combined entry support in update-registry.py
-- Orchestration flow types: sequential, parallel, conditional
+- ASCII art banner with Hustle branding
+- 8-step progress indicators
+- Animated spinners for long operations
+- Optional tools: Storybook, Playwright, Sandpack
 
-## [3.7.0] - 2025-12-01
+**Additional Commands:**
 
-### 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/
+- TDD: `/red`, `/green`, `/refactor`, `/cycle`
+- Git: `/commit`, `/pr`, `/busycommit`
+- Planning: `/plan`, `/gap`, `/issue`
+- Worktrees: `/worktree-add`, `/worktree-cleanup`
 
-## [3.6.7] - 2025-11-28
+**Infrastructure:**
 
-### Added
-- Phase 13 completion output with curl examples
-- Scope coverage report
-- Research cache location in output
-- Gap fixes for file tracking and verification
+- State tracking in `.claude/api-dev-state.json`
+- Research cache with 7-day freshness
+- Registry for all created APIs/components
+- Environment template in `templates/.env.example`
 
 ---
 
-Note: v3.x is the final major version. All future updates will be v3.x.y releases.
+See [ROADMAP.md](./ROADMAP.md) for planned features.