π¦ Detailed Installation Guide
A complete guide to ECC installation and configuration options.
System Requirementsβ
- Node.js: >= 20.0
- CodeBuddy: Latest version
- Git: For cloning rule files
Full Installation Processβ
1. Install CodeBuddyβ
If you haven't installed CodeBuddy yet:
# macOS (Homebrew)
brew install codebuddy
# For other platforms, refer to the official documentation
2. Add the ECC Marketplaceβ
codebuddy plugin marketplace add https://github.com/affaan-m/everything-claude-code
This adds the ECC plugin source to your CodeBuddy configuration.
3. Install the ECC Pluginβ
codebuddy plugin install everything-claude-code@everything-claude-code
Includes:
- 13+ Agents
- 31+ Slash Commands
- 28+ Skills
- 20+ Automated Hooks
4. Install Rules (Critical Step)β
β οΈ Important: The ECC plugin cannot automatically distribute rule files β they must be installed manually!
Create the Rules Directoryβ
mkdir -p .codebuddy/rules
Copy Common Rulesβ
cp -r /path/to/everything-claude-code/rules/common/* .codebuddy/rules/
Common rules include:
agents.md- Agent delegation specificationscoding-style.md- Coding style guidegit-workflow.md- Git workflowtesting.md- Testing standards (TDD, 80% coverage)performance.md- Performance optimizationpatterns.md- Design patternshooks.md- Hook architecturesecurity.md- Security standards
Add Language-Specific Rules Based on Your Stackβ
TypeScript projects:
cp -r /path/to/everything-claude-code/rules/typescript/* .codebuddy/rules/
Python projects:
cp -r /path/to/everything-claude-code/rules/python/* .codebuddy/rules/
Go projects:
cp -r /path/to/everything-claude-code/rules/golang/* .codebuddy/rules/
π§ Advanced Configurationβ
Package Manager Setupβ
ECC detects package managers using a priority order:
- Environment variable
CLAUDE_PACKAGE_MANAGER .claude/package-manager.jsonpackageManagerfield inpackage.json- Lock file detection
- Global configuration
- Fallback to first available
Set Preference Manuallyβ
# View currently detected package manager
/setup-pm --detect
# Set to pnpm
/setup-pm --set pnpm
# Set to yarn
/setup-pm --set yarn
# Set to npm
/setup-pm --set npm
Context Configurationβ
Contexts let you use different "personas" for different scenarios:
Create Custom Contextsβ
Create .md files in the .codebuddy/contexts/ directory:
dev.md:
You are an engineer focused on feature development.
- Prioritize TDD methodology
- Focus on code quality and test coverage
- Follow project coding standards
review.md:
You are a strict code reviewer.
- Check for security vulnerabilities
- Verify code style consistency
- Ensure test coverage reaches 80%
Use Contextsβ
# Load a specific context at startup
codebuddy --context dev.md
# Switch context during a session
/context dev.md
π οΈ Troubleshootingβ
Issue: Commands Not Availableβ
Symptom: Typing /plan shows "command not found"
Solution:
- Verify the plugin is installed:
codebuddy plugin list - Restart CodeBuddy
- Check that rules are correctly copied to
.codebuddy/rules/
Issue: Rules Not Taking Effectβ
Symptom: AI doesn't follow the rules and standards
Solution:
- Check rule file paths:
.codebuddy/rules/*.md - Verify rule file format is correct
- Restart the CodeBuddy session
Issue: Wrong Package Manager Detectedβ
Symptom: Using the wrong package manager
Solution:
# Set manually
/setup-pm --set <your-preference>
# Or create .claude/package-manager.json
{
"packageManager": "pnpm"
}
β Verify Installationβ
Run through this checklist:
# 1. Check plugin list
codebuddy plugin list
# Should see everything-claude-code
# 2. Check rule files
ls .codebuddy/rules/
# Should see agents.md, coding-style.md, etc.
# 3. Test a command
codebuddy
# Then type: /plan "test"
# Should see planner agent output
π Congratulations!β
You've completed the full ECC installation! Now you can start exploring:
- Your First Command - Experience the power of /plan
- Core Concepts - Deep dive into Agents/Commands/Skills