Claude Code Kit
Config tools for Claude Code. Write hooks, CLAUDE.md, permission rules, slash commands and settings.json here, then paste the result into your project.
Hooks generator
All 33 events, 10 examples and how hooks runHook
Added
settings.json
Merge the "hooks" key into your existing settings file. Do not replace the whole file. Handler type is command here; the docs also list http, mcp_tool, prompt and agent handlers.
The other tools
- CLAUDE.md
CLAUDE.mdFour templates, plus a checker for the file you already have.
- Permissions
permissions in settings.jsonBuild allow, ask, deny rules and test a call against them.
- Slash commands
.claude/commands/*.mdGenerate the .md file with frontmatter, arguments, and allowed-tools.
- settings.json
.claude/settings.jsonBuild from common keys, or paste yours to validate.
- Best practices
checklistA checklist with progress saved in your browser.
How these fit together
CLAUDE.md tells Claude what to do. Permission rules decide what it may do. Hooks run your code at fixed points. Permission rules and hooks live in settings files, and the settings.json tool combines them.
Rules are checked against Anthropic's Claude Code docs. Where a detail could not be confirmed, the page says unverified. See About.
FAQ
What is Claude Code Kit?
A set of free tools for the config files Claude Code reads: hooks, CLAUDE.md, permission rules, slash commands and settings.json. Each tool runs in your browser and gives you text to copy into your project. It is not affiliated with Anthropic.
Is anything I paste uploaded?
No. The generators and checkers run in the page itself. Nothing you type or paste is sent to a server.
Where do Claude Code settings live?
~/.claude/settings.json applies to all your projects, .claude/settings.json is shared with your team through the repo, and .claude/settings.local.json holds your own uncommitted overrides. Hooks and permission rules go in any of these files.
Which file should I set up first?
Start with CLAUDE.md, since it shapes every session. Add permission rules once you know which commands you approve again and again. Add hooks when you need something to happen every time, such as formatting after an edit.