lore

lore — Framework-agnostic Memory Management

What this skill is

A long-term knowledge base for a software project, maintained by AI agents. It is not a dev journal or a changelog. It captures the kind of context that normally lives only in the original developer's head:

• What the project is, how it is shaped (architecture)
• Why specific choices were made over alternatives (decisions)
• How code should be written and what to avoid (conventions)

This knowledge is persisted as plain Markdown files in .lore/ at the project root. Any agent that can read files can consume them.

When to Use

The skill uses a two-tier trigger model.

Tier 1 — Loading the skill

Load this skill when the user explicitly invokes lore, names a subcommand, references .lore/, or asks to record, recall, audit, sync, or compress project memory about decisions, architecture, conventions, or monorepo scopes. Generic phrases like "init", "compress", "audit", or "query" alone are not enough — they may map to the agent's native commands or unrelated tasks (Claude Code's /init, /compact, security audits, SQL queries, etc.).

User says (examples)	Command
"lore init" / "create lore memory bank" / "initialize lore"	init
"lore sync" / "sync this change to lore" / "record this decision in lore"	sync
"lore query" / "query lore" / "what's the projec