Save This

How to Give Claude
Perfect Memory

Steal My 3 Layer System

By default, Claude forgets your context, your preferences, your tone — basically everything that makes it useful. These three layers fix that completely.

Claude’s memory is pretty bad out of the box. It saves random facts, forgets important ones, and loses everything the second you start a new chat. Most people have been living with this for months without knowing there’s a better way.

Here are three layers of memory systems that change everything:

Layer 1 — Basic Memory (Beginner) — 4 quick wins, takes minutes
Layer 2 — Context File System (Intermediate) — ~60 min setup, changes how Claude operates entirely
Layer 3 — AI Second Brain (Advanced) — turns Claude into a self-evolving system trained on all your data

Start wherever you are. Each layer builds on the last.

Layer 1 — Beginner Basic Memory — 4 Quick Wins

This is where everyone should start. Four quick fixes that take minutes and immediately improve every conversation.

1. Clean Up Your Memory Page

Go to Settings → Memory right now. This is the most overlooked page in all of Claude. You’ll see everything Claude has stored about you — preferences, facts, habits, working styles — accumulated across every conversation you’ve ever had. Left unmanaged, it fills up with garbage. Read through everything. Delete anything outdated, inaccurate, or irrelevant. Then manually add the context you actually want Claude to carry permanently.

2. Fill In Your Project Instructions

If you use Claude Projects (you should), fill in your Project Instructions field for every project. This tells Claude the context for that specific workspace — your role, your rules, your audience, your files. Create projects for your most-used workflows, then give each one detailed instructions so Claude never starts from scratch.

3. Tell Claude Directly

The simplest hack on this list. Mid-conversation, just tell Claude what to remember:

“Remember that I never want bullet points in emails”
“Remember that my role is [x] at [company]”
“Update your memory: I prefer responses under 400 words”
“Forget that I mentioned [x]”

Claude stores these immediately. You can verify by checking your Memory page after.

4. Import From ChatGPT (or Other LLMs)

If you’ve built up context in ChatGPT, you don’t have to start from scratch. Two options:

Option A: Tell ChatGPT you’re switching platforms and ask it to generate a memory export: “I’m switching to Claude. Give me a complete summary of everything you know about me, my preferences, my work, and my communication style.” Copy that output and paste it into Claude.

Option B: Use Claude’s built-in import tool. Go to Settings → Memory and look for Import/Export. Claude can import full data from other LLMs directly.

Who This Is For

This layer is enough for 90%+ of people. It’s available on all plans including Free and makes an immediate difference. If you want to go deeper, keep reading.

Paste This Into Claude — Full Memory Setup
I need you to remember the following about me. Save all of this to your memory so it applies to every future conversation we have. WHO I AM: - My name is [YOUR NAME] - My job title is [YOUR TITLE] at [YOUR COMPANY/BUSINESS] - I work in the [YOUR INDUSTRY] industry - I've been doing this for [X] years - My main responsibilities are: [LIST 3-5 KEY THINGS YOU DO] HOW I WORK: - My communication style is [direct / casual / formal / friendly but professional] - When I ask for writing, I want it to sound like [describe your voice — conversational? authoritative? warm? no-nonsense?] - I prefer [short and punchy / detailed and thorough / somewhere in between] responses - I hate when AI [uses corporate jargon / adds unnecessary caveats / gives vague answers / adds emojis / starts with "Great question!" — list your pet peeves] - When I say "draft this," I mean ready to send — not a rough outline MY TOOLS: - I use [list the apps you use daily — Gmail, Slack, Notion, Google Docs, Salesforce, etc.] - My calendar is on [Google Calendar / Outlook / Apple Calendar] - I manage projects in [Notion / Asana / Monday / Trello / etc.] MY GOALS RIGHT NOW: - My #1 priority at work right now is: [WHAT YOU'RE FOCUSED ON] - A secondary goal is: [SOMETHING ELSE YOU'RE WORKING TOWARD] - By the end of this [month / quarter / year], I want to have: [SPECIFIC OUTCOME] WHAT I NEED FROM YOU: - Default to being [proactive / brief / thorough] — don't wait for me to ask follow-up questions if the answer is obviously incomplete - If I ask you to write something, match my voice every time - Challenge my ideas when they have obvious flaws. Don't just agree with me. - If you're not sure about something, say so. Don't make things up. Save all of this. I should never have to explain any of it again.
Layer 2 — Intermediate Context File System

Layer 1 fixes the basic memory problems. Layer 2 builds something more powerful: a file-based memory system that lives on your computer and loads automatically into Cowork and Claude Code.

Instead of relying on Claude’s built-in memory (which is unreliable), you store all your context in .md files on your desktop that Claude reads every time you work. You can also attach these files to any LLM or AI agent system.

The 4 Files You Need

1. Instructions.md — Tells Claude all your rules and instructions. Who you are, what you do, how you want things done, what good output looks like. Important: include the line “Update Memory.md with my preferences over time” — this is how Claude creates a running memory log automatically.

2. Memory.md — This is the “brain” of Claude. It starts mostly empty and gets updated over time as you work. Whenever you say something like “stop using em dashes” or “I prefer shorter emails,” Claude goes into this file and updates it. Sections: Preferences, Corrections, Patterns, Decisions.

3. Context.md — The specific context for whatever project you’re working on. Your business, your audience, your goals, your active priorities. You can create a general “business context” file or separate ones per project.

4. Archive Copies — Claude will update your memory files as you work. Occasionally it overwrites something incorrectly. Without a backup, that context is gone. Once a week, copy your entire master folder into a separate archive folder that Claude can’t access. Label it with the date. If anything breaks, restore from the archive.

How to Use It

Create a folder on your desktop called “Claude Master Folder.” Put all 4 files inside. Anytime you work in Cowork or Claude Code, attach this folder. Claude reads the files, follows your rules, and updates your Memory.md as you work. You can also manually update the files anytime and create new context files for specific projects within the folder.

You can build all 4 files yourself, or just paste this prompt into Cowork and Claude will build them for you:

Paste Into Cowork — Claude Builds Your Master Folder
Go into my "Claude Master Folder" in my connected workspace and build these four markdown files inside it: 1. Instructions.md — include these sections: ## Who I Am [My name, role, company, industry, years of experience] ## What I Do [My primary responsibilities and the type of work I do daily] ## Rules - Match my communication style: [direct / casual / formal / friendly but professional] - My writing voice is: [describe — conversational, authoritative, warm, no-nonsense, etc.] - Default response length: [short and punchy / detailed / somewhere in between] - Never use these words or phrases: [list your banned words — "leverage," "synergy," "delve," "it's worth noting," etc.] - Never start responses with: "Great question!" / "Absolutely!" / "Of course!" - Never add disclaimers like "As an AI..." unless I specifically ask - When I say "draft this" I mean ready to send — not bullet points or an outline - If I ask "what do you think?" give me your actual recommendation, not just pros and cons - If you're unsure about something, say so instead of guessing - Challenge my ideas when they have obvious flaws ## What Good Output Looks Like - Lead with the answer, then explain if needed - Use headers and bullets for anything longer than 3 paragraphs - Bold the most important point in each section - Write at an 8th grade reading level. Short sentences. Real words. Use contractions. - Keep paragraphs under 4 sentences ## Memory Rule Update Memory.md with my preferences, corrections, and patterns over time. Whenever I correct you, tell you I prefer something a certain way, or establish a pattern — log it in Memory.md so you never make the same mistake twice. 2. Memory.md — include these sections with placeholder examples so I know what to add: ## Preferences - [Example: Prefers bullet points over numbered lists when order doesn't matter] - [Example: Wants all emails to end with a clear next step] - [Example: Prefers casual tone in Slack, formal in client emails] ## Corrections - [Example: Stopped using em dashes after user requested — use regular dashes instead] - [Example: User corrected that their company name is capitalized as "TechFlow" not "Techflow"] ## Patterns - [Example: User typically asks for email drafts on Monday mornings] - [Example: User prefers to review outlines before full drafts on large projects] ## Decisions - [Example: Decided to use Notion instead of Asana for project tracking as of March 2026] - [Example: Changed email signature format — now includes phone number] ## Personal Context - [Example: User is based in EST timezone] - [Example: User's manager is Sarah — prefers formal updates to her] 3. Context.md — include these sections with a template format I can fill in: ## About This Project / Business [What the business does, who it serves, what makes it different] ## Audience [Who I'm talking to — clients, team, executives, customers, followers] [What they care about, how they prefer to communicate] ## Key People & Collaborators [Names, roles, and relationship context for the people I work with most] ## Active Projects & Priorities [What I'm working on right now, deadlines, milestones] ## Tools & Stack [The apps and tools I use daily and what each one is for] ## Important Background / History [Context that doesn't fit above but matters — past decisions, company history, industry context] 4. Archive-Guide.md — a step-by-step guide explaining: - Why archiving matters (Claude can accidentally overwrite memory) - How to do it weekly (duplicate the Master Folder, rename it with the date like "Archive-2026-04-28", move it somewhere Claude can't access) - What to include in each archive (all .md files in their current state) - How to restore if something breaks (copy the archived file back into the Master Folder, overwriting the broken version) - Where to store backups (a separate folder on your desktop, a cloud drive, or anywhere outside the Master Folder) Make all four files clean, well-organized, and ready for me to fill in with my real information. Use markdown formatting throughout.
Layer 3 — Advanced AI Second Brain

This is the deepest level and it’s not for everyone. It requires setup and ongoing maintenance. But if you build it, Claude becomes a self-evolving second brain trained on everything you think, read, write, and work on.

There are two options depending on how you work.

Option 1: Claude + Notion (Easier)

Connecting Claude to Notion is the highest-leverage thing you can do in 5 minutes.

Step 1: Go to Claude → Settings → Connectors and enable the Notion connector.

Step 2: Once connected, Claude can read your entire Notion workspace directly inside any chat. All your tasks, CRMs, notes, tables — instantly accessible and editable.

Step 3: Create a new Notion database called “Memory Database” where you store all your AI preferences, rules, and important context.

Step 4: As you work with Claude, tell it: “Send this to my Notion Memory Database.” Over time, this becomes a searchable, visual knowledge base of everything Claude knows about you.

Notion Bonus

You get Notion’s built-in board views, to-do lists, and filters on top of your memory data. You can also export this data to other LLMs via CSV or the Notion MCP connector.

Option 2: Claude + Obsidian (Most Powerful)

Obsidian stores everything as plain Markdown files on your computer. This makes it the most powerful option for building a second brain with Claude — because Claude can read, write, search, and evolve your entire knowledge base over time.

Claude + Obsidian — Full Setup Guide
CLAUDE + OBSIDIAN: BUILD YOUR AI SECOND BRAIN ============================================= STEP 1: DOWNLOAD OBSIDIAN ============================================= Go to obsidian.md and download the app (free). Create a new Vault — this is just a folder on your computer where everything lives. ============================================= STEP 2: CONNECT TO CLAUDE ============================================= Open the Claude Desktop app and click "Select Folder." Point it at your Obsidian Vault folder. Claude now has direct read AND write access to everything inside it. No plugins required for basic access — Obsidian vaults are just folders of markdown files, and Claude can read folders. For a deeper connection (searchable from claude.ai, not just desktop): - Inside Obsidian, go to Settings → Community Plugins → Browse - Search for "Claude Code MCP" by Ian Sinnott - Install and enable it - This runs a small server that Claude can connect to for full search and access ============================================= STEP 3: INJECT THE KNOWLEDGE BASE PROMPT ============================================= This is the key step. Paste a system prompt into Claude that tells it how to build, maintain, and evolve your wiki over time. The best one available is Andrej Karpathy's LLM Knowledge Base system prompt. It tells Claude how to: - Organize information into linked wiki pages - Extract key concepts from anything you feed it - Cross-reference new information with existing notes - Build an evolving knowledge graph that gets smarter over time Find it here: gist.github.com/karpathy/442a6bf555914893e9891c11519de94f Copy that entire prompt and paste it into your Claude conversation (or save it as your Project Instructions for this vault). ============================================= STEP 4: FEED IT YOUR DATA ============================================= Drop in everything you want Claude to know: - Existing notes from any app (export from Notion, Google Docs, Apple Notes, etc.) - CSV files, article exports, PDF summaries - Meeting notes, research documents, project briefs - Anything you've written that contains useful context Claude ingests each source, extracts the key information, and integrates it into an evolving knowledge wiki with linked pages. ============================================= WHAT TO KEEP ADDING OVER TIME ============================================= The more you put in, the smarter it gets: Meeting notes: After every meeting — who was there, what was discussed, decisions made, action items. Claude can prep you for follow-ups by reading the last one. Project briefs: For every active project — goal, timeline, stakeholders, status. Claude reads this before helping you with anything project-related. Client/contact notes: A note per client or key contact — what they care about, past conversations, preferences, deals in progress. Claude drafts personalized emails using this. Research and ideas: Articles you've read, ideas you've had, things you want to remember. Claude connects dots between ideas you forgot you had. Templates and processes: How you do things — your email template, proposal format, weekly review process. Claude follows YOUR process instead of making up its own. Daily notes: A quick end-of-day brain dump — what you worked on, what's stuck, what's next. Over time this becomes a searchable log of your entire work history. ============================================= THE RESULT ============================================= After a few weeks: - Claude knows what you discussed in last Tuesday's meeting - Claude references the proposal you wrote 3 months ago - Claude remembers your client prefers formal language - Claude connects your research from last month to today's project - Claude gets smarter every single day because your vault keeps growing This is what real AI memory looks like. Not a list of random facts in a settings page. A living, growing knowledge base that Claude searches, references, and learns from every time you talk to it. ============================================= WHICH ONE SHOULD YOU CHOOSE? ============================================= Notion = fast setup, visual interface, good if you already use Notion daily Obsidian = local storage, deeper integration, Claude has full read/write access, most powerful memory system available If you're not sure: start with Notion. If you want the best possible setup and you're willing to spend 1-2 hours building it: Obsidian.

This is one system. The Weekend Bootcamp walks you through setting up Claude as a complete operating system for your specific job — memory, Projects, Skills, connectors, scheduled tasks — all wired together. One weekend.

Go Deeper

Memory Is Layer One.
Build the Full System.

The Weekend Bootcamp walks you through setting up Claude as a complete system for your specific job — Projects, Skills, Cowork, connectors, scheduled tasks — all wired together. One weekend.

25

Job-specific chapters

4

Phases per chapter

1

Weekend to finish

Account Executive • Real Estate Agent • Marketing Coordinator • HR & Recruiter • Operations Manager • Financial Analyst • Executive Assistant • Project Manager • Customer Success Manager • Teacher & Educator • Social Media Manager • Content Creator • E-Commerce Owner • Copywriter • Graphic Designer • Virtual Assistant • Photographer • Coach • Healthcare Admin • Real Estate Investor • Event Planner • Interior Designer • Attorney • Accountant • Insurance & Mortgage Broker

Most People Finish in a Single Saturday

This is the lowest price the bootcamp will ever be. It goes up as new chapters are added.

Start the Weekend Bootcamp →

© 2026 Mariah Brunner. All rights reserved.