mirror of
https://github.com/affaan-m/ECC.git
synced 2026-10-26 18:35:05 +00:00
Affaan Mustafa
c05b2d6614
* chore: retire the Everything Claude Code name, ECC only Replace the expanded product name and the everything-claude-code slug with ECC across READMEs, translated docs, harness folders, skills, commands, scripts and examples. Repo URLs now point at affaan-m/ECC. Rename repo-internal artifacts to ecc forms (ecc-conventions skill, ecc-guardrails, ecc-research-playbook, ecc-team-config, ecc-instincts with ecc-* ids) and update .claude/ecc-tools.json. Legacy install ids, plugin dirs, package names and MCP prefixes stay where existing installs resolve against them. The codex global-state check and harness-audit repo detection accept the new name first and the legacy one as a fallback. The Discord bot prefers ~/GitHub/ECC and falls back to the nested legacy checkout path. Refresh the skill-triggers registryDigest for the changed skill text. * fix(ecc-tools): drop managed paths to the removed Claude repo skill .claude/skills/<repo-skill>/SKILL.md was deleted in #2770 but stayed listed in ecc-tools.json and the team config. Remove those entries and point the Claude Code adapter at the existing .agents/skills/ecc-conventions/SKILL.md.
163 lines
4.0 KiB
YAML
163 lines
4.0 KiB
YAML
# Curated instincts for affaan-m/ECC
|
|
# Import with: /instinct-import .claude/homunculus/instincts/inherited/ecc-instincts.yaml
|
|
|
|
---
|
|
id: ecc-conventional-commits
|
|
trigger: "when making a commit in ECC"
|
|
confidence: 0.9
|
|
domain: git
|
|
source: repo-curation
|
|
source_repo: affaan-m/ECC
|
|
---
|
|
|
|
# ECC Conventional Commits
|
|
|
|
## Action
|
|
|
|
Use conventional commit prefixes such as `feat:`, `fix:`, `docs:`, `test:`, `chore:`, and `refactor:`.
|
|
|
|
## Evidence
|
|
|
|
- Mainline history consistently uses conventional commit subjects.
|
|
- Release and changelog automation expect readable commit categorization.
|
|
|
|
---
|
|
id: ecc-commit-length
|
|
trigger: "when writing a commit subject in ECC"
|
|
confidence: 0.8
|
|
domain: git
|
|
source: repo-curation
|
|
source_repo: affaan-m/ECC
|
|
---
|
|
|
|
# ECC Commit Length
|
|
|
|
## Action
|
|
|
|
Keep commit subjects concise and close to the repository norm of about 70 characters.
|
|
|
|
## Evidence
|
|
|
|
- Recent history clusters around ~70 characters, not ~50.
|
|
- Short, descriptive subjects read well in release notes and PR summaries.
|
|
|
|
---
|
|
id: ecc-js-file-naming
|
|
trigger: "when creating a new JavaScript or TypeScript module in ECC"
|
|
confidence: 0.85
|
|
domain: code-style
|
|
source: repo-curation
|
|
source_repo: affaan-m/ECC
|
|
---
|
|
|
|
# ECC JS File Naming
|
|
|
|
## Action
|
|
|
|
Prefer camelCase for JavaScript and TypeScript module filenames, and keep skill or command directories in kebab-case.
|
|
|
|
## Evidence
|
|
|
|
- `scripts/` and test helpers mostly use camelCase module names.
|
|
- `skills/` and `commands/` directories use kebab-case consistently.
|
|
|
|
---
|
|
id: ecc-test-runner
|
|
trigger: "when adding or updating tests in ECC"
|
|
confidence: 0.9
|
|
domain: testing
|
|
source: repo-curation
|
|
source_repo: affaan-m/ECC
|
|
---
|
|
|
|
# ECC Test Runner
|
|
|
|
## Action
|
|
|
|
Use the repository's existing Node-based test flow: targeted `*.test.js` files first, then `node tests/run-all.js` or `npm test` for broader verification.
|
|
|
|
## Evidence
|
|
|
|
- The repo uses `tests/run-all.js` as the central test orchestrator.
|
|
- Test files follow the `*.test.js` naming pattern across hook, CI, and integration coverage.
|
|
|
|
---
|
|
id: ecc-hooks-change-set
|
|
trigger: "when modifying hooks or hook-adjacent behavior in ECC"
|
|
confidence: 0.88
|
|
domain: workflow
|
|
source: repo-curation
|
|
source_repo: affaan-m/ECC
|
|
---
|
|
|
|
# ECC Hooks Change Set
|
|
|
|
## Action
|
|
|
|
Update the hook script, its configuration, its tests, and its user-facing documentation together.
|
|
|
|
## Evidence
|
|
|
|
- Hook fixes routinely span `hooks/hooks.json`, `scripts/hooks/`, `tests/hooks/`, `tests/integration/`, and `hooks/README.md`.
|
|
- Partial hook changes are a common source of regressions and stale docs.
|
|
|
|
---
|
|
id: ecc-cross-platform-sync
|
|
trigger: "when shipping a user-visible feature across ECC surfaces"
|
|
confidence: 0.9
|
|
domain: workflow
|
|
source: repo-curation
|
|
source_repo: affaan-m/ECC
|
|
---
|
|
|
|
# ECC Cross Platform Sync
|
|
|
|
## Action
|
|
|
|
Treat the root repo as the source of truth, then mirror shipped changes to `.cursor/`, `.codex/`, `.opencode/`, and `.agents/` only where the feature actually exists.
|
|
|
|
## Evidence
|
|
|
|
- ECC maintains multiple harness-specific surfaces with overlapping but not identical files.
|
|
- The safest workflow is root-first followed by explicit parity updates.
|
|
|
|
---
|
|
id: ecc-release-sync
|
|
trigger: "when preparing a release for ECC"
|
|
confidence: 0.86
|
|
domain: workflow
|
|
source: repo-curation
|
|
source_repo: affaan-m/ECC
|
|
---
|
|
|
|
# ECC Release Sync
|
|
|
|
## Action
|
|
|
|
Keep package versions, plugin manifests, and release-facing docs synchronized before publishing.
|
|
|
|
## Evidence
|
|
|
|
- Release work spans `package.json`, `.claude-plugin/*`, `.opencode/package.json`, and release-note content.
|
|
- Version drift causes broken update paths and confusing install surfaces.
|
|
|
|
---
|
|
id: ecc-learning-curation
|
|
trigger: "when importing or evolving instincts for ECC"
|
|
confidence: 0.84
|
|
domain: workflow
|
|
source: repo-curation
|
|
source_repo: affaan-m/ECC
|
|
---
|
|
|
|
# ECC Learning Curation
|
|
|
|
## Action
|
|
|
|
Prefer a small set of accurate instincts over bulk-generated, duplicated, or contradictory instincts.
|
|
|
|
## Evidence
|
|
|
|
- Auto-generated instinct dumps can duplicate rules, widen triggers too far, or preserve placeholder detector output.
|
|
- Curated instincts are easier to import, audit, and trust during continuous-learning workflows.
|