.claude/homunculus/instincts/inherited/marketing-council-pack-instincts.yaml

# Instincts generated from https://github.com/imMamdouhaboammar/marketing-council-pack
# Generated: 2026-09-03T10:15:26.128Z
# Version: 2.0
# NOTE: This file supplements (does not replace) any existing curated instincts.
# High-confidence manually curated instincts should be preserved alongside these.

---
id: marketing-council-pack-commit-conventional
trigger: "when writing a commit message"
confidence: 0.85
domain: git
source: repo-analysis
source_repo: https://github.com/imMamdouhaboammar/marketing-council-pack
---

# Marketing Council Pack Commit Conventional

## Action

Use conventional commit format with prefixes: fix, test, ci, feat, docs

## Evidence

- 33 commits analyzed
- Detected conventional commit pattern
- Examples: ci: add plugin release verification workflow, test: define ChatGPT plugin discovery and routing regression gates

---
id: marketing-council-pack-commit-length
trigger: "when writing a commit message"
confidence: 0.6
domain: git
source: repo-analysis
source_repo: https://github.com/imMamdouhaboammar/marketing-council-pack
---

# Marketing Council Pack Commit Length

## Action

Write moderate-length commit messages (~51 characters)

## Evidence

- Average commit message length: 51 chars
- Based on 33 commits

---
id: marketing-council-pack-naming-files
trigger: "when creating a new file"
confidence: 0.8
domain: code-style
source: repo-analysis
source_repo: https://github.com/imMamdouhaboammar/marketing-council-pack
---

# Marketing Council Pack Naming Files

## Action

Use snake_case naming convention

## Evidence

- Analyzed file naming patterns in repository
- Dominant pattern: snake_case

---
id: marketing-council-pack-import-relative
trigger: "when importing modules"
confidence: 0.75
domain: code-style
source: repo-analysis
source_repo: https://github.com/imMamdouhaboammar/marketing-council-pack
---

# Marketing Council Pack Import Relative

## Action

Use relative imports for project files

## Evidence

- Import analysis shows relative import pattern
- Example: import { x } from '../lib/x'

---
id: marketing-council-pack-export-style
trigger: "when exporting from a module"
confidence: 0.7
domain: code-style
source: repo-analysis
source_repo: https://github.com/imMamdouhaboammar/marketing-council-pack
---

# Marketing Council Pack Export Style

## Action

Prefer named exports

## Evidence

- Export pattern analysis
- Dominant style: named

---
id: marketing-council-pack-test-separate
trigger: "when writing tests"
confidence: 0.8
domain: testing
source: repo-analysis
source_repo: https://github.com/imMamdouhaboammar/marketing-council-pack
---

# Marketing Council Pack Test Separate

## Action

Place tests in the tests/ or __tests__/ directory, mirroring src structure

## Evidence

- Separate test directory pattern detected
- Tests live in dedicated test folders

---
id: marketing-council-pack-test-naming
trigger: "when creating a test file"
confidence: 0.85
domain: testing
source: repo-analysis
source_repo: https://github.com/imMamdouhaboammar/marketing-council-pack
---

# Marketing Council Pack Test Naming

## Action

Name test files using the pattern: *.test.ts

## Evidence

- File pattern: *.test.ts
- Consistent across test files

---
id: marketing-council-pack-workflow-feature-development
trigger: "when implementing a new feature"
confidence: 0.75
domain: workflow
source: repo-analysis
source_repo: https://github.com/imMamdouhaboammar/marketing-council-pack
---

# Marketing Council Pack Workflow Feature Development

## Action

Follow the feature-development workflow:
1. Add feature implementation
2. Add tests for feature
3. Update documentation

## Evidence

- Workflow detected from commit patterns
- Frequency: ~5x per month
- Files: **/api/**