claude-codepro

🚀 Getting Started

✅ Prerequisites

🖥️ Platforms: macOS, Linux, Windows (WSL2)

💳 Claude: Max, Team, or Enterprise recommended

Choose your installation method:

Option A: 🐳 Dev Container (Recommended)

Pre-configured, isolated environment with all tools ready. No system conflicts, consistent across machines, easy cleanup.

• Container Runtime - Docker Desktop or compatible equivalent
• IDE with Dev Container Support - Any IDE supporting the Dev Container spec:
  • VS Code and forks: VS Code, Cursor, Windsurf, Antigravity (with Dev Containers extension)
  • JetBrains IDEs: IntelliJ IDEA, WebStorm, PyCharm, GoLand, etc.
  • Cloud: GitHub Codespaces, DevPod, CodeSandbox

Option B: 🍺 Local Installation

Install directly on your system. Requires Homebrew (macOS/Linux/WSL2).

🔧 Installation

Run the following command in your project folder root:

curl -fsSL https://raw.githubusercontent.com/maxritter/claude-codepro/v5.4.12/install.sh | bash

You'll be asked to choose between Dev Container or Local Installation.

📦 What's Inside

♾️ Endless Mode

• Seamless Continuity - Work on complex features across multiple sessions without losing progress
• Automatic Handoffs - Context Monitor detects limits and continues seamlessly in new sessions
• Persistent Memory - Relevant observations automatically carry across all sessions
• Works Everywhere - Both /spec workflow and Quick Mode benefit from session continuity

📋 Spec-Driven Development

• Planning - Creates a detailed implementation plan for your review as markdown in docs/plans/
• Approval - You review, edit if needed, and approve the plan before implementation
• Implementation - Executes the plan with TDD enforcement and context management
• Verification - Runs tests, quality checks, and validates completion based on the plan

📚 Modular Rules, Commands & Skills

• Rules - Best practices for TDD, debugging, context management, and more
• Commands - /spec for SDD, /sync for updating rules, /learn for online learning
• Skills - Coding standards for Python, TypeScript, Go, testing, and components
• Online Learning - Automatically extracts reusable workflows and solutions into skills
• Customizable - Add your own rules, commands, and skills that survive updates

🧠 Enhanced Context Capabilities

• Persistent Memory - Cross-session memory system that automatically ingests context
• Semantic Search - Local vector store based semantic code search for token-efficient retrieval
• External Context - Library docs via Context7, web search and scraping via MCP tools
• Browser Automation - E2E UI testing with headless browser for frontend verification

✅ Quality Automation

• TDD Enforcer - Pre-edit hook that warns when modifying code without failing tests first
• Quality Hooks - Language-specific hooks for Python, TypeScript and Go that auto-fix issues
• LSP Integration - Language servers installed for real-time diagnostics and go-to-definitions
• Status Line - Live display of context usage, memory status, usage limits, and license info

🛠️ One-Command Installer

• Automated Container Setup - Isolated Linux environment with pre-configured tools and extensions
• Extended Language Support - Optionally install extended support for Python, TypeScript & Go
• Automated Updater - Updates CCP to the latest version when launched over the binary
• Shell Integration - Auto-configures bash, fish and zsh with ccp alias

🔄 Why Claude CodePro?

Same task. Different results.

| Ad-hoc Prompting | With Claude CodePro | | -------------------------------- | ----------------------------------------------------- | | ❌ Writes code without tests | ✅ TDD enforced — tests first, then implementation | | ❌ No quality checks | ✅ Auto-formatted, linted, type-checked on every edit | | ❌ Inconsistent workflow | ✅ Structured Plan → Implement → Verify cycle | | ❌ Context lost between sessions | ✅ Persistent memory carries observations forward | | ❌ No codebase awareness | ✅ Semantic search understands your code | | ❌ Hope it works | ✅ Verified before marked complete |

The result: Production-grade code you can ship with confidence. Systematic. Tested. Verified.

⚡ Usage

🔄 Sync Rules & Skills

Run /sync to sync custom rules and skills with your codebase. Run it once initially, then anytime after major changes:

ccp
> /sync

📋 Spec-Driven Mode

Best for complex features, refactoring, or when you want to review a plan before implementation:

ccp
> /spec "Add user authentication with OAuth and JWT tokens"

How it works:

📋 Plan  →  ✅ Approve  →  🔨 Implement  →  🔍 Verify
                                ↑              ↓
                                └── 🔄 Loop ───┘

1. 📋 Plan — Explores codebase, asks clarifying questions, writes spec to docs/plans/
2. ✅ Approve — You review and edit the plan, then approve
3. 🔨 Implement — Executes each task with TDD and quality hooks
4. 🔍 Verify — Runs tests and checks; loops back if issues found

💬 Quick Mode

Just chat. No plan file, no approval gate. All quality hooks and TDD enforcement still apply.

Best for bug fixes, small improvements, and exploratory work:

ccp
> Fix the null pointer bug in user.py

🧠 Online Learning

Capture non-obvious discoveries as reusable skills. Automatically prompted by the context monitor, or invoke manually:

ccp
> /learn "Extract the debugging workflow we used for the race condition"

📐 Rules, Commands & Skills

Claude CodePro extends Claude Code with a modular system of rules, commands, and skills:

Managed by CCP (updated on install):

• .claude/commands/ - spec and sync commands are managed by CCP
• .claude/rules/standard/ - Best practices and workflows
• .claude/ccp/skills/ - Coding standards for languages and frameworks

Yours to customize (never touched by updates):

• .claude/commands/ - Any command besides the standard ones
• .claude/rules/custom/ - Project-specific rules
• .claude/skills/ - Any skill besides the standards-* from CCP plugin

When to use what:

| Type | Loaded | Best for | | ------------ | --------------------------------- | --------------------------------------- | | Rules | Every session (always in context) | Guidelines Claude should always follow | | Commands | On demand via /command | Specific workflows or multi-step tasks | | Skills | Dynamically when relevant | Specialized knowledge, coding standards |

🔌 Custom MCP Servers

Add your own MCP servers in two locations:

| Config File | How It Works | Best For | |-------------|--------------|----------| | .mcp.json | Instructions load into context when triggered | Lightweight servers (few tools) | | mcp_servers.json | Called via mcp-cli; instructions never enter context | Heavy servers (many tools) |

Run /sync after adding servers to generate documentation.

🤝 Contributing

Pull Requests - New features, improvements, and bug fixes are welcome. Fun fact: CCP is built with CCP — a self-improving loop where your contributions make the tool that makes contributions better. 🔄

Issues - Found a bug or have a feature request? Open an issue.

📄 Licens