Be honest — how many times this week have you re-explained yourself to Claude? Who you are, what you're working on, what you're actually trying to do… typed out again, from scratch, in a brand-new chat.
That's not you being disorganized. It's that Claude has no memory of you. Every new chat, it starts from zero and guesses who you are — and that guessing is exactly why the answers come back generic.
I've built software for 13 years, and I use Claude every day to run this channel and ship real work. The very first thing I set up — before any other tool, any trick — fixes this in one conversation. No coding. You do it once, and Claude knows you from then on. Let's build yours.
Why Claude guesses in the first place
Claude — and every AI chatbot like it — only has a limited amount of context it can hold during a session. So when you open a new chat, it knows a few stored scraps at best, and that's it. Everything else, it fills in with the average answer. Generic in, generic out.
That's exactly what a Master Statement solves. It hands Claude the right context in every conversation, in a form it can digest easily — which gives you sharper output and continuity across all your different chats and projects.
What a Master Statement is
It's a short profile that covers how you learn, your skills, your goals, what you're working on, who you are, and how you want it to talk to you.
And you don't write it. Claude interviews you and writes it for you — you build it together. Once you have it, it's a living document: you add to it over time and drop it into any future project.
Step 1 — Start the interview
It starts with one prompt. Paste this into Claude:
I want you to help me write a "Master Statement" — a short profile you'll
use to understand me in every future conversation.
Interview me ONE question at a time. Cover these areas, in order:
1. How I learn best (examples? step-by-step? big-picture first?)
2. My skills and background
3. My current goals
4. The projects I'm actively working on
5. A bit about who I am — defining life experiences, what I've been
through, and my interests or hobbies outside of work
6. How I want you to communicate with me (tone, level of detail,
format — concise and bullet-first, or thorough and detailed)
Ask one question, wait for my answer, and ask a follow-up if my answer
is vague. When you have enough, tell me you're ready to write it.
Two things that make this go better:
- Use the strongest model for the interview (I used Opus 4.8). You want it asking you the best questions, not just fast ones.
- Answer with voice input if you can — it's far easier than typing out full answers, and you'll say more.
Step 2 — Answer like a person
Claude asks one question at a time. Just talk. When it asked me how I like to learn something new — a full walk-through, or the big picture first — I told it I like the big picture as a bullet-point list, then to dive deeper from there. It used that, then followed up: when I dig into something specific, what helps most — a concrete example, an analogy, something familiar?
That back-and-forth is the point. From here on, Claude knows my skill level and tailors its answers — for me, it knows I'm a software engineer of 13 years, so it pitches things accordingly.
One tip from experience: add some personal details too — your story, the struggles, the progressions you've been through. It's not just about skills. The more it knows you as a person, the more useful it gets over time.
Step 3 — Have Claude write it
When it has enough, have it turn the interview into a document you can reuse:
Great — now write my Master Statement as a clean one-page profile, in the
second person ("You are…", "You're working on…"), so I can paste it into a
Claude Project. Keep it tight and specific.
Read what it gives you and fix anything that's off — it's yours. This is a great first start, and it'll improve your AI sessions immensely.
Step 4 — Make it permanent
Drop it where Claude will always see it:
- In Claude, create a Project (left sidebar → Projects → New). Name it (e.g. "My Work").
- Paste your Master Statement into the Project's instructions (or add it as a knowledge file).
- Done — every chat you start inside that project now begins already knowing you.
The moment it clicks
Start a fresh chat inside your Project and ask something only someone who knows you could answer well:
"Given my goals and how I learn, what should I focus on this week — and explain it the way that works for me."
Watch it answer like it actually knows you — your projects, your goals, in your preferred style — with nothing pasted into that chat. That's the difference between Claude guessing and Claude knowing you.
This is the floor, not the ceiling
Your Master Statement is one page — powerful, but a snapshot. The next step is a second brain: everything — your notes, projects, ideas, references — organized into one structured place Claude can work across. That's the difference between Claude knowing a paragraph about you and Claude being your second brain. (That's a whole video of its own — it's coming.)
For today, here's all I want you to do: stop re-explaining yourself to Claude. Give it a memory once — a Master Statement — and it knows you in every chat after that. Grab the one-page version with the exact prompts above, and go build yours.
