Why

Setting up a productive Claude Code workflow takes 30-90 minutes per project for experienced users. Newcomers don't even know what's possible. cc-boost makes the full toolkit available immediately:

npx cc-boost init

That's it. Your project now has code navigation, structural search, framework-specific conventions, reusable workflows, and auto-indexing — all configured correctly for your stack.

Quick Start

# In any project directory
npx cc-boost init

cc-boost will:

1. Detect your language and framework stack
2. Show what it found and let you confirm
3. Configure MCP servers, LSP, skills, CLAUDE.md, and git hooks
4. Install any missing dependencies (with your approval)

Non-interactive mode (CI, scripting, team onboarding):

npx cc-boost init --yes

Preview without changes:

npx cc-boost init --dry-run

What It Does

Stack Detection

Scans your project files to identify languages and frameworks. Uses corroboration — a single tsconfig.json isn't enough; it needs multiple signals (e.g., .ts files + TypeScript in package.json devDependencies) to confirm a stack with high confidence.

MCP Server Configuration

Generates .mcp.json at your repo root with:

| Server | What It Does | |--------|-------------| | codebase-memory | Structural code indexing — Claude can search your codebase | | cclsp | Language Server Protocol — go-to-definition, find-references, hover | | ast-grep | AST-based code search and transformation | | context7 | Up-to-date library documentation lookup (optional) | | sequential-thinking | Step-by-step reasoning for complex problems (optional) |

LSP Setup

Generates .claude/cclsp.json with the correct language server configuration for your stack — right command, file extensions, and rootDir. Includes reliability warnings for Tier 2 servers (Kotlin, Java, C#) and manual setup notes for Tier 3 (clangd).

Skills

Creates .claude/skills/ with ready-to-use slash commands:

Universal (every project):

| Skill | What It Does | |-------|-------------| | /ccb-reindex | Re-index codebase for structural search | | /ccb-new-feature | Scaffold a new feature with tests | | /ccb-security-review | Review code for security vulnerabilities | | /ccb-debug | Debug an issue systematically | | /ccb-code-review | Review code for quality and correctness | | /ccb-create-pr | Create a pull request with summary | | /ccb-document | Generate documentation for code |

Stack-specific (when applicable):

| Skill | When | What It Does | |-------|------|-------------| | /ccb-new-endpoint | Backend detected | Scaffold a new API endpoint following your framework's conventions | | /ccb-new-component | Frontend detected | Create a new component with the right patterns for your framework | | /ccb-new-migration | ORM detected | Generate a database migration |

Convention skills auto-activate per detected framework (e.g., Django conventions, React patterns, Spring Boot idioms) — no slash command needed, Claude just knows them.

CLAUDE.md Generation

Adds a managed section to your CLAUDE.md with:

• Code intelligence tools available (MCP servers)
• Project structure (detected stacks)
• Available skills
• LSP notes and warnings
• Stack-specific conventions

Safely merges with existing content using delimiters (<!-- cc-boost:start --> / <!-- cc-boost:end -->). Your content above and below is never touched.

Git Hooks

Installs post-checkout, post-merge, and post-rewrite hooks that re-index codebase-memory in the background. Claude's code search stays fresh as you switch branches and pull changes.

Hooks use guard comments (# >>> cc-boost:start / # <<< cc-boost:end) so they coexist with your existing hooks.

Dependency Installation

Detects missing LSP servers and MCP tools, groups everything into one confirmation prompt, and installs via the right package manager:

• macOS: Homebrew
• Linux: apt, pacman
• Language-specific: npm, pip, cargo, go install, gem

Never installs silently. If you decline, it prints the exact manual commands.

Supported Stacks

15 languages, 25+ framework stacks:

| Language | Frameworks | |----------|-----------| | TypeScript | React, Next.js, Vue, Nuxt, Angular, Express, Node | | JavaScript | React, Express, Node | | Python | Django, FastAPI, Flask | | Go | Generic, Gin, Echo | | Rust | Generic, Axum, Actix, Rocket | | Java | Spring Boot (Maven/Gradle) | | Kotlin | Spring Boot | | PHP | Laravel, Symfony | | Ruby | Rails | | C# | .NET | | C/C++ | CMake | | Swift | Xcode projects | | Vue SFC | Single-file components | | Angular | Angular CLI projects |

Monorepo and multi-stack projects are supported — each stack gets its own LSP entry with the correct rootDir.

Commands

cc-boost init

Full setup flow: detect, confirm, generate, install.

npx cc-boost init              # Interactive
npx cc-boost init --yes        # Non-interactive (uses defaults or cc-boost.json)
npx cc-boost init --dry-run    # Preview changes without writing files
npx cc-boost init --no-install # Skip dependency installation

cc-boost status

Show current configuration: detected stacks, MCP servers, LSP servers, configuration drift.

npx cc-boost status

cc-boost update

Re-scan the project for new or removed stacks. Offers to add new config entries and clean up orphaned ones.

npx cc-boost update
npx cc-boost update --yes      # Non-interactive
npx cc-boost update --dry-run  # Preview changes

cc-boost add <stack>

Add a single stack to an existing configuration without running full detection.

npx cc-boost add react
npx cc-boost add python-django

How It Works

npx cc-boost init
        |
        v
  +------------------+
  | Stack Detection   |  Scan files, parse dependency manifests,
  | (15 languages)    |  score confidence with corroboration
  +------------------+
        |
        v
  +------------------+
  | Confirmation      |  Show detected stacks, let user
  | Wizard            |  toggle, accept, or skip
  +------------------+
        |
        v
  +------------------+
  | File Generators   |  .mcp.json, cclsp.json, CLAUDE.md,
  | (merge, never     |  skills/, git hooks
  |  replace)         |
  +------------------+
        |
        v
  +------------------+
  | Dependency        |  Detect missing tools, group install,
  | Installer         |  confirm, verify in PATH
  +------------------+
        |
        v
  +------------------+
  | cc-boost.json     |  Save choices for team reproducibility
  +------------------+

Team Usage

cc-boost generates a cc-boost.json that captures your detected stacks, MCP servers, skill selections, and hook preferences. Check it into version control:

git add cc-boost.json
git commit -m "chore: add cc-boost config for team setup"

When a teammate runs npx cc-boost init, it reads cc-boost.json and skips interactive prompts — everyone gets the exact same environment.

Idempotency

Running cc-boost init again on an already-configured project is always safe:

• CLAUDE.md: Only the managed section between delimiters is replaced
• .mcp.json: New entries are merged; existing user-added servers are preserved
• Git hooks: Only the cc-boost block is updated; surrounding hook content is preserved
• Skills: Overwritten with identical content (safe)

Requirements

• Node.js 22+
• macOS or Linux (Windows support planned for v2)

License

MIT