zsp/everything-claude-code
1
0
Fork 0
mirror of https://github.com/affaan-m/everything-claude-code.git synced 2026-04-29 21:43:29 +08:00
Code Issues Packages Projects Releases Wiki Activity

feat(ecc2): finalize rc1 release surface

Browse Source
This commit is contained in:
Affaan Mustafa
2026-04-28 22:10:04 -04:00
parent 4e66b2882d
commit 0a87323eda
40 changed files with 863 additions and 76 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/HERMES-SETUP.md
View File

@@ -100,9 +100,9 @@ This stack is useful when you want:
- automation that can nudge, audit, and escalate
- a public repo that shows the system shape without exposing your private operator state
## Public Preview Scope
## Public Release Candidate Scope
ECC 2.0 preview documents the Hermes surface and ships launch collateral now.
ECC v2.0.0-rc.1 documents the Hermes surface and ships launch collateral now.
The remaining private pieces can be layered later:

2
docs/SELECTIVE-INSTALL-ARCHITECTURE.md
View File

@@ -703,7 +703,7 @@ Suggested payload:
"skippedModules": []
},
"source": {
"repoVersion": "1.10.0",
"repoVersion": "2.0.0-rc.1",
"repoCommit": "git-sha",
"manifestVersion": 1
},

111
docs/architecture/cross-harness.md Normal file
View File

@@ -0,0 +1,111 @@
# Cross-Harness Architecture
ECC is the reusable workflow layer. Harnesses are execution surfaces.
The goal is to keep the durable parts of agentic work in one repo:
- skills
- rules and instructions
- hooks where the harness supports them
- MCP configuration
- install manifests
- session and orchestration patterns
Claude Code, Codex, OpenCode, Cursor, Gemini, and future harnesses should adapt those assets at the edge instead of requiring a new workflow model for every tool.
## Portability Model
| Surface | Shared Source | Harness Adapter | Current Status |
|---------|---------------|-----------------|----------------|
| Skills | `skills/*/SKILL.md` | Claude plugin, Codex plugin, `.agents/skills`, Cursor skill copies, OpenCode plugin/config | Supported with harness-specific packaging |
| Rules and instructions | `rules/`, `AGENTS.md`, translated docs | Claude rules install, Codex `AGENTS.md`, Cursor rules, OpenCode instructions | Supported, but not identical across harnesses |
| Hooks | `hooks/hooks.json`, `scripts/hooks/` | Claude native hooks, OpenCode plugin events, Cursor hook adapter | Hook-backed in Claude/OpenCode/Cursor; instruction-backed in Codex |
| MCPs | `.mcp.json`, `mcp-configs/` | Native MCP config import per harness | Supported where the harness exposes MCP |
| Commands | `commands/`, CLI scripts | Claude slash commands, compatibility shims, CLI entrypoints | Supported, but command semantics vary |
| Sessions | `ecc2/`, session adapters, orchestration scripts | TUI/daemon, tmux/worktree orchestration, harness-specific runners | Alpha |
## What Travels Unchanged
`SKILL.md` is the most portable unit.
A good ECC skill should:
- use YAML frontmatter with `name`, `description`, and `origin`
- describe when to use the skill
- state required tools or connectors without embedding secrets
- keep examples repo-relative or generic
- avoid harness-only command assumptions unless the section is clearly labeled
The same source skill can be installed into multiple harnesses because it is mostly instructions, constraints, and workflow shape.
## What Gets Adapted
Each harness has different loading and enforcement behavior:
- Claude Code loads plugin assets and has native hook execution.
- Codex reads `AGENTS.md`, plugin metadata, skills, and MCP config, but hook parity is instruction-driven.
- OpenCode has a plugin/event system that can reuse ECC hook logic through an adapter layer.
- Cursor uses its own rule and hook layout, so ECC maintains translated surfaces under `.cursor/`.
- Gemini support is install/instruction oriented and should be treated as a compatibility surface, not as full hook parity.
Adapters should stay thin. The shared behavior belongs in `skills/`, `rules/`, `hooks/`, `scripts/`, and `mcp-configs/`.
## Hermes Boundary
Hermes is not the public ECC runtime.
Hermes is an operator shell that can consume ECC assets:
- import selected ECC skills into a Hermes skills directory
- use ECC MCP conventions for tool access
- route chat, CLI, cron, and handoff workflows through reusable ECC patterns
- distill repeated local operator work back into sanitized ECC skills
The public repo should ship reusable patterns, not local Hermes state.
Do ship:
- sanitized setup docs
- repo-relative demo prompts
- general operator skills
- examples that do not depend on private credentials
Do not ship:
- OAuth tokens or API keys
- raw `~/.hermes` exports
- personal workspace memory
- private datasets
- local-only automation packs that have not been reviewed
## Today vs Later
Supported today:
- shared skill source in `skills/`
- Claude Code plugin packaging
- Codex plugin metadata and MCP reference config
- OpenCode package/plugin surface
- Cursor-adapted rules, hooks, and skills
- `ecc2/` as an alpha Rust control plane
Still maturing:
- exact hook parity across all harnesses
- automated skill sync into Hermes
- release packaging for `ecc2/`
- cross-harness session resume semantics
- deeper memory and operator planning layers
## Rule For New Work
When adding a workflow, put the durable behavior in ECC first.
Use harness-specific files only for:
- loading the shared asset
- adapting event shapes
- mapping command names
- handling platform limits
If a workflow only works in one harness, document that boundary directly.

2
docs/pt-BR/README.md
View File

@@ -80,7 +80,7 @@ Este repositório contém apenas o código. Os guias explicam tudo.
## O Que Há de Novo
### v1.10.0 — Sincronização de Superfície, Fluxos Operacionais e ECC 2.0 Alpha (Abr 2026)
### v2.0.0-rc.1 — Sincronização de Superfície, Fluxos Operacionais e ECC 2.0 Alpha (Abr 2026)
- **Superfície pública sincronizada com o repositório real** — metadados, contagens de catálogo, manifests de plugin e documentação de instalação agora refletem a superfície OSS que realmente é entregue.
- **Expansão dos fluxos operacionais e externos** — `brand-voice`, `social-graph-ranker`, `customer-billing-ops`, `google-workspace-ops` e skills relacionadas fortalecem a trilha operacional dentro do mesmo sistema.

61
docs/releases/2.0.0-rc.1/article-outline.md Normal file
View File

@@ -0,0 +1,61 @@
# Article Outline - ECC v2.0.0-rc.1
## Working Title
Turning ECC Into a Cross-Harness Operator System
## Core Argument
Most agentic work breaks down because the tools stay isolated.
The leverage comes from treating the harness, reusable workflow layer, and operator shell as one system:
- skills for repeatable work
- hooks and tests for enforcement
- MCPs for tool access
- memory and handoffs for continuity
- one operator shell that can route daily execution
## Structure
### 1. The Problem
- too many chat windows
- too many tool-specific workflows
- too much context living in personal habit instead of reusable system shape
### 2. What ECC Already Solved
- reusable skill format
- cross-harness install surfaces
- hooks and verification discipline
- security and review patterns
- operator workflow skills around content, research, and business ops
### 3. Why Hermes Is the Operator Layer
- chat, CLI, TUI, cron, and handoffs can sit above the reusable ECC layer
- business and content work can run next to engineering work
- the daily loop becomes easier to inspect and improve
### 4. What Ships in rc.1
- sanitized Hermes setup guide
- release and distribution collateral
- cross-harness architecture doc
- Hermes import guidance
- clearer 2.0 positioning in the repo
### 5. What Stays Local
- secrets and auth
- raw workspace exports
- personal datasets
- operator-specific automations that have not been sanitized
- deeper CRM, finance, and Google Workspace playbooks
### 6. Closing Point
The goal is not to copy one exact stack.
The goal is to build an operator system that turns repeated work into reusable, measurable surfaces.

42
docs/releases/2.0.0-rc.1/demo-prompts.md Normal file
View File

@@ -0,0 +1,42 @@
# Hermes x ECC Demo Prompts
## Prompt 1: ECC Builds ECC
Use the current ECC repo and the public release pack at `docs/releases/2.0.0-rc.1/`.
Do 4 things in order:
1. Inspect git status and the current repo diff, then give me a concise ECC v2.0.0-rc.1 PR or release summary that proves ECC is being used to build ECC itself.
2. Finalize one strong X thread.
3. Finalize one strong LinkedIn post.
4. Tell me the exact 3 recordings I should do next plus what Hermes can generate automatically after I record.
Keep it decisive and practical.
## Prompt 2: Turn Recording Into Assets
Assume I just recorded:
- one face-camera hook
- one screen capture of Hermes using ECC to ship ECC v2.0.0-rc.1
- one setup walkthrough of the Hermes x ECC workspace
Give me:
1. a short-form edit plan for X, LinkedIn, TikTok, and YouTube Shorts
2. a voiceover script if I want to re-record clean audio
3. the exact repo-relative filenames and folders I should use for raw footage
4. the assets Hermes can generate automatically after I drop the files in place
Keep it operational.
## Prompt 3: Public Launch Push
Using the ECC v2.0.0-rc.1 release pack, give me:
1. one release tweet
2. one follow-up tweet
3. one LinkedIn comment I can paste under the post
4. one short Telegram handoff I can send to Hermes later to keep distributing this launch across channels
Make it sound like an operator shipping real work, not a launch thread cliche.

41
docs/releases/2.0.0-rc.1/launch-checklist.md Normal file
View File

@@ -0,0 +1,41 @@
# ECC v2.0.0-rc.1 Launch Checklist
## Repo
- verify local `main` is synced to `origin/main`
- verify `docs/HERMES-SETUP.md` is present
- verify `docs/architecture/cross-harness.md` is present
- verify this release directory is committed
- keep private tokens, personal docs, and raw workspace exports out of the repo
## Release Surface
- confirm package and plugin version policy for `2.0.0-rc.1` (drafted in manifest bump prep)
- confirm whether `ecc2/Cargo.toml` moves from `0.1.0` to `2.0.0-rc.1`
- update release metadata in one dedicated release-version PR
- run the root test suite
- run `cd ecc2 && cargo test`
## Content
- publish the X thread from `x-thread.md`
- publish the LinkedIn draft from `linkedin-post.md`
- use `article-outline.md` for the longer writeup
- record one 30-60 second proof-of-work clip
## Demo Asset Suggestions
- Hermes plus ECC side by side
- release docs being generated or reviewed from the repo
- a workflow moving from brief to post to checklist
- `ecc2/` dashboard or session surface with alpha framing
## Messaging
Use language like:
- "release candidate"
- "sanitized operator stack"
- "cross-harness operating system for agentic work"
- "ECC is the reusable substrate; Hermes is the operator shell"
- "private/local integrations land after sanitization"

28
docs/releases/2.0.0-rc.1/linkedin-post.md Normal file
View File

@@ -0,0 +1,28 @@
# LinkedIn Draft - ECC v2.0.0-rc.1
ECC v2.0.0-rc.1 is live as the first release-candidate pass at the 2.0 direction.
The practical shift is simple: ECC is no longer framed as only a Claude Code plugin or config bundle.
It is becoming a cross-harness operating system for agentic work:
- reusable skills instead of one-off prompts
- hooks and tests instead of manual discipline
- MCP-backed access to docs, code, browser automation, and research
- Codex, OpenCode, Cursor, Gemini, and Claude Code surfaces that share the same core workflow layer
- Hermes as the operator shell for chat, cron, handoffs, and daily work routing
For this release-candidate surface, I kept the repo honest.
I did not publish private workspace state. I shipped the reusable layer:
- sanitized Hermes setup documentation
- release notes and launch collateral
- cross-harness architecture notes
- Hermes import guidance for turning local operator patterns into public ECC skills
The leverage is not just better prompting.
It is reducing the number of isolated surfaces, turning repeated workflows into reusable skills, and making the operating system around the agent measurable.
There is still more to harden before GA, especially around packaging, installers, and the `ecc2/` control plane. But rc.1 is enough to show the shape clearly.

54
docs/releases/2.0.0-rc.1/release-notes.md Normal file
View File

@@ -0,0 +1,54 @@
# ECC v2.0.0-rc.1 Release Notes
## Positioning
ECC v2.0.0-rc.1 is the first release-candidate surface for ECC as a cross-harness operating system for agentic work.
Claude Code remains a core target. Codex, OpenCode, Cursor, Gemini, and other harnesses are treated as execution surfaces that can share the same skills, rules, MCP conventions, and operator workflows. ECC is the reusable substrate; Hermes is documented as the operator shell that can sit on top of that layer.
## What Changed
- Added the sanitized Hermes setup guide to the public release story.
- Added launch collateral in-repo so the release can ship from one reviewed surface.
- Clarified the split between ECC as the reusable substrate and Hermes as the operator shell.
- Documented the cross-harness portability model for skills, hooks, MCPs, rules, and instructions.
- Added a Hermes import playbook for turning local operator patterns into publishable ECC skills.
## Why This Matters
ECC is no longer only a Claude Code plugin or config bundle.
The system now has a clearer shape:
- reusable skills instead of one-off prompts
- hooks and tests for workflow discipline
- MCP-backed access to docs, code, browser automation, and research
- cross-harness install surfaces for Claude Code, Codex, OpenCode, Cursor, and related tools
- Hermes as an optional operator shell for chat, cron, handoffs, and daily work routing
## Preview Boundaries
This is a release candidate, not the final GA claim.
What ships in this surface:
- public Hermes setup documentation
- release notes and launch collateral
- cross-harness architecture documentation
- Hermes import guidance for sanitized operator workflows
What stays local:
- secrets, OAuth tokens, and API keys
- private workspace exports
- personal datasets
- operator-specific automations that have not been sanitized
- deeper CRM, finance, and Google Workspace playbooks
## Upgrade Motion
1. Read the [Hermes setup guide](../../HERMES-SETUP.md).
2. Review the [cross-harness architecture](../../architecture/cross-harness.md).
3. Start with one workflow lane: engineering, research, content, or outreach.
4. Import only sanitized operator patterns into ECC skills.
5. Treat `ecc2/` as an alpha control plane until release packaging and installer behavior are finalized.

26
docs/releases/2.0.0-rc.1/telegram-handoff.md Normal file
View File

@@ -0,0 +1,26 @@
# Telegram Handoff For Hermes
Send this to Hermes when you want it to help package the launch workflow.
```text
Use the public ECC release pack in the repo:
- docs/releases/2.0.0-rc.1/release-notes.md
- docs/releases/2.0.0-rc.1/x-thread.md
- docs/releases/2.0.0-rc.1/linkedin-post.md
- docs/releases/2.0.0-rc.1/article-outline.md
- docs/releases/2.0.0-rc.1/launch-checklist.md
- docs/HERMES-SETUP.md
- docs/architecture/cross-harness.md
Task:
1. Finalize one strong X thread for ECC v2.0.0-rc.1.
2. Finalize one strong LinkedIn post for ECC v2.0.0-rc.1.
3. Give me one 30-60 second Hermes x ECC video script and one 15-30 second variant.
4. Tell me exactly what to record now with screen capture, face camera, and voice lines.
5. Tell me what Hermes can generate automatically after I record.
6. End with a minimal checklist of the assets or logins still needed.
Be decisive. Return final drafts plus a practical recording checklist.
```

65
docs/releases/2.0.0-rc.1/x-thread.md Normal file
View File

@@ -0,0 +1,65 @@
# X Thread Draft - ECC v2.0.0-rc.1
1/ ECC v2.0.0-rc.1 is the first release-candidate pass at the 2.0 direction.
The repo is moving from a Claude Code config pack into a cross-harness operating system for agentic work.
2/ The important split:
ECC is the reusable substrate.
Hermes is the operator shell that can run on top.
Skills, hooks, MCP configs, rules, and workflow packs live in ECC.
3/ Claude Code is still a core target.
Codex, OpenCode, Cursor, Gemini, and other harnesses are part of the same story now.
The goal is fewer one-off harness tricks and more reusable workflow surface.
4/ The rc.1 surface ships the public pieces:
- Hermes setup guide
- release notes
- launch checklist
- X and LinkedIn drafts
- cross-harness architecture doc
- Hermes import guidance
5/ It does not ship private workspace state.
No secrets.
No OAuth tokens.
No raw local exports.
No personal datasets.
The point is to publish the reusable system shape.
6/ Why Hermes matters:
Most agent systems fail in the daily operating loop.
They can code, but they do not keep research, content, handoffs, reminders, and execution in one measurable surface.
7/ ECC gives the reusable layer.
Hermes gives the operator shell.
Together they make the work feel less like scattered chat windows and more like a system you can run.
8/ This is still a release candidate.
The public docs and reusable surfaces are ready for review.
The deeper local integrations stay local until they are sanitized.
9/ Start here:
Repo:
<https://github.com/affaan-m/everything-claude-code>
Hermes x ECC setup:
<https://github.com/affaan-m/everything-claude-code/blob/main/docs/HERMES-SETUP.md>
Release notes:
<https://github.com/affaan-m/everything-claude-code/blob/main/docs/releases/2.0.0-rc.1/release-notes.md>

2
docs/tr/AGENTS.md
View File

@@ -2,7 +2,7 @@
Bu, yazılım geliştirme için 28 özel agent, 116 skill, 59 command ve otomatik hook iş akışları sağlayan **üretime hazır bir AI kodlama eklentisidir**.
**Sürüm:** 1.10.0
**Sürüm:** 2.0.0-rc.1
## Temel İlkeler

2
docs/tr/README.md
View File

@@ -79,7 +79,7 @@ Bu repository yalnızca ham kodu içerir. Rehberler her şeyi açıklıyor.
## Yenilikler
### v1.10.0 — Surface Sync, Operatör İş Akışları ve ECC 2.0 Alpha (Nis 2026)
### v2.0.0-rc.1 — Surface Sync, Operatör İş Akışları ve ECC 2.0 Alpha (Nis 2026)
- **Public surface canlı repo ile senkronlandı** — metadata, katalog sayıları, plugin manifest'leri ve kurulum odaklı dokümanlar artık gerçek OSS yüzeyiyle eşleşiyor.
- **Operatör ve dışa dönük iş akışları büyüdü** — `brand-voice`, `social-graph-ranker`, `customer-billing-ops`, `google-workspace-ops` ve ilgili operatör skill'leri aynı sistem içinde tamamlandı.

6
docs/zh-CN/AGENTS.md
View File

@@ -1,8 +1,8 @@
# Everything Claude Code (ECC) — 智能体指令
这是一个**生产就绪的 AI 编码插件**，提供 48 个专业代理、183 项技能、79 条命令以及自动化钩子工作流，用于软件开发。
这是一个**生产就绪的 AI 编码插件**，提供 48 个专业代理、184 项技能、79 条命令以及自动化钩子工作流，用于软件开发。
**版本:** 1.10.0
**版本:** 2.0.0-rc.1
## 核心原则
@@ -147,7 +147,7 @@
```
agents/ — 48 个专业子代理
skills/ — 183 个工作流技能和领域知识
skills/ — 184 个工作流技能和领域知识
commands/ — 79 个斜杠命令
hooks/ — 基于触发的自动化
rules/ — 始终遵循的指导方针（通用 + 每种语言）

8
docs/zh-CN/README.md
View File

@@ -215,7 +215,7 @@ Copy-Item -Recurse rules/typescript "$HOME/.claude/rules/"
/plugin list everything-claude-code@everything-claude-code
```
**搞定！** 你现在可以使用 48 个智能体、183 项技能和 79 个命令了。
**搞定！** 你现在可以使用 48 个智能体、184 项技能和 79 个命令了。
***
@@ -1102,7 +1102,7 @@ opencode
|---------|-------------|----------|--------|
| 智能体 | PASS: 48 个 | PASS: 12 个 | **Claude Code 领先** |
| 命令 | PASS: 79 个 | PASS: 31 个 | **Claude Code 领先** |
| 技能 | PASS: 183 项 | PASS: 37 项 | **Claude Code 领先** |
| 技能 | PASS: 184 项 | PASS: 37 项 | **Claude Code 领先** |
| 钩子 | PASS: 8 种事件类型 | PASS: 11 种事件 | **OpenCode 更多！** |
| 规则 | PASS: 29 条 | PASS: 13 条指令 | **Claude Code 领先** |
| MCP 服务器 | PASS: 14 个 | PASS: 完整 | **完全对等** |
@@ -1214,7 +1214,7 @@ ECC 是**第一个最大化利用每个主要 AI 编码工具的插件**。以
|---------|------------|------------|-----------|----------|
| **智能体** | 48 | 共享 (AGENTS.md) | 共享 (AGENTS.md) | 12 |
| **命令** | 79 | 共享 | 基于指令 | 31 |
| **技能** | 183 | 共享 | 10 (原生格式) | 37 |
| **技能** | 184 | 共享 | 10 (原生格式) | 37 |
| **钩子事件** | 8 种类型 | 15 种类型 | 暂无 | 11 种类型 |
| **钩子脚本** | 20+ 个脚本 | 16 个脚本 (DRY 适配器) | N/A | 插件钩子 |
| **规则** | 34 (通用 + 语言) | 34 (YAML 前页) | 基于指令 | 13 条指令 |
@@ -1224,7 +1224,7 @@ ECC 是**第一个最大化利用每个主要 AI 编码工具的插件**。以
| **上下文文件** | CLAUDE.md + AGENTS.md | AGENTS.md | AGENTS.md | AGENTS.md |
| **秘密检测** | 基于钩子 | beforeSubmitPrompt 钩子 | 基于沙箱 | 基于钩子 |
| **自动格式化** | PostToolUse 钩子 | afterFileEdit 钩子 | N/A | file.edited 钩子 |
| **版本** | 插件 | 插件 | 参考配置 | 1.10.0 |
| **版本** | 插件 | 插件 | 参考配置 | 2.0.0-rc.1 |
**关键架构决策：**