Skip to content

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.

Create custom slash commands for your team’s specific workflows:

Terminal window
/deploy-staging # Your deployment workflow
/audit-deps # Custom dependency audit
/release-notes # Generate release notes your way

Learn how to create commands →

Define behavioral modes for different work contexts:

Terminal window
/mode pair-programming # Your pair programming style
/mode documentation # Documentation-focused mode
/mode production-debug # Emergency debugging mode

Learn how to create modes →

Add knowledge modules for your tech stack:

Terminal window
.claude/skills/
├── languages/rust/ # Rust best practices
├── frameworks/svelte/ # Svelte patterns
└── custom/your-api/ # Your internal API docs

Learn how to create skills →

Configure project-specific behavior, conventions, and agent overrides:

  • Tech stack and architecture
  • Code conventions
  • Testing standards
  • Security requirements
  • Agent behavior overrides

CLAUDE.md reference →

Claude Kit supports three levels of customization:

LevelWhat to ChangeWhen to Use
ConfigurationEdit CLAUDE.mdSet project conventions, tech stack, standards
CompositionAdd modes and skillsExtend behavior without coding
ExtensionCreate commandsBuild custom workflows

Create .claude/commands/deploy.md:

# /deploy - Deploy Application
## Usage
/deploy [environment]
---
Deploy to **$ARGUMENTS** environment:
1. Run tests
2. Build production bundle
3. Deploy to environment
4. Verify deployment

Full command creation guide →

Edit .claude/CLAUDE.md:

## Tech Stack
- **Backend**: Ruby on Rails
- **Frontend**: Vue.js
- **Database**: MySQL
- **Testing**: RSpec, Cypress

Full CLAUDE.md guide →

Create .claude/skills/custom/internal-api/SKILL.md:

# Internal API Standards
## Authentication
All endpoints require JWT bearer tokens...
## Error Handling
Use standard error format...

Full skill creation guide →

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.md

Don’t try to customize everything at once:

  1. First: Configure CLAUDE.md for your project
  2. Then: Add a mode or two for your common workflows
  3. Finally: Create custom commands for repeated tasks

Add comments to your custom files explaining:

  • Why the customization exists
  • When to use it
  • What it does differently

Custom commands and modes are project-specific, so they should be:

  • Committed to version control
  • Documented in your project README
  • Shared with your team

Each skill should:

  • Cover one specific topic
  • Be 50-200 lines
  • Include practical examples
  • Reference official docs

Add to CLAUDE.md:

## Tester Agent
- **TDD Required**: Always write tests first
- **Coverage Minimum**: 90%
- **Test Type**: Integration tests for all endpoints

Create .claude/modes/security-audit.md:

# Security Audit Mode
Focus exclusively on security issues:
- Authentication/authorization
- Input validation
- XSS/CSRF protection
- Secrets management

Create .claude/commands/finish-feature.md:

# /finish-feature - Complete Feature
1. Squash commits
2. Update changelog
3. Create PR with template
4. Assign reviewers

Choose what to customize: