Skip to content

AnkitClassicVision/claude-modular

Β 
Β 

Repository files navigation

Claude Code Modular Framework

A comprehensive, production-ready modular framework template for Claude Code that achieves 2-10x productivity gains through proven patterns, token optimization, and systematic development workflows.

πŸš€ Quick Start

1. Clone and Setup

git clone https://github.com/your-username/claude-modular.git
cd claude-modular
cp templates/CLAUDE.md.template CLAUDE.md
# Edit CLAUDE.md with your project-specific details

2. Initialize Your Project

# Copy the .claude directory to your project root
cp -r .claude /path/to/your/project/

# Customize configuration for your environment
cd /path/to/your/project/.claude/config
# Edit settings.json, development.json, etc.

3. Start Using Commands

# In your project with Claude Code
/project:setup-environment
/project:create-feature user-authentication
/test:generate-tests
/dev:code-review

πŸ“š Features

βœ… Token Optimization (50-80% savings)

  • Progressive disclosure - Load only necessary context
  • Modular instructions - Just-in-time command loading
  • Context compression - Efficient context management
  • Smart boundaries - Automatic context switching

βœ… 20+ Production-Ready Commands

  • Project Management - Feature creation, component scaffolding
  • Development Workflow - Code review, refactoring, debugging
  • Testing Automation - Test generation, coverage analysis
  • Deployment - Release preparation, staging deployment, rollback
  • Documentation - API docs, README updates, architecture review

βœ… Environment-Specific Configuration

  • Development - Relaxed rules, verbose logging
  • Staging - Quality gates, review requirements
  • Production - Strict security, multi-factor auth

βœ… Security-First Design

  • Secret scanning prevention
  • Permission validation for sensitive operations
  • Audit logging for compliance
  • Environment variable management

πŸ—οΈ Architecture

Directory Structure

your-project/
β”œβ”€β”€ .claude/                    # Framework configuration
β”‚   β”œβ”€β”€ config/                 # Environment-specific settings
β”‚   β”‚   β”œβ”€β”€ settings.json       # Base configuration
β”‚   β”‚   β”œβ”€β”€ development.json    # Dev environment
β”‚   β”‚   β”œβ”€β”€ staging.json        # Staging environment
β”‚   β”‚   └── production.json     # Production environment
β”‚   └── commands/               # Modular command library
β”‚       β”œβ”€β”€ project/            # Project management
β”‚       β”œβ”€β”€ development/        # Development workflow
β”‚       β”œβ”€β”€ testing/            # Testing automation
β”‚       β”œβ”€β”€ deployment/         # Deployment operations
β”‚       └── documentation/      # Documentation generation
β”œβ”€β”€ CLAUDE.md                   # Your project-specific configuration
└── [your project files]

Command Structure

Each command follows a proven XML structure:

<instructions>
  <context>When and why to use this command</context>
  <requirements>Prerequisites and dependencies</requirements>
  <execution>Step-by-step implementation</execution>
  <validation>Quality checks and acceptance criteria</validation>
  <examples>Concrete usage examples</examples>
</instructions>

πŸ“– Command Reference

Project Management

  • /project:create-feature - Full feature scaffolding with tests and docs
  • /project:scaffold-component - Component creation with boilerplate
  • /project:setup-environment - Development environment initialization

Development Workflow

  • /dev:code-review - Structured code review with automated analysis
  • /dev:refactor-analysis - Code improvement recommendations
  • /dev:debug-session - Systematic debugging and problem solving

Testing

  • /test:generate-tests - Comprehensive test suite generation
  • /test:coverage-analysis - Test coverage assessment and improvement
  • /test:integration-tests - Integration test creation and execution

Deployment

  • /deploy:prepare-release - Release preparation with quality gates
  • /deploy:deploy-staging - Staging deployment with validation
  • /deploy:rollback-procedure - Emergency rollback execution

Documentation

  • /docs:api-docs - API documentation generation
  • /docs:update-readme - README maintenance and updates
  • /docs:architecture-review - Architecture documentation and review

βš™οΈ Configuration

Environment Configuration

The framework supports layered configuration inheritance:

// Base settings.json
{
  "defaults": {
    "max_tokens_per_session": 50000,
    "progressive_disclosure": true
  }
}

// development.json overrides
{
  "extends": "./settings.json",
  "overrides": {
    "defaults": {
      "max_tokens_per_session": 100000
    }
  }
}

Security Configuration

{
  "security": {
    "require_env_vars": true,
    "audit_logging": true,
    "permission_validation": true,
    "secret_scanning": true
  }
}

πŸ”§ Customization

Creating Custom Commands

  1. Create a new command file in appropriate category
  2. Follow the XML structure template
  3. Include comprehensive examples
  4. Test with realistic scenarios

Adapting for Your Stack

  1. Edit templates/CLAUDE.md.template with your technologies
  2. Update command examples for your build tools
  3. Customize quality gates for your requirements
  4. Add stack-specific validation rules

πŸ“Š Performance Metrics

Token Optimization Results

  • 50-80% token savings vs monolithic setups
  • Sub-30-second setup time for new projects
  • 20+ core commands covering 80% of workflows
  • Progressive disclosure reduces context overhead

Quality Improvements

  • Consistent code review quality
  • Automated testing coverage
  • Standardized deployment procedures
  • Comprehensive documentation generation

πŸ› οΈ Integration

MCP Server Support

  • Memory MCP - Context persistence between sessions
  • Git MCP - Version control integration
  • Filesystem MCP - File operations and watching
  • Linear MCP - Issue tracking integration
  • Notion MCP - Documentation synchronization

CI/CD Integration

  • GitHub Actions support
  • Quality gate enforcement
  • Automated testing pipelines
  • Deployment automation

πŸ“š Examples

Basic Usage

# Setup new project
/project:setup-environment

# Create a feature
/project:create-feature user-authentication --type=service

# Review code
/dev:code-review --focus=security,performance

# Deploy to staging
/deploy:deploy-staging

Advanced Workflows

# Complex feature development
/project:create-feature payment-processing --framework=express --database=postgresql

# Comprehensive testing
/test:generate-tests --types=unit,integration,e2e
/test:coverage-analysis --target=90%

# Production deployment
/deploy:prepare-release --type=major
/deploy:deploy-staging --validate
/deploy:rollback-procedure --preserve-data

🀝 Contributing

  1. Fork the repository
  2. Create feature branch: git checkout -b feature/new-command
  3. Add your command following the XML structure
  4. Include comprehensive examples and tests
  5. Update documentation
  6. Submit pull request

πŸ“„ License

MIT License - see LICENSE file for details.

πŸ™ Acknowledgments

Based on research papers:

  • "The modular Claude Code implementation playbook"
  • "Optimizing Agentic Development Workflows with Claude Code"

πŸ“ž Support


Start building better, faster, and more consistently with Claude Code's modular framework.

About

No description, website, or topics provided.

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published