Claude Kit

Claude Kit
Reusable configuration kit for Claude Code

English | Русский

Structured multi-agent development workflow with built-in planning, implementation, and code review phases. Supports any language and framework — Go, Python, TypeScript, Rust, Java, and 26 more via tree-sitter analysis.

Note: Defaults are tuned for Go (sparse paths, pre-commit-build.sh runs go build, CLAUDE.md Language Profile pins Go ≥ 1.24). For other stacks: edit CLAUDE.md Language Profile, adjust worktree.sparsePaths in .claude/settings.local.json, and replace or disable the Go-specific build hook. See ⚙️ Configuration Files.

📑 Table of Contents

• ⚡ Quick Start
• 🔧 Commands
• 🏗 Architecture
• 🔌 MCP Servers
• 🪨 Token Optimization (Caveman)
• ⚙️ Configuration Files
• 📂 Project Structure
• 🪝 Hooks
• 📐 Conventions

⚡ Quick Start

Requirements: Claude Code >= 2.1.141 (the kit's hooks rely on the exec-form args: invariant from v2.1.139 and terminalSequence JSON output from v2.1.141). On earlier versions hooks silently no-op / degrade.

/workflow orchestrates planning → implementation → review → commit for any task. Onboarding in four steps.

1. Install — plugin (recommended)

Install claude-kit as a native Claude Code plugin: shared across all your projects, versioned, updated through the marketplace, with nothing copied into your repo. This repo doubles as its own marketplace (.claude-plugin/marketplace.json + .claude-plugin/plugin.json).

/plugin marketplace add hex0xdeadbeef/claude-kit
/plugin install claude-kit@claude-kit

Plugin commands are namespaced — you run /claude-kit:workflow, /claude-kit:planner, /claude-kit:coder, /claude-kit:designer. The internal pipeline delegation (planner → plan-reviewer → coder → code-reviewer) resolves automatically by description, so it works regardless of the prefix.

curl -sL https://raw.githubusercontent.com/hex0xdeadbeef/claude-kit/main/install.sh | bash

Plugin vs install.sh — both coexist:

• Plugin — reuse the pipeline across many projects, versioned updates, nothing copied into your repo. You still supply your project's own config (Language Profile in CLAUDE.md, architecture rules, .claude/PROJECT-KNOWLEDGE.md).
• install.sh — project-scoped: the kit lives in your repo, customizable and committed with your team.

2. First run

/project-researcher                          # writes .claude/PROJECT-KNOWLEDGE.md
/workflow Add new REST endpoint for profiles

/project-researcher gives the agents context for your codebase (architecture, modules, dependencies, language profile). Edit the CLAUDE.md Language Profile first if your stack is not Go (the kit's default). Then /workflow drives the full cycle: task analysis → [design — L/XL only] → planning → plan review → implementation → code review → commit. (In plugin mode, prefix the commands: /claude-kit:project-researcher, /claude-kit:workflow.)

3. Configure the kit — overriding variables

The kit is tuned with environment variables (validation strictness, prompt-cache TTL, terse-output mode, and more). Where you set a variable decides its scope — and the mechanism is identical for the plugin and the install.sh install: Claude Code injects the env block into the session, and every hook script (plugin hooks included) inherits it as a subprocess.