Short answer: do not install ECC directly in C:\ as a loose root-level setup. Put your projects in a normal workspace folder, for example C:\Users\<you>\Projects\my-app, and decide whether ECC should be global or project-local from there.

Recommended path for most Claude Code users:

1. Install the ECC plugin once in Claude Code:

/plugin marketplace add https://github.com/affaan-m/ECC
/plugin install ecc@ecc

2. Then copy only the rule folders you actually want. If you want ECC behavior everywhere, copy them under your user Claude folder. If you want different rules per repo, copy them into that project instead.

For Windows user-level rules, the folder is usually:

%USERPROFILE%\.claude\rules\ecc\

For project-local rules, use this inside the repo:

.claude\rules\ecc\

Start small: rules/common plus the language/framework you use, such as rules/typescript or rules/python. Do not copy every rules folder unless you intentionally want all of that context loaded.

The main thing is: pick one install path only. Do not run /plugin install and then also run install.ps1 --profile full or npx ecc-install --profile full, because that can duplicate commands/hooks/skills. Use the manual installer only if you are intentionally skipping the plugin path or need finer-grained control.

Docs: https://github.com/affaan-m/ECC#quick-start