/transmute-lore

name: transmute-lore
description: >-
  Use when a project's existing criteria must be operated as a whole, or when criteria are scattered,
  duplicated, in mixed languages, or possibly disconnected. Also for older skills that need migration.
  Trigger on "transmute", "poda en lore", "prune-lore", "crystallize Lore", "run MYCELIUM", "corre el
  micelio", or "leave Lore". Not yours: adding one lesson belongs to save-to-lore; designing new Lore
  belongs to brainstorming-lore.

Transmute Lore

> Invoke with the Skill tool as `transmute-lore`, or with the phrases «transmute the lore of {proyecto}» / «poda en lore» / «corre el micelio» / «¿está conectado el lore?».

> 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 criteria is already there. It is in a README nobody finishes, in a `CLAUDE.md` that grew by accretion, in a comment that says *don't touch this, it breaks hydration* — written by people who paid for it, sitting in shapes nothing can load. Nothing is missing. Nothing is reachable either.

This skill operates a project's body of criteria. Eight modes, one skill:

• **ADD** — the project **never applied** the Lore method (or has a rough/incomplete `lore/`).

Valuable criteria is *trapped* in non-distillable forms: long READMEs, an everything-mixed instruction contracts (`CLAUDE.md` or `AGENTS.md`), comments, tacit knowledge. ADD extracts it and lifts it to the six-piece standard **without losing it and without inventing what never existed**.

• **CLEAN** — the project already has the standard, but carries **per-project copies of thematic

modules that duplicate what its area already owns**. CLEAN removes those modules, keeps `identidad.md` / `principios.md` / `index.md`, and rewrites `index.md` to point at the **area's** modules — but only after confirming that criteria already lives in the area (or reporting it if it does not).

• **TRANSLATE** — the Lore exists but its **language is mixed or wrong** (e.g. artifacts generated

in English when the user works in Spanish). TRANSLATE standardizes every Lore artifact into one target language — **content and localizable filenames** — preserving structure, link integrity, confidence markers and — above all — **meaning**: it is a translation, never a rewrite.

• **UPGRADE** — the Lore is **in the standard and in active use**, but was written against an older

version of these skills. It is structurally fine and materially behind: it lacks the gates and distinctions the kit learned after it was written. UPGRADE arbitrates the existing Lore **against the current version of the kit** and raises it, without rewriting what is already earned.

• **PRUNE** — the Lore is in the standard, in active use, and **nothing in it is wrong**. It decayed

by accumulating correct things until their sum no longer fits the deliverable. PRUNE is the only mode that asks *does any of this need to be here?* and counts apparatus against content. What it shrinks is **the deliverable's surface**, not necessarily the corpus — see the warning in Phase 4. It is not CLEAN: nothing here is a duplicate.

• **MYCELIUM** — the Lore is in the standard and nothing in it is wrong, and you are about to lean on

it for real work. MYCELIUM walks the network and reports which clues **nothing runs**: no step of any procedure runs them. It writes nothing. It is the only mode that asks *can this fire?* instead of *is this correct?* — and the two are independent, which is why no reading finds it. *Un Lore sin micelio es un herbario* — countable, not fireable. *Ese es el silencio dentro del silencio*: a check can run and its result never be consumed — two separate joints — and it is why MYCELIUM blocks the next operation until every finding is written or explicitly declined.

• **LEAVE** — the project outgrows Lore or the person chooses to leave (H13). LEAVE removes governance (`<!-- lore:always-on -->`) but keeps `lore/` and routing as plain `enrutamiento.md`, leaving `FASES.md` with `leave:` marker so `UPGRADE` can return. Project stays buildable without the kit.
• **CRYSTALLIZE** — the Lore is healthy and must travel as a **single Markdown derivative** into a

chat, an AI project, or a notebook such as NotebookLM. It resolves the live routing into one traceable snapshot while leaving every source untouched. The snapshot is **extractable**: unpacking it rebuilds a mini-root whose routing table resolves, so a third person's AI session can work as closely as possible to the crystallizer's. It **does not replace the six live artifacts** and is not the normal format for work inside an agent or IDE that can read the live tree.

When to use

• **ADD:** a project with real criteria but no standard structure — no `lore/identidad.md` or

`lore/principios.md`, state living inline in the instruction contract, or an incomplete/stale `lore/`. Triggers: *"transmute the lore of {project}"*, *"this old project isn't in the new format"*, *"migrate this project to the lore standard"*.

• **CLEAN:** a project inside an area that has redundant thematic modules (e.g. its own

`lore/animation.md` identical to the area's). Trigger: *"clean the lore of {project}"*.

• **TRANSLATE:** a Lore whose content is in the wrong language, or mixes languages across artifacts.

Triggers: *"standardize the language of the lore of {project}"*, *"translate the lore of {project} to {language}"*, *"estandariza el idioma del lore"*.

• **UPGRADE:** a healthy Lore that predates the installed version of the kit — nothing looks broken,

which is the point. Triggers: *"improve the lore of {project} with the new version"*, *"bring this lore up to date with the plugin"*, *"arbitra mi lore contra la versión nueva"*, *"mejora este lore con lo n