lore
Makes your agent remember important project information. It helps maintain consistency and follow rules in large projects.
What it does
It's a way to store important information about a software project so that the artificial intelligence (AI) remembers it. It saves details about the project's structure, decisions made, and how the code should be written.
When to use it
- ✓When starting a new project to record its structure.
- ✓After making an important project decision.
- ✓When you want the AI to remember specific coding conventions.
Example of what to ask your AI
“Remember this decision about the project architecture.”
Want more? Open the sections below.
How to use
The easiest way: copy the message below and paste it into Claude, ChatGPT, Cursor or any AI. It reads the skill and follows the instructions.
Skill link
Ready-to-paste message
How it works
Information is saved in plain text files (Markdown) in a folder called `.lore/`. Any AI that can read files can access this information.
Installation
Easiest way: copy the skill link and paste it into Claude, ChatGPT or Cursor asking it to follow the instructions.
In the terminal (Claude Code, Codex, Cursor), in your project folder:
npx skills add sickn33/agentic-awesome-skills --skill loreOr download just the file:
curl -L https://raw.githubusercontent.com/sickn33/agentic-awesome-skills/main/plugins/agentic-awesome-skills-claude/skills/lore/SKILL.md -o SKILL.mdTechnical content (original SKILL.md)
Original text by the author, straight from GitHub.
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.
syncproposes when 50+ changed lines span 2+ directories, OR a new top-level module/directory/dependency was added or removed, OR a new convention was explicitly discussed in chat.compressappends a[COMPRESS NOTICE]to sync proposals when entries > 500,SUMMARY.mdis missing, or last compression > 30 days ago.syncemits[ALERT]markers when an active entry conflicts with current code or with a candidate change.mirrorregenerates automatically duringcompressifauto_mirror: trueis set in.lore/.config.json.
Other commands (init, query, history) are always explicit — they need user intent. See references/workflows.md for when each workflow is used.
Which command do I need?
| User goal | Command | When | Procedure |
|---|---|---|---|
| First-time setup, or start over | init |
One-time setup | references/workflows.md#init, then references/platform-mirrors.md + references/monorepo-detection.md |
| "Remember this change" after a feature / refactor / bug fix | sync |
After a non-trivial change | references/workflows.md#sync, then references/stale-new-markers.md |
| "What is the project convention / why was X chosen?" | query |
Answer from memory | references/workflows.md#query |
| "Is memory still accurate?" | audit |
Memory may have drifted from reality | references/workflows.md#audit, then references/audit-template.md |
| "Summarize the memory bank" | compress |
SUMMARY.md stale, or entries > 500 | references/workflows.md#compress, then references/summary-template.md |
| "Update CLAUDE.md / AGENTS.md / mirrors" | mirror |
Explicit publish of mirror changes | references/workflows.md#mirror, then references/platform-mirrors.md |
| "Why does this decision exist?" / "show the commits behind this" | history |
Git story behind an entry | references/workflows.md#history, then references/history-command.md |
…
FAQ
What's the difference between 'lore' and a dev journal?
'Lore' focuses on long-term project information (architecture, decisions, conventions), not a daily activity log.
Do I need to use all 'lore' commands?
No, you use commands as needed: `init` to start, `sync` to record changes, `query` to ask, `audit` to check, `compress` to summarize, and `mirror` to update documentation.
What happens if I don't use 'lore'?
The AI might forget important project details, leading to inconsistencies or repeated decisions.
Details
Original description by the author
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.
Popularity
- GitHub stars
- 48k
- Ranking position
- #3504
- License
- MIT
- Updated
- 10/15/2026
Comments
- …
More skills from this repository
00-andruia-consultant
Helps your agent start or improve AI projects. It analyzes code, suggests tools, and creates action plans in Spanish.
sickn33/agentic-awesome-skills
007
Lets your agent perform security audits and threat modeling. It's useful for protecting projects against attacks and vulnerabilities.
sickn33/agentic-awesome-skills
10-andruia-skill-smith
Helps your agent create or improve AI tools. It defines how tools work, writes documentation, and validates the structure.
sickn33/agentic-awesome-skills
20-andruia-niche-intelligence
Lets your agent create a summary about a specific industry. It's useful for understanding the context, rules, usage patterns, and risks of a project, using reliable sources.
sickn33/agentic-awesome-skills
Similar skills
architecture-decision-records
Has your agent record important project structure decisions. It helps to understand the reasoning behind choices and maintain a clear history of changes.
affaan-m/ECC
code-tour
Lets your agent create step-by-step code walkthroughs with exact file and line anchors. It's useful for project introductions, code explanations, or change reviews. Helps understand how a system works.
affaan-m/ECC
codebase-onboarding
Helps your agent analyze unfamiliar code and create an onboarding guide. It includes an architecture map, entry points, and conventions. Ideal for starting on a new project.
affaan-m/ECC