Skip to main content

​
Installing Individual Components

Claude Code Templates provides over 600 individual components that you can install one at a time. Each component type serves a specific purpose in your development workflow.

​
Component Types

Before installing, understand what each component type does:
  • Agents (162+) - AI specialists for specific tasks (e.g., security-auditor, frontend-developer)
  • Commands (210+) - Custom slash commands for workflows (e.g., /setup-testing, /docker-setup)
  • MCPs (65+) - Model Context Protocol integrations for external services
  • Settings (60+) - Configuration files for Claude Code behavior
  • Hooks (45+) - Automation triggers for events (e.g., before bash, after file edit)
  • Skills - Specialized knowledge domains for Claude to reference

​
Installation Syntax

All components follow the same installation pattern:

​
Installing Agents

Agents are AI specialists stored in .claude/agents/.
Agent Discovery: Can’t find an agent? Use the search on aitmpl.com to search by description, category, or use case.

​
Installing Commands

Commands are custom slash commands stored in .claude/commands/.

​
Installing MCPs

MCPs (Model Context Protocols) enable external service integrations. They merge into .mcp.json.

​
Installing Settings

Settings configure Claude Code behavior. You can install them at multiple levels.
Conflict Detection: The CLI checks for conflicts when merging settings. If a setting already exists with a different value, you’ll be prompted to confirm overwrite.

​
Installing Hooks

Hooks enable event-driven automation. They’re stored in settings files.

​
Installing Skills

Skills provide specialized knowledge domains for Claude to reference.

​
Component Naming Conventions

All components follow kebab-case naming: ✅ Correct:
❌ Incorrect:

​
Common Installation Flags

​
Directory Target

Install to a specific directory:

​
Skip Prompts

Use defaults without confirmation:

​
Dry Run

Preview what would be installed without making changes:

​
Verbose Logging

Enable detailed installation logs:

​
Viewing Component Details

Before installing, you can view component details on the web:

​
Troubleshooting

​
Component Not Found

If you get a 404 error:
Solutions:
  1. Check spelling - component names are exact
  2. Search on aitmpl.com for the correct name
  3. Verify the component exists in the catalog

​
Permission Errors

If installation fails with permission errors:

​
Merge Conflicts

If settings/hooks conflict with existing config:
Choose:
  • y - Replace existing value with new value
  • N - Keep existing value, skip installation

​
File Locations Reference

​
Next Steps

Batch Installation

Install multiple components at once

Interactive Mode

Use the visual component selector

Workflows

Create reusable installation workflows

Global Agents

Create agents you can run from anywhere