mirror of
https://github.com/affaan-m/everything-claude-code.git
synced 2026-04-05 08:43:29 +08:00
60 lines
1.5 KiB
Markdown
60 lines
1.5 KiB
Markdown
# X Thread Draft - ECC 2.0 Preview
|
|
|
|
1/ ECC 2.0 preview is live.
|
|
|
|
This is the first public pass at the setup I actually want to run daily: one operator stack for coding, research, content, outreach, and business ops.
|
|
|
|
2/ The shift is simple:
|
|
|
|
ECC is no longer just a Claude Code config pack.
|
|
It is a cross-harness operating system for agentic work.
|
|
|
|
3/ Claude Code, Codex, Cursor, and OpenCode are still in the mix.
|
|
|
|
Now Hermes joins the public story as the operator shell on top of ECC skills, MCPs, hooks, and workflow packs.
|
|
|
|
4/ I wanted fewer surfaces, not more.
|
|
|
|
Less “which app do I open?”
|
|
More “one place where the system already knows the workflows.”
|
|
|
|
5/ The preview ships a sanitized Hermes setup guide, not a raw private workspace dump.
|
|
|
|
That means:
|
|
- no secrets
|
|
- no personal tokens
|
|
- no fake polish
|
|
- just the reusable system shape
|
|
|
|
6/ I also added release collateral directly in the repo:
|
|
- release notes
|
|
- launch checklist
|
|
- LinkedIn draft
|
|
- short-form video scripts
|
|
|
|
7/ Why?
|
|
|
|
Because half the battle with agent systems is not building them.
|
|
It is operationalizing them:
|
|
- shipping content
|
|
- tracking revenue
|
|
- triaging comms
|
|
- keeping research and execution in one loop
|
|
|
|
8/ If you want the repo:
|
|
read the Hermes setup doc first, then lift the parts you need.
|
|
|
|
You do not need my exact stack.
|
|
You need a system that compounds.
|
|
|
|
9/ ECC 2.0 is still preview.
|
|
|
|
The public docs ship now.
|
|
The rest lands incrementally as the operator surface hardens.
|
|
|
|
10/ Repo + docs:
|
|
<repo-link>
|
|
|
|
Hermes x ECC setup:
|
|
<repo-link>/blob/main/docs/HERMES-SETUP.md
|