Skip to main content

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.

The ecc install family of commands handles everything from deploying a named profile to a specific AI harness, to inspecting what would be installed, to discovering all available component IDs. All four commands (install, plan, catalog, consult) read the same bundled manifest files — manifests/install-profiles.json and manifests/install-modules.json — and share the same harness target list.

ecc install

Deploy ECC content into a supported AI harness target. ecc install resolves a profile or explicit module list against the bundled manifests, adapts the file set for the chosen target, copies files into the correct target directory, and writes an install-state record so subsequent doctor, repair, and auto-update calls can track the installation.

Usage

ecc install [--profile <name>] [--target <harness>] [options]
ecc install --modules <id,id,...> --target <harness>
ecc install --with <selector> --without <selector> --target <harness>
When invoked without a command (i.e. ecc typescript), positional language names are routed to ecc install for legacy compatibility.

Flags

--profile
string
Named install profile to resolve. Profiles map to curated sets of modules.Available profiles:
ProfileDescription
minimalSmallest useful footprint — core rules only
opencodeTuned defaults for the OpenCode harness
coreStandard rules, hooks, and baseline skills
developerFull developer workflow with TDD, hooks, and MCP patterns
securitySecurity-focused rules, skills, and audit hooks
researchResearch and API documentation modules
fullAll available modules for the selected target
--target
string
The AI harness to install into. Determines the destination directory and adapter used for file placement.
TargetInstall root
claude~/.claude/ (global)
claude-project./.claude/ (per-project)
cursor./.cursor/
codex~/.codex/
gemini./.gemini/
opencode~/.opencode/
zed./.zed/
codebuddy./.codebuddy/
joycode./.joycode/
hermes~/.hermes/
kimi./.kimi/
qwen~/.qwen/
openclaw~/.openclaw/
antigravity./.agent/
Defaults to claude when --target is omitted.
--modules
string
Comma-separated list of explicit module IDs to install, bypassing profile resolution. Use ecc catalog or ecc plan --list-modules to discover available module IDs.
ecc install --modules security,research-apis,tdd --target claude
--with
string
Include an additional user-facing component by its selector ID, such as capability:security or lang:python. Repeatable (pass --with multiple times). May be combined with --profile or --modules.
ecc install --profile core --with capability:security --target claude
--without
string
Exclude a user-facing component by its selector ID. Repeatable. Use to strip unwanted modules from an otherwise complete profile.
ecc install --profile full --without lang:perl --target claude
--skills
string
Install one or more skill directories by ID, e.g. continuous-learning-v2. Comma-separated. IDs are automatically prefixed with skill: if not already present.
ecc install --skills continuous-learning-v2 --target claude
--locale
string
Install translated documentation to ~/.claude/docs/<locale>/ (or ./.claude/docs/<locale>/ for claude-project). Supported only on claude and claude-project targets. Can be combined with --profile or --modules.
--config
string
Load the install intent from an ecc-install.json configuration file. When ecc-install.json is present in the project root it is auto-detected; --config overrides that path.
--dry-run
flag
Show the resolved install plan — file copy operations, target directory, and install-state path — without writing any files. Equivalent to running ecc plan for the same arguments.
--json
flag
Emit a machine-readable JSON object containing either the dry-run plan or the applied result instead of the human-readable summary.

Examples

ecc install --profile minimal --target claude

Output

Human-readable output reports the resolved plan followed by the list of file operations and the path where install-state was written:
Applying install plan:

Mode: profile
Target: claude
Adapter: claude-global
Install root: /Users/you/.claude
Install-state: /Users/you/.claude/install-state/ecc-install-state.json
Profile: developer
Selected modules: tdd, hooks-core, mcp-patterns, security, ...
Operations: 42

Planned file operations:
- rules/ecc/core.md -> /Users/you/.claude/rules/ecc/core.md
- skills/ecc/tdd.md -> /Users/you/.claude/skills/ecc/tdd.md
...

Done. Install-state written to /Users/you/.claude/install-state/ecc-install-state.json

ecc plan

Inspect what a profile or module set would install — including selected modules, skipped modules (excluded by the target adapter), and the full file-operation list — without writing any files or mutating targets.

Usage

ecc plan --list-profiles
ecc plan --list-modules
ecc plan --list-components [--family <family>] [--target <target>]
ecc plan --profile <name> [--target <target>] [--json]
ecc plan --modules <id,id,...> [--target <target>] [--json]

Flags

--list-profiles
flag
Print all available install profiles with their module counts and descriptions.
--list-modules
flag
Print all install modules with their kind, supported targets, default-install flag, cost, and stability metadata.
--list-components
flag
Print all user-facing install components. Filter by --family or --target.
--family
string
Filter --list-components output by component family, such as language, capability, or framework.
--profile
string
Resolve a named profile and print the selected modules, skipped modules (for the given --target), and the operation plan.
--modules
string
Resolve explicit comma-separated module IDs and print the plan.
--target
string
Filter the resolved plan for a specific harness target so skipped modules (those not supported by the adapter) are highlighted.
--json
flag
Emit machine-readable JSON instead of the human-readable plan summary.

Examples

ecc plan --list-profiles

ecc catalog

Discover all available profiles, components, and module IDs from the bundled manifests. No flags are required — catalog subcommands give you a browsable view of everything installable.

Usage

ecc catalog profiles
ecc catalog components [--family <family>]
ecc catalog show <component-id>

Examples

ecc catalog profiles
Pipe ecc catalog components through grep or jq to find the exact component ID for a --with or --without selector before running ecc install.

ecc consult

Recommend ECC components, profiles, and module IDs based on a plain-English description of your project or workflow. ecc consult reads the manifest metadata and returns a ranked list of matching components.

Usage

ecc consult "<query>" [--target <harness>]

Examples

ecc consult "I work on security-sensitive Python APIs"
ecc consult is a recommendation tool — it does not install anything. Pass the suggested profile or module IDs to ecc install to apply them.

Build docs developers (and LLMs) love