lore 플러그인
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.
lore 플러그인 설치 방법
두 명령을 모두 Claude Code 안에서 실행하십시오. 첫 번째는 마켓플레이스를 한 번 추가하고, 두 번째는 플러그인을 설치합니다.
/plugin marketplace add andresanemic/lore-plugin
/plugin install lore@lore-pluginlore 구성 요소
플러그인 파일에서 읽어온 15개의 항목입니다.
Commands 1
/lore:name 으로 실행- /lore:nivel[off|lite|full]
Ver o cambiar el nivel del recordatorio de Lore Plugin (off, lite, full).
Agents 1
@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가 로드합니다- 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
다음 이벤트에서 실행됩니다- PostToolUsecommand
Agent|Task
- PreCompactcommand
manual|auto
- PreToolUsecommand
apply_patch|Edit|Write|MultiEdit|NotebookEdit, Agent|Task
- SessionStartcommand
파일에 설명이 없습니다.
Claude Code에서 lore 사용하기
Claude Code 세션에서 명령어를 입력하세요:
/lore:nivel [off|lite|full]이름으로 agent를 요청하세요:
@agent-lore:lore-workerSkills는 명령어가 필요하지 않습니다. 요청이 설명과 일치하면 Claude가 이를 읽습니다.
업데이트, 비활성화 또는 삭제
- 플러그인 업데이트 (shell)
- claude plugin update lore@lore-plugin
- marketplace 새로고침
- /plugin marketplace update lore-plugin
- 일시적으로 비활성화
- /plugin disable lore@lore-plugin
- 삭제
- /plugin uninstall lore@lore-plugin
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개 파일7스타 - 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개 파일7스타 - 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개 파일7스타 - 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개 파일7스타 - 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개 파일7스타 - 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개 파일7스타 - 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.
7스타 - 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.
7스타 - 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.
7스타
lore 플러그인 질문
lore 플러그인은 어떻게 설치하나요?
Claude Code에서 /plugin marketplace add andresanemic/lore-plugin를 실행한 다음 /plugin install lore@lore-plugin을 실행하십시오.
lore 플러그인에는 무엇이 포함되나요?
lore은(는) 1개 명령, 1개 에이전트, 9개 스킬, 훅을(를) 묶습니다.
lore 플러그인은 어떤 명령어를 추가하나요?
/lore:nivel를 추가합니다. Claude Code에서 플러그인 접두사를 사용하여 실행하세요. 예: /lore:nivel.
lore에는 어떤 agent가 포함되어 있나요?
lore-worker입니다. @agent-lore:lore-worker로 호출하세요.
lore 플러그인을 어떻게 업데이트하거나 삭제하나요?
shell에서 claude plugin update lore@lore-plugin를 사용하여 업데이트하거나 /plugin의 Installed 탭에서 수행하세요. 삭제하려면 /plugin uninstall lore@lore-plugin을 사용하세요.