Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Professional development environment for Claude Code with spec-driven workflow, TDD enforcement, cross-session memory, semantic search, quality hooks, and modular rules 🛠️

License

Notifications You must be signed in to change notification settings

maxritter/claude-codepro

Open more actions menu

Repository files navigation

Claude CodePro

🛠️ Professional Development Environment for Claude Code (CC)

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

License: AGPL-3.0 Opus 4.5 Modular Rules Spec-Driven TDD


🚀 Getting Started

Prerequisites

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.2.11/install.sh | bash
  1. Reopen in Container: Cmd+Shift+P → "Dev Containers: Reopen in Container"
  2. 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 via Slash Commands

  • /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

Built on Claude Code's modular rules - rules are loaded automatically as project memory.

  • 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 and Capabilities via MCP Servers

  • Claude Mem - Cross-session persistent memory system that automatically ingest context
  • Claude Context - Local vector store based semantic code search for token-efficient retrieval
  • Tavily - Real-time web search capabilities and powerful web mapping tool
  • Ref - AI-powered code context retrieval, similar to Context7 but uses less context
  • MCP Lazy Loading - Intelligently reduces context usage by lazy loading MCP servers

🛠️ Intelligent Hooks for Quality, Standards and Context

  • Qlty Quality - Post-edit hook for automated formatting and code checking for all languages
  • Python Quality - Post-edit hook for uv, ruff, mypy, basedpyright linting and type checking (optional)
  • 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
  • Claude Memory - Various hooks that intelligently manage Claude Memory context injection via claude-mem

🏗️ One-Command Installation

  • Global Tools - Python tools, qlty, Claude Code, dotenvx installed globally
  • Dev Container Required - Isolated Linux environment with pre-configured tools and extensions
  • Automated Setup Script - Installs and configures everything in one command
  • Shell Integration - Auto-configures bash and zsh with ccp alias
  • IDE Compatible - Works with VS Code, Cursor, Windsurf or Antigravity

📒 How-to-use

⚙️ Configuration

  1. Open Claude Code in the IDE Terminal, Extension or an external Terminal with the ccp command

  2. In CC, run /config to set Auto-connect to IDE=true and set Auto-compact=false for best experience Setup config Screenshot

  3. In CC, run /ide to connect to VS Code diagnostics and make sure all MCP servers for /mcp are online Setup mcp Screenshot

  4. In CC, run /plugins → Marketplaces → thedotmack → Click "Update marketplace" & "Enable auto-update" → Restart with ccp → Open http://localhost:37777/ to see Web UI Setup plugin Screenshot

  5. In CC, run /context to verify context looks similar to this screenshot with rules loaded Setup context Screenshot

👣 First Steps

  • 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
  • After spec completion, run /verify to run end-to-end review, all tests, and quality checks

🎯 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

Morty Proxy This is a proxified and sanitized view of the page, visit original site.