$git clone https://github.com/serpro69/claude-toolboxMinimal by design, explicitly multi-lang, production-ready and battle-tested collection of configs and plugins for your Claude Code agentic development workflows: mcp, configs, skills, agents and more.
| 1 | <div align="center"> |
| 2 | <picture> |
| 3 | <source media="(prefers-color-scheme: dark)" srcset="docs/assets/images/lockup-dark.svg"> |
| 4 | <img src="docs/assets/images/lockup-light.svg" alt="claude-toolbox" width="720"> |
| 5 | </picture> |
| 6 | </div> |
| 7 | |
| 8 | # claude-toolbox |
| 9 | |
| 10 | [](https://github.com/serpro69/claude-toolbox/releases) |
| 11 | [](https://github.com/hesreallyhim/awesome-claude-code) |
| 12 | [](https://serpro69.github.io/claude-toolbox/) |
| 13 | |
| 14 | <div align="center" |
| 15 | <picture> |
| 16 | <img width="1080" alt="image" src="https://github.com/user-attachments/assets/27ef7269-0153-47c0-b07d-ed6a9504a176" /> |
| 17 | </picture> |
| 18 | </div> |
| 19 | |
| 20 | `claude-toolbox` is a collection of "tools" for all your agentic workflows — pre-configured MCP servers, skills, sub-agents, commands, hooks, statuslines with themes, and more - everything you need for AI-powered development workflows, used and battle-tested daily on many of my own projects. |
| 21 | |
| 22 | **Supported providers:** [Claude Code](https://serpro69.github.io/claude-toolbox/latest/providers/claude-code/) · [Codex](https://serpro69.github.io/claude-toolbox/latest/providers/codex/) |
| 23 | |
| 24 | <div align="center"> |
| 25 | |
| 26 | ## [Read the full documentation →](https://serpro69.github.io/claude-toolbox/) |
| 27 | |
| 28 | <a href="https://serpro69.github.io/claude-toolbox/"> |
| 29 | <img width="1080" alt="image" src="https://github.com/user-attachments/assets/7b735db9-9fa2-425b-8176-0991f6ff64ad" /> |
| 30 | </a> |
| 31 | |
| 32 | </div> |
| 33 | |
| 34 | --- |
| 35 | |
| 36 | > [!IMPORTANT] |
| 37 | > This project was created with the help of Claude-Code. Is it, however, always reviewed, tested, and reworked with a human-in-the-loop. |
| 38 | > |
| 39 | > No AI slop here. Purely AI-made skills are hot garbage, and that's putting it mildly. |
| 40 | > |
| 41 | > That said, if you have any problems with code that is written by AI - you've been warned. But, then again, why would you be interested in AI-related configs and skills in the first place... `¯\_(ツ)_/¯` |
| 42 | |
| 43 | ## Why claude-toolbox? |
| 44 | |
| 45 | Tools like Claude Code and Codex are powerful on their own, but LLMs don't know your development workflow. This project started as a way for me to streamline claude configurations across all my projects without needing to copy-paste things. With time, patterns and re-curring prompts evolved into skills and agents. Currently, claude-toolbox gives you two things: |
| 46 | |
| 47 | **A minimal, opinionated Claude Code and Codex configuration** — sensible permission baselines, a rich statusline, MCP server wiring, and sync infrastructure to keep it all up to date across your projects. Think of it as a dotfiles repo for Claude Code and Codex. |
| 48 | |
| 49 | **A structured development pipeline** — 11 workflow skills with explicit multi-language support that take you from idea through design, implementation, code review, testing, to documentation, with persistent knowledge that carries across sessions. |
| 50 | |
| 51 | ``` |
| 52 | /kk:design → /kk:review-design → /kk:implement → /kk:review-code → /kk:test → /kk:document |
| 53 | ``` |
| 54 | |
| 55 | Out of the box you get: |
| 56 | |
| 57 | - **11 workflow skills** — a complete development pipeline invoked as `/kk:<skill-name>`, with many skills integrated with each other. |
| 58 | - **Multi-language support** — precise and distinct instructions from design, to implementation, to testing, to review for: go, java, js/ts, kotlin, kubernetes, and python |
| 59 | - **Multi-model code review** — independent reviewers using sub-agents and external models (Gemini, etc.) |
| 60 | - **Persistent knowledge base** — findings, decisions, and conventions that survive across sessions via Capy |
| 61 | - **Up-to-date library docs** — always-current documentation lookup via Context7 |
| 62 | - **Battle-tested configuration** — permissions, statusline themes, hooks, sensible defaults |
| 63 | |
| 64 | ## Choose Your Path |
| 65 | |
| 66 | **Starting a new project?** Use the template — you get the full configuration and plugin pre-wired, plus sync infrastructure to pull future updates. |
| 67 | → [Template Setup](https://serpro69.github.io/claude-toolbox/latest/getting-started/template-setup/) |
| 68 | |
| 69 | **Existing project, want the full setup?** Adopt the configuration, plugin, and sync infrastructure without creating from the template. |
| 70 | → [Adopting into Existing Repositories](https://serpro69.github.io/claude-toolbox/latest/getting-started/adopting/) |
| 71 | |
| 72 | **Just want the skills?** Install the kk plugin — no template needed. |
| 73 | → [Plugin-Only Setup](https://serpro69.github.io/claude-toolbox/latest/getting-started/plugin-only/) |
| 74 | |
| 75 | ## Try It |
| 76 | |
| 77 | After setup, try the core workflow: |
| 78 | |
| 79 | 1. **Start with an idea.** Type `/kk:design` and describe a feature you want to build. Claude will ask you refinement questions one at a time, then produce design docs and a task list in `docs/wip/`. |
| 80 | |
| 81 | 2. **Review the design.** Run `/kk:review-design your-feature` to catch gaps before writing code. |
| 82 | |
| 83 | 3. **Build it.** Type `/kk:imple |