ECC uses a manifest-driven installer that resolves exactly which files to write for your chosen harness and profile, then records everything in a local state store. That state record is what makes upgrades, repairs, and clean uninstalls reliable — ECC only touches files it installed.Documentation 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.
Requirements
- Node.js 18 or later — all ECC scripts, hooks, and the installer itself run on Node.js. Earlier versions are not supported.
- A supported AI coding harness — see the targets table below.
- Claude Code v2.1.0 or later — required when targeting
claude. Earlier Claude Code builds handle plugin hooks differently and produce duplicate-detection errors.
Supported Targets
ECC’s installer accepts a--target flag that controls which harness-specific adapter files are written. All 14 targets share the same skill library and agent definitions; only platform configs, hook adapters, and directory layouts differ.
| Target ID | Harness |
|---|---|
claude | Claude Code CLI (primary target) |
claude-project | Claude.ai project-level install |
cursor | Cursor IDE |
antigravity | Antigravity IDE |
codex | OpenAI Codex app and CLI |
gemini | Gemini CLI |
opencode | OpenCode |
codebuddy | CodeBuddy |
joycode | JoyCode |
qwen | Qwen CLI |
zed | Zed editor |
hermes | Hermes operator surface |
openclaw | OpenClaw |
kimi | Kimi |
Three Install Paths
Choose exactly one. Layering methods (for example, plugin install followed by--profile full) creates duplicate skills and duplicate hook execution. If you already have a layered setup, see Uninstall before reinstalling.
- macOS / Linux
- Windows (PowerShell)
Path 1 — npx (recommended, no global install)
npx downloads ecc-universal from npm and runs it once. Nothing is left in your global Node environment.Path 2 — npm global
ecc binary globally so you can invoke it from any directory without npx.Path 3 — git clone
Install Profiles
Profiles are named module bundles. Pass the profile name with--profile to control what gets installed.
minimal — rules, agents, commands, platform configs, quality skills (no hooks)
minimal — rules, agents, commands, platform configs, quality skills (no hooks)
Best for: Low-context setups, users who want ECC’s rule and skill layer without runtime hook enforcement.Modules:
rules-core, agents-core, commands-core, platform-configs, workflow-qualityThe minimal profile intentionally excludes hooks-runtime. You get full rules, all 67 agents, the core command library, platform configurations for your target harness, and the complete quality/TDD/verification skill pack — but hooks do not run automatically. Add hooks later with --modules hooks-runtime when you want runtime enforcement.opencode — commands, platform configs, quality skills (OpenCode default)
opencode — commands, platform configs, quality skills (OpenCode default)
Best for: OpenCode users who want the standard command surface without hooks.Modules:
commands-core, platform-configs, workflow-qualityThe opencode profile is the recommended starting point for OpenCode. It excludes both rules-core (OpenCode uses its own instruction format) and hooks-runtime — opt in with --modules hooks-runtime when ready.core — minimal + hooks-runtime
core — minimal + hooks-runtime
Best for: Users who want the standard harness baseline with automatic hook enforcement.Modules:
rules-core, agents-core, commands-core, hooks-runtime, platform-configs, workflow-qualityAdds the hook runtime on top of minimal. Hooks fire on tool events — auto-formatting after file edits, TypeScript type-checking, console.log detection, dev-server tmux reminders, session persistence on Stop, and more. To install core without hooks on a specific baseline:developer — core + framework/language, database, orchestration
developer — core + framework/language, database, orchestration
Best for: Day-to-day app engineering across multiple frameworks and languages.Modules:
rules-core, agents-core, commands-core, hooks-runtime, platform-configs, workflow-quality, framework-language, database, orchestrationThe developer profile is the recommended default for most ECC users working on app codebases. It adds the full framework and language skill pack (React, Next.js, Django, Laravel, Spring Boot, Quarkus, NestJS, Go, Rust, Kotlin, Swift, C++, Dart/Flutter, .NET, and more), database skills (PostgreSQL, MySQL, ClickHouse, Prisma, JPA), and the worktree/tmux orchestration runtime.security — core + security skills
security — core + security skills
Best for: Security-focused workflows, audits, compliance checks, and AgentShield integration.Modules:
rules-core, agents-core, commands-core, hooks-runtime, platform-configs, workflow-quality, securityAdds the full security module: security-review, security-scan (AgentShield), security-bounty-hunter, hipaa-compliance, healthcare-phi-compliance, framework-specific security skills (Django, Laravel, Spring Boot, Quarkus), DeFi/AMM security, LLM trading agent security, and the complete Security Guide.research — core + research APIs, business content, social distribution
research — core + research APIs, business content, social distribution
full — all currently classified modules
full — all currently classified modules
Best for: Power users who want the entire ECC surface installed at once.Modules: All modules —
rules-core, agents-core, commands-core, hooks-runtime, platform-configs, framework-language, database, workflow-quality, security, research-apis, business-content, operator-workflows, optimization-workflows, prediction-market-skills, social-distribution, media-generation, orchestration, swift-apple, agentic-patterns, devops-infra, machine-learning, supply-chain-domain, document-processingSelective Module Install
Instead of a profile, you can name specific modules directly with--modules. This is useful for adding a single capability on top of an existing install:
manifests/install-modules.json):
rules-core · agents-core · commands-core · hooks-runtime · platform-configs · framework-language · database · workflow-quality · security · research-apis · business-content · operator-workflows · optimization-workflows · prediction-market-skills · social-distribution · media-generation · orchestration · swift-apple · agentic-patterns · devops-infra · machine-learning · supply-chain-domain · document-processing
Include and Exclude Syntax
The installer supports capability-tagged--with and --without flags for fine-grained selection within a profile:
(baseline|lang|framework|capability):<name>.
Preview Before Installing
Use--dry-run on any install command to see exactly what files would be written without touching the filesystem:
plan command for a structured view of the resolved install plan:
Verify, Repair, and Diagnose
Upgrade
Pull the latest ECC changes and reinstall all currently managed targets:Uninstall
ECC only removes files it recorded in its install state — it will never delete unrelated files.- Remove the Claude Code plugin install (
/plugin remove ecc@eccin Claude Code). - Run
npx ecc uninstallto remove install-state-managed files. - Delete any rule folders you copied manually under
~/.claude/rules/ecc/. - Reinstall once, using a single path.
Hook Runtime Controls
After installing a profile that includeshooks-runtime, tune hook behavior with environment variables without editing hook files:
- macOS / Linux
- Windows (PowerShell)
Add these to your shell profile (
~/.zshrc, ~/.bashrc, etc.) to make them persistent:Multi-Harness Isolation
When running ECC in both Claude Code and Cursor on the same machine, set a separate agent data root for Cursor to prevent session files from overwriting each other:| Path | Purpose |
|---|---|
$ECC_AGENT_DATA_HOME/session-data/ | Session summaries |
$ECC_AGENT_DATA_HOME/skills/learned/ | Skills learned from evaluate-session |
$ECC_AGENT_DATA_HOME/session-aliases.json | Session aliases |
$ECC_AGENT_DATA_HOME/metrics/ | Cost and activity metrics |