ECC ships a complete manifest-driven installer that drops the right files into the right place for your harness and profile, then tracks exactly what was installed so upgrades and repairs are deterministic. The fastest path is a singleDocumentation Index
Fetch the complete documentation index at: https://mintlify.com/affaan-m/ECC/llms.txt
Use this file to discover all available pages before exploring further.
npx command with a profile flag — no global install required.
Install ECC
ECC requires Node.js 18 or later and at least one supported AI coding harness. Check both before proceeding:
node --version # must be >= 18.0.0
claude --version # or: cursor --version | codex --version | opencode --version
If you are targeting Claude Code, version v2.1.0 or later is required. Earlier versions handle the plugin hook system differently and will produce duplicate-hook errors.
Pick exactly one install path and stick with it. Layering multiple methods (for example, plugin install followed by a full manual install) creates duplicate skills and duplicate hook execution.
Start with
--profile minimal — it gives you rules, agents, commands, platform configs, and quality workflow skills without the hook runtime. Hooks add powerful automation but also surface-level complexity. Expand to --profile core or --profile developer once you are comfortable with the baseline.ECC’s installer is profile-driven. Each profile is a named set of modules that controls exactly what gets installed for your target harness.
minimalrules-core, agents-core, commands-core, platform-configs, workflow-qualityopencodecommands-core, platform-configs, workflow-qualitycoreminimal + hooks-runtimedevelopercore + framework-language, database, orchestrationsecuritycore + securityresearchcore + research-apis, business-content, social-distributionfullnpx ecc install --profile minimal --target cursor
npx ecc install --profile minimal --target codex
npx ecc install --profile opencode --target opencode
# List all files ECC installed for the current context
npx ecc list-installed
# Query the install state and readiness summary
npx ecc status
You should see a list of installed modules and a readiness indicator. If anything looks wrong, run the doctor and repair commands:
# Diagnose missing or drifted ECC-managed files
npx ecc doctor
# Restore drifted or missing files without reinstalling everything
npx ecc repair
Before adding more components, ask ECC’s advisor which skills and profiles match your actual workflow:
# Get component recommendations from a natural language description
npx ecc consult "I need TypeScript code review" --target claude
# Scope recommendations to a specific domain
npx ecc consult "mlops training model deployment" --target claude
The advisor returns matching component IDs, related profiles, and the exact install command to run. Use
--dry-run on the install command to preview the file plan without writing anything:Skills are the primary workflow surface in ECC. With the install complete, open your harness and invoke a skill directly.
# Step 1: Plan the feature
/ecc:plan "Add rate limiting to the API"
# Step 2: Write tests first with the tdd-workflow skill
# Open the tdd-workflow skill and follow the Red-Green-Improve cycle
# Step 3: Review what was built
/code-review
What’s installed where
After a--target claude install, ECC places files in standard Claude Code locations:
| Content | Location |
|---|---|
| Rules | ~/.claude/rules/ecc/ |
| Agents | ~/.claude/agents/ |
| Skills | ~/.claude/skills/ |
| Commands | ~/.claude/commands/ |
| Hooks | ~/.claude/hooks/hooks.json |
| Platform config | ~/.claude/settings.json (merged, not overwritten) |
npx ecc list-installed shows the full manifest.
Next steps
- Add more modules — Run
npx ecc install --modules hooks-runtime,securityto layer in specific modules without changing your profile. - Upgrade — Run
npx ecc auto-updateto pull the latest ECC changes and reinstall managed targets. - Uninstall — Run
npx ecc uninstall --dry-runto preview removal, thennpx ecc uninstallto clean up all ECC-managed files. - Full installation reference — See Installation for all targets, profiles, module flags, and platform-specific notes.