Make it yours: memory, Projects, repeatable workflows
Eight days in, you can brief, verify, and build. And yet every chat still begins with you introducing yourself — again. Today you stop re-introducing yourself to your own assistant: standing instructions it follows everywhere, a memory you can read and edit, and a workspace that already knows your files. This is the day the time savings stop being one-offs and start compounding.
100x starts when your assistant stops forgetting you: memory and custom instructions make it remember who you are, Projects and Gems keep your files and context loaded, and saved playbooks turn one-off wins into routines.
1The silent time-leak: groundhog-day prompting
Think back over your last eight days of chats. The Briefing Formula email on Day 2. The Deep Research shortlist on Day 4. The week plan on Day 5, the deck outline on Day 6. Real wins, every one. Now notice what you did before each one: you introduced yourself. Who you are, what you do, what you're working on, how you like your answers. Again. And again. And again tomorrow.
Here's why. On Day 1 you learned that a chat remembers what was said within the thread — and that's exactly where it ends. A brand-new chat is a blank slate. Nothing carries over from yesterday's conversation unless the assistant has been given somewhere to keep it. That's partly by design: a fresh chat that knows nothing about you is also a chat that can't mix up your projects or leak one topic into another. But it means that, out of the box, every new conversation is a new intern's first morning on the job.
The cost is real and almost perfectly invisible. Call it groundhog-day prompting: re-typing your context into a fresh chat, forever. Each instance feels like "only" a minute or two — which is exactly why nobody notices it. But it repeats across every fresh chat, every day, week after week, and those small re-introductions quietly add up. The exact toll depends on how often you start from scratch, but for most people it's a meaningful slice of time spent telling the same tool the same facts about the same person — typed away a minute at a time, by someone who already learned how to brief on Day 2.
Day 1's Confident Intern frame had three consequences, and we've cashed in two: you brief an intern (Day 2), and you check an intern's work (Day 4). Today is the third: an intern gets better the longer they work with you — but only if they're allowed to keep notes, hold a standing brief, and have a desk where your files stay put. Today you hand your intern all three.
2The Persistence Ladder: three rungs of "it knows me"
Every major assistant — ChatGPT, Claude, Gemini — now offers the same three levels of persistence, under slightly different names. We'll call it the Persistence Ladder, and you'll climb all three rungs today. Each rung answers the same question — "what does the assistant already know when I start typing?" — with a bigger answer than the last.
One conversation remembers itself — and nothing else. You've been using this rung since Day 1.
Your account remembers you across every chat — and you can read, edit and delete what it holds.
A workspace with standing instructions plus your reference files — every chat inside starts already briefed. The move-in rung.
Rung 1 — the thread. This is the cheapest persistence there is, and most people waste it. Because a conversation remembers itself, the move is to keep one ongoing thread per topic instead of scattering a topic across ten fresh chats. Renovating the kitchen? One thread, renamed "Kitchen renovation" (the Day 1 renaming habit), returned to every time. The context you built last Tuesday is still sitting there on Thursday. The limits are obvious: long threads get cluttered, and nothing in them helps a different chat. That's what the next rung is for.
Rung 2 — the account level. Two tools live here, and they're different in a useful way. Custom instructions are standing orders you write deliberately — a short note the assistant applies to every new chat: who you are, what you do, how you like your answers. Write them once, and you never again type "keep it short and skip the buzzwords." Memory is the same idea, but accumulated: as you chat, the assistant quietly retains facts about you — your job, your projects, your preferences — and uses them in later conversations. As of mid-2026, all three assistants include memory on free accounts — ChatGPT's free tier has a lighter version (a deeper memory upgrade is still rolling out as of June 2026), Claude added free memory in March 2026, and Gemini includes it. These plans shift often — if availability looks different on your screen, the workflow still works the same. The principle of rung 2 in five words: standing orders beat repeated orders.
Rung 3 — Projects and Gems. A Project (ChatGPT and Claude) or a Gem (Gemini) is a workspace: standing instructions plus your uploaded reference files, scoped to one area of your life. Every chat you start inside it begins already knowing the context — your CV, your client notes, your renovation quotes. Remember grounding from Day 5? When the assistant works from text you supplied, confident mistakes drop dramatically. A Project is grounding made permanent: instead of re-attaching the same files every time, they live in the workspace, and every chat draws on them automatically. As of mid-2026, Projects are available on the free plans of both ChatGPT and Claude (Claude's free plan caps how many you can have), and Gems are part of free Gemini. This rung is the single biggest quality-of-life upgrade in this course.
3Memory is yours: view it, edit it, delete it
A tool that remembers you across conversations deserves a clear-eyed minute, so let's give it one — calmly. The Privacy Line from Day 5 said: don't paste anything you wouldn't email to an outside contractor. That rule still stands, and it applies with full force to the files you upload into a Project. Today adds the second half of the rule, and it's good news: memory is not a black box. On all three assistants you can open the memory controls, read every fact that's been stored about you, edit what's wrong, and delete what you'd rather not have there — one fact at a time or all of it. The Privacy Line, revisited, isn't a warning. It's control.
There's a second, less obvious reason to look inside: stale facts. Memory accumulates whatever you talked about — including the job you left, the trip you already took, the diet you abandoned in February. An assistant working from outdated facts is like a well-meaning colleague who still thinks you're in your old role: not malicious, just confidently behind. So treat memory the way you'd treat that colleague — update it. A practical cadence: once a month or so, ask your assistant what it remembers about you (you'll do this in a minute), and spend ninety seconds pruning. Two questions per fact: Is it still true? and Do I want it in there? Delete accordingly, with zero guilt.
A hotel room is excellent and forgets you at checkout. Every stay starts from zero: you explain your preferences at the desk, you hunt for the light switches, nothing on the shelf is yours. Home is different because it accumulates: your books on the shelf, your handwriting on the calendar, the chair shaped like you after a thousand evenings. Nobody briefs their own kitchen. For eight days you've been staying in hotels — superb ones, but hotels: every conversation checked you in as a stranger. Custom instructions, memory and a Project are the bookshelf, the calendar and the chair. Today you move in.
Do this in your daily driver (Day 3). The concepts are identical in all three assistants — only the names move: Projects in ChatGPT and Claude, Gems in Gemini; memory and custom instructions live under settings/personalization in each. Interfaces shuffle their menus every few months, so everything below is described by what it does, not by where a button sat this morning. One convention, used once more: square brackets in a prompt mean replace with your own words — [your role] becomes "school office manager," brackets gone.
Part 1 · Set your custom instructions (~3 min)
- Open the settings menu — usually behind your profile picture or initials — and look for the section about personalization, custom instructions, or saved info. Every assistant has one; the wording differs. a place to tell the assistant about yourself — one or two empty text boxes inviting exactly that.
- Paste and adapt this — it's a standing brief, so fill it with your real situation:
Copy-paste · custom instructionsI'm [your name], I work as [your role / what fills your days]. I prefer concise answers in plain language — no buzzwords, no padding. For writing tasks, default to [the language and tone you usually write in]. If you're not sure about a fact, say so instead of guessing.Save it. a confirmation that your instructions are saved — they now apply to every new chat.
- Prove it to yourself: open a brand-new chat and ask any quick question you'd normally ask. an answer that's already in your style — short, plain, your language — without you asking for any of it. That's a standing order working.
Part 2 · Meet your memory (~4 min)
- In any chat, ask the question directly:
Copy-paste promptWhat do you remember about me so far?a short list of stored facts — or a note that nothing is stored yet. (Empty is fine: free tiers store less, and a new or rarely-used account may have nothing to show. The review habit matters more than today's contents.)
- Review the list with the two questions from earlier: still true? and do I want it in there? A typical review looks like this:
What it remembers · example reviewyour call"Works as an office manager at a school"true + useful → keep"Prefers short answers in plain language"useful → keep"Is planning a trip to Lisbon" — went in Marchstale → delete"Daughter attends [school name]"someone else's privacy → delete
- Delete or edit anything you flagged. The controls live near the memory / personalization settings from Part 1 — you can remove a single fact or clear everything. the deleted fact is gone the next time you ask what it remembers. Yours to view, yours to edit, yours to delete.
Part 3 · Build your first Project (~8 min)
- Find the feature in the sidebar: a Projects section with a "new project" option in ChatGPT or Claude, or Gems in Gemini's menu. Create a new one. a setup screen asking for a name and instructions for this workspace.
- Name it after a real ongoing area of your life — not a test. Good names: "[Your name]'s Job Search", "Newsletter", "Renovation", "Family admin". The narrower and more real, the better it works.
- Write two or three lines of standing instructions for this area only:
Copy-paste · project instructionsThis project is about [your ongoing area — e.g. my job search in marketing]. About me, for this context: [one line]. Keep answers practical and concise, and treat the files in this project as the source of truth. If something in a file contradicts what I say, point it out.
- Upload 2–3 reference files using the project's add-files control (the same paper-clip idea as Day 5). For a job search: your CV, a list of target roles, your best cover letter. The Privacy Line applies in full — nothing you wouldn't email an outside contractor. your filenames listed inside the workspace, attached to the project rather than to any single chat.
- Start a chat inside the project and give it a real task:
Copy-paste promptBased on the files in this project, [one real task — e.g. draft the next outreach email / summarize where we left off and what to do next].an answer built from YOUR documents — your wording quoted back, your situation understood — with zero re-explaining from you. Name that feeling. That's rung 3.
Here's what you've built, as a workspace:
From now on, every chat about this area starts inside this workspace — already briefed, already grounded in your files. Free-plan limits as of mid-2026 are generous enough for everything this course asks of you.
4From wins to workflows: your first playbooks
Persistence has one more layer, and it doesn't live in any setting — it lives in your notes. Since Day 5 you've been keeping a Prompt Notebook: every prompt that worked, saved verbatim. A recipe box, not a textbook. Today the notebook graduates. A prompt that worked once is a win; a prompt with a schedule and a quality bar is a workflow. We'll call that a playbook, and it has exactly three parts: trigger → prompt → done-check. The trigger says when you run it, the prompt is your saved winner with placeholders for the parts that change, and the done-check says how you know the result is good enough to use.
Here's the shape, using the most useful playbook in the course:
Three playbooks are worth assembling from the days you've already done — consider them the starter set:
- The Weekly Planning ritual — trigger: Monday morning. Prompt: your Day 5 Plan winner (above). Done-check: a realistic plan plus a "won't fit" list you've pushed back on at least once.
- The Inbox triage ritual — trigger: opening an inbox with more than five unanswered emails. Prompt: your Day 5 Draft winner ("Here's an email I received: […]. Draft a reply that […]"). Done-check: a reply you've read end-to-end and lightly edited before sending — the intern's draft never leaves your desk unread.
- The Learning ritual — trigger: a question that's come back three times this month. Prompt: the Day 4 research prompt for the big version, then Day 5 Distill on what comes back. Done-check: the Three-Click Check done, one summary saved where you'll find it.
One sentence on the horizon, then we move on: paid tiers of the big assistants now offer scheduled and automatic tasks that can run routines like these for you — genuinely nice later, genuinely not needed now. A playbook in your notebook plus a recurring slot in your calendar does the same job for $0.
The mirror-image mistake after today is hoarding: a Project stuffed with every file you own works worse than one with the 2–3 documents that matter — the assistant grounds best on a small, current set. Same for memory: left unaudited, it becomes a colleague confidently working from last year's file on you.
The fix for both is persistence, managed: 2–3 live files per Project, memory pruned monthly.
Climb all three rungs for real, today:
- Rung 2a: set custom instructions on your daily driver (Part 1's prompt, your real details).
- Rung 2b: ask "What do you remember about me so far?" — review, then delete at least one stale or unwanted fact (if memory is empty on your plan, you've done the review; move on).
- Rung 3: build ONE Project or Gem around an actual ongoing area of your life, load 2–3 real files (Privacy Line!), and run its first real task from inside it.
- Graduate the notebook: open your Prompt Notebook, pick the entry you've reused most, and write it up as one playbook — trigger → prompt → done-check. If you'd like help, hand it over:
Save the playbook in your notebook, right next to the prompt it grew from. Tomorrow it earns a place on your toolkit one-pager.
Today's recap — 30 seconds
- The Persistence Ladder: thread → memory + custom instructions → Projects/Gems — each rung answers "what does it already know?" with more.
- Standing orders beat repeated orders: custom instructions written once apply to every chat; groundhog-day prompting ends today.
- Memory is yours — view it, edit it, delete from it; audit it like you'd update a colleague who still thinks you're in your old job. The Privacy Line, now as control.
- Projects/Gems = chats that start already knowing your context: standing instructions + your files, grounding (Day 5) made permanent — the biggest quality-of-life upgrade in this course.
- Playbooks turn wins into routines: trigger → prompt → done-check — your Prompt Notebook just graduated.