Claude Capsule Kit

Definition

Claude Capsule Kit (CCK) is an advanced toolkit for Claude Code that solves practical problems: session isolation, dependency awareness, large file navigation, and parallel multi-branch work. It is built entirely on Claude Code's official hook system, with no patches and no hacks.

Install is global, then cck setup, then a restart so hooks turn on by themselves. The kit is v3.0.4 under MIT, with 75 stars, 8 forks, and 4 contributors. File reads, edits, and agent calls land in a local SQLite file named capsule.db.

Basic Information

Installation

npm install -g claude-capsule-kit
cck setup

Restart Claude Code. Everything activates automatically via hooks.

Architecture

claude-capsule-kit/
├── agents/         # 18 specialist agents
├── bin/            # CLI binaries
├── commands/       # Slash commands
├── crew/           # Crew team management
├── docs/           # Documentation
├── hooks/          # 6 lifecycle hooks
├── lib/            # Core libraries (blink-query)
├── scripts/        # Utility scripts
├── skills/         # Auto-trigger skills
├── templates/      # Project templates
└── tools/          # Dependency tools (Go)

Core Features

Session Memory

Hooks capture every file read, edit, and agent invocation into a local SQLite database (blink-query).

Dependency Tools

Large File Navigation

The progressive reader parses the AST and splits files into navigable chunks:

• 75-97% token savings on large files
• Supports TypeScript, JavaScript, Python, Go

progressive-reader --path src/huge-file.ts --list     # See structure
progressive-reader --path src/huge-file.ts --chunk 3   # Read specific section

18 Specialist Agents

Crew Teams

Parallel agent teams, where each teammate works on its own git branch via worktrees.

{
  "team": {
    "name": "my-feature",
    "teammates": [
      { "name": "backend", "branch": "feat/api", "role": "developer", "focus": "Build REST API" },
      { "name": "frontend", "branch": "feat/ui", "role": "developer", "focus": "Build React UI" }
    ]
  }
}

Roles: developer (sonnet, auto-commit) | reviewer (sonnet, read-only) | tester (haiku, auto-commit) | architect (opus, read-only)

Hooks

CLI Commands

cck setup              # Install hooks, tools, context
cck teardown           # Remove CCK (keeps data)
cck status             # Show what's installed
cck build              # Build Go binaries
cck stats <cmd>        # Usage analytics
cck prune [days]       # Clean old records

cck crew init          # Create .crew-config.json
cck crew start         # Launch team
cck crew stop          # Stop team
cck crew status        # Show team state
cck crew doctor        # Check teammate health
cck crew merge-preview # Preview branch merges
cck crew merge         # Execute branch merges
cck crew decompose     # Dependency-aware task splitting

Tech Stack

Requirements

• Node.js 18+
• Claude Code with hooks support
• Git
• Go 1.20+ (optional, for dependency scanner)

Pros

Cons

When to Use

• Long coding sessions: Need session continuity across restarts
• Dependency-heavy projects: Need import graph awareness
• Large codebases: Files over 50KB need progressive reading
• Parallel features: Want to work on several features at once with crew teams
• Zero-config preference: Want everything automatic through hooks

A finished session stores a summary with branch context, and the next start restores it. If context fills up, a continuity doc is saved before compaction. Six hooks run the lifecycle. SessionStart restores context and detects a crew. PostToolUse writes file ops into capsule.db. PreToolUse enforces the dependency tools and blocks large files. PreCompact saves the continuity doc. SessionEnd stores the summary, the branch, and the file count. Stop runs a quality check. query-deps answers imports both ways. impact-analysis says what breaks on a change. find-circular and find-dead-code hunt loops and code that nothing imports. The progressive reader splits a file by its AST and lists a 75-97% token saving. It supports TypeScript, JavaScript, Python, and Go. Crew teams put each teammate on a git branch through worktrees. Developer and tester auto-commit. Reviewer and architect stay read-only. Teardown keeps capsule.db. You need Node.js 18 or newer, Claude Code hooks, and Git. Go 1.20 or newer is optional. SQLite does not scale to very large projects, and there is no MCP support. The agent list is shorter than ECC.

References:

• arpitnath/claude-capsule-kit
• npm: claude-capsule-kit
• blink-query

See also: Kit Comparison · Everything Claude Code · ClaudeKit