lore plugin
Local fine-tuning for your own tasks, except the one doing the training is you. Operate Lore with use-lore, brainstorming-lore, create-area, create-project, create-bot, save-to-lore, transmute-lore, stale-lore, and vespi.
How to install the lore plugin
Run both commands inside Claude Code. The first adds the marketplace once; the second installs the plugin.
/plugin marketplace add andresanemic/lore-plugin
/plugin install lore@lore-pluginWhat's inside lore
15 parts read from the plugin's own files.
Commands 1
Run as /lore:name- /lore:nivel[off|lite|full]
Ver o cambiar el nivel del recordatorio de Lore Plugin (off, lite, full).
Agents 1
Call as @agent-lore:name- @agent-lore:lore-worker
Worker for one bounded task of an operation coordinated with Lore Plugin. Its prompt is the commission; its method ships with the kit.
Skills 9
Claude loads it when the task matches- brainstorming-lore
Use only when designing or materially changing an artifact owned by the Lore system, or when the person says quiero hacer esto y no se como yet adds hay que pensar el diseño antes de construir — the same no-shape sentence narrowed to the design of a bot, area, project, transmutation or skill. Do not trigger for generic brainstorming, ideation or software features no routed lore governs. Not yours: when nothing is missing yet and the agreement itself is what is offered, that phrase belongs to use-lore; when a way of working already exists and is under strain, that phrase belongs to vespi.
- create-area
Use when starting a brand-new WORK AREA that groups several projects of the same kind (web, research, blog, video, apps…) — before it has any Lore, contract or project registry of its own. Trigger on "create a work area for X", "I want to start working on a domain with Lore", or a shared mold or starter for future projects. Not yours: operating existing criteria in place belongs to transmute-lore.
- create-bot
Use when building a BOT, federating existing Areas under one bot, or auditing a bot that already exists (its scope, README or sources). Trigger on "create a bot for X", "a bot that works on several projects", "federate these areas", "audit my bot", or "fix my bot's scope". Not yours: a new area or project belongs to create-area/create-project; a one-off task does not need a bot.
- create-project
Use when starting a brand-new PROJECT inside an existing WORK AREA (created with create-area) — before it has its own identidad.md, principios.md or index.md. Replaces the old web-only nuevo-sitio. Trigger on "create project X in area Y" or "start project X inside an area". Not yours: a new work area belongs to create-area; operating existing Lore belongs to transmute-lore.
- save-to-lore
Use when saving a lesson to the Lore after a worthwhile fix, distilling an external body of criteria, or reviewing loose notes. Trigger on "save to lore", "distill this skill", "destila esta skill", "revisa mis notas", or after a friction produced a reusable lesson. Not yours: designing a new shape for the work belongs to brainstorming-lore or use-lore; operating an existing Lore method belongs to transmute-lore.
- stale-lore
Use when the kit's published surface must be reconciled against actual usage in the user's tree. Trigger on "stale-lore", "retira capacidades", "capacidades sin ejercicio", "purge unused skills", or after a major refactoring that renames or replaces published capabilities. Not yours: operating a project's criteria body belongs to transmute-lore; saving one lesson belongs to save-to-lore.
- transmute-lore
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.
- use-lore
Use when the person says quiero hacer esto y no se como or todavia no hay forma de trabajo — no hay forma de trabajo yet, so what is missing is the shape itself and the agreement is what is offered. Also when the user mentions lore, installs or updates the plugin, is unsure which Lore skill to invoke, or keeps loose notes in the same folder tree as their Lore. Not yours: if the same sentence narrows to thinking the design of a Lore-owned artifact, that phrase belongs to brainstorming-lore; if a way of working already exists and is under strain, that phrase belongs to vespi. Starting a new work area, project or bot is create-area, create-project or create-bot, not this skill.
- vespi
Use when an operation is under pressure: it must continue across sessions, the route may not suffice, effects carry authority, or resuming silently would pretend nothing changed. Called by the coordinator in role, never by parsing human phrases — strain phrases route through use-lore's canonical table. Not yours: no way of working yet belongs to use-lore; designing a Lore-owned artifact belongs to brainstorming-lore. Only save-to-lore writes Lore.
Hooks 4
Runs on these events- PostToolUsecommand
Agent|Task
- PreCompactcommand
manual|auto
- PreToolUsecommand
apply_patch|Edit|Write|MultiEdit|NotebookEdit, Agent|Task
- SessionStartcommand
No description in the file.
Using lore in Claude Code
Type a command in a Claude Code session:
/lore:nivel [off|lite|full]Ask for an agent by name:
@agent-lore:lore-workerSkills need no command. Claude reads them when your request matches what they describe.
Update, turn off or remove
- Update the plugin (shell)
- claude plugin update lore@lore-plugin
- Refresh the marketplace
- /plugin marketplace update lore-plugin
- Turn it off for now
- /plugin disable lore@lore-plugin
- Remove it
- /plugin uninstall lore@lore-plugin
Skills in lore
- create-botandresanemic/lore-plugin
Use when building a BOT, federating existing Areas under one bot, or auditing a bot that already exists (its scope, README or sources). Trigger on "create a bot for X", "a bot that works on several projects", "federate these areas", "audit my bot", or "fix my bot's scope". Not yours: a new area or project belongs to create-area/create-project; a one-off task does not need a bot.
3 files7stars - save-to-loreandresanemic/lore-plugin
Use when saving a lesson to the Lore after a worthwhile fix, distilling an external body of criteria, or reviewing loose notes. Trigger on "save to lore", "distill this skill", "destila esta skill", "revisa mis notas", or after a friction produced a reusable lesson. Not yours: designing a new shape for the work belongs to brainstorming-lore or use-lore; operating an existing Lore method belongs to transmute-lore.
3 files7stars - stale-loreandresanemic/lore-plugin
Use when the kit's published surface must be reconciled against actual usage in the user's tree. Trigger on "stale-lore", "retira capacidades", "capacidades sin ejercicio", "purge unused skills", or after a major refactoring that renames or replaces published capabilities. Not yours: operating a project's criteria body belongs to transmute-lore; saving one lesson belongs to save-to-lore.
4 files7stars - transmute-loreandresanemic/lore-plugin
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.
11 files7stars - use-loreandresanemic/lore-plugin
Use when the person says quiero hacer esto y no se como or todavia no hay forma de trabajo — no hay forma de trabajo yet, so what is missing is the shape itself and the agreement is what is offered. Also when the user mentions lore, installs or updates the plugin, is unsure which Lore skill to invoke, or keeps loose notes in the same folder tree as their Lore. Not yours: if the same sentence narrows to thinking the design of a Lore-owned artifact, that phrase belongs to brainstorming-lore; if a way of working already exists and is under strain, that phrase belongs to vespi. Starting a new work area, project or bot is create-area, create-project or create-bot, not this skill.
2 files7stars - vespiandresanemic/lore-plugin
Use when an operation is under pressure: it must continue across sessions, the route may not suffice, effects carry authority, or resuming silently would pretend nothing changed. Called by the coordinator in role, never by parsing human phrases — strain phrases route through use-lore's canonical table. Not yours: no way of working yet belongs to use-lore; designing a Lore-owned artifact belongs to brainstorming-lore. Only save-to-lore writes Lore.
38 files7stars - brainstorming-loreandresanemic/lore-plugin
Use only when designing or materially changing an artifact owned by the Lore system, or when the person says quiero hacer esto y no se como yet adds hay que pensar el diseño antes de construir — the same no-shape sentence narrowed to the design of a bot, area, project, transmutation or skill. Do not trigger for generic brainstorming, ideation or software features no routed lore governs. Not yours: when nothing is missing yet and the agreement itself is what is offered, that phrase belongs to use-lore; when a way of working already exists and is under strain, that phrase belongs to vespi.
7stars - create-areaandresanemic/lore-plugin
Use when starting a brand-new WORK AREA that groups several projects of the same kind (web, research, blog, video, apps…) — before it has any Lore, contract or project registry of its own. Trigger on "create a work area for X", "I want to start working on a domain with Lore", or a shared mold or starter for future projects. Not yours: operating existing criteria in place belongs to transmute-lore.
7stars - create-projectandresanemic/lore-plugin
Use when starting a brand-new PROJECT inside an existing WORK AREA (created with create-area) — before it has its own identidad.md, principios.md or index.md. Replaces the old web-only nuevo-sitio. Trigger on "create project X in area Y" or "start project X inside an area". Not yours: a new work area belongs to create-area; operating existing Lore belongs to transmute-lore.
7stars
lore plugin questions
How do I install the lore plugin?
In Claude Code run /plugin marketplace add andresanemic/lore-plugin, then /plugin install lore@lore-plugin.
What does the lore plugin include?
lore bundles 1 command, 1 agent, 9 skills, hooks.
What commands does the lore plugin add?
It adds /lore:nivel. Run them in Claude Code with the plugin prefix, for example /lore:nivel.
Which agents come with lore?
lore-worker. Call one with @agent-lore:lore-worker.
How do I update or remove the lore plugin?
Update it with claude plugin update lore@lore-plugin in your shell, or from the Installed tab of /plugin. Remove it with /plugin uninstall lore@lore-plugin.