New Features:
- 🎯 Single prompt for batch installations - ask locations once for all components
- ✅ Accurate success counting - shows actual vs attempted installations
- 📝 General terminology - 'configuration components' instead of 'settings and hooks'
Improvements:
- ⚠️ Clear error messages when installations fail due to permissions
- 🔄 Consistent location selection across all components in batch mode
- 📋 Better feedback showing selected locations before installation
- 🎨 Cleaner user experience with no repeated prompts
Bug Fixes:
- Fixed misleading success messages when some locations fail
- Fixed repetitive prompts during batch installations
- Fixed inconsistent default locations between silent and interactive modes
Available on npm: npm install -g claude-code-templates@latest
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Change 'settings and hooks' to 'configuration components'
- More flexible terminology that doesn't expose internal categorization
- Cleaner user experience with generic language
Before:
📍 Choose installation locations for settings and hooks:
? Where would you like to install settings and hooks?
📋 Will install settings and hooks in: user, local
After:
📍 Choose installation locations for configuration components:
? Where would you like to install the configuration components?
📋 Will install configuration components in: user, local
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Ask installation locations ONCE at the beginning for all settings and hooks
- Eliminate repeated prompts during batch installation
- Add sharedInstallLocations parameter to individual functions
- Use shared locations when provided, fall back to individual prompts otherwise
- Show clear message about selected locations before installation begins
Flow:
1. User runs: --setting=model/use-sonnet,telemetry/enable-telemetry
2. CLI asks ONCE: 'Where would you like to install settings and hooks?'
3. User selects locations (e.g., user, project, local)
4. CLI shows: 'Will install settings and hooks in: user, project, local'
5. All settings install to those same locations automatically
6. No additional prompts, CLI exits after completion
Prevents the frustrating loop where each component shows its own
installation menu, creating a better user experience for batch operations.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Add successfulInstallations counter to track actual successful installations
- Show accurate count in summary messages instead of total attempted
- Differentiate between complete success and partial success:
- 🎉 Green message when all locations successful
- ⚠️ Yellow message when some locations failed
- ❌ Red details showing number of failed installations
- Prevents misleading 'successfully installed in 4 location(s)!' when only 3 succeeded
Example outputs:
✅ All successful: '🎉 Setting installed in 3 location(s)!'
⚠️ Partial success: '⚠️ Setting installed in 3 of 4 location(s).'
'❌ 1 installation(s) failed due to permission or other errors.'
Fixes the case where enterprise settings fail due to permission denied
but user still sees success message for all locations.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Settings and hooks now support checkbox selection for multiple installation locations
- Users can install the same component in multiple environments simultaneously:
- 🏠 User Settings (~/.claude/settings.json) - Global
- 📁 Project Settings (.claude/settings.json) - Team shared
- ⚙️ Local Settings (.claude/settings.local.json) - Personal
- 🏢 Enterprise Settings - System-wide (requires admin)
- Interactive prompts show checkbox interface with validation
- Each location is processed independently with conflict detection
- Progress messages show installation status for each location
- Tracking includes installation_location for analytics
- Graceful error handling - failed locations don't stop others
- Summary message shows total installations completed
Example: Install allow-npm-commands in both user and project settings
for global availability plus team sharing.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Settings and hooks now show interactive prompts for installation location
- Fixed inconsistency between silent mode default and interactive mode default
- Both now default to 'local' settings (.claude/settings.local.json)
- Respects --yes flag to skip prompts when needed
- Users will now see the 4 installation options:
- 🏠 User Settings (~/.claude/settings.json) - Global
- 📁 Project Settings (.claude/settings.json) - Team shared
- ⚙️ Local Settings (.claude/settings.local.json) - Personal
- 🏢 Enterprise Settings - System-wide (requires admin)
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Added detailed Settings documentation (300+ lines) covering all configuration hierarchy levels
- Added comprehensive Hooks documentation (400+ lines) with event-driven automation examples
- Created Telegram notification hooks with complete setup guide
- Updated overview page to include Settings and Hooks as new component types
- Updated sidebar navigation to include new documentation sections
- Documented installation location selection for both Settings and Hooks
- Added security guidelines, troubleshooting, and best practices
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
✨ New Features:
- Interactive prompt to choose installation location for settings and hooks
- Support for all Claude Code configuration files hierarchy:
• User settings (~/.claude/settings.json) - Global for all projects
• Project settings (.claude/settings.json) - Shared with team
• Local settings (.claude/settings.local.json) - Personal, not committed
• Enterprise managed settings - System-wide policy (requires admin)
🖥️ Platform Support:
- macOS: /Library/Application Support/ClaudeCode/managed-settings.json
- Linux/WSL: /etc/claude-code/managed-settings.json
- Windows: C:\ProgramData\ClaudeCode\managed-settings.json
🔧 Technical Improvements:
- Unified installation logic for both hooks and settings
- Admin privilege detection and error handling for enterprise settings
- Proper directory creation for different installation locations
- Clear user feedback about target paths and requirements
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
✅ Fixed ALL remaining hooks (20 total):
- Updated post-tool/ and pre-tool/ hooks to Claude Code array format
- Fixed git-add-changes, format-javascript-files, format-python-files, run-tests-after-changes
- Fixed backup-before-edit, notify-before-bash
🧠 Added AI Hook Specification System:
- CLAUDE_HOOK_SPECIFICATION.md - Complete hook format guide for AI
- AI_HOOK_TEMPLATE.json - Structured template with examples for AI parsing
- HOOK_PATTERNS_COMPRESSED.json - Compressed patterns for rapid AI reference
📊 Technical Improvements:
- All 20 hooks now use proper array/matcher structure
- Regenerated components.json with corrected hook metadata
- Added comprehensive validation rules and anti-patterns
- Included environment variables and cross-platform compatibility guides
🎯 AI Context Enhancement:
- Future Claude Code sessions can reference these files for correct hook generation
- Compressed format optimizes AI parsing while maintaining completeness
- Common patterns and validation rules prevent structure errors
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Fixed CLI hook installation logic to properly handle Claude Code array format
- Improved hook merging to support both old and new formats during migration
- Published to npm with corrected hook processing capabilities
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Update all 14 hooks to use proper Claude Code array/matcher format
- Fix CLI merge logic to handle new hook structure correctly
- Add support for both old and new hook formats during migration
- Remove conflict detection for hooks (Claude Code arrays support multiple entries)
- Ensure hooks follow proper structure:
{
"hooks": {
"EventName": [
{
"matcher": "ToolPattern",
"hooks": [
{"type": "command", "command": "bash-command"}
]
}
]
}
}
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Add Unity Game Developer agent for Unity-specific development
- Add Unreal Engine Developer agent for Epic Games/Unreal development
- Add Unity project setup command for project initialization
- Support game development workflows and best practices
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Add 9 Settings components (telemetry, permissions, model, cleanup)
- Add 6 Hooks components (formatting, git integration, backups, testing)
- Implement CLI installation with --setting and --hook flags
- Add conflict detection that prompts user before overwriting
- Merge settings into .claude/settings.json with intelligent deep merge
- Update data-loader.js to handle new component types
- Add filter buttons for Settings and Hooks in web interface
- Generate components.json with new Settings and Hooks sections
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Added mobile-first chats interface in Quick Start section
- Highlighted --tunnel option with Cloudflare installation requirements
- Updated Core Features with new mobile interface and tunnel support
- Added installation instructions for cloudflared across platforms
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Added padding-bottom to chat-messages container
- Footer now has proper spacing and doesn't cover content
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Add Shopify-style cart sidebar with drag-from-right animation
- Implement Add to Stack buttons for all component cards
- Create dynamic command generation for agents, commands, and MCPs
- Add cart state management with localStorage persistence
- Implement notification system with auto-dismiss
- Add social sharing for X/Twitter and Threads
- Create overlay copy buttons for command text in cards and cart
- Optimize card layout grid system (4 columns desktop, 2 tablet, 1 mobile)
- Add cart floating button with item count badge
- Fix scroll prevention and notification persistence issues
- Remove quotes from agent parameters in generated commands
- Implement compact cart item design with Clear All repositioning
- Add comprehensive cart styling with responsive design
- Include share functionality with proper URL encoding
- Update CLI package version to 1.14.16 for npm compatibility
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Add description field to MCP JSON files for frontend display
- Update generate_components_json.py to extract MCP descriptions
- Modify CLI to exclude description field from downloaded .mcp.json files
- Update frontend to display MCP descriptions in component cards
- Implement separate description handling for MCPs vs other components
Key changes:
• MCP JSON files now include description field above mcpServers
• Python script extracts descriptions into separate field in components.json
• CLI automatically removes description field during installation
• Frontend shows descriptive text for MCP cards using description field
• Maintains backward compatibility with existing MCP installations
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Update components.json with latest data
- Clean up temporary test directories and files
- Prepare for merge to main branch
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Implement exponential backoff for GitHub API rate limits (5 retries max)
- Add sophisticated rate limit detection with exact wait times
- Handle missing files/directories gracefully instead of failing completely
- Add comprehensive download statistics and progress tracking
- Distinguish between different types of 403 errors (rate limit vs permissions)
- Continue installation even when some template files are unavailable
- Provide detailed summary of successful, skipped, and failed downloads
- Support workflow where some templates may have missing optional files
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
## Major Features Added
### 🏗️ Templates System Overhaul
- **New data source**: Templates now load from `components.json` generated from `cli-tool/templates/`
- **Enhanced structure**: Support for both language and framework templates
- **Recursive file scanning**: Includes `.claude/` folder contents (agents, commands, settings)
- **Smart categorization**: Language-based category filters for templates
- **Proper install commands**: `--template=python --yes` for languages, `--template=django --yes` for frameworks
### 📦 Template Management
- **Updated generate_components_json.py**: Scans `cli-tool/templates/` recursively
- **File inventory**: Tracks all template files including Claude Code configuration
- **Template modal**: Shows complete file list for each template
- **GitHub integration**: Direct links to template folders
### 🎨 UI/UX Improvements
- **Card flip animations**: Restored original template card functionality from script.js
- **MCP optimization**: Removed unnecessary descriptions from MCP cards and modals
- **Category filters**: Templates now show language-based filters (python, ruby, etc.)
- **Filter reset**: Switching main filters automatically resets category selection
- **Enhanced modals**: Comprehensive template contribution guide with language vs framework instructions
### 🔧 Code Organization
- **Structured directories**: Moved all CSS files to `css/` and JS files to `js/`
- **Updated references**: All HTML files now reference organized file paths
- **Better maintainability**: Cleaner project structure for future development
### 🚀 Enhanced Contribution Flow
- **Detailed template modal**: Step-by-step guide for contributing languages vs frameworks
- **Required file structure**: Clear documentation of Claude Code configuration files
- **GitHub workflow**: Proper git commands and testing instructions
## Technical Improvements
- Fixed card flip functionality conflicts
- Enhanced pagination system
- Improved modal management
- Better error handling and fallbacks
- Consistent styling across components
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
## 🔧 Workflow Builder Web Interface
- **Drag-and-Drop Canvas**: Visual workflow building with sortable steps
- **Component Library**: Browse and search all agents, commands, and MCPs
- **Real-time Preview**: Live workflow statistics and step management
- **Hash Generation**: Secure workflow encoding with CryptoJS
- **YAML Export**: Generate executable workflow files
- **Modal Interface**: Professional workflow generation dialog
## ⚡ CLI Workflow Installation
- **--workflow option**: Install workflows from hash (format: #hash)
- **Batch Installation**: Download all workflow components automatically
- **Silent Mode**: Clean output when installing multiple components
- **YAML Generation**: Create step-by-step execution files
- **Error Handling**: Comprehensive validation and user guidance
## 🎨 UI/UX Features
- **Responsive Design**: Works on desktop and mobile devices
- **Professional Styling**: Clean, modern interface with proper theming
- **Interactive Components**: Hover effects, drag feedback, and animations
- **Search Functionality**: Filter components by name and category
- **Navigation Integration**: Added workflows link to main header
## 🔗 Architecture
- **Modular Frontend**: Separate CSS and JS files for maintainability
- **GitHub Integration**: Dynamic component loading from organized categories
- **Local Storage**: Workflow state management for hash generation
- **Component Tracking**: Analytics integration for usage monitoring
## 🚀 Workflow Execution Flow
1. **Build**: Create workflows in drag-and-drop interface
2. **Generate**: Export hash and YAML configuration
3. **Install**: Use CLI with generated hash to download all components
4. **Execute**: Use YAML file with Claude Code for step-by-step automation
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
* feat: add support for agent subcategories with dynamic GitHub discovery
- Support agent installation from subcategories (e.g., deep-research-team/academic-researcher)
- Add dynamic GitHub API integration to discover available agents in real-time
- Automatically organize agents by category folders
- Preserve folder structure when installing categorized agents
- Add comprehensive agent teams from merged PR #46:
- Deep Research Team (9 specialized research agents)
- FFmpeg Clip Team (6 media processing agents)
- MCP Development Team (5 MCP server agents)
- Obsidian Operations Team (5 knowledge management agents)
- OCR Extraction Team (5 text processing agents)
- Podcast Creator Team (9 content creation agents)
- Plus individual specialized agents
Technical improvements:
- Remove hardcoded agent lists in favor of GitHub repository scanning
- Support both 'agent-name' and 'category/agent-name' formats
- Fallback mechanism when GitHub API is unavailable
- Maintains backward compatibility with existing CLI usage
- Real-time agent discovery without requiring CLI updates
Usage examples:
- cct --agent api-security-audit (existing agents)
- cct --agent deep-research-team/academic-researcher (new categorized agents)
- cct --agent help (shows all available agents dynamically)
Co-authored-by: Cam10001110101 <cameron@cameronrohn.com>
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
* feat: add support for new DeepGraph components and enhance filtering functionality
---------
Co-authored-by: Claude <noreply@anthropic.com>
- Support agent installation from subcategories (e.g., deep-research-team/academic-researcher)
- Add dynamic GitHub API integration to discover available agents in real-time
- Automatically organize agents by category folders
- Preserve folder structure when installing categorized agents
- Add comprehensive agent teams from merged PR #46:
- Deep Research Team (9 specialized research agents)
- FFmpeg Clip Team (6 media processing agents)
- MCP Development Team (5 MCP server agents)
- Obsidian Operations Team (5 knowledge management agents)
- OCR Extraction Team (5 text processing agents)
- Podcast Creator Team (9 content creation agents)
- Plus individual specialized agents
Technical improvements:
- Remove hardcoded agent lists in favor of GitHub repository scanning
- Support both 'agent-name' and 'category/agent-name' formats
- Fallback mechanism when GitHub API is unavailable
- Maintains backward compatibility with existing CLI usage
- Real-time agent discovery without requiring CLI updates
Usage examples:
- cct --agent api-security-audit (existing agents)
- cct --agent deep-research-team/academic-researcher (new categorized agents)
- cct --agent help (shows all available agents dynamically)
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-authored-by: Claude <noreply@anthropic.com>
- Add automated workflow to publish CLI package to GitHub Packages
- Configure package scoping with @davila7/claude-code-templates
- Include version bumping and automatic GitHub releases
- Add .npmrc for proper registry configuration
- Support both manual triggers and release-based publishing
Package will be available as:
npm install -g @davila7/claude-code-templates --registry=https://npm.pkg.github.com🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Released with MCP installation deep merge fix
- Fixes MCP server configuration overwriting issues
- Published to npm registry
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Fix MCP installation overwriting existing mcpServers configurations
- Add deep merge logic specifically for mcpServers key to preserve existing MCP entries
- Ensure individual MCP installations (--mcp=<name>) properly merge with existing .mcp.json
- Tested with multiple MCP installations (memory-integration, filesystem-access)
Fixes issue where installing a new MCP would overwrite all existing MCP server configurations
due to shallow merge behavior of spread operator.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-authored-by: Claude <noreply@anthropic.com>
daniel