claude-code-templates 1.21.13 → 1.22.1

package/docu/docs/components/commands.md

@@ -1,90 +0,0 @@
----
-sidebar_position: 3
----
-
-# Commands
-
-Custom slash commands that automate development workflows. Browse and install from **[aitmpl.com](https://aitmpl.com)**.
-
-## ⚡ What are Commands?
-
-Commands are custom slash commands for Claude Code that automate common development tasks. Type `/command-name` in Claude Code to execute them.
-
-## Installation
-
-### 📦 Basic Installation
-Install this component locally in your project. Works with your existing Claude Code setup.
-
-```bash
-npx claude-code-templates@latest --command testing/generate-tests --yes
-```
-
-### Multiple Commands
-```bash
-npx claude-code-templates@latest --command setup/setup-testing,performance/optimize-bundle --yes
-```
-
-## 💡 Usage After Installation
-
-Once installed, use commands in Claude Code:
-```
-/generate-tests
-/optimize-bundle
-/security-audit
-/setup-testing
-```
-
-## 📁 Command Categories
-
-Browse commands by workflow area to find the right automation for your needs:
-
-### Setup & Configuration
-Project initialization and foundation setup. Examples: `setup-ci-cd-pipeline` for automated builds, `setup-testing` for test frameworks, `migrate-to-typescript` for type safety.
-
-### Testing
-Test automation and quality assurance workflows. Examples: `generate-tests` for automatic test creation, `setup-e2e` for end-to-end testing, `test-coverage` for coverage analysis.
-
-### Performance
-Optimization and performance analysis tools. Examples: `optimize-bundle` for build optimization, `performance-audit` for speed analysis, `add-caching` for performance improvements.
-
-### Database
-Database operations and management automation. Examples: `supabase-migration-assistant` for schema changes, `supabase-security-audit` for database security, `supabase-type-generator` for TypeScript types.
-
-### Documentation
-Documentation generation and maintenance tools. Examples: `generate-api-docs` for API documentation, `update-readme` for project documentation, `create-guide` for user guides.
-
-### Security
-Security analysis and hardening automation. Examples: `security-audit` for vulnerability scanning, `dependency-audit` for package security, `fix-vulnerabilities` for security patches.
-
-## 🎯 How to Choose Commands
-
-Select commands based on your current workflow needs:
-
-### By Development Phase
-- **Project Start**: Begin with `setup/*` commands for foundation setup
-- **Development**: Use `testing/*` and `documentation/*` for quality workflows
-- **Pre-launch**: Add `security/*` and `performance/*` for optimization
-- **Maintenance**: Focus on `database/*` and `performance/*` for ongoing operations
-
-### By Technology Stack
-- **Supabase projects**: Choose `database/supabase-*` commands for database management
-- **React applications**: Use `performance/optimize-bundle` for build optimization
-- **API projects**: Select `documentation/generate-api-docs` for API documentation
-- **Any project**: Start with `setup/setup-testing` for quality foundation
-
-### By Current Challenges
-- **Slow builds**: Use `performance/optimize-bundle` for build optimization
-- **Missing tests**: Choose `testing/generate-tests` for test automation
-- **Security concerns**: Select `security/security-audit` for vulnerability assessment
-- **Poor documentation**: Pick `documentation/update-readme` for documentation improvements
-
-## 🔧 Pro Tips
-
-- **Install setup commands first** for new projects
-- **Use testing commands early** in development
-- **Add security commands** before deployment
-- **Browse [aitmpl.com](https://aitmpl.com)** for specific workflows
-
----
-
-**Find more commands:** [Browse all commands on aitmpl.com](https://aitmpl.com) → Filter by "Commands"

package/docu/docs/components/hooks.md

@@ -1,114 +0,0 @@
----
-sidebar_position: 4
----
-
-# Hooks
-
-Automation triggers that execute actions based on events. Browse and install from **[aitmpl.com](https://aitmpl.com)**.
-
-## 🪝 What are Hooks?
-
-Hooks are automation scripts that trigger actions when specific events occur in your development workflow. They run automatically in the background.
-
-## Installation
-
-### 📦 Basic Installation
-Install this component locally in your project. Works with your existing Claude Code setup.
-
-```bash
-npx claude-code-templates@latest --hook git/auto-git-add --yes
-```
-
-### Multiple Hooks
-```bash
-npx claude-code-templates@latest --hook notifications/discord-notifications,git/smart-commit --yes
-```
-
-## ⚙️ Hook Configuration
-
-Most hooks require configuration after installation:
-
-### Environment Variables
-```bash
-# Notification hooks
-DISCORD_WEBHOOK_URL=your_discord_webhook
-SLACK_WEBHOOK_URL=your_slack_webhook
-TELEGRAM_BOT_TOKEN=your_telegram_token
-
-# Deployment hooks
-DEPLOY_API_KEY=your_deploy_key
-STAGING_URL=your_staging_url
-PRODUCTION_URL=your_production_url
-```
-
-## 🔄 Hook Events
-
-Hooks trigger on various events:
-- **File changes** → `git/auto-git-add`
-- **Commits** → `git/pre-commit-validation`
-- **File save** → `quality/lint-on-save`
-- **Test run** → `testing/coverage-reporter`
-
-## 🛠️ Managing Hooks
-
-### Enable/Disable Hooks
-```bash
-# Disable a hook
-echo '{"enabled": false}' > .claude/hooks/discord-notifications.json
-
-# Re-enable a hook
-echo '{"enabled": true}' > .claude/hooks/discord-notifications.json
-```
-
-## 📁 Hook Categories
-
-Browse hooks by automation area to add the right triggers for your workflow:
-
-### Git Automation
-Automatic Git operations and version control workflows. Examples: `auto-git-add` for automatic staging, `smart-commit` for intelligent commits, `pre-commit-validation` for quality checks.
-
-### Notifications
-Real-time alerts to communication platforms. Examples: `discord-notifications` for Discord alerts, `slack-notifications` for team updates, `telegram-notifications` for mobile alerts.
-
-### Testing & Quality
-Automated testing and code quality enforcement. Examples: `auto-test-runner` for continuous testing, `coverage-reporter` for test metrics, `lint-on-save` for code quality.
-
-### Performance Monitoring
-Performance tracking and system optimization. Examples: `performance-monitor` for system metrics, `memory-tracker` for resource usage, `build-time-tracker` for compilation monitoring.
-
-### Deployment
-Automated deployment and CI/CD triggers. Examples: `auto-deploy` for automatic deployment, `staging-deploy` for environment management, `production-guard` for safety checks.
-
-### Documentation
-Automatic documentation maintenance. Examples: `auto-doc-update` for documentation sync, `changelog-generator` for release notes, `api-doc-sync` for API documentation.
-
-## 🎯 How to Choose Hooks
-
-Select hooks based on your team structure and automation needs:
-
-### By Team Size
-- **Solo projects**: Use `auto-git-add` and `performance-monitor` for personal productivity
-- **Small teams**: Add `slack-notifications` and `auto-test-runner` for coordination
-- **Large teams**: Include `pre-commit-validation` and `production-guard` for safety
-
-### By Project Type
-- **Web applications**: Choose `auto-test-runner` and `auto-deploy` for development automation
-- **Open source libraries**: Use `changelog-generator` and `lint-on-save` for maintenance
-- **API services**: Select `performance-monitor` and `api-doc-sync` for service management
-
-### By Development Stage
-- **Active development**: Focus on `auto-git-add` and `lint-on-save` for productivity
-- **Testing phase**: Use `coverage-reporter` and `slack-notifications` for visibility
-- **Production**: Add `production-guard` and `deployment-metrics` for reliability
-
-## 💡 Pro Tips
-
-- **Start with Git hooks** for basic automation
-- **Add notifications** for team coordination
-- **Use testing hooks** for quality assurance
-- **Monitor performance** with tracking hooks
-- **Browse [aitmpl.com](https://aitmpl.com)** for specialized automation
-
----
-
-**Find more hooks:** [Browse all hooks on aitmpl.com](https://aitmpl.com) → Filter by "Hooks"

package/docu/docs/components/mcps.md

@@ -1,109 +0,0 @@
----
-sidebar_position: 5
----
-
-# MCPs (Model Context Protocol)
-
-External service integrations that extend Claude Code with real-time data access. Browse and install from **[aitmpl.com](https://aitmpl.com)**.
-
-## 🔌 What are MCPs?
-
-MCPs connect Claude Code to external services, databases, and APIs. They provide real-time access to live data and services during conversations.
-
-## Installation
-
-### 📦 Basic Installation
-Install this component locally in your project. Works with your existing Claude Code setup.
-
-```bash
-npx claude-code-templates@latest --mcp database/supabase --yes
-```
-
-### Multiple MCPs
-```bash
-npx claude-code-templates@latest --mcp database/supabase,development/github-integration --yes
-```
-
-## ⚙️ Configuration
-
-Most MCPs require configuration after installation:
-
-### API Keys
-Add required API keys to environment variables:
-```bash
-# Database MCPs
-DATABASE_URL=your_database_url
-SUPABASE_URL=your_supabase_url
-SUPABASE_ANON_KEY=your_anon_key
-
-# GitHub MCP
-GITHUB_TOKEN=your_github_token
-
-# Cloud MCPs
-AWS_ACCESS_KEY_ID=your_aws_key
-AWS_SECRET_ACCESS_KEY=your_aws_secret
-```
-
-## 💡 Usage After Installation
-
-MCPs provide real-time data access:
-- **Query databases** directly in conversations
-- **Access GitHub repos** and issues
-- **Browse documentation** with context
-- **Control browsers** for testing
-- **Interact with cloud services**
-
-## 📁 MCP Categories
-
-Browse MCPs by integration type to connect Claude Code with external services:
-
-### Database Integrations
-Connect to databases and data sources for real-time data access. Examples: `supabase` for Supabase integration, `postgresql-integration` for PostgreSQL access, `mongodb-integration` for MongoDB queries.
-
-### Development Tools
-GitHub, version control, and development service connections. Examples: `github-integration` for repository access, `filesystem-access` for file operations, `npm-registry` for package management.
-
-### Documentation & Context
-Documentation and knowledge base access for contextual information. Examples: `context7` for documentation lookup, `confluence-integration` for enterprise wikis, `notion-integration` for team knowledge bases.
-
-### Browser Automation
-Web scraping and browser control for testing and automation. Examples: `playwright-mcp` for web automation, `browsermcp` for browser control, `selenium-integration` for legacy browser testing.
-
-### Cloud Services
-AWS, Google Cloud, and other cloud platform integrations. Examples: `aws-integration` for AWS services, `gcp-integration` for Google Cloud, `vercel-integration` for deployment management.
-
-### Communication
-Slack, Discord, and other communication tool connections. Examples: `slack-integration` for team communication, `discord-integration` for community management, `teams-integration` for enterprise chat.
-
-## 🎯 How to Choose MCPs
-
-Select MCPs based on your project's external service requirements:
-
-### By Project Type
-- **Web applications**: Choose `supabase` and `github-integration` for database and version control
-- **Data projects**: Use `postgresql-integration` and `context7` for data access and documentation
-- **API services**: Select `github-integration` and `aws-integration` for development and deployment
-- **Testing projects**: Pick `playwright-mcp` and `filesystem-access` for automation and file handling
-
-### By Data Requirements
-- **Live database access**: Choose appropriate `database/*` MCPs for real-time queries
-- **Documentation lookup**: Use `context7` for intelligent documentation search
-- **Repository access**: Select `github-integration` for code and issue management
-- **Web automation**: Pick `browser/*` MCPs for web scraping and testing
-
-### By Integration Needs
-- **Supabase projects**: Essential `supabase` MCP for database operations
-- **GitHub workflows**: Required `github-integration` for repository management
-- **AWS deployments**: Use `aws-integration` for cloud service management
-- **Browser testing**: Select `playwright-mcp` for automated web testing
-
-## 🔧 Pro Tips
-
-- **Start with essential MCPs** for your stack
-- **Configure environment variables** properly
-- **Test connections** after installation
-- **Browse [aitmpl.com](https://aitmpl.com)** for specialized integrations
-
----
-
-**Find more MCPs:** [Browse all MCPs on aitmpl.com](https://aitmpl.com) → Filter by "MCPs"

package/docu/docs/components/overview.md

@@ -1,73 +0,0 @@
----
-sidebar_position: 1
----
-
-# Overview
-
-Browse and search over 500 Claude Code components on **[aitmpl.com](https://aitmpl.com)**.
-
-## 🌐 How to Use aitmpl.com
-
-1. **Visit [aitmpl.com](https://aitmpl.com)**
-2. **Search or browse** by category
-3. **Copy the installation command** from any component
-4. **Run it in your project**
-
-## 🔍 Component Types
-
-### 🤖 **Agents** (AI Specialists)
-```bash
-npx claude-code-templates@latest --agent development/frontend-developer
-npx claude-code-templates@latest --agent security/security-auditor
-npx claude-code-templates@latest --agent data-ai/ml-engineer
-```
-
-### ⚡ **Commands** (Slash Commands)
-```bash
-npx claude-code-templates@latest --command testing/generate-tests
-npx claude-code-templates@latest --command performance/optimize-bundle
-npx claude-code-templates@latest --command setup/setup-ci-cd-pipeline
-```
-
-### 🔌 **MCPs** (External Integrations)
-```bash
-npx claude-code-templates@latest --mcp database/supabase
-npx claude-code-templates@latest --mcp development/github-integration
-npx claude-code-templates@latest --mcp browser/playwright-mcp
-```
-
-### ⚙️ **Settings** (Claude Code Configs)
-```bash
-npx claude-code-templates@latest --setting performance/performance-optimization
-npx claude-code-templates@latest --setting security/read-only-mode
-```
-
-### 🪝 **Hooks** (Automation)
-```bash
-npx claude-code-templates@latest --hook git/auto-git-add
-npx claude-code-templates@latest --hook notifications/discord-notifications
-```
-
-## 🎯 Quick Search Tips
-
-**Search by what you need:**
-- **"React performance"** → Performance optimization agents
-- **"Testing setup"** → Testing commands and agents
-- **"Database integration"** → Database MCPs
-- **"Security audit"** → Security agents and commands
-
-**Use filters:**
-- Filter by component type (Agent, Command, MCP, etc.)
-- Sort by popularity or recent additions
-- Filter by technology (React, Python, Node.js, etc.)
-
-## 📋 From Discovery to Installation
-
-1. **Find a component** on aitmpl.com
-2. **Copy the command** shown on the component page
-3. **Run it in your terminal** in your project directory
-4. **Start using** the component immediately
-
----
-
-**Next step:** [CLI Options](../cli-options) - Learn the different ways to install components

package/docu/docs/components/settings.md

@@ -1,105 +0,0 @@
----
-sidebar_position: 3
----
-
-# Settings
-
-Claude Code configurations that customize behavior and performance. Browse and install from **[aitmpl.com](https://aitmpl.com)**.
-
-## ⚙️ What are Settings?
-
-Settings modify how Claude Code behaves in your project. They control performance, security, interface, and workflow preferences.
-
-## Installation
-
-### 📦 Basic Installation
-Install this component locally in your project. Works with your existing Claude Code setup.
-
-```bash
-npx claude-code-templates@latest --setting performance/performance-optimization --yes
-```
-
-### Multiple Settings
-```bash
-npx claude-code-templates@latest --setting security/read-only-mode,performance/bash-timeouts --yes
-```
-
-## 🔧 Special: Statusline Settings
-
-Statuslines include Python scripts for real-time monitoring:
-
-### Git Branch Monitor
-```bash
-npx claude-code-templates@latest --setting statusline/git-branch-statusline --yes
-```
-Shows current Git branch and status in Claude Code interface.
-
-### Context Monitor
-```bash
-npx claude-code-templates@latest --setting statusline/context-monitor --yes
-```
-Displays project context and active files.
-
-## ⚠️ Important Notes
-
-### File Locations
-Settings are installed to:
-- **`.claude/settings/`** - JSON configuration files
-- **`.claude/scripts/`** - Python scripts (for statuslines)
-
-### Environment Impact
-- **Performance settings** affect Claude Code speed
-- **Security settings** may restrict functionality
-- **Git settings** change version control behavior
-
-## 📁 Setting Categories
-
-Browse settings by functional area to customize Claude Code behavior:
-
-### Performance
-Optimize Claude Code speed and resource usage. Examples: `performance-optimization` for faster execution, `bash-timeouts` for command limits, `memory-optimization` for resource management.
-
-### Security
-Control access and protect sensitive operations. Examples: `read-only-mode` for restricted file access, `deny-sensitive-files` for blocking confidential data, `sandbox-mode` for isolated execution.
-
-### Git Integration
-Version control and Git workflow configurations. Examples: `allow-git-operations` for Git access, `auto-commit-settings` for automated commits, `commit-message-templates` for consistent messaging.
-
-### Interface
-Customize Claude Code appearance and interaction. Examples: `dark-mode` for visual preference, `compact-mode` for space efficiency, `keyboard-shortcuts` for productivity.
-
-### Statuslines
-Real-time monitoring with Python scripts. Examples: `git-branch-statusline` for Git status display, `context-monitor` for project awareness, `performance-monitor` for system metrics.
-
-### Workflow
-Development process optimizations. Examples: `auto-save` for automatic saving, `smart-suggestions` for intelligent recommendations, `code-formatting` for consistent styling.
-
-## 🎯 How to Choose Settings
-
-Select settings based on your project requirements and preferences:
-
-### By Project Security Level
-- **High security projects**: Use `read-only-mode` and `deny-sensitive-files` for maximum protection
-- **Medium security**: Apply `restrict-file-access` for controlled access
-- **Development environment**: Enable `allow-git-operations` for full Git functionality
-
-### By Performance Needs
-- **Large projects**: Choose `performance-optimization` and `memory-optimization` for better handling
-- **Slow command execution**: Use `bash-timeouts` to prevent hanging processes
-- **MCP connection issues**: Apply `mcp-timeouts` for reliable integrations
-
-### By Workflow Type
-- **Git-heavy workflows**: Enable `allow-git-operations` with `git-branch-statusline` for Git awareness
-- **Team collaboration**: Use `commit-message-templates` and `code-formatting` for consistency
-- **Solo development**: Focus on `auto-save` and `custom-theme` for personal productivity
-
-## 💡 Pro Tips
-
-- **Start with performance settings** for better experience
-- **Add security settings** for production projects
-- **Use statuslines** for real-time project monitoring
-- **Browse [aitmpl.com](https://aitmpl.com)** for specialized configurations
-
----
-
-**Find more settings:** [Browse all settings on aitmpl.com](https://aitmpl.com) → Filter by "Settings"

package/docu/docs/components/templates.md

@@ -1,119 +0,0 @@
----
-sidebar_position: 6
----
-
-# Templates
-
-Complete project setups with pre-configured components and best practices. Browse and install from **[aitmpl.com](https://aitmpl.com)**.
-
-## 📦 What are Templates?
-
-Templates are complete project configurations that install multiple components together. They provide opinionated setups for common technology stacks.
-
-## Installation
-
-### 📦 Basic Installation
-Install this component locally in your project. Works with your existing Claude Code setup.
-
-```bash
-npx claude-code-templates@latest --template react --yes
-```
-
-### Template with Directory
-```bash
-npx claude-code-templates@latest --template nextjs --directory ./my-app --yes
-```
-
-### Template with Additional Components
-```bash
-npx claude-code-templates@latest \
-  --template react \
-  --agent security/security-auditor \
-  --hook notifications/slack-notifications
-```
-
-## 📁 What Gets Installed
-
-Templates create a complete setup:
-
-### File Structure
-```
-.claude/
-├── agents/           # Template-specific agents
-├── commands/         # Curated commands
-├── mcps/            # Relevant integrations
-├── settings/        # Optimized settings
-└── hooks/           # Workflow automation
-
-CLAUDE.md             # Template-specific instructions
-```
-
-### Configuration
-- **CLAUDE.md**: Tailored project instructions
-- **Component configs**: Optimized for the template
-- **Environment setup**: Required variables and setup steps
-
-## 💡 Template Benefits
-
-### Faster Setup
-- **Pre-configured components** for your stack
-- **Best practices** built-in
-- **Tested combinations** of agents and tools
-
-### Consistency
-- **Standardized setups** across projects
-- **Team alignment** on tooling
-- **Proven configurations**
-
-## 🚀 Template Categories
-
-Browse templates by development stack to find complete setups for your technology:
-
-### Frontend Templates
-Modern frontend development stacks for client-side applications. Examples: `react` for React applications, `vue` for Vue.js projects, `nextjs` for full-stack React, `angular` for enterprise applications.
-
-### Backend Templates
-Server-side development setups for API and service development. Examples: `nodejs` for Node.js services, `express` for web APIs, `fastapi` for Python APIs, `django` for web applications.
-
-### Full-Stack Templates
-Complete application stacks with frontend and backend. Examples: `fullstack-js` for JavaScript stacks, `t3-stack` for TypeScript full-stack, `mern-stack` for MongoDB-Express-React-Node, `python-web` for Python web apps.
-
-### Mobile Templates
-Mobile development configurations for cross-platform apps. Examples: `react-native` for native mobile, `flutter` for cross-platform, `ionic` for hybrid apps, `expo` for React Native development.
-
-### Data & AI Templates
-Data science and machine learning project setups. Examples: `data-science` for analytics projects, `machine-learning` for ML workflows, `jupyter-notebook` for research, `tensorflow` for deep learning.
-
-### DevOps Templates
-Infrastructure and deployment configurations. Examples: `docker` for containerization, `kubernetes` for orchestration, `aws-lambda` for serverless, `vercel-app` for frontend deployment.
-
-## 🎯 How to Choose Templates
-
-Select templates based on your project requirements and team expertise:
-
-### By Technology Preference
-- **React ecosystem**: Choose `react`, `nextjs`, or `t3-stack` based on complexity needs
-- **Python development**: Select `fastapi`, `django`, or `data-science` based on application type
-- **Node.js backend**: Pick `nodejs`, `express`, or `fullstack-js` based on project scope
-- **Mobile applications**: Use `react-native`, `flutter`, or `expo` based on platform requirements
-
-### By Project Complexity
-- **Simple projects**: Start with `react`, `nodejs`, or `fastapi` for straightforward setups
-- **Medium projects**: Use `nextjs`, `express`, or `django` for moderate complexity
-- **Complex projects**: Choose `t3-stack`, `mern-stack`, or `kubernetes` for advanced requirements
-
-### By Team Experience
-- **Beginner teams**: Begin with `react`, `nodejs`, or `express` for easier learning curves
-- **Intermediate teams**: Use `nextjs`, `fastapi`, or `docker` for balanced complexity
-- **Advanced teams**: Select `t3-stack`, `kubernetes`, or `machine-learning` for sophisticated setups
-
-## 🔧 Pro Tips
-
-- **Start with templates** for new projects
-- **Customize templates** with additional components
-- **Study template configurations** to learn best practices
-- **Browse [aitmpl.com](https://aitmpl.com)** for specialized templates
-
----
-
-**Find more templates:** [Browse all templates on aitmpl.com](https://aitmpl.com) → Filter by "Templates"

package/docu/docs/intro.md

@@ -1,40 +0,0 @@
----
-sidebar_position: 1
----
-
-# Claude Code Templates
-
-**Claude Code Templates** is an open-source CLI tool that configures Claude Code projects and provides specialized components to enhance your AI-powered development workflow.
-
-Browse over 500 components at **[aitmpl.com](https://aitmpl.com)** or contribute to the project on **[GitHub](https://github.com/davila7/claude-code-templates)**.
-
-## What does this CLI do?
-
-Simplifies Claude Code usage through:
-
-- **🔍 Pre-configured components**: Over 500 agents, commands, and configurations ready to use
-- **📦 Automatic installation**: Complete project setup or individual components  
-- **🛠️ Additional tools**: Analytics, health checks, sandbox, and more
-
-## Quick Start
-
-### Interactive Installation
-```bash
-npx claude-code-templates@latest
-```
-
-### Specific Component
-```bash
-npx claude-code-templates@latest --agent performance-testing/react-performance-optimization
-npx claude-code-templates@latest --command testing/generate-tests
-```
-
-## Next Steps
-
-👉 **[Discover Components](https://aitmpl.com)** - Explore and search components on aitmpl.com
-
-👉 **[CLI Options](./cli-options)** - Methods to download components  
-
-👉 **[Components](./components/overview)** - Complete list of available components
-
-👉 **[Tools](./tools/overview)** - Analytics, health check, sandbox, and more

package/docu/docs/safety-features.md

@@ -1,13 +0,0 @@
----
-sidebar_position: 1
----
-
-# Safety Features
-
-`claude-code-templates` is designed with several safety features to ensure that your project and data are protected during the setup and configuration process.
-
--   **Automatic Backups**: Existing files are automatically backed up before any changes are made, allowing you to revert to a previous state if needed.
--   **Confirmation Required**: The CLI always asks for your confirmation before making significant changes to your project (unless the `--yes` flag is used), giving you full control over the process.
--   **Dry Run Mode**: You can preview the installation and changes without actually modifying your files by using the `--dry-run` option.
--   **Cancel Anytime**: You can cancel the operation at any point by pressing `Ctrl+C` or by answering 'No' to confirmation prompts.
--   **Back Navigation**: During interactive setup, you can navigate back to modify previous selections, preventing accidental configurations.

package/docu/docs/support.md

@@ -1,13 +0,0 @@
----
-sidebar_position: 1
----
-
-# Support
-
-If you encounter any issues, have questions, or need assistance with `claude-code-templates`, please refer to the following resources:
-
--   **🐛 Issues**: [Report bugs or request features](https://github.com/davila7/claude-code-templates/issues)
--   **💬 Discussions**: [Join community discussions](https://github.com/davila7/claude-code-templates/discussions)
--   **🔒 Security**: [Report security vulnerabilities](https://github.com/davila7/claude-code-templates/blob/main/SECURITY.md)
--   **📖 Documentation**: [Claude Code Official Docs](https://docs.anthropic.com/en/docs/claude-code)
--   **🤝 Contributing**: [Read our contribution guidelines](https://github.com/davila7/claude-code-templates/blob/main/CONTRIBUTING.md)