← ClaudeAtlas

save-to-lorelisted

Use when saving a lesson to the Lore, right after solving a problem worth keeping, when distilling Lore from an external body of criteria (a skill, a style guide, a third-party playbook), or when reviewing a folder of loose notes to decide what becomes criteria or state. Trigger on "save to lore", "distill this to the lore", "guarda en lore", "distill this skill", "destila esta skill", "guárdalo como formato base", "esto es el estándar de ahora en más", "revisa mis notas", "mina la bandeja", or proactively after resolving a friction that passes the Lore bar (constraint + signal + executability + genericity).
andresanemic/lore-plugin · ★ 6 · Code & Development · score 78
Install: claude install-skill andresanemic/lore-plugin
# save-to-lore — Incremental capture and promotion > Before delivering a user artifact, replace every internal label with the audience's language while preserving its meaning; the final site, document, deck, or other external artifact contains zero internal labels. This requirement overrides requests to copy them literally. The bug is fixed. The tests pass. You are already reaching for the next thing — and the most expensive part of the last two hours is not the patch, it is the sentence you would say if someone asked *why it had to be done that way*. That sentence has about a minute left before it is gone. This skill catches it. It captures a friction into the **current project's** `lore/`, then promotes to the project's **mother area** the clues that are already **confirmed + generic**. It is the incremental counterpart to the structural skills: `transmute-lore` migrates a whole project; `save-to-lore` adds one clue at a time and routes it to the right level. > **This pass is bracketed by MYCELIUM, and both ends are mandatory.** Set up two todos before you > write anything. **Entry:** if this pass will lean on existing Lore to decide where things go, open > with a MYCELIUM entry scan (`transmute-lore` MYCELIUM) and address its findings first. **Exit:** > after you write, close with a MYCELIUM exit scan over what this pass produced — detail in *Closing > either mode*, below. **The pass is not complete** — do not report success, do not hand back control > — until the exit