Backtalk6858claude-config
The home for everything about how we use Claude and Claude Code to do work — research on the current setup and where we want to take it, the decisions that come out of that research, and the actual config/implementation work when we adopt something.
If we research a tool or workflow and decide to use it, the setup happens here too. Example: the current research covers jcode/OpenCode as open-source alternatives to Claude Code — if we decide to adopt one, its install + Claude integration is done from this directory.
How this is organized
| Path | Holds |
|---|---|
research/ |
Research findings — one file per topic. Start at research/INDEX.md. |
decisions/DECISIONS.md |
Every adopt / reject / defer call, dated, pointing back to the research that drove it. |
config/ |
Implementation artifacts once a decision moves to action (scripts, wiring notes). |
.claude/context.md |
Auto-injected into every session started here, so a fresh session knows the mission. |
Working conventions
- New research → new file in
research/, then add a row toresearch/INDEX.md. Findings move fast (local models, jcode, LifeOS) — re-verify versions/repos/Linux support before acting. - New decision → dated entry in
decisions/DECISIONS.mdlinking the research and the outcome. - Implementation → artifacts in
config/; but live homelab config (~/.claude/settings.jsonand the hooks/skills under/opt/appdata/docker/.claude/) is edited in place — this directory tracks the work and the reasoning, it is not a relocation of the running config.
What lives elsewhere (on purpose)
- Live Claude Code config —
~/.claude/settings.json, hooks + skills under/opt/appdata/docker/.claude/. Authoritative there; we edit in place. - Memory — the homelab-wide memory directories; not migrated here.