Agent skill · writing content · sickn33
lore
Markdown project memory for AI agents. Use for decisions, architecture, conventions, monorepo scopes, `.lore/`, or `lore` commands; not native `/init`/`/compact` or generic init/compress/audit/query.
Why this skill is useful
Provides a structured approach to managing project memory and conventions that the AI wouldn't reliably generate on its own.
What it needs
About 11k tokens when loaded. Last updated 2026-08-07. 44,571 stars on the source repository.
What this skill does
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 project convention" query "lore audit" / "check lore" / "is memory still accurate" audit "lore compress" / "compress lore" / "summarize lore" compress "lore mirror" / "update CLAUDE.md" / "refresh mirror" mirror "lore history" / "show the git history of this entry" / "show me the commits behind this" history Tier 2 — Internal proposals (after the skill is loaded) Once the skill is loaded for this session, certain commands may proactively propose themselves based on internal thresholds. These proposals still require user acceptance — the skill never mutates files silently. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sickn33/lore