JavaScriptListed by innotive

ECC

affaan-m/ECC

276,430 stars41,230 forks

The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor

The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.

ai-agentsanthropicclaudeclaude-codedeveloper-toolsllmmcpproductivity

Project page

This project has not published an innotive.md page yet.

Repo-native content, AI-friendly workflow

Create innotive.md at the repository root. innotive renders that file as the project page — we do not host an editor.

Keep the content in your repo so it stays versioned with your code. Many teams already run AI in their repositories; drafting innotive.md with your usual AI workflow is usually the fastest path.

Create innotive.md on GitHub

# ECC

One-line summary of what this project does.

## What it solves

Explain the problem and who it's for.

## Quick start

```bash
# install / run commands
```

## Key features

- Feature one
- Feature two

Latest release

Most recent version synced from GitHub.

v2.2.3

Oct 1, 2026

# ECC 2.2.3 ECC 2.2.3 is a naming and release-reliability update. The project is called ECC everywhere it ships, starting with the `pi/core` profile, and the release workflow now waits long enough for npm to serve a freshly published version. ## Naming - `pi/core` no longer expands the project name: its README and the bundled `blueprint` skill refer to ECC only. The profile contents are otherwise unchanged: 123 curated skills and 24 prompt commands, 35,006 characters of skill description text. - Downstream packagers need no changes. The package is still `ecc-pi-core`, the directory is still `pi/core/`, and existing install paths keep working. ## Release workflow - After `npm publish`, the release workflow polls the registry for up to five minutes before verifying the published artifact. In 2.2.2 it gave up after about 30 seconds while npm was still processing the upload, so the run failed before promoting `latest` and creating the GitHub Release, and had to be re-run. Downstream consumption is unchanged: poll `/releases`, download `archive/refs/tags/vX.Y.Z.tar.gz`, pin its sha256, copy `pi/core/`, and load it offline.