PROMPTS.Md

PROMPTS.md

**Understanding CLAUDE.md, MEMORY.md, SKILLS.md, SOUL.md, and Related Prompting Mechanisms**

As agentic systems like Claude become embedded in developer workflows, a new class of "context files" has emerged — structured documents that shape how an agent behaves, remembers, learns, and acts. Names like `CLAUDE.md`, `MEMORY.md`, `SKILLS.md`, and `SOUL.md` are increasingly common in repos, agent frameworks, and personal AI setups.

This guide explains what each of these files is, why they exist, how they differ from one another, and how developers and power users can use them to build more capable, consistent, and personalized AI workflows.

---

Part 1: What Are Context Files?

Before diving into specific files, it helps to understand the broader concept.

Large language models like Claude have no persistent memory by default. Each conversation begins with a blank slate — unless you explicitly provide context. Context files are a solution to this problem: they are plain-text or Markdown documents you include at the start of a session (or inject into the system prompt) to give the model structured information about who it is, what it knows, what it can do, and how it should behave.

The names `CLAUDE.md`, `MEMORY.md`, `SKILLS.md`, and `SOUL.md` are conventions — not enforced standards — but they've become widely adopted because they mirror how developers think about project documentation (`README.md`, `CHANGELOG.md`, etc.). The `.md` suffix signals that these are human-readable Markdown files, typically placed in the root of a project or agent directory.

Think of these files collectively as a "personality package" or "agent configuration layer." Together they answer four core questions:

• CLAUDE.md — What is this project and how should I work within it?
• MEMORY.md — What do I already know about this user or context?
• SKILLS.md — What specialized capabilities can I invoke?
• SOUL.md — Who am I and what do I value?

---

P