Memory

6 memory files that persist across conversations. They store component registries, team profiles, and project state — so Claude never forgets what was built, who's on the team, or what patterns exist.

Memory Files

Project-Level Memory

Stored at ~/.claude/projects/[project]/memory/:

How Memory Works

Memory files are JSON or markdown files in ~/.claude/memory/. Claude reads them at the start of each conversation and updates them when new information is learned.

Auto-Memory

Claude automatically saves memories when it learns:

• User info — role, preferences, expertise level
• Feedback — corrections, confirmations, working style
• Project state — active work, decisions, deadlines
• References — where to find things in external systems

Memory Index

MEMORY.md is the index file — always loaded into context. Each entry is one line pointing to a memory file:

Copy# Memory Index
 
- [Company Profile](company_databayt.md) — Team of 4
- [Team Profiles](team_profiles.md) — All 4 members

Component Registry

The atom, template, and block memory files serve as a registry of all components built across projects:

Copy{
  "atoms": [
    {
      "name": "tabs",
      "primitives": ["Tabs", "TabsList", "TabsTrigger", "TabsContent"],
      "path": "src/components/atom/tabs.tsx"
    }
  ]
}

When you say atom tabs, Claude checks the registry first before creating something new.

Team Memory

team.json stores profiles of all 4 team members:

Copy{
  "team": [
    {
      "name": "Abdout",
      "role": "founder-tech-lead",
      "installRole": "engineer"
    }
  ]
}

This allows agents to tailor their output to each team member's role.