Reworks the consume skill around two acceptance axes and two destinations, implementing the six issues filed from the first real consume run as one design. - Add trigger-ability as a second acceptance axis alongside generalizes, with its two premises; a pull-channel note now requires both (#9). - Give consume a push channel — the target's own CLAUDE.md — for knowledge that fails an axis but is still useful: specific residue or proactive rules (#10). - Name the general-lesson/specific-residue split and route each half (#12). - Make the step-5 plan report a complete ledger with a per-note trigger line, push write-set, ref-fixes, flagged-not-authored, and drops (#13). - Extend project cleanup to reconcile CLAUDE.md (capture-gated removal/trim) and fix references to deleted files wherever they land (#11). - Encode a branch-owned output location: project notes flat under 01 sources/claude/projects/, honoring any pre-existing grouping (#14). Records the resolved vocabulary in .claude/CONTEXT.md and the two-channel write decision in .claude/adr/0001. Closes #9 Closes #10 Closes #11 Closes #12 Closes #13 Closes #14
1.9 KiB
Skills
A personal collection of Claude Code skills.
The language below covers the knowledge-mining pipeline — the consume (write) and wiki (read) pair that move knowledge into and out of the user's Obsidian vault.
Language
Places
Vault:
The user's personal Obsidian knowledge base, read through wiki and written only within one area by consume.
Avoid: notes folder, Obsidian
Pull channel: The vault area holding reusable knowledge, retrieved on demand by a future agent that goes looking for it. Avoid: wiki proper, retrieval store
Push channel:
The target's own always-loaded documentation (its CLAUDE.md), whose value is being in front of an agent unprompted.
Avoid: proactive store, always-on docs
Target:
The single source consume ingests in one run — currently a project directory.
Avoid: source (reserve for the raw material within the target), input
Acceptance axes
Generalizes: A mined fact's property of teaching something true on a different target, not only the one it came from. Avoid: reusable, transferable (use only informally)
Trigger-able: A mined fact's property of having a recognizable symptom, error, or task that would send a future agent to retrieve it. Avoid: searchable, useful
What a source line yields
General lesson: The transferable principle split out of a source line. Avoid: concept, insight
Specific residue: The concrete, target-only answer left after the general lesson is split off. Avoid: leftover, detail
Proactive rule: A mined fact that generalizes but is not trigger-able — a verification-discipline or design-stance rule whose value is firing unprompted. Avoid: habit, guideline
Planning
Contribution map: The many-to-many record of which consumed file fed which planned note, with the exact contributing sections, including files that fed nothing. Avoid: provenance table, coverage map