capy

claude-toolbox

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.

Supported providers: Claude Code · Codex

Read the full documentation →

Important This project was created with the help of Claude-Code. Is it, however, always reviewed, tested, and reworked with a human-in-the-loop.

No AI slop here. Purely AI-made skills are hot garbage, and that's putting it mildly.

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... ¯\_(ツ)_/¯

Why claude-toolbox?

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:

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.

A structured development pipeline — 16 workflow and utility 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.

/kk:design → /kk:review-design → /kk:implement → /kk:review-code → /kk:test → /kk:document

Out of the box you get:

• 16 workflow and utility skills — a complete development pipeline invoked as /kk:<skill-name>, plus utilities such as /kk:clarify-docs for improving existing documentation, PR drafts and issue descriptions, and explicit /kk:handoff publication of task context to a secret GitHub gist.
• Multi-language support — precise and distinct instructions from design, to implementation, to testing, to review for: go, java, js/ts, kotlin, kubernetes, and python
• Multi-model code review — independent reviewers using sub-agents and external models (Gemini, etc.)
• Persistent knowledge base — findings, decisions, and conventions that survive across sessions via Capy
• Up-to-date library docs — always-current documentation lookup via Context7
• Battle-tested configuration — permissions, statusline themes, hooks, sensible defaults

Choose Your Path

Starting a new project? Use the template — you get the full configuration and plugin pre-wired, plus sync infrastructure to pull future updates. → Template Setup

Existing project, want the full setup? Adopt the configuration, plugin, and sync infrastructure without creating from the template. → Adopting into Existing Repositories

Just want the skills? Install the kk plugin — no template needed. → Plugin-Only Setup

Try It

After setup, try the core workflow:

For an optional conversation first, use /kk:brainstorm to think through a technical idea. It adapts the interview to your next decision and ends with a chat recap of decisions, rationale, and open assumptions. It creates no files or automatic handoff; request /kk:design when you want written planning.

1. Write a plan. Type /kk:design and describe a feature you want to build. Claude will ask refinement questions and confirm decisions, then produce design docs, an implementation plan, and a task list in docs/feat/wip/.

2. Review the design. Run /kk:review-design your-feature to catch gaps before writing code.

3. Build it. Type /kk:implement — Claude establishes the task's behavior and compatibility constraints, implements it, and supplies current evidence to independent review. Standalone fixes also work without design documents.

4. Review the code. /kk:review-code traces intended behavior, unchanged callers and affected compatibility contracts alongside SOLID, security and quality checks. Use /kk:review-code:isolated for independent review without the implementation conversation: an internal reviewer plus external review through PAL, using an API model when one is configured and otherwise your installed CLIs from other vendors (see isolated reviews).

Reviews distinguish current regressions from inherited issues and code support from deployment readiness. Missing evidence stays explicit; green tests support the paths exercised. Verification is proportionate to the change, while explicit repository and release checks remain required. See functional review and implementation for examples and limits.

This is the core loop. See the Skills documentation for all available skills and the full workflow pipeline.

To clarify a bug report or feature request, use /kk:clarify-docs issue-draft.md or supply an issue URL or pasted description with a local destination. The skill preserves evidence limits and produces a local draft; it does not publish or implement the issue. See issue-description examples for output selection and audience rules. Clarification remains optional.

Examples

Examples of actual Claude Code workflows executed using this template's configs, skills, and tools: examples/

Contributing

Contributions are welcome! See the Contributing guide for guidelines, Architecture for how components fit together, and Testing for test conventions.

License

Copyright © 2025 - present, serpro69

Distributed under the ELv2 License.

See LICENSE.md file for more information.