# How to Install and Configure Everything Claude Code: Complete Setup Guide > Install and configure Everything Claude Code with our complete setup guide. Learn to use 27 agents and 59 commands after quick installation via plugin marketplace or file copy. - Repository: [Affaan Mustafa/everything-claude-code](https://github.com/affaan-m/everything-claude-code) - Tags: getting-started - Published: 2026-03-20 --- **Everything Claude Code (ECC) installs via the Claude Code plugin marketplace or manual file copy, requires separate installation of language-specific rules to `~/.claude/rules` or `.claude/rules`, and activates 27 agents and 59 commands immediately upon configuration.** Everything Claude Code (ECC) is a modular Claude Code plugin that bundles 27 specialized agents, 114 skills, 59 commands, and a comprehensive hook system. Because Claude Code cannot automatically distribute the `rules/` directory, the installation requires a two-step process: adding the plugin manifest and copying language-specific rule sets. This guide covers both the automated plugin installation and manual configuration methods using the exact file paths and commands defined in the `affaan-m/everything-claude-code` repository. ## Install Everything Claude Code via Plugin Marketplace (Recommended) The plugin method is the fastest way to activate ECC's architecture. The system automatically loads the hook registry from [`hooks/hooks.json`](https://github.com/affaan-m/everything-claude-code/blob/main/hooks/hooks.json) without requiring manual edits to [`plugin.json`](https://github.com/affaan-m/everything-claude-code/blob/main/plugin.json). ### Add the Plugin to Claude Code Register the marketplace entry and install the plugin using Claude Code's built-in commands: ```bash /plugin marketplace add affaan-m/everything-claude-code /plugin install everything-claude-code@everything-claude-code ``` The first command makes the repository discoverable by the `/plugin` command. The second downloads the manifest from [`.claude-plugin/plugin.json`](https://github.com/affaan-m/everything-claude-code/blob/main/.claude-plugin/plugin.json) and registers all agents from `agents/`, skills from `skills/`, and commands from `commands/`. ### Verify the Installation Confirm that all components loaded correctly: ```bash /plugin list everything-claude-code@everything-claude-code ``` You should see the full catalog of 27 agents and 59 commands. If the list appears empty, verify that the [`plugin.json`](https://github.com/affaan-m/everything-claude-code/blob/main/plugin.json) manifest is accessible in the repository root. ## Install Language-Specific Rules Rules provide the "always-apply" lint-style and security guidelines that ECC agents rely on for code review. Because Claude Code cannot distribute the `rules/` directory automatically, you must copy these files manually to either a user-wide or project-local location. ### User-Wide Configuration Apply ECC rules to every project you open with Claude Code: ```bash mkdir -p ~/.claude/rules cp -r everything-claude-code/rules/common/* ~/.claude/rules/ cp -r everything-claude-code/rules/typescript/* ~/.claude/rules/ cp -r everything-claude-code/rules/python/* ~/.claude/rules/ ``` Repeat the `cp -r` step for each language you use (golang, php, etc.). The `rules/common/` directory contains universal checks for immutability and security that apply across all languages. ### Project-Local Configuration Restrict ECC rules to a single repository: ```bash mkdir -p .claude/rules cp -r everything-claude-code/rules/common/* .claude/rules/ cp -r everything-claude-code/rules/typescript/* .claude/rules/ ``` Project-local rules override user-wide settings. Consult [`rules/README.md`](https://github.com/affaan-m/everything-claude-code/blob/main/rules/README.md) in the repository for details on creating custom language packs or modifying existing rule sets. ## Manual Installation for Full Control If you prefer not to use the plugin marketplace, clone the repository and copy files directly to Claude Code's configuration directories. ### Clone and Copy Core Components Download the source and install agents, commands, and skills: ```bash git clone https://github.com/affaan-m/everything-claude-code.git cd everything-claude-code cp agents/*.md ~/.claude/agents/ cp commands/*.md ~/.claude/commands/ cp -r skills/.agents/skills/* ~/.claude/skills/ ``` For language-specific capabilities, copy additional skill directories as needed: ```bash cp -r skills/django-patterns ~/.claude/skills/ cp -r skills/react-performance ~/.claude/skills/ ``` ### Install Optional Hook Scripts The hook system enforces style and security checks during editing sessions. To activate runtime behavior, merge the hook registry into your settings: ```bash cp hooks/hooks.json ~/.claude/settings.json ``` Run the package manager detection script to ensure ECC can identify your npm-compatible manager: ```bash node scripts/setup-package-manager.js --detect ``` Alternatively, use the interactive installation wizard for specific targets like Cursor or Antigravity: ```bash ./install.sh --target cursor typescript python golang ``` Windows users can run the PowerShell equivalent: ```powershell .\install.ps1 --target cursor typescript python ``` ## Configure Runtime Behavior with Environment Variables Tune ECC's hook system without editing configuration files by setting these environment variables before launching Claude Code: - **`ECC_HOOK_PROFILE`** – Controls strictness level. Accepts `minimal`, `standard` (default), or `strict`. - **`ECC_DISABLED_HOOKS`** – Comma-separated list of hook IDs to disable temporarily, such as `pre:bash:tmux-reminder,post:edit:typecheck`. - **`CLAUDE_PACKAGE_MANAGER`** – Forces a specific package manager (`npm`, `pnpm`, `yarn`, or `bun`) instead of auto-detection via [`scripts/lib/package-manager.js`](https://github.com/affaan-m/everything-claude-code/blob/main/scripts/lib/package-manager.js). - **`ANTHROPIC_BASE_URL`** and **`ANTHROPIC_AUTH_TOKEN`** – Override the default Claude Code gateway if you operate a custom endpoint. Add these to your shell profile or a `.env` file that you source before running `claude`. ## Verify Your Installation Run a basic command to test agent connectivity: ```bash /everything-claude-code:plan "Add user authentication" ``` The planner agent should return a numbered implementation blueprint. If the command fails, confirm the plugin appears in `/plugin list` and that rule files exist in your configured rules directory. Run the test suite to validate the full installation: ```bash node tests/run-all.js ``` ## Summary - **Plugin installation** requires two commands (`/plugin marketplace add` and `/plugin install`) and automatically loads [`hooks/hooks.json`](https://github.com/affaan-m/everything-claude-code/blob/main/hooks/hooks.json). - **Rules must be copied manually** to `~/.claude/rules` (user-wide) or `.claude/rules` (project-local) because Claude Code cannot distribute the `rules/` directory. - **Manual installation** involves cloning the repo and copying files from `agents/`, `commands/`, and `skills/` to corresponding `~/.claude/` subdirectories. - **Environment variables** like `ECC_HOOK_PROFILE` and `ECC_DISABLED_HOOKS` control runtime behavior without file edits. - **Verification** succeeds when `/everything-claude-code:plan` returns a structured blueprint. ## Frequently Asked Questions ### Why do I need to copy the rules directory separately? Claude Code's plugin architecture cannot automatically distribute the `rules/` directory, so ECC requires manual copying of files from `rules/common/` and language-specific subdirectories to either `~/.claude/rules` (global) or `.claude/rules` (project-specific). This design allows you to customize or omit specific language guidelines while maintaining the core plugin functionality. ### Can I install ECC without using the plugin marketplace? Yes. Clone the repository and manually copy components to Claude Code's configuration directories: `agents/*.md` to `~/.claude/agents/`, `commands/*.md` to `~/.claude/commands/`, and `skills/.agents/skills/*` to `~/.claude/skills/`. Then copy [`hooks/hooks.json`](https://github.com/affaan-m/everything-claude-code/blob/main/hooks/hooks.json) to `~/.claude/settings.json` and run `node scripts/setup-package-manager.js --detect` to enable full functionality. ### How do I disable specific hooks temporarily? Set the `ECC_DISABLED_HOOKS` environment variable to a comma-separated list of hook IDs before launching Claude Code. For example, `export ECC_DISABLED_HOOKS=pre:bash:tmux-reminder,post:edit:typecheck` disables the tmux reminder and post-edit type checking hooks for that session without modifying [`hooks/hooks.json`](https://github.com/affaan-m/everything-claude-code/blob/main/hooks/hooks.json). ### What is the difference between user-wide and project-local rules? User-wide rules in `~/.claude/rules` apply to every repository you open with Claude Code, while project-local rules in `.claude/rules` (relative to your project root) apply only to that specific repository. Project-local configurations override user-wide settings, allowing you to enforce different standards for different codebases.