lore

Plugin lore from marketplace muki-ai-plugins in mukiwu/muki-ai-plugins. Commands read from the repo's manifest — 21 days ago.

Skills (8)

• lore-capture

  Use when the conversation surfaces knowledge that code, types, tests, or git history can't reveal — the user explains a business rule or a spec, shares a gotcha, gives the why behind a decision, says "that's intentional, not a bug", or you hit a pitfall or dig up a non-obvious root cause while debug

• lore-check

  Use when asked whether the project's lore is healthy or still helping, or when the 30-day heartbeat suggests a re-check — audits coverage, link health, freshness, entry quality, adoption, and language health, read-only, then hands fixes off to lore-maintain, lore-capture, and lore-ul.

• lore-consult

  Use when about to plan a feature, fix a bug, or touch unfamiliar code in a repo that has a docs/lore/ folder, before writing any implementation — surfaces the business rules, pitfalls, glossary terms, and API map relevant to the task, and flags entries that look stale.

• lore-eval

  Use when asked whether lore actually catches the mistakes it records, after rewording entries or changing lore-guard, or when lore-check suggests measuring — replays past violations against a fresh lore-guard pass, scores which entries get caught, and hands the misses to lore-maintain. Read-only tow

• lore-guard

  Use when about to commit, open a PR, or claim a change is done in a repo that has docs/lore/ — maps the changed files to lore entries through their code: links and reports any business rule, pitfall, or glossary naming rule the change violates. Read-only for both code and lore.

• lore-init

  Use when a project has no docs/lore/ yet and implicit knowledge starts coming up in conversation, or when the user asks to initialize, bootstrap, or set up project lore — scaffolds the docs/lore/ knowledge base.

• lore-maintain

  Use when lore looks stale or noisy, when a lore-check report flags problems, or on a periodic sweep — finds stale, duplicate, or wrong entries, checks that code links and the README index still hold, and prunes obsolete content; marking over deleting, with confirmation for destructive actions.

• lore-ul

  Use when a conversation hits a vague or overloaded term, the same word means different things in different places, the user quietly rewords something you said, the user keeps using a word the glossary doesn't have, or code names disagree with how the user talks — align the term into the project's gl

Hooks (4)

• SessionStart

  "${CLAUDE_PLUGIN_ROOT}/hooks/run-hook.cmd" lore-session-start

• PreToolUse

  "${CLAUDE_PLUGIN_ROOT}/hooks/run-hook.cmd" lore-gate pre-edit

• PreToolUse

  "${CLAUDE_PLUGIN_ROOT}/hooks/run-hook.cmd" lore-gate pre-bash

• PostToolUse

  "${CLAUDE_PLUGIN_ROOT}/hooks/run-hook.cmd" lore-gate post-skill

Similar plugins