Skip to content

kromahlusenii-ops/ham / ham

Set up and maintain Hierarchical Agent Memory (HAM) for Codex using scoped local memory files. Trigger on "go ham", "set up HAM", "ham commands", "ham help", "ham route", "ham remove", "ham update", "ham status", "ham benchmark", "ham baseline start", "ham baseline stop", "ham metrics clear", "HAM savings", "HAM stats", "HAM dashboard", "HAM sandwich", "HAM insights", "HAM carbon", or "HAM audit".

FileKindSize
SKILL.mdskill md10.6 KB
agents/openai.yamlconfig181 B
references/platforms.mdmarkdown1.1 KB
references/setup-and-scopes.mdmarkdown2.2 KB
references/templates.mdmarkdown1.8 KB

references/platforms.md

View on GitHub
# Platforms

Use this reference to choose source roots and likely scope boundaries when running `go ham`.

## Source Roots

- Web: `src/` or `app/`
- iOS: project directory matching `.xcodeproj`, or `Sources/`
- Android: `app/src/main/java/` or `app/src/main/kotlin/`
- Flutter: `lib/`
- React Native: `src/` or `app/`

## Platform Signals

- iOS: `*.xcodeproj`, `Package.swift`
- Android: `build.gradle`, `build.gradle.kts`, `settings.gradle`
- Flutter: `pubspec.yaml`
- React Native: `package.json` with `react-native`
- Web: `package.json` with `next`, `nuxt`, `vite`, `svelte`, or similar framework signals
- Python: `pyproject.toml`, `requirements.txt`
- Rust: `Cargo.toml`
- Go: `go.mod`

## Brownfield Hints

When scoping a brownfield repo, prioritize directories where local guidance changes implementation behavior:

- API layers
- shared UI or components
- persistence or data layers
- mobile feature modules
- test directories with specialized fixture patterns

Do not create scoped `CLAUDE.md` files for every directory. Create them only where local conventions, integrations, or gotchas differ materially from the parent scope.
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall