How to install ECC in Claude Code without duplicates: plugin, npx, Windows and profiles
At the end of the article you'll find the install command, a ready-to-paste prompt and a .md to download.
To install ECC in Claude Code, run npx ecc-universal@2.2.3 setup, choose the scope (user, project or local) and the hook profile, and confirm; you can also use the native commands /plugin marketplace add https://github.com/affaan-m/ECC and /plugin install ecc@ecc. Pick one method only: installing ECC twice into the same agent duplicates skills, commands and hooks.
This is part 2 of the complete ECC guide. Below are the three install paths, which one to choose, how to install just a small profile, how to check that everything landed and how to uninstall without leftovers. We ran the v2.2.3 installer against an empty HOME and wrote down what it actually did.
Requirements
- Node.js 18 or newer (the installer is a Node CLI).
- Git on your
PATH. - Claude Code 2.1 or newer (
claude --version). We used 2.1.329.
On Windows, open PowerShell and check all three:
node --version
git --version
claude --versionIf one is missing, install it first. The installer will not fix it for you.
Which method to choose
| Method | Command | Who it is for |
|---|---|---|
| Guided setup (recommended) | `npx ecc-universal@2.2.3 setup` | Most people: installs the `ecc@ecc` plugin and lets you pick scope and hooks |
| Native plugin | `/plugin install ecc@ecc` inside Claude Code | If you prefer not to run npx |
| Selective installer | `npx ecc-universal@2.2.3 install --profile minimal --target claude` | If you want to control which files are copied and how much context they use |
| Several agents at once | `npx ecc-universal@2.2.3 install --guided` | Claude Code + Codex + Kimi Code in one pass |
The README is blunt: do not stack methods. Plugin plus a full manual install in Claude Code is the combination that breaks most often. Installing it once in Claude Code and once in Codex is fine.
Option 1: the guided setup
npx ecc-universal@2.2.3 setupThe wizard first inventories every Claude Code install scope, then installs, updates or moves ecc@ecc to the scope you choose. For a typical personal setup:
- Choose Global user as the scope.
- Choose Standard as the hook profile.
- Confirm.
- Start a new Claude Code session and run
/plugin list:ecc@eccshould be enabled.
Run the same command again to update ECC or change its scope. With pnpm use pnpm dlx ecc-universal@2.2.3 setup; with Bun, bunx ecc-universal@2.2.3 setup.
Always pin the version (@2.2.3). The README itself says a pin is not an audit: if supply chain risk worries you, read the code first, as you would with any skill you install.
Option 2: native plugin commands
Inside Claude Code:
/plugin marketplace add https://github.com/affaan-m/ECC
/plugin install ecc@eccThis installs the plugin's skills, agents, commands and hooks. Commands are namespaced: /ecc:plan, /ecc:code-review and so on. Once installed, /ecc:configure-ecc opens the same configuration flow as setup.
What the plugin cannot install is rules: Claude Code does not let plugins ship them. Copy them by hand, and only the ones you use:
git clone https://github.com/affaan-m/ECC.git
cd ECC
mkdir -p ~/.claude/rules/ecc
cp -R rules/common ~/.claude/rules/ecc/
cp -R rules/typescript ~/.claude/rules/ecc/Swap typescript for your stack (python, golang, php, rust…). Copy the whole folder, not individual files, so internal references keep working.
Option 3: install a single profile (what we tested)
If context matters to you, the selective installer lets you pick a profile and preview what it will copy. Dry run first, nothing written:
npx ecc-universal@2.2.3 install --profile minimal --target claude --dry-runThe minimal profile requested 5 modules and the installer resolved 7 (it adds skill-unified-memory and shared-script-utils as dependencies). After a real install into an empty HOME, this is what ended up in ~/.claude:
| Folder | Files | Size |
|---|---|---|
| `agents/` | 72 | 624 KB |
| `commands/` | 99 | 604 KB |
| `skills/` | 113 | 1.5 MB |
| `rules/ecc/` | 122 | 664 KB |
Two things we did not expect:
- It copies the rules for every language (Angular, Rust, Swift, PHP…), but 111 of the 122 files carry
paths:in their frontmatter, so Claude Code only loads them when you touch a matching file. The 11 always-loaded files are the common ones, about 2,900 words. - It writes
"includeCoAuthoredBy": falseto~/.claude/settings.json, turning off theCo-Authored-Bytrailer Claude Code adds to your commits. This is deliberate (seescripts/lib/claude-commit-attribution.js) and it respects your choice if you already set that key. If you want to keep attribution, set it totruebefore installing.
For the core profile without hooks, or to add hooks later:
npx ecc-universal@2.2.3 install --profile core --no-hooks --target claude
npx ecc-universal@2.2.3 install --target claude --modules hooks-runtime --enable-hooksIf a profile includes hooks and you pass neither --enable-hooks nor --no-hooks, the installer explains what hooks can do and stops without writing anything. That is a good guardrail: hooks run commands on your machine.
Check the result: list-installed and doctor
npx ecc-universal@2.2.3 list-installed
npx ecc-universal@2.2.3 doctordoctor compares the saved state with the actual files. If you deleted or changed something, repair restores it. If your Claude setup was reset, the README recommends this order before reinstalling: list-installed, doctor, repair.
Common errors
"Missing dependency 'sql.js'". We hit it running the installer from the cloned repository without npm install. Files were copied and doctor reported OK, but the final step failed. Fix: run npm install at the root of the clone, or use npx ecc-universal, which ships its dependencies. The same error shows up if you installed through the marketplace and then run CLI scripts from that copy.
Duplicated skills or commands. You installed with two methods. Uninstall in this order: remove the Claude Code plugin, run uninstall from the folder where you installed, delete the rule folders you copied by hand, then reinstall with a single method.
Hooks firing twice. You copied the repository's hooks/hooks.json into your settings.json while also having the plugin. Claude Code 2.1+ already loads plugin hooks; remove them from settings.json.
/multi-* commands do not work. They need a separate runtime (ccg-workflow) that ECC does not bundle.
Native Windows. The core works, but the continuous learning v2 observer has open Windows bugs. If you plan to lean on it, use WSL.
Uninstall without leftovers
npx ecc-universal@2.2.3 uninstall --dry-run
npx ecc-universal@2.2.3 uninstallECC only deletes what its install state records. In our test the dry run listed 436 files to remove (the 435 copied plus the state file itself) and none of yours. If you used the plugin, remove it from Claude Code with /plugin and delete any rules you copied by hand.
FAQ
Plugin or selective installer? Plugin if you want one-command updates and context is not a concern. Selective with minimal or developer if you want to know exactly what you load.
Can I install it for one project only? Yes: pick the project scope in the wizard, or use the claude-project target with the installer, which copies skills into the repository's .claude/skills/.
Does it work alongside Codex? Yes. npx ecc-universal@2.2.3 install --guided lets you tick Claude Code, Codex and Kimi Code, checks every destination before writing and asks for one final confirmation.
Conclusion
Installing ECC well comes down to three choices: one method, a small profile and rules for your stack only. Run the dry run first and doctor at the end. With ECC installed, the next step is using it: part 3 walks through plan, TDD, code review and build-fix on a sample project.
// resource · use it now
ECC installed and verified in Claude Code
Pick a single install method, run it and check the result with `doctor`. Works with Claude Code 2.1 or newer, Node.js 18+ and Git.
Repository license: MIT
1. Install
npx ecc-universal@2.2.3 setupnpx ecc-universal@2.2.3 install --profile minimal --target claude --dry-run
npx ecc-universal@2.2.3 install --profile minimal --target claude
npx ecc-universal@2.2.3 doctor2. Pick your case
I just installed ECC (the ecc@ecc plugin) in Claude Code. Before using it in this new project:
1. Run /plugin list and confirm ecc@ecc is enabled and there is no other manual ECC copy in ~/.claude.
2. Tell me this project's stack (language and framework) and which ECC rules/ folder matches it. Copy only rules/common and that folder into the project's .claude/rules/ecc/.
3. Create a short CLAUDE.md with: test command, build command, commit convention and the rule "use /ecc:plan before any new feature".
4. Do not install more skills or MCPs. Show me the .claude/ tree when you finish.3. How to use it
- Paste the prompt as the first message in the project folder.
- Check which rules it copied: only
commonand your language should be there. - Start working with
/ecc:plan "what you want to build".
This project already has a CLAUDE.md, its own skills and maybe MCPs. I want to add ECC without breaking anything or duplicating instructions.
1. List what already exists in .claude/ (skills, agents, commands, rules, hooks in settings.json) and in ~/.claude/.
2. Run `npx ecc-universal@2.2.3 consult "<describe our stack and what we do>" --target claude` and propose the smallest profile and components.
3. Flag conflicts: skills with the same name, hooks that would run twice, rules that contradict our CLAUDE.md.
4. Show me the install command with --dry-run and wait for my OK before installing.
5. After installing, run doctor and tell me whether includeCoAuthoredBy changed in settings.json.3. How to use it
- Run the prompt at the repository root.
- Read the conflict list before approving anything.
- Install with the approved dry run and keep the
doctoroutput in the PR.
Help us grow
codigoagente is free, with no paywalls. If this article helped you, any of these keeps the blog going.
- Share it with someone who'll find it usefulWhatsAppLinkedInXFacebook
- Meet our sponsorSafe Build Labs
More on AI agents

- Skills for your agents
- Claude Code

guide · Marketing psychology guide for AI agents · #3
- Skills for your agents
- Claude Code

guide · Marketing psychology guide for AI agents · #2
- Skills for your agents
- Claude Code