mirror of
https://github.com/affaan-m/everything-claude-code.git
synced 2026-03-30 13:43:26 +08:00
63 lines
1.5 KiB
Markdown
63 lines
1.5 KiB
Markdown
# Social Launch Copy (X + LinkedIn)
|
|
|
|
Use these templates as launch-ready starting points. Replace placeholders before posting.
|
|
|
|
## X Post: Release Announcement
|
|
|
|
```text
|
|
ECC v1.8.0 is live.
|
|
|
|
We moved from “config pack” to an agent harness performance system:
|
|
- hook reliability fixes
|
|
- new harness commands
|
|
- cross-tool parity (Claude Code, Cursor, OpenCode, Codex)
|
|
|
|
Start here: <repo-link>
|
|
```
|
|
|
|
## X Post: Proof + Metrics
|
|
|
|
```text
|
|
If you evaluate agent tooling, use blended distribution metrics:
|
|
- npm installs (`ecc-universal`, `ecc-agentshield`)
|
|
- GitHub App installs
|
|
- repo adoption (stars/forks/contributors)
|
|
|
|
We now track this monthly in-repo for sponsor transparency.
|
|
```
|
|
|
|
## X Quote Tweet: Eval Skills Article
|
|
|
|
```text
|
|
Strong point on eval discipline.
|
|
|
|
In ECC we turned this into production checks via:
|
|
- /harness-audit
|
|
- /quality-gate
|
|
- Stop-phase session summaries
|
|
|
|
This is where harness performance compounds over time.
|
|
```
|
|
|
|
## X Quote Tweet: Plankton / deslop workflow
|
|
|
|
```text
|
|
This workflow direction is right: optimize the harness, not just prompts.
|
|
|
|
Our v1.8.0 focus was reliability + parity + measurable quality gates across toolchains.
|
|
```
|
|
|
|
## LinkedIn Post: Partner-Friendly Summary
|
|
|
|
```text
|
|
We shipped ECC v1.8.0 with one objective: improve agent harness performance in production.
|
|
|
|
Highlights:
|
|
- more reliable hook lifecycle behavior
|
|
- new harness-level quality commands
|
|
- parity across Claude Code, Cursor, OpenCode, and Codex
|
|
- stronger sponsor-facing metrics tracking
|
|
|
|
If your team runs AI coding agents daily, this is designed for operational use.
|
|
```
|