🛠️ Professional Development Environment for Claude Code (CC)

Start shipping systematically with Spec-Driven Development, Skills, TDD, LSP, Semantic Search, Persistent Memory, Context Management, Quality Hooks, Modular Rules System, and much more 🚀

⭐ Star this repository - 🌐 Visit the website

---

🚀 Getting Started

Prerequisites

• Container Runtime - Docker Desktop or OrbStack (macOS)
• IDE - VS Code, Cursor, Windsurf, or Antigravity
• Dev Containers extension - Install from Marketplace

Note: Claude CodePro runs inside a Dev Container for complete isolation, consistent tooling, and cross-platform compatibility.

Installation

Claude CodePro can be installed into any existing project:

1. Open your project folder in your IDE
2. Run this command in the terminal:

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

3. Reopen in Container: Cmd+Shift+P → "Dev Containers: Reopen in Container"
4. Installation completes automatically inside the container

Cursor, Windsurf, Antigravity users: These IDEs don't auto-execute postCreateCommand. After the container starts, run the install command from step 2 again.

---

📦 What's Inside

📋 Spec-Driven Workflow

• /setup - Initialize project context, semantic search indexing, and persistent memory
• /plan - Based on your input asks the right questions → Detailed spec with exact code
• /implement - Execute spec with mandatory TDD → Auto-manages context when full
• /verify - End-to-end spec verification → All tests, quality, security

💡 Modular Rules System

• Auto Loading - Claude Code automatically loads all .claude/rules/*.md files as project memory
• Standard Rules - Best-Practices for TDD, Context Management, etc. in .claude/rules/standard/
• Custom Rules - Project-specific rules in .claude/rules/custom/ (never touched by updates)
• Commands - Workflow-specific modes: /plan, /implement, /verify, /setup
• Skills - Domain-specific @-referenceable guides (e.g., @backend-python-standards)

🔌 Enhanced Context Capabilities

• Claude Mem - Cross-session persistent memory system that automatically ingest context
• Vexor - Local vector store based semantic code search for token-efficient retrieval
• Context7 - AI-powered code context retrieval installed as a plugin with wide support
• Firecrawl - Various tools for searching and scraping the web and direct code fetching
• LSP Servers - Python and TypeScript CC Language Servers for extended code intelligence

🛠️ Intelligent Hook Automation

• Python Quality - Post-edit hook for ruff, mypy, basedpyright linting and type checking (optional)
• TypeScript Quality - Post-edit hook for eslint, tsc, prettier checks (optional)
• General Quality - Post-edit hook for all languages for automated formatting and checking using qlty
• TDD Enforcer - Pre-edit hook that warns when modifying code without failing tests first
• Context Monitor - Post-tool hook that warns CC automatically at 85%/95% context usage

🏗️ One Command Installation

• Dev Container Required - Isolated Linux environment with pre-configured tools and extensions
• Extended Language Support - Optionally install extended support for Python & TypeScript
• Automated Setup Script - Installs and configures everything in one installation command
• Shell Integration - Auto-configures bash, fish and zsh with ccp alias
• IDE Compatible - Works with VS Code, Cursor, Windsurf or Antigravity

---

📒 How-to-use

👣 First Steps

• Use the ccp alias command inside the dev container to open Claude CodePro in any terminal
• Start with /plan - Provide your input and it will ask clarifying questions to create a spec
• Use /implement to execute the spec with automatic TDD, best practices and context management
• When context fills up, run /clear then continue with /implement mentioning your plan file
• After spec completion, run /verify to run end-to-end review, all tests, and quality checks

📖 Context Management

Never use /compact - Claude CodePro is designed to use the full 200k context window:

• Auto-compact must be disabled in /config
• Ignore the compact warning in the bottom right of Claude Code - it appears too early
• Use the full context during /implement sessions until context is actually full
• When context is full, run /clear to start a fresh session
• Claude Mem auto-injects relevant context from your previous session when you continue with /implement

This approach ensures maximum context utilization and seamless session continuity via persistent memory.

🎯 Customizing Rules

Claude CodePro uses Claude Code's modular rules:

• Standard Rules in .claude/rules/standard/ - Updated on install, don't modify
• Custom Rules in .claude/rules/custom/ - Your project-specific rules, never touched by updates
• Path-Specific Rules - Use YAML frontmatter with paths: to scope rules to specific files

Add custom rules by creating .md files in .claude/rules/custom/. You can also use path-specific rules:

---
paths: src/**/*.py
---
# Python-specific rules for this project

---

🙏 Acknowledgments

• thedotmack/claude-mem - CC Persistent Memory system
• sirmalloc/ccstatusline - CC Status line integration
• Piebald-AI/tweakcc - CC Customizations and tweaks for LSP
• scarletkc/vexor - CC Semantic code search
• upstash/context7 - Library code context retrieval
• firecrawl/firecrawl - Web search and scraping tool
• astral-sh/uv - Fast Python package manager
• astral-sh/ruff - Fast Python linter and formatter
• qltysh/qlty - Code quality automation
• DetachHead/basedpyright - Enhanced Python type checker
• dotenvx/dotenvx - Automatic .env loading for Claude Code