mirror of
https://github.com/affaan-m/everything-claude-code.git
synced 2026-03-30 13:43:26 +08:00
163 lines
4.6 KiB
YAML
163 lines
4.6 KiB
YAML
# Curated instincts for affaan-m/everything-claude-code
|
|
# Import with: /instinct-import .claude/homunculus/instincts/inherited/everything-claude-code-instincts.yaml
|
|
|
|
---
|
|
id: everything-claude-code-conventional-commits
|
|
trigger: "when making a commit in everything-claude-code"
|
|
confidence: 0.9
|
|
domain: git
|
|
source: repo-curation
|
|
source_repo: affaan-m/everything-claude-code
|
|
---
|
|
|
|
# Everything Claude Code 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: everything-claude-code-commit-length
|
|
trigger: "when writing a commit subject in everything-claude-code"
|
|
confidence: 0.8
|
|
domain: git
|
|
source: repo-curation
|
|
source_repo: affaan-m/everything-claude-code
|
|
---
|
|
|
|
# Everything Claude Code 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: everything-claude-code-js-file-naming
|
|
trigger: "when creating a new JavaScript or TypeScript module in everything-claude-code"
|
|
confidence: 0.85
|
|
domain: code-style
|
|
source: repo-curation
|
|
source_repo: affaan-m/everything-claude-code
|
|
---
|
|
|
|
# Everything Claude Code 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: everything-claude-code-test-runner
|
|
trigger: "when adding or updating tests in everything-claude-code"
|
|
confidence: 0.9
|
|
domain: testing
|
|
source: repo-curation
|
|
source_repo: affaan-m/everything-claude-code
|
|
---
|
|
|
|
# Everything Claude Code 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: everything-claude-code-hooks-change-set
|
|
trigger: "when modifying hooks or hook-adjacent behavior in everything-claude-code"
|
|
confidence: 0.88
|
|
domain: workflow
|
|
source: repo-curation
|
|
source_repo: affaan-m/everything-claude-code
|
|
---
|
|
|
|
# Everything Claude Code 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: everything-claude-code-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/everything-claude-code
|
|
---
|
|
|
|
# Everything Claude Code 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: everything-claude-code-release-sync
|
|
trigger: "when preparing a release for everything-claude-code"
|
|
confidence: 0.86
|
|
domain: workflow
|
|
source: repo-curation
|
|
source_repo: affaan-m/everything-claude-code
|
|
---
|
|
|
|
# Everything Claude Code 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: everything-claude-code-learning-curation
|
|
trigger: "when importing or evolving instincts for everything-claude-code"
|
|
confidence: 0.84
|
|
domain: workflow
|
|
source: repo-curation
|
|
source_repo: affaan-m/everything-claude-code
|
|
---
|
|
|
|
# Everything Claude Code 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.
|