Skip to main content

Installation Guide

This guide covers everything you need to know about installing Claude Code Templates, from basic usage to advanced configuration and batch installation.

Prerequisites

Required Software

  • Node.js 14+: Required to run the CLI tool
  • Claude Code: Anthropic’s Claude Code IDE (download)
  • Git (optional): For version control integration
Claude Code Templates works with any project type. The CLI automatically detects your project structure and recommends appropriate components.

Basic Installation

No installation required - run directly with npx:
The @latest tag ensures you always get the newest components:
Package Information

Install Globally

For frequent use, install globally:
Global installation may use an older version unless you update regularly:

Component Types

Claude Code Templates provides six types of components:

🤖 Agents (400+)

What they are: AI specialists with domain-specific knowledge and context. Location: .claude/agents/ Installation:
Usage: Reference in Claude Code with @agent-name Examples:
  • development-team/frontend-developer - Expert in React, Vue, Angular
  • security/security-auditor - Security analysis and vulnerability detection
  • devops-infrastructure/kubernetes-expert - Container orchestration specialist
  • data-ai/machine-learning-engineer - ML model development and training
Categories:
  • Development Team (Frontend, Backend, Fullstack)
  • Development Tools (Code Review, Refactoring)
  • Security (Auditing, Penetration Testing)
  • DevOps & Infrastructure (Docker, Kubernetes, AWS)
  • Data & AI (ML, Data Science, Analytics)
  • Documentation (Technical Writing, API Docs)
  • Testing & QA (Unit Testing, E2E Testing)
  • Database (PostgreSQL, MongoDB, Redis)
  • API & GraphQL (REST, GraphQL, API Design)
  • And 20+ more categories…

⚡ Commands (225+)

What they are: Custom slash commands for automated workflows. Location: .claude/commands/ Installation:
Usage: Type /command-name in Claude Code Examples:
  • /generate-tests - Generate unit tests for selected code
  • /optimize-bundle - Analyze and optimize bundle size
  • /check-security - Run security audit on dependencies
  • /setup-ci - Configure CI/CD pipeline
  • /refactor-code - Suggest refactoring improvements
Categories:
  • Testing (Unit Tests, E2E Tests, Coverage)
  • Performance (Bundle Optimization, Profiling)
  • Security (Vulnerability Scanning, SAST)
  • Documentation (README, API Docs, Changelog)
  • Code Quality (Linting, Formatting, Review)
  • Deployment (CI/CD, Docker, Cloud)

🔌 MCPs (65+)

What they are: Model Context Protocol integrations for external services. Location: .claude/mcps/ Installation:
Usage: Claude Code connects automatically on startup Examples:
  • development/github-integration - GitHub API access
  • database/postgresql-integration - PostgreSQL queries
  • cloud/aws-integration - AWS service management
  • payment/stripe-integration - Stripe API integration
  • ai/openai-integration - OpenAI API access
Categories:
  • Development (GitHub, GitLab, Bitbucket)
  • Database (PostgreSQL, MySQL, MongoDB, Redis)
  • Cloud (AWS, Azure, GCP, Vercel)
  • Payment (Stripe, PayPal)
  • AI & ML (OpenAI, Anthropic, Hugging Face)
  • Communication (Slack, Discord, Telegram)
MCPs often require API credentials. Check component documentation for required environment variables.

⚙️ Settings (60+)

What they are: Claude Code configuration presets. Location: .claude/settings/ Installation:
Examples:
  • performance/mcp-timeouts - Optimize MCP connection timeouts
  • memory/large-projects - Memory settings for large codebases
  • output/verbose-logging - Enable detailed logging
  • read-only-mode - Prevent file modifications

🪝 Hooks (45+)

What they are: Automation triggers for development workflows. Location: .claude/hooks/ Installation:
Examples:
  • git/pre-commit-validation - Validate code before commits
  • automation/simple-notifications - Send notifications on events
  • deployment/post-deploy-check - Verify deployments

🎨 Skills (300+)

What they are: Reusable capabilities with progressive disclosure. Location: .claude/skills/ Installation:
Examples:
  • pdf-processing - Generate and manipulate PDFs
  • excel-automation - Automate Excel operations
  • scientific-computing - Scientific computation tools

Installation Methods

Interactive Mode

Launch the interactive CLI to browse and select components:
Workflow:
  1. Main menu appears
  2. Select “Project Setup”
  3. Choose component type (Agent, Command, MCP, etc.)
  4. Browse categories
  5. Select specific components
  6. Confirm installation
Interactive mode is great for discovering new components and learning what’s available.

Direct Installation

Install specific components directly:
Single Component

Batch Installation

Install multiple components in one command:
Multiple Components
You can install multiple of the same type by repeating the flag:

Skip Prompts

Use --yes to skip all confirmation prompts:
Perfect for:
  • Automated scripts
  • CI/CD pipelines
  • Team onboarding scripts
  • Docker containers

Advanced Installation

Install to Specific Directory

By default, components install to the current directory’s .claude/ folder. Change the target:

Dry Run

See what would be installed without actually installing:
Output shows:
  • Files that would be created
  • Directories that would be modified
  • Configuration changes

Comma-Separated Values

Install multiple components of the same type with commas:

Workflow Installation

Install complete workflows from templates:
Workflows are pre-configured sets of components that work together.

Project Templates

For new projects, use complete project templates:
JavaScript/TypeScript
Python
Ruby
Common (Language Agnostic)
Templates include:
  • Language-specific agents
  • Common commands
  • Recommended MCPs
  • Standard hooks
  • Configuration presets

Configuration

Component Configuration

After installation, components are configured in .claude/:
Directory Structure

Environment Variables

Some components require environment variables:
.env
Never commit .env files to version control. Add to .gitignore:

Python Command Configuration

On Windows, the CLI automatically detects and uses the correct Python command:
  • Windows: python or py
  • Unix/Linux/Mac: python3
Statusline settings with Python scripts work automatically across platforms.

CLI Reference

Complete CLI options:
Command Line Options

Verification

Health Check

Verify installation with the health check tool:
Checks:
  • ✓ Claude Code installation
  • ✓ Configuration file validity
  • ✓ Component integrity
  • ✓ Dependency availability
  • ✓ Environment variable configuration
  • ✓ File permissions

Manual Verification

Check installed components:

Troubleshooting

On Unix systems, ensure you have write permissions:
  1. Make sure Claude Code is running in the correct directory:
  2. Restart Claude Code to reload configuration
  3. Check Claude Code output for errors
  4. Run health check:
  1. Check required environment variables:
  2. Verify credentials are valid
  3. Check MCP configuration:
  4. Look for error messages in Claude Code output
  5. Some MCPs require external services to be running
Install Node.js 14 or higher:
  1. Check Python installation:
  2. Verify script permissions:
  3. Check script path in statusline configuration
  4. The CLI automatically handles platform differences
Global agents require additional setup:

Next Steps

Browse Components

Explore 900+ components in the interactive catalog.

CLI Reference

Complete documentation for all CLI commands and options.

Analytics Dashboard

Monitor your Claude Code sessions in real-time.

Contributing

Add your own components to the collection.

Need help?

Join our GitHub Discussions to ask questions and get support from the community.