cc-rig

Set up Claude Code right, then keep it right.

  Two Commands ·
  Why Cache ·
  Install ·
  Tune ·
  What Gets Generated ·
  FAQ

cc-rig started with one mission: make setting up Claude Code painless, back when the config surface was a scattered mess of docs and community repos. That part is mostly solved now. Native tooling scaffolds a CLAUDE.md and the marketplace has the plugins, so getting a config is easy. Getting it right is still the hard part: most configs are generic, bloat the context window, skip the guards that stop a destructive command and quietly break the prompt cache.

cc-rig gets your config right, then keeps it right. cc-rig init generates a lean, stack-tailored setup in one command: a tight CLAUDE.md, hooks that gate on your framework's real test and lint commands, plus agents, skills, memory and curated plugins. cc-rig tune then scores that config on six published dimensions, ranks what to fix and applies the safe fixes, so it stays correct as your project and Claude Code both move.

Native Claude Code files, nothing proprietary. Delete cc-rig tomorrow and your project keeps working.

The two commands

cc-rig init writes the config

Tell it what you're building and how you like to work. It writes 30-65 native Claude Code files tuned to your framework: a cache-aware CLAUDE.md, settings with hooks and permissions, specialized agents, slash commands, skills, memory and curated plugins.

A typical Claude Code project:

After cc-rig init (one command, two questions, ~30 seconds):

cc-rig tune keeps it correct

Run it any time. It reads your config, plus your session history when there is one, scores six weighted dimensions and ranks the fixes by severity. Where your own logs can measure what a cache problem costs, the finding carries that figure.

Real…