Short answer: memory is what Claude remembers about you. A Project is a workspace with instructions and files for one body of work. A skill is a packaged way of doing one task. None of them is a single record of your company, so the trick is to feed all three from the same files.
| Memory | Projects | Skills | |
|---|---|---|---|
| What it holds | A summary of you and your past chats, written by Claude [1] | Your instructions plus uploaded files for one workspace [4] | Instructions, and sometimes scripts and templates, for one repeatable task [5] |
| Who writes it | Claude, from your conversations | You | You, or whoever made the skill |
| When Claude reads it | When relevant to a chat [1] | In every chat inside that Project [4] | When Claude judges the skill relevant to the task [5] |
| Who sees it | You | People you share the Project with (Team and Enterprise plans) [4] | Whoever has the skill turned on |
| Best for | Your preferences, work in flight | One client, one product, one long job | "How we do X": a report, a post, a review |
| Where it stops | Not a checked record; not shared with teammates | Facts don't travel to other Projects or to Claude Code | Says how to do a task, not what is true about your company |
Memory: about you, written by Claude
Claude can search past chats and keep a memory of you [1]. Use it for your style and preferences. Don't rely on it for prices, customers or rules: it's a summary, and in Anthropic's tests Claude Sonnet 4.6 read its memory before answering less than half the time [3].
Projects: one workspace, its own facts
A Project is the right home for one body of work. The catch is copies: three Projects means three versions of "who we are", and they drift apart.
Skills: how to do a task
A skill tells Claude how to do something the same way every time. It's the right place for a procedure, and the wrong place for facts that change, like a price.
Claude Code has its own memory too
Claude Code reads memory files from your project folder and loads only the first 200 lines of its index [2]. Keep that index short and point it at the rest.
How to make all three agree
Keep your company facts in one folder of plain, dated files. Point every Project at it, write skills that read from it instead of repeating it, and let memory hold only what's personal. When a fact changes, you change one file, not five copies.
Chet sets that folder up from your own documents, grades your Claude setup, and fixes what breaks. $99 a month, cancel anytime.
Maximize Claude with Chet: https://www.coworkers.global/get-chet?utm_source=blog&utm_medium=internal&utm_campaign=chet&utm_content=claude-projects-vs-memory-vs-skills-cta
Sources
- Claude Help Center, chat search and memory: https://support.claude.com/en/articles/11817273-use-claude-s-chat-search-and-memory-to-build-on-previous-context
- Claude Code docs, memory: https://code.claude.com/docs/en/memory
- Anthropic, components of agent memory: https://anthropic.com/research/components-of-agent-memory
- Claude Help Center, what are projects: https://support.claude.com/en/articles/9517075-what-are-projects
- Claude Help Center, what are skills: https://support.claude.com/en/articles/12512176-what-are-skills
Regards,
Charles Stack
Founder, Coworkers.Global