Skip to content

Claude CodePro is a Professional System for Building Quality Code. It features Spec-Driven Development with Skills, TDD, Automated Dev Container, Semantic Search, Persistent Memory, AI Code Review, and much more πŸš€

License

Notifications You must be signed in to change notification settings

maxritter/claude-codepro

Folders and files

NameName
Last commit message
Last commit date

Latest commit

Β 

History

69 Commits
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 

Repository files navigation

Claude CodePro

A Professional System for Building Quality Code

Stop vibe coding, start shipping systematically with Spec-Driven Development, TDD, and automated workflows.

License: MIT Claude Code Spec-Driven TDD PRs Welcome


πŸ†• What's New in v2.1.0

  • Automated Rules Builder - Modular system that auto-generates Slash Commands and Skills
  • /quick Command - Alternative to spec-driven workflow for fast fixes and refactoring


πŸ“¦ What's Inside

IDE Screenshot

πŸ“‹ Flexible Development Workflows via Slash Commands

Quick Development (For fast fixes, refactoring, experiments):

  • /quick - Fast, focused development without spec-driven overhead β†’ No mandatory TDD (Sonnet 4.5)

Spec-Driven Workflow (For complex features requiring planning and testing):

  • /plan - Based on your input asks the right questions β†’ Detailed spec with exact code (Opus 4.1)
  • /implement - Execute spec with mandatory TDD β†’ Auto-manages context when full (Sonnet 4.5)
  • /remember - Stores learnings in cross-session memory β†’ Continue after /clear (Sonnet 4.5)
  • /verify - E2E spec verification with CodeRabbit AI review β†’ All tests, quality, security (Sonnet 4.5)

πŸ’‘ Modular Rules System with Auto-Generated Commands & Skills

  • Rules Builder - Automatically assembles commands and skills from markdown rules on every cc startup
  • Core Rules - Coding standards, TDD enforcement, error handling, validation, context management
  • Extended Rules - Domain-specific rules auto-converted to skills (@backend-api, @frontend-components, etc.)
  • Workflow Rules - Command-specific behavior for /plan, /implement, /verify, /quick, /remember
  • Flexible Customization - Edit .claude/rules/config.yaml to adjust which rules apply to which commands

πŸ”Œ Enhanced Context and Capabilities via MCP Servers

  • Cipher & Claude Context - Cross-session memory and semantic code search for optimal context
  • Context7 & Ref - Up-to-date library documentation with limited context blur
  • DBHub & FireCrawl - Database access and web scraping for dynamic data retrieval
  • MCP Funnel - Allows to plug-in more MCP servers as needed without wasting context

πŸ› οΈ Testing and Quality via Automated Tool Installation

  • CodeRabbit - AI-powered code review for quality and security
  • Qlty - Automated code quality hooks for all programming languages
  • Newman - API end-to-end testing with Postman collections
  • uv, ruff, mypy, basedpyright - Python linter, formatter, and type checker

πŸ—οΈ Automated Dev Container Setup (VS Code / Cursor / Windsurf)

  • Integrated Features - Zsh, Node.js, Docker-in-Docker, uv, ruff, basedpyright, git, fzf
  • IDE Extensions - Python, Docker, SQL, testing, formatting, and development tools
  • CLI Tools - qlty, Claude Code, Statusline, dotenvx, CodeRabbit, Cipher, Newman
  • Local Database - Local PostgreSQL instance on port 5433 for development and testing

πŸš€ Getting Started

πŸ“‹ Prerequisites

πŸ“₯ Installation

  1. Clone this repository: git clone https://github.com/maxritter/claude-codepro.git
  2. Copy .env.example to .env and add your credentials and API keys
cp .env.example .env
vim .env
  1. Open folder in VS Code, click on the button on the bottom-left: Reopen in Container or open the command pallette via Ctrl + Shift + P and then use > Dev Containers: Reopen in Container
  2. Wait for automatic build to finish, this can take a couple of minutes (feel free to watch the logs in Terminal)

Setup finish Screenshot

5. Run `cc` (which is an alias we created) in the Terminal to finish CC Setup, `cr` to finish CodeRabbit setup ```bash # alias to spawn claude code with loaded environment varaibles cc # code rabbit cmd line tool and setup cr ```

πŸ“’ How-to-use

βš™οΈ Configuration

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

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

Setup config Screenshot

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

Setup mcp Screenshot

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

Setup context Screenshot

  1. In VS Code, click START in the lower bar of the IDE to start a split terminal and monitor CC usage with /usage

Start command Screenshot

πŸ‘£ First Steps

For Quick Changes:

  • Use /quick - Fast development for fixes, refactoring, or experiments without spec overhead
  • TDD not enforced, but best practices still apply via core rules and auto-injected skills

For Complex Features (Spec-Driven & TDD):

  • 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 CodeRabbit AI review, all tests, and quality checks

🎯 Rules Builder

The system uses a modular rules-based architecture that automatically generates slash commands and skills:

  • .claude/rules/core/ - Fundamental rules injected into all commands
  • .claude/rules/workflow/ - Command-specific behavior (plan.md, implement.md, verify.md, quick.md, remember.md)
  • .claude/rules/extended/ - Domain-specific rules auto-converted to individual skills
  • .claude/rules/config.yaml - Defines which rules are included in which commands
  • .claude/rules/builder.py - Assembles markdown rules into commands and skills

Auto-Rebuild: Commands and skills are automatically regenerated on every cc startup, making customization seamless.

βš–οΈ What Makes This Different

Compared to Other Spec-Driven Frameworks (SpecKit, AgentOS, OpenSpec):

  • πŸ’Ύ Persistent Memory - Cross-session memory maintains knowledge between resets
  • ⚑ Token-Optimized - No tokens wasted during too complex planning, just works
  • βœ… Production-Grade - Actively used in client and enterprise projects
  • πŸ“ Enforced TDD - Code written before tests gets deleted automatically
  • πŸ’― Real Verification - Must show actual outputs based on tests, not assumptions
  • πŸ› οΈ Complete Ecosystem - Skills, MCP servers, testing tools are integrated and configured
  • πŸ“¦ Works Immediately - Pre-configured automated setup with everything you need

πŸ‘₯ Who This Is For

  • Professional Developers - Shipping to production with quality standards
  • Solo Builders - Managing complex features without losing context
  • Engineering Teams - Ensuring consistent TDD and code quality
  • Frustrated Coders - Tired of half-tested, "should work" implementations

πŸŽ“ Claude CodePro Academy Coming Soon!

If you want to dive deeper into the setup and advanced usage of Claude CodePro, check out the upcoming academy that starts with 10 comprehensive modules where we do a deep-dive into all important topics:

➑️ www.claude-code.pro


🀝 Contributing

Contributions welcome: custom skills, MCP integrations, workflow improvements, bug reports.


πŸ™ Acknowledgments


Made with ❀️ by Max Ritter

🌐 claude-code.pro

About

Claude CodePro is a Professional System for Building Quality Code. It features Spec-Driven Development with Skills, TDD, Automated Dev Container, Semantic Search, Persistent Memory, AI Code Review, and much more πŸš€

Topics

Resources

License

Stars

Watchers

Forks

Contributors 2

  •  
  •