Claude Project Bundle (CPB)

Claude Project Bundle (CPB) creates comprehensive project snapshots for maintaining context in conversations with Claude AI. When working with complex projects, each new conversation with Claude starts fresh. CPB solves this by generating a well-structured XML document containing your project's current state, making it easy for Claude to understand your project's context.

Installation

You can install CPB globally for regular use:

yarn global add claude-project-bundler

Or use it immediately without installation via npx:

npx claude-project-bundler [directory]

Requirements

• Node.js version 18 or higher
• yarn version 1 or higher

Usage

Basic usage with default settings:

# Using the installed command
cpb

# Or using the full command
claude-project-bundler

Create a bundle for a specific directory:

cpb /path/to/your/project

Create a bundle with custom output location:

cpb --output ./my-bundles --filename project-snapshot.txt

Initialize a new configuration file:

cpb init

Extract project files from a bundle:

cpb extract path/to/bundle.txt -o ./extracted-project

Configuration

CPB works with sensible defaults but can be customized through a configuration file. Create one using:

cpb init

Or manually create cpb.config.json in your project root:

{
  "output": {
    "directory": "./cpb-output",
    "filename": "project-knowledge.txt",
    "timestamped": true
  },
  "files": {
    "include": {
      "asciidoc": [".adoc", ".asc", ".asciidoc"],
      "code": [".js", ".jsx", ".ts", ".tsx", ".py", ".rb", ".java", ".cpp"],
      "docs": [".md", ".json", ".yaml", ".yml"],
      "config": [".json", ".yml", ".yaml", ".toml"]
    },
    "exclude": {
      "directories": ["node_modules", "dist", "build", ".git"],
      "files": [".env", ".DS_Store", "package-lock.json"],
      "patterns": ["*.test.*", "*.spec.*"]
    },
    "binary": {
      "extensions": [".png", ".jpg", ".pdf", ".zip"],
      "maxSize": 1048576
    }
  },
  "project": {
    "mainFiles": ["README.md", "package.json"],
    "typeRules": {
      "node": ["package.json"],
      "python": ["requirements.txt", "setup.py"],
      "asciidoc": [".adoc", ".asc"]
    }
  }
}

Output Format

CPB generates a structured XML document containing:

1. Project Metadata

   • Creation timestamp
   • Project path
   • Configuration settings

2. File Contents

   • Organized by file type (code, docs, config)
   • Preserves directory structure
   • Includes file content with proper XML escaping

Example output structure:

<?xml version="1.0" encoding="UTF-8"?>
<bundle>
  <metadata>
    <created>2024-12-22T16:18:55.123Z</created>
    <projectPath>/path/to/project</projectPath>
    <config>...</config>
  </metadata>
  <files>
    <file path="src/index.js" type="code">
      <content>// File content here</content>
    </file>
  </files>
</bundle>

Command Line Interface

The CLI provides several commands and options:

Usage: cpb [options] [directory]

Options:
  -V, --version           Output version number
  -o, --output <path>     Output directory (default: "./out")
  -f, --filename <name>   Output filename (default: "project_bundle.txt")
  --config <path>        Custom config file path
  --no-timestamp        Disable timestamp in filename
  -h, --help             Display help information

Commands:
  bundle [options] [dir]  Create a project bundle (default)
  init [options] [dir]    Create a default configuration file
  extract <bundle>        Extract project files from a bundle
    Options:
      -o, --output <directory>  Output directory (default: "./extracted")

Using with Claude

1. Generate your project bundle:

   cpb

2. Start a new conversation with Claude and share the generated bundle file.

3. Provide context and instructions for optimal collaboration. Here's an example that combines project context with specific working preferences:

   I'm working on [project description]. I've shared a CPB (Claude Project Bundle) 
   that contains my project's current state. Please reference this context as we work.
   
   Please follow these instructions for our collaboration:
   - always look at the latest project bundle in the project knowledge. my chat prompts will always be about the code
   - always use yarn instead of npm
   - always give full artifacts, never partial. never tell me change this and that. this is very confusing and does not allow me to copy-paste code easily
   - try to do as little changes as possible, so as not to mess up other areas of a file you are updating
   - always specify the full path in accordance with the project bundle in the project knowledge
   - if you ever need to link to the github repo, my username is my_github_username and the repo lives at https://github.com/my_github_username/reponame
   

4. Regenerate the bundle when making significant project changes to keep Claude's context current.

Project File Recovery

You can reconstruct your project files from a bundle using the extract command:

cpb extract path/to/bundle.txt -o ./extracted-project

This will:

• Parse the bundle XML file
• Recreate the original directory structure
• Extract all files with their content
• Preserve file types and paths
• Provide statistics about the extraction process

This feature is useful for:

• Project backup and recovery
• Creating project templates
• Sharing project structures
• Quick project setup for testing

Best Practices

1. Keep bundles up to date with your project's latest state
2. Share bundles at the start of new conversations
3. Include relevant configuration files
4. Maintain a clean project structure for better context
5. Use timestamped filenames to track bundle versions
6. Exclude unnecessary files and directories

Contributing

Contributions are welcome! Please read our Contributing Guidelines for details on our code of conduct and the process for submitting pull requests.

License

This project is licensed under the MIT License - see the LICENSE file for details.

Author

Dennis Decoene

Support

• Report bugs: Issue Tracker
• Get help: Discussions
• Documentation: Wiki