claude-code-templates 1.21.1 → 1.21.3

package/docu/docs/components/overview.md

@@ -1,287 +0,0 @@
----
-sidebar_position: 1
----
-
-# Individual Components
-
-In addition to complete project templates, **Claude Code Templates** now offers **Individual Components** that can be browsed and installed separately. This gives you granular control over which specific tools and integrations you want to add to your Claude Code setup.
-
-## Component Types
-
-The system provides five distinct types of components:
-
-### 🤖 Agents
-**AI specialists for specific development tasks**
-
-Agents are specialized Claude Code assistants designed to excel in particular areas of development. Each agent comes with domain-specific knowledge and optimized prompts for focused tasks.
-
-**Examples:**
-- `react-performance-optimization` - Specializes in React performance analysis and optimization
-- `api-security-audit` - Focuses on API security best practices and vulnerability detection  
-- `database-optimization` - Expert in database query optimization and schema design
-
-[Learn more about Agents →](./agents)
-
-### ⚡ Commands
-**Custom slash commands for Claude Code**
-
-Commands are pre-built slash commands that extend Claude Code's functionality with project-specific actions. They provide quick access to common development tasks and workflows.
-
-**Examples:**
-- `check-file` - Quickly analyze file structure and potential issues
-- `generate-tests` - Auto-generate test files based on existing code
-- `optimize-imports` - Clean up and optimize import statements
-
-[Learn more about Commands →](./commands)
-
-### 🔌 MCPs (Model Context Protocol)
-**External service integrations**
-
-MCPs enable Claude Code to interact with external services and tools, expanding its capabilities beyond the local development environment.
-
-**Examples:**
-- `github-integration` - Direct GitHub repository interactions
-- `database-integration` - Connect to and query databases directly
-- `deepgraph-react` - Advanced React component analysis and visualization
-
-[Learn more about MCPs →](./mcps)
-
-### ⚙️ Settings
-**Configuration options to customize Claude Code behavior**
-
-Settings are JSON-based configuration components that customize how Claude Code operates. They allow you to configure environment variables, permissions, model preferences, and cleanup policies to match your development workflow.
-
-**Examples:**
-- `allow-npm-commands` - Enable npm-related operations
-- `use-sonnet` - Configure Claude 3.5 Sonnet model
-- `enable-telemetry` - Enable usage analytics and improvements
-
-[Learn more about Settings →](./settings)
-
-### 🪝 Hooks
-**Event-driven automation for Claude Code workflows**
-
-Hooks are powerful automation components that execute shell commands in response to specific Claude Code events. They enable automated workflows, notifications, and integrations that react to your development activities.
-
-**Examples:**
-- `auto-git-add` - Automatically stage modified files with git
-- `telegram-notifications` - Send Telegram messages when work completes
-- `smart-formatting` - Auto-format code using appropriate tools
-
-[Learn more about Hooks →](./hooks)
-
-## Web Interface
-
-The **unified web interface** provides an intuitive way to browse and install individual components:
-
-To access the web interface, simply go to https://aitmpl.com
-
-**Interface Features:**
-- **Unified Filter System**: Browse all component types (Templates, Agents, Commands, MCPs, Settings, Hooks) in a single view
-- **Category Filtering**: Filter by specific component types using the navigation bar
-- **Card Flip Functionality**: Hover over component cards to reveal installation commands
-- **Individual Browsing**: Each component shows detailed information and usage examples
-- **"Add New" Cards**: Easy contribution workflow for adding new components
-
-## Installation Methods
-
-### Complete Templates vs Individual Components
-
-| Method | Use Case | Installation |
-|--------|----------|-------------|
-| **Complete Templates** | Full project setup with multiple components | `npx claude-code-templates@latest --template=react --yes` |
-| **Individual Components** | Selective component installation | `npx claude-code-templates@latest --agent=name --yes` |
-
-### Installation Commands by Type
-
-#### Installing Agents
-Agents can now be installed individually using the `--agent` parameter:
-
-```bash
-# Install specific agents directly
-npx claude-code-templates@latest --agent=react-performance --yes
-npx claude-code-templates@latest --agent=api-security-audit --yes
-npx claude-code-templates@latest --agent=database-optimization --yes
-
-# Install complete template with all agents
-npx claude-code-templates@latest --template=react --yes
-
-# Or browse available agents in the web interface
-npx claude-code-templates@latest
-```
-
-#### Installing Commands
-Commands can now be installed using the `--command` parameter or manually:
-
-```bash
-# Install specific commands using CLI parameter (recommended)
-npx claude-code-templates@latest --command=check-file --yes
-npx claude-code-templates@latest --command=generate-tests --yes
-npx claude-code-templates@latest --command=optimize-imports --yes
-
-# Manual installation (alternative method)
-# Create commands directory first
-mkdir -p .claude/commands
-
-# Download specific commands
-curl -o .claude/commands/check-file.md \
-  https://raw.githubusercontent.com/davila7/claude-code-templates/main/components/commands/check-file.md
-
-curl -o .claude/commands/generate-tests.md \
-  https://raw.githubusercontent.com/davila7/claude-code-templates/main/components/commands/generate-tests.md
-```
-
-#### Installing MCPs
-MCPs can now be installed using the `--mcp` parameter or manually:
-
-```bash
-# Install specific MCPs using CLI parameter (recommended)
-npx claude-code-templates@latest --mcp=github-integration --yes
-npx claude-code-templates@latest --mcp=database-integration --yes
-npx claude-code-templates@latest --mcp=deepgraph-react --yes
-
-# Manual installation (alternative method)
-# Download specific MCPs
-curl -o ./github-integration.json \
-  https://raw.githubusercontent.com/davila7/claude-code-templates/main/components/mcps/github-integration.json
-
-curl -o ./database-integration.json \
-  https://raw.githubusercontent.com/davila7/claude-code-templates/main/components/mcps/database-integration.json
-```
-
-#### Installing Settings
-Settings can be installed using the `--setting` parameter with interactive location selection:
-
-```bash
-# Install specific settings with location prompt
-npx claude-code-templates@latest --setting=permissions/allow-npm-commands
-npx claude-code-templates@latest --setting=model/use-sonnet
-npx claude-code-templates@latest --setting=telemetry/enable-telemetry
-
-# Install to default location (local settings)
-npx claude-code-templates@latest --setting=cleanup/retention-7-days --yes
-
-# Install multiple settings
-npx claude-code-templates@latest --setting=model/use-sonnet,telemetry/enable-telemetry --yes
-```
-
-**Installation Location Options:**
-- **🏠 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 settings** - System-wide policy (requires admin)
-
-#### Installing Hooks
-Hooks can be installed using the `--hook` parameter with location selection:
-
-```bash
-# Install specific hooks with location prompt
-npx claude-code-templates@latest --hook=git-workflow/auto-git-add
-npx claude-code-templates@latest --hook=automation/telegram-notifications
-npx claude-code-templates@latest --hook=development-tools/smart-formatting
-
-# Install to default location (local settings)
-npx claude-code-templates@latest --hook=testing/test-runner --yes
-
-# Install multiple hooks
-npx claude-code-templates@latest --hook=development-tools/file-backup,security/file-protection --yes
-```
-
-**Hook Categories:**
-- **🔧 development-tools** - Essential development workflow automation
-- **🔄 git-workflow** - Git integration and version control
-- **🧪 testing** - Automated testing integration
-- **⚡ automation** - General purpose automation and notifications
-- **🔒 security** - Security monitoring and file protection
-- **📊 performance** - Performance monitoring and optimization
-
-## When to Use Templates vs Components
-
-### Use Complete Templates When:
-- ✅ Setting up a new project from scratch
-- ✅ You want a comprehensive, tested configuration
-- ✅ You're new to Claude Code and want everything configured properly
-- ✅ You prefer opinionated setups with best practices included
-
-### Use Individual Components When:
-- ✅ You have an existing Claude Code setup to enhance
-- ✅ You only need specific functionality (e.g., just GitHub integration)
-- ✅ You want to gradually add capabilities to your workflow
-- ✅ You're experimenting with new tools and integrations
-- ✅ You have custom requirements that don't match standard templates
-
-## Component Discovery
-
-### Via Web Interface
-The primary way to discover components is through the unified web interface:
-
-1. Run `npx claude-code-templates@latest`
-2. Select "⚙️ Project Setup"
-3. Browse components with the unified filter system
-4. Use category filters to focus on specific types
-5. Hover over cards to see installation commands
-
-### Via CLI Parameters
-The quickest way to install components is using dedicated CLI parameters:
-
-```bash
-# Direct component installation
-npx claude-code-templates@latest --agent=react-performance --yes
-npx claude-code-templates@latest --command=check-file --yes
-npx claude-code-templates@latest --mcp=github-integration --yes
-npx claude-code-templates@latest --setting=model/use-sonnet --yes
-npx claude-code-templates@latest --hook=git-workflow/auto-git-add --yes
-```
-
-### Via GitHub Repository
-You can also browse components directly in the repository:
-
-- **Templates**: `/templates/` directory
-- **Agents**: `/components/agents/` directory  
-- **Commands**: `/components/commands/` directory
-- **MCPs**: `/components/mcps/` directory
-- **Settings**: `/components/settings/` directory
-- **Hooks**: `/components/hooks/` directory
-
-## Contributing Components
-
-The system welcomes community contributions! Each component type has "Add New" cards in the web interface that guide you through the contribution process.
-
-**General Contribution Workflow:**
-1. Fork the repository
-2. Add your component to the appropriate directory
-3. Follow the component-specific guidelines
-4. Test your component thoroughly
-5. Submit a pull request with documentation
-
-[Learn more about contributing →](../contributing)
-
-## Best Practices
-
-### Component Selection
-- **Start Small**: Begin with individual components to understand their impact
-- **Test Thoroughly**: Always test components in a development environment first
-- **Read Documentation**: Each component includes specific usage instructions
-- **Check Dependencies**: Ensure your environment supports the component's requirements
-
-### Installation Management
-- **Use Version Control**: Commit your `.claude/` directory to track changes
-- **Document Choices**: Keep notes on why you selected specific components
-- **Regular Updates**: Periodically check for component updates
-- **Backup Configurations**: Save working configurations before adding new components
-
-### Integration Strategy
-- **Gradual Integration**: Add components one at a time to identify issues
-- **Compatibility Testing**: Ensure new components work with existing setup
-- **Performance Monitoring**: Watch for performance impacts after adding components
-- **Workflow Optimization**: Regularly review and optimize your component setup
-
----
-
-**Next Steps:**
-- [Explore Agents →](./agents) - Learn about AI specialists for development tasks
-- [Discover Commands →](./commands) - Find slash commands to enhance your workflow  
-- [Understand MCPs →](./mcps) - Integrate external services with Claude Code
-- [Configure Settings →](./settings) - Customize Claude Code behavior and preferences
-- [Automate with Hooks →](./hooks) - Set up event-driven automation workflows
-- [Browse All Components](https://aitmpl.com) - Visit the web interface

package/docu/docs/components/settings.md

@@ -1,223 +0,0 @@
----
-sidebar_position: 4
----
-
-# ⚙️ Settings
-
-**Configuration options to customize Claude Code behavior**
-
-Settings are JSON-based configuration components that customize how Claude Code operates. They allow you to configure environment variables, permissions, model preferences, and cleanup policies to match your development workflow.
-
-## What are Settings?
-
-Settings are individual configuration files that merge into your Claude Code settings hierarchy. Each setting focuses on a specific aspect of Claude Code configuration, making them modular and easy to manage.
-
-**Key Features:**
-- ⚙️ **Modular Configuration**: Each setting handles one specific aspect
-- 🏗️ **Hierarchical**: Supports user, project, local, and enterprise configurations  
-- 🔧 **Environment Variables**: Configure environment settings
-- 🛡️ **Permissions**: Control what Claude Code can and cannot do
-- 🤖 **Model Selection**: Choose between different Claude models
-- 🧹 **Cleanup Policies**: Manage conversation retention and cleanup
-
-## Available Settings Categories
-
-### 🛡️ Permissions
-Control what operations Claude Code is allowed to perform:
-
-- **`allow-npm-commands`** - Enable npm-related commands
-- **`deny-sensitive-files`** - Prevent modification of sensitive files
-
-### 🤖 Model Configuration
-Choose which Claude model to use:
-
-- **`use-sonnet`** - Configure Claude 3.5 Sonnet (balanced)
-- **`use-haiku`** - Configure Claude 3 Haiku (fast and efficient)
-
-### 📊 Telemetry
-Configure usage analytics and data collection:
-
-- **`enable-telemetry`** - Enable Claude Code usage analytics
-- **`disable-telemetry`** - Disable all telemetry collection
-- **`custom-telemetry`** - Custom telemetry configuration
-
-### 🧹 Cleanup
-Manage conversation history and data retention:
-
-- **`retention-7-days`** - Keep conversations for 7 days
-- **`retention-90-days`** - Keep conversations for 90 days
-
-## Installation Options
-
-Settings can be installed at different levels of your Claude Code configuration hierarchy:
-
-### 🏠 User Settings (`~/.claude/settings.json`)
-- **Scope**: Global - applies to all projects
-- **Use case**: Personal preferences and global configurations
-- **Shared**: No, personal to your user account
-
-### 📁 Project Settings (`.claude/settings.json`)
-- **Scope**: Project-specific 
-- **Use case**: Team-shared configurations, project requirements
-- **Shared**: Yes, committed to version control
-
-### ⚙️ Local Settings (`.claude/settings.local.json`)
-- **Scope**: Project-specific, personal
-- **Use case**: Personal overrides, experimentation, sensitive data
-- **Shared**: No, automatically ignored by git
-
-### 🏢 Enterprise Settings (Platform-specific)
-- **Scope**: System-wide policy
-- **Use case**: Organization-wide policies and restrictions
-- **Requires**: Administrator privileges
-
-**Platform Locations:**
-- macOS: `/Library/Application Support/ClaudeCode/managed-settings.json`
-- Linux/WSL: `/etc/claude-code/managed-settings.json`
-- Windows: `C:\ProgramData\ClaudeCode\managed-settings.json`
-
-## Installation Methods
-
-### Using CLI (Recommended)
-```bash
-# Install with interactive location selection
-npx claude-code-templates@latest --setting=permissions/allow-npm-commands
-
-# Install multiple settings
-npx claude-code-templates@latest --setting=model/use-sonnet,telemetry/enable-telemetry
-
-# Skip location prompt with --yes (defaults to local settings)
-npx claude-code-templates@latest --setting=cleanup/retention-7-days --yes
-```
-
-### Installation Flow
-When you install a setting, you'll be prompted to choose the installation location:
-
-1. **🏠 User settings** - Global configuration
-2. **📁 Project settings** - Shared with team
-3. **⚙️ Local settings** - Personal, not committed (default)
-4. **🏢 Enterprise settings** - System-wide (requires admin)
-
-## Usage Examples
-
-### Basic Permission Setup
-```bash
-# Allow npm commands in this project
-npx claude-code-templates@latest --setting=permissions/allow-npm-commands
-
-# Prevent modification of sensitive files globally
-npx claude-code-templates@latest --setting=permissions/deny-sensitive-files
-```
-
-### Model Configuration
-```bash
-# Use Claude 3.5 Sonnet for this project
-npx claude-code-templates@latest --setting=model/use-sonnet
-
-# Use Claude 3 Haiku for faster responses
-npx claude-code-templates@latest --setting=model/use-haiku
-```
-
-### Telemetry Management
-```bash
-# Enable telemetry for usage analytics
-npx claude-code-templates@latest --setting=telemetry/enable-telemetry
-
-# Disable all telemetry collection
-npx claude-code-templates@latest --setting=telemetry/disable-telemetry
-```
-
-### Cleanup Policies
-```bash
-# Set 7-day retention policy
-npx claude-code-templates@latest --setting=cleanup/retention-7-days
-
-# Set 90-day retention for long-term projects
-npx claude-code-templates@latest --setting=cleanup/retention-90-days
-```
-
-## Setting Structure
-
-Each setting is a JSON file that merges into your Claude Code configuration:
-
-```json
-{
-  "description": "Human-readable description of what this setting does",
-  "env": {
-    "ENVIRONMENT_VARIABLE": "value"
-  },
-  "permissions": {
-    "allow": ["operation1", "operation2"],
-    "deny": ["restricted-operation"]
-  },
-  "model": {
-    "name": "claude-3-5-sonnet-20241022"
-  }
-}
-```
-
-## Conflict Resolution
-
-When installing settings, the CLI will:
-
-1. **Detect Conflicts**: Check if settings would override existing configurations
-2. **Prompt User**: Ask whether to proceed with conflicting changes
-3. **Merge Intelligently**: Combine settings where possible
-4. **Preserve Existing**: Keep current settings unless explicitly overridden
-
-## Best Practices
-
-### Setting Selection
-- **Start Local**: Use local settings for experimentation
-- **Graduate to Project**: Move stable configurations to project settings
-- **Use Enterprise Sparingly**: Only for organization-wide policies
-- **Document Choices**: Keep notes on why specific settings were chosen
-
-### Configuration Management
-- **Version Control**: Commit `.claude/settings.json` for team sharing
-- **Ignore Sensitive**: Keep `.claude/settings.local.json` out of version control
-- **Regular Review**: Periodically audit your settings for relevance
-- **Backup Important**: Save working configurations before major changes
-
-### Security Considerations
-- **Sensitive Data**: Use local settings for API keys and personal tokens
-- **Team Safety**: Be cautious with permission settings in shared projects
-- **Regular Updates**: Keep settings up-to-date with security patches
-- **Least Privilege**: Only enable permissions that are actually needed
-
-## Troubleshooting
-
-### Setting Not Applied?
-- Check setting hierarchy (enterprise > user > project > local)
-- Verify JSON syntax with a validator
-- Restart Claude Code after major setting changes
-- Check for typos in environment variable names
-
-### Permission Denied?
-- Verify the setting allows the operation you're trying to perform
-- Check if enterprise settings override your local configuration
-- Ensure you have necessary system permissions for the operation
-- Review the `permissions.deny` array for blocked operations
-
-### Environment Variables Not Working?
-- Restart your terminal/IDE after setting environment variables
-- Use `echo $VARIABLE_NAME` to verify environment variables are set
-- Check if the setting is in the correct configuration file
-- Verify environment variables are correctly formatted
-
-## Contributing Settings
-
-Want to add a new setting? Follow these guidelines:
-
-1. **Focus on One Thing**: Each setting should configure one specific aspect
-2. **Clear Description**: Include a detailed description of what the setting does
-3. **Safe Defaults**: Use conservative defaults that won't break existing setups
-4. **Documentation**: Include usage examples and potential conflicts
-5. **Testing**: Test with different installation locations and conflict scenarios
-
----
-
-**Next Steps:**
-- [Explore Hooks →](./hooks) - Learn about automation and event-driven actions
-- [Browse All Settings](https://aitmpl.com) - View available settings in the web interface
-- [Contributing Guide →](../contributing) - Add your own settings to the collection

package/docu/docs/components/slack-notifications.md

@@ -1,67 +0,0 @@
-# Slack Notifications
-
-Get instant Slack notifications when Claude Code finishes working.
-
-## Quick Setup
-
-### 1. Create Slack App
-
-1. Go to [api.slack.com/apps](https://api.slack.com/apps)
-2. **Create New App** → **From scratch**
-3. Name it "Claude Code Notifier"
-4. Select your workspace
-
-### 2. Enable Webhook
-
-1. Go to **Features** → **Incoming Webhooks**
-2. Toggle **Activate Incoming Webhooks** to ON
-3. **Add New Webhook to Workspace**
-4. Select your channel (e.g., #dev-notifications)
-5. **Copy the Webhook URL**
-
-### 3. Install Hook
-
-```bash
-# Basic notifications
-npx claude-code-templates@latest --hook automation/slack-notifications
-
-# Rich block notifications with session details
-npx claude-code-templates@latest --hook automation/slack-detailed-notifications
-
-# Long operation monitoring
-npx claude-code-templates@latest --hook automation/slack-error-notifications
-```
-
-### 4. Set Environment Variable
-
-```bash
-# Temporary (current session)
-export SLACK_WEBHOOK_URL="https://hooks.slack.com/services/YOUR_WEBHOOK_URL"
-
-# Permanent (add to ~/.zshrc or ~/.bashrc)
-echo 'export SLACK_WEBHOOK_URL="https://hooks.slack.com/services/YOUR_WEBHOOK_URL"' >> ~/.zshrc
-source ~/.zshrc
-```
-
-### 5. Test
-
-```bash
-curl -X POST $SLACK_WEBHOOK_URL \
-     -H 'Content-type: application/json' \
-     -d '{"text":"🧪 Test notification"}'
-```
-
-## What You Get
-
-- **Session completion** → "🤖 Claude Code finished working"
-- **Rich blocks** → Structured messages with project info, duration, memory usage
-- **Long operation alerts** → Warnings for commands taking >30 seconds
-- **Team collaboration** → Perfect for development teams
-
-## Environment Variable
-
-The hook requires `SLACK_WEBHOOK_URL` to be set in your environment.
-
-Your webhook URL format: `https://hooks.slack.com/services/T.../B.../...`
-
-That's it! The hook works automatically once installed and configured.

package/docu/docs/components/telegram-notifications.md

@@ -1,73 +0,0 @@
-# Telegram Notifications
-
-Get instant Telegram notifications when Claude Code finishes working.
-
-## Quick Setup
-
-### 1. Create Telegram Bot
-
-1. Open Telegram and search for **@BotFather**
-2. Send `/newbot` command
-3. Choose a name: "Claude Code Notifier"
-4. Choose username: "your_bot_name_bot"
-5. **Copy the Bot Token** (looks like `123456789:ABCdef...`)
-
-### 2. Get Chat ID
-
-1. Send any message to your new bot
-2. Open this URL in browser (replace YOUR_BOT_TOKEN):
-   ```
-   https://api.telegram.org/botYOUR_BOT_TOKEN/getUpdates
-   ```
-3. Find `"chat":{"id":123456789}` in the response
-4. **Copy the Chat ID** (the number)
-
-### 3. Install Hook
-
-```bash
-# Basic notifications
-npx claude-code-templates@latest --hook automation/telegram-notifications
-
-# Detailed notifications with session info
-npx claude-code-templates@latest --hook automation/telegram-detailed-notifications
-
-# Long operation monitoring
-npx claude-code-templates@latest --hook automation/telegram-error-notifications
-```
-
-### 4. Set Environment Variables
-
-```bash
-# Temporary (current session)
-export TELEGRAM_BOT_TOKEN="123456789:ABCdef..."
-export TELEGRAM_CHAT_ID="987654321"
-
-# Permanent (add to ~/.zshrc or ~/.bashrc)
-echo 'export TELEGRAM_BOT_TOKEN="123456789:ABCdef..."' >> ~/.zshrc
-echo 'export TELEGRAM_CHAT_ID="987654321"' >> ~/.zshrc
-source ~/.zshrc
-```
-
-### 5. Test
-
-```bash
-curl -X POST "https://api.telegram.org/bot$TELEGRAM_BOT_TOKEN/sendMessage" \
-     -d "chat_id=$TELEGRAM_CHAT_ID" \
-     -d "text=🧪 Test notification"
-```
-
-## What You Get
-
-- **Session completion** → "🤖 Claude Code finished working"
-- **Detailed session info** → Project name, duration, memory usage
-- **Long operation alerts** → Warnings for commands taking >30 seconds
-- **Mobile first** → Perfect for staying updated on your phone
-
-## Environment Variables
-
-The hook requires two environment variables:
-
-- `TELEGRAM_BOT_TOKEN` - Your bot token from BotFather
-- `TELEGRAM_CHAT_ID` - Your chat ID number
-
-That's it! The hook works automatically once installed and configured.

package/docu/docs/contributing.md

@@ -1,11 +0,0 @@
----
-sidebar_position: 1
----
-
-# Contributing
-
-We welcome contributions from the open source community! This project thrives on community input and collaboration.
-
-**Please read our [Code of Conduct](https://github.com/davila7/claude-code-templates/blob/main/CODE_OF_CONDUCT.md) before contributing to ensure a welcoming environment for everyone.**
-
-**See [CONTRIBUTING.md](https://github.com/davila7/claude-code-templates/blob/main/CONTRIBUTING.md) for detailed guidelines**

package/docu/docs/health-check/overview.md

@@ -1,33 +0,0 @@
----
-sidebar_position: 1
----
-
-# Health Check Overview
-
-The `claude-code-templates` CLI provides a comprehensive health check feature to validate your Claude Code configuration and system environment. This ensures that your setup is optimal for running Claude Code and helps identify any potential issues.
-
-## Running the Health Check
-
-You can run the comprehensive diagnostics on your Claude Code setup using the following command:
-
-```bash
-npx claude-code-templates --health-check
-# or
-npx claude-code-templates --health
-# or
-npx claude-code-templates --check
-# or
-npx claude-code-templates --verify
-```
-
-## What the Health Check Analyzes
-
-The health check performs a complete system validation and configuration verification, including:
-
--   **System Requirements**: Validates your operating system, Node.js version, memory, and network connectivity.
--   **Claude Code Setup**: Verifies Claude Code installation, authentication, and permissions.
--   **Project Configuration**: Checks your project structure and configuration files, including `CLAUDE.md` files.
--   **Custom Commands**: Validates your custom slash commands and their syntax.
--   **Hooks Configuration**: Verifies the availability and correct configuration of your automation hooks.
--   **Interactive Results**: Provides real-time progress with immediate feedback and recommendations.
--   **Health Score**: Presents an overall system health percentage with actionable insights and performance optimization recommendations.