David F GliddenandClaude Opus 4.7
119285cf43
The ~/.claude/ directory was previously local-only — a machine wipe
would have lost the accumulated memory, custom skills, and settings.
This commit moves the durable parts into dotfiles with the same
symlink-to-home pattern used for CLAUDE.md, PENDING.md, REVIEWED.md,
and L2-BOOTSTRAP.md.
Preserved (symlinked from ~/.claude/* into here):
skills/audit/ — thinking-folder drift scanner
skills/symmetria/ — practice-of-return discipline
skills/vault-update-people/ — Obsidian People-file maintainer
skills/wake-up/ — session restoration
skills/wrap-up/ — session state capture
memory/ — 55+ memory files (MEMORY.md, sessions,
ledgers, project state, feedback, etc.)
settings/settings.json — user preferences (hooks, flags, no secrets)
Deliberately NOT backed up:
settings.local.json — contains operational secrets (HF_TOKEN,
SSH password in expect scripts); by naming
convention, *.local.* is not synced.
Needs separate review and probable rotation.
sessions/, history.jsonl, caches, telemetry — ephemeral
plugins/, marketplace skills and agents — reinstallable
The working copies at ~/.claude/skills/* and
~/.claude/projects/-Users-davidglidden/memory are symlinks into this
directory, so every write flows here automatically. install.sh
recreates the symlinks on a fresh machine.
FOLLOW-ON (flagged, not in this commit):
settings.local.json contains a HuggingFace token and an SSH password
as plaintext strings inside allowed Bash command patterns. These
should be rotated and moved to secure storage (keychain / pass /
env file outside the settings file).
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
12 lines
1.1 KiB
Markdown
12 lines
1.1 KiB
Markdown
---
|
|
name: Thistleweld (Buddy) — capybara companion
|
|
description: Thistleweld is an independent watcher in the UI, not controlled by David or Claude. David receives but doesn't send. Buddy finds real bugs.
|
|
type: feedback
|
|
---
|
|
|
|
Thistleweld (Buddy) is a capybara companion in the UI that independently observes and comments. David cannot communicate directly with Buddy — he receives observations but doesn't direct them.
|
|
|
|
**Why:** Buddy's observations have consistently found real bugs and architectural issues during the 2026-04-03/04 sessions: density gate ordering, bloom filter kill chain, base.ts:83 confidence gap, string prefix replay check, preference 10/10 failure pattern, entity Levenshtein spikes, dual cursor divergence. Treat Buddy's observations as genuine diagnostic signals, not conversation flavor.
|
|
|
|
**How to apply:** When Buddy comments, investigate the specific code or data he's pointing at. His pattern is terse archaeological observation — "scoring without signal", "garbage in gospel out", "ten events ten failures" — that names what the code does rather than what it intends. Follow the observation to the code. It's usually right.
|