🛠️ 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 🚀

⭐ Star this repo

---

🚀 Getting Started

Prerequisites

• Claude Code - Install Claude Code CLI
• Node.js 22+ - Install via nvm (recommended) or nodejs.org
• Python 3.12+ - python.org or via package manager
• Local Infrastructure - Milvus vector database and Ollama for embeddings

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/aliparoya/claude-codepro/main/install.sh | bash

3. Follow the prompts to configure your Milvus/Ollama endpoints
4. Run claude to start Claude Code with the enhanced configuration

---

📦 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
• /remember - Stores learnings in cross-session memory → Continue after /clear

💡 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, /remember, /setup
• Skills - Domain-specific @-referenceable guides (e.g., @backend-python-standards)

🔌 Enhanced Context and Capabilities via MCP Servers

• Cipher - Cross-session memory for persistent knowledge and learnings stored in Vector DB
• Claude Context - Semantic code search for optimal codebase context retrieval
• MCP Funnel - Allows to plug-in more MCP servers as needed without wasting context

🛠️ 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)
• Rules Supervisor - Stop hook that analyzes /implement sessions using Claude CLI
• TDD Enforcer - Pre-edit hook that warns when modifying code without failing tests first
• Context Monitor - Post-tool hook that warns at 85%/95% context usage

🏗️ Simple Installation

• Project-Level Setup - Installs rules, hooks, and MCP config into your project
• Local Infrastructure - Uses your own Milvus and Ollama instances
• Cross-Platform - Works on Linux, macOS, WSL, or Git Bash on Windows
• IDE Compatible - Works with VS Code, Cursor, Windsurf or Antigravity

---

📒 How-to-use

⚙️ Configuration

1. Open Claude Code in the IDE Terminal or Extension with the claude command

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

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

4. In CC, run /context to verify context looks similar to this screenshot with less than 20% used

👣 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
• When context fills, /remember automatically updates your plan and stores learnings
• 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

• qltysh/qlty - Code quality automation
• obra/superpowers - CC Skills inspiration
• buildermethods/agent-os - CC Spec-Driven inspiration
• campfirein/cipher - CC Cross-session memory
• zilliztech/claude-context - CC Semantic code search
• sirmalloc/ccstatusline - CC Status line integration
• chris-schra/mcp-funnel - MCP Tool filtering
• astral-sh/uv - Fast Python package manager
• astral-sh/ruff - Fast Python linter and formatter
• DetachHead/basedpyright - Enhanced Python type checker
• python/mypy - Static type checker for Python
• dotenvx/dotenvx - Automatic .env loading for Claude Code