Customization Overview
Customization Overview
Section titled “Customization Overview”Claude Kit is designed to be fully customizable. You can create your own commands, modes, and skills, and configure Claude’s behavior for your specific project needs.
What Can You Customize?
Section titled “What Can You Customize?”1. Commands
Section titled “1. Commands”Create custom slash commands for your team’s specific workflows:
/deploy-staging # Your deployment workflow/audit-deps # Custom dependency audit/release-notes # Generate release notes your wayLearn how to create commands →
2. Modes
Section titled “2. Modes”Define behavioral modes for different work contexts:
/mode pair-programming # Your pair programming style/mode documentation # Documentation-focused mode/mode production-debug # Emergency debugging mode3. Skills
Section titled “3. Skills”Add knowledge modules for your tech stack:
.claude/skills/├── languages/rust/ # Rust best practices├── frameworks/svelte/ # Svelte patterns└── custom/your-api/ # Your internal API docs4. CLAUDE.md Configuration
Section titled “4. CLAUDE.md Configuration”Configure project-specific behavior, conventions, and agent overrides:
- Tech stack and architecture
- Code conventions
- Testing standards
- Security requirements
- Agent behavior overrides
Customization Levels
Section titled “Customization Levels”Claude Kit supports three levels of customization:
| Level | What to Change | When to Use |
|---|---|---|
| Configuration | Edit CLAUDE.md | Set project conventions, tech stack, standards |
| Composition | Add modes and skills | Extend behavior without coding |
| Extension | Create commands | Build custom workflows |
Quick Start Examples
Section titled “Quick Start Examples”Example 1: Add a Custom Command
Section titled “Example 1: Add a Custom Command”Create .claude/commands/deploy.md:
# /deploy - Deploy Application
## Usage/deploy [environment]
---
Deploy to **$ARGUMENTS** environment:
1. Run tests2. Build production bundle3. Deploy to environment4. Verify deploymentExample 2: Configure for Your Stack
Section titled “Example 2: Configure for Your Stack”Edit .claude/CLAUDE.md:
## Tech Stack
- **Backend**: Ruby on Rails- **Frontend**: Vue.js- **Database**: MySQL- **Testing**: RSpec, CypressExample 3: Add a Custom Skill
Section titled “Example 3: Add a Custom Skill”Create .claude/skills/custom/internal-api/SKILL.md:
# Internal API Standards
## AuthenticationAll endpoints require JWT bearer tokens...
## Error HandlingUse standard error format...File Structure
Section titled “File Structure”Claude Kit customizations live in your .claude folder:
.claude/├── CLAUDE.md # Main configuration├── commands/ # Custom commands│ ├── deploy.md│ └── your-command.md├── modes/ # Custom modes│ ├── your-mode.md│ └── another-mode.md└── skills/ # Custom skills ├── custom/ │ └── your-skill/ │ └── SKILL.md └── overrides/ └── language/ └── SKILL.mdBest Practices
Section titled “Best Practices”Start Small
Section titled “Start Small”Don’t try to customize everything at once:
- First: Configure
CLAUDE.mdfor your project - Then: Add a mode or two for your common workflows
- Finally: Create custom commands for repeated tasks
Document Your Customizations
Section titled “Document Your Customizations”Add comments to your custom files explaining:
- Why the customization exists
- When to use it
- What it does differently
Share Customizations
Section titled “Share Customizations”Custom commands and modes are project-specific, so they should be:
- Committed to version control
- Documented in your project README
- Shared with your team
Keep Skills Focused
Section titled “Keep Skills Focused”Each skill should:
- Cover one specific topic
- Be 50-200 lines
- Include practical examples
- Reference official docs
Common Customization Patterns
Section titled “Common Customization Patterns”Pattern 1: Strict TDD Workflow
Section titled “Pattern 1: Strict TDD Workflow”Add to CLAUDE.md:
## Tester Agent- **TDD Required**: Always write tests first- **Coverage Minimum**: 90%- **Test Type**: Integration tests for all endpointsPattern 2: Security-First Reviews
Section titled “Pattern 2: Security-First Reviews”Create .claude/modes/security-audit.md:
# Security Audit Mode
Focus exclusively on security issues:- Authentication/authorization- Input validation- XSS/CSRF protection- Secrets managementPattern 3: Custom Git Workflow
Section titled “Pattern 3: Custom Git Workflow”Create .claude/commands/finish-feature.md:
# /finish-feature - Complete Feature
1. Squash commits2. Update changelog3. Create PR with template4. Assign reviewersNext Steps
Section titled “Next Steps”Choose what to customize:
- Create Custom Commands — Build workflow automation
- Create Custom Modes — Define behavioral patterns
- Create Custom Skills — Add knowledge modules
- Configure CLAUDE.md — Set project standards
Getting Help
Section titled “Getting Help”- Check the example commands in the repo
- Look at built-in modes for patterns
- Review existing skills for structure