Installation

Everything Claude Code can be installed as a plugin (recommended) or manually for full control over what’s installed.

Requirements

Minimum version: Claude Code CLI v2.1.0 or laterThis plugin requires Claude Code CLI v2.1.0+ due to changes in how the plugin system handles hooks.Check your version:

claude --version

Platform Support

Everything Claude Code provides full cross-platform support:

✅ Windows - All hooks and scripts rewritten in Node.js for compatibility
✅ macOS - Native support
✅ Linux - Native support

All hooks and scripts have been rewritten in Node.js for maximum compatibility across platforms.

Package Manager Support

The plugin automatically detects your preferred package manager:

npm - Node Package Manager
pnpm - Performant npm
yarn - Yarn Package Manager
bun - Bun Runtime & Package Manager

Detection priority:

Environment variable: CLAUDE_PACKAGE_MANAGER
Project config: .claude/package-manager.json
package.json: packageManager field
Lock file: package-lock.json, yarn.lock, pnpm-lock.yaml, bun.lockb
Global config: ~/.claude/package-manager.json
Fallback: First available package manager

Option 1: Install as Plugin (Recommended)

The easiest way to use Everything Claude Code - install as a Claude Code plugin.

Add Marketplace

Add the Everything Claude Code marketplace to your Claude Code settings:

/plugin marketplace add affaan-m/everything-claude-code

Install Plugin

Install the plugin:

/plugin install everything-claude-code@everything-claude-code

This installs:

13 specialized agents (planner, architect, tdd-guide, code-reviewer, etc.)
33 slash commands (/plan, /tdd, /code-review, etc.)
56+ skills (coding standards, TDD workflow, security review, etc.)
Automated hooks (memory persistence, strategic compaction, security warnings)

Install Rules (Required)

Claude Code plugins cannot distribute rules automatically (upstream limitation). You need to install rules manually.

Clone the repository:

git clone https://github.com/affaan-m/everything-claude-code.git
cd everything-claude-code

Use the installer script (recommended):

./install.sh typescript

The installer:

Always installs common rules (language-agnostic)
Installs requested language-specific rules
Maintains directory structure (common/, typescript/, etc.)
Warns if destination already exists
Validates language names to prevent path traversal

Verify Installation

Verify the plugin is installed and commands are available:

# List all commands from the plugin
/plugin list everything-claude-code@everything-claude-code

# Try a command
/everything-claude-code:plan "Add user authentication"

# Check rules installation
ls -la ~/.claude/rules/

Plugin commands use namespaced form: /everything-claude-code:planManual installation uses shorter form: /plan

Option 2: Manual Installation

For full control over what’s installed, use manual installation.

Clone Repository

Clone the Everything Claude Code repository:

git clone https://github.com/affaan-m/everything-claude-code.git
cd everything-claude-code

Install Agents

Copy agents to your Claude config:

mkdir -p ~/.claude/agents
cp agents/*.md ~/.claude/agents/

This installs 13 specialized agents:

planner, architect, tdd-guide
code-reviewer, security-reviewer
build-error-resolver, go-build-resolver
e2e-runner, refactor-cleaner, doc-updater
go-reviewer, python-reviewer, database-reviewer

Install Rules

Automated (Recommended)
Manual

Use the installer script:

./install.sh typescript

The installer:

Always installs common/ rules (9 files)
Installs requested language rules
Maintains directory structure
Installs to ~/.claude/rules/ by default

Copy rules maintaining directory structure:

# Common rules (always install)
mkdir -p ~/.claude/rules
cp -r rules/common/* ~/.claude/rules/

# Language-specific rules (pick your stack)
cp -r rules/typescript/* ~/.claude/rules/   # TypeScript/JavaScript
cp -r rules/python/* ~/.claude/rules/       # Python
cp -r rules/golang/* ~/.claude/rules/       # Go

Maintain directory structure!Rules must be organized into common/ and language-specific directories so that:

Files with the same name don’t overwrite each other
Relative references (e.g., ../common/coding-style.md) remain valid

Install Commands

Copy commands to your Claude config:

mkdir -p ~/.claude/commands
cp commands/*.md ~/.claude/commands/

This installs 33 slash commands:

/plan, /tdd, /code-review, /build-fix
/e2e, /refactor-clean, /orchestrate
/learn, /checkpoint, /verify, /eval
/go-review, /go-test, /go-build
/python-review, /multi-plan, /multi-execute
And more…

Install Skills

Install core skills or selectively install what you need:

Core Skills Only (Recommended)
All Skills
Selective Installation

Install essential skills for all projects:

mkdir -p ~/.claude/skills

# Core skills from .agents/skills/
cp -r .agents/skills/* ~/.claude/skills/

# Essential general skills
cp -r skills/search-first ~/.claude/skills/
cp -r skills/continuous-learning-v2 ~/.claude/skills/
cp -r skills/strategic-compact ~/.claude/skills/

Install all 56+ skills:

mkdir -p ~/.claude/skills
cp -r skills/* ~/.claude/skills/

Installing all skills may increase context usage. Consider installing only the skills you need.

Install only framework-specific or domain-specific skills:

mkdir -p ~/.claude/skills

# Core skills
cp -r .agents/skills/* ~/.claude/skills/

# Backend patterns
cp -r skills/backend-patterns ~/.claude/skills/
cp -r skills/api-design ~/.claude/skills/

# Django (if using Django)
cp -r skills/django-patterns ~/.claude/skills/
cp -r skills/django-tdd ~/.claude/skills/

# Spring Boot (if using Spring Boot)
cp -r skills/springboot-patterns ~/.claude/skills/
cp -r skills/springboot-tdd ~/.claude/skills/

Configure Hooks

Add hooks to your ~/.claude/settings.json:

# Merge hooks from hooks/hooks.json into your settings.json
# This requires manual editing to avoid overwriting existing config

Copy the hooks section from hooks/hooks.json to your ~/.claude/settings.json. Be careful not to overwrite existing hooks.

Configure MCP Servers (Optional)

Copy desired MCP servers from mcp-configs/mcp-servers.json to your ~/.claude.json:

{
  "mcpServers": {
    "github": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-github"],
      "env": {
        "GITHUB_PERSONAL_ACCESS_TOKEN": "YOUR_TOKEN_HERE"
      }
    },
    "supabase": {
      "command": "npx",
      "args": ["-y", "@supabase/mcp"],
      "env": {
        "SUPABASE_URL": "YOUR_URL_HERE",
        "SUPABASE_SERVICE_ROLE_KEY": "YOUR_KEY_HERE"
      }
    }
  }
}

Replace YOUR_*_HERE placeholders with your actual API keys.Never commit MCP configs with real API keys to version control.

Keep under 10 MCP servers enabled to avoid context window issues. Each MCP tool description consumes tokens.

Cross-Platform Installation

Cursor IDE

Install Everything Claude Code for Cursor IDE:

./install.sh --target cursor typescript
./install.sh --target cursor typescript python golang

Cursor installation includes:

15 hook events (sessionStart, beforeShellExecution, afterFileEdit, etc.)
16 hook scripts (DRY adapter pattern)
29 rules (9 common + 20 language-specific)
Shared agents, skills, and MCP configs via AGENTS.md

OpenCode

Install Everything Claude Code for OpenCode:

cd everything-claude-code
opencode

OpenCode installation includes:

12 agents (shared via plugin system)
24 commands (slash commands)
37 skills (workflow definitions)
11 hook events (via plugin hooks)
6 native custom tools (run-tests, check-coverage, security-audit)

Codex CLI

Install Everything Claude Code for Codex CLI:

# Copy reference config
cp .codex/config.toml ~/.codex/config.toml

# Run in the repo (AGENTS.md auto-detected)
codex

Codex installation includes:

AGENTS.md at root (universal) + .codex/AGENTS.md (Codex-specific)
16 skills from .agents/skills/ (auto-loaded)
4 MCP servers (GitHub, Context7, Memory, Sequential Thinking)
Instruction-based rules via persistent_instructions

Codex CLI does not yet support hooks (GitHub Issue #2109).

Package Manager Configuration

Configure your preferred package manager:

Environment Variable
Global Config
Project Config
package.json
Claude Code Command

Set via environment variable (highest priority):

export CLAUDE_PACKAGE_MANAGER=npm

Set via global config:

node scripts/setup-package-manager.js --global pnpm

This creates ~/.claude/package-manager.json:

{
  "packageManager": "pnpm"
}

Set via project config:

node scripts/setup-package-manager.js --project bun

This creates .claude/package-manager.json:

{
  "packageManager": "bun"
}

Set via package.json:

{
  "packageManager": "[email protected]"
}

Use the /setup-pm command:

/setup-pm

Provides interactive package manager configuration.

Post-Installation

Verify Installation

Verify all components are installed:

# List plugin commands
/plugin list everything-claude-code@everything-claude-code

# Check rules
ls -la ~/.claude/rules/

Test Commands

Test that commands work:

/everything-claude-code:plan "Add user authentication"

Review Configuration

Review and customize settings in ~/.claude/settings.json:

Token optimization settings (model, MAX_THINKING_TOKENS, etc.)
Disabled MCP servers (keep under 10 enabled)
Hook configurations
Package manager preferences

Troubleshooting

Commands not found after plugin installation

Verify the plugin is enabled in ~/.claude/settings.json:

{
  "enabledPlugins": {
    "everything-claude-code@everything-claude-code": true
  }
}

Restart Claude Code after enabling the plugin.

Hooks not working / 'Duplicate hooks file' errors

Do NOT add a "hooks" field to .claude-plugin/plugin.json.Claude Code v2.1+ automatically loads hooks/hooks.json from installed plugins by convention. Explicitly declaring it causes duplicate detection errors.See issues #29, #52, #103.

Rules not being followed

Verify rules maintain directory structure:

ls -la ~/.claude/rules/
# Should show:
# common/
# typescript/ (or python/, golang/, etc.)

Rules files must be in subdirectories, not flat in ~/.claude/rules/.

Context window shrinking

Too many MCP servers consume your context window. Each MCP tool description uses tokens.Fix: Disable unused MCPs in .claude/settings.json:

{
  "disabledMcpServers": ["supabase", "railway", "vercel"]
}

Keep under 10 MCPs enabled and under 80 tools active.

Permission errors on install.sh

Make the installer executable:

chmod +x install.sh
./install.sh typescript

Hooks failing on Windows

Ensure you’re using Claude Code v2.1.0+ and Node.js 18+.All hooks have been rewritten in Node.js for cross-platform compatibility.

# Check Node.js version
node --version
# Should be v18.0.0 or higher

Updating

Plugin
Manual

Update the plugin to the latest version:

# Uninstall old version
/plugin uninstall everything-claude-code@everything-claude-code

# Install latest version
/plugin install everything-claude-code@everything-claude-code

# Update rules manually
cd everything-claude-code
git pull
./install.sh typescript  # or your languages

Update manual installation:

cd everything-claude-code
git pull

# Copy updated components
cp agents/*.md ~/.claude/agents/
cp commands/*.md ~/.claude/commands/
./install.sh typescript python golang

# Update skills (selective or all)
cp -r .agents/skills/* ~/.claude/skills/

Next Steps

Quick Start

Get up and running in under 2 minutes

Key Concepts

Learn about agents, skills, hooks, and rules

Token Optimization

Reduce costs without sacrificing quality

Get Started

Core Concepts

Platform Support

Guides

Installation

Installation

Requirements

Platform Support

Package Manager Support

Option 1: Install as Plugin (Recommended)

Option 2: Manual Installation

Cross-Platform Installation

Cursor IDE

OpenCode

Codex CLI

Package Manager Configuration

Post-Installation

Troubleshooting

Updating

Next Steps

Quick Start

Key Concepts

Token Optimization

Get Started

Core Concepts

Platform Support

Guides

​Installation

​Requirements

​Platform Support

​Package Manager Support

​Option 1: Install as Plugin (Recommended)

​Option 2: Manual Installation

​Cross-Platform Installation

​Cursor IDE

​OpenCode

​Codex CLI

​Package Manager Configuration

​Post-Installation

​Troubleshooting

​Updating

​Next Steps

Quick Start

Key Concepts

Token Optimization

Installation

Requirements

Platform Support

Package Manager Support

Option 1: Install as Plugin (Recommended)

Option 2: Manual Installation

Cross-Platform Installation

Cursor IDE

OpenCode

Codex CLI

Package Manager Configuration

Post-Installation

Troubleshooting

Updating

Next Steps