lode-capturelisted

Capture a single insight into the lode/ documentation store. Routes the insight to the correct lode file based on topic, writes it as a current-state fact, and timestamps the file. Lightweight alternative to lode-sync for one-off captures. Triggers on: save this to the lode, capture this insight, capture to lode, remember this for next time, save this knowledge, capture that knowledge.
e128/dotnet-reference · ★ 2 · Data & Documents · score 71

Install: claude install-skill e128/dotnet-reference

# Lode Capture Persist a single insight into `lode/`. One insight, one file, one timestamp. ## Workflow ### 1. Extract the insight Parse the insight from `$ARGUMENTS` or the preceding conversation context. ### 2. Route to the correct file | Topic signals | Target lode file | | ------------------------------------------------------------------- | ---------------------------------------------- | | C#, .NET, dotnet, async, analyzer, Roslyn, nullable | `lode/dotnet/*.md` (find closest match) | | Infrastructure, CI, GitHub Actions, hooks, skills, agents | `lode/infrastructure/*.md` | | Scripts, shell | `lode/infrastructure/*.md` | | Practices, code style, conventions, patterns | `lode/practices.md` | | Dependencies, NuGet, packages | `lode/dependency-policy.md` | | Project-wide, architecture, overview | `lode/summary.md` | | Terminology, domain words, definitions | `lode/terminology.md` | ### 3. Read the target file, find the best section heading ### 4. Check file size before writing ```bash scripts/lode-guard.sh lode/path/to/file.md ``` If over li