You know the first loss. The day you stop. Life gets in the way, energy drops, the project goes quiet. That one you can see coming.
The second loss is quieter. It happens when you come back. You open a new conversation and Claude doesn't know who you are, doesn't know what you built, doesn't know what you decided three weeks ago. So you start explaining. And somewhere in the explaining, you feel the thing you built getting smaller — not because it's gone, but because you can't find your way back into it. The thread is lost.
Most long projects don't fail at the hard part. They fail at the re-entry.
Claude Projects is a container — a dedicated workspace where your files, your instructions, and your conversation history all persist between sessions. You open it and Claude already knows where you are. You pick up instead of starting over.
But the container is only as good as what you put in it. This module is about building it right — so that coming back feels like walking into a room that's been waiting for you, not a room you have to rebuild from memory.
Tell Claude Who You Are — Once
Every Project has Custom Instructions. This is where you establish the creative relationship before the work begins — your voice, your standards, what you need Claude to do and not do. Write it once and it applies to every conversation in the Project forever. No re-explaining. No re-orienting. Claude walks in already briefed.
The instructions aren't a description of the project. They're a description of the partnership. How you write. What honest feedback looks like for you. What role Claude plays. What to show first and when to explain. Write it like you're briefing a collaborator who's about to spend the next year with you.
Your Briefing Book
The file library inside a Project is your briefing book — documents Claude can reference in any conversation without you pasting them in. Your voice document. A sample that captures the tone you're building toward. Character or subject profiles. Any structural document — outline, timeline, chapter map.
Start lean. Four files is enough to orient a first session completely. Upload what shows, not just what tells. A well-chosen sample scene tells Claude more about your voice than a ten-page description of it.
Threads and the Long Game
Inside a Project, every conversation thread is saved. Name them when you open them — not "New Chat" but "Chapter 6 — the confrontation" or "Voice — testing third person." Three months from now you'll be glad you did.
Keep threads focused. When one starts circling across too many problems, start a new one. The old thread stays exactly where you left it. Focus is the feature.
The Table of Contents Move
When a thread runs weeks-long, Claude's recall starts to compress at the edges. Ask for a summary and you might get the last third, not the whole arc. The fix is an anchor — go back to the very first message, copy it, and ask Claude to build a complete table of contents with that message as the start and the current message as the end.
The bookends force full recall. This technique came out of the 46-day single-thread collaboration that became this course. Without the anchor, half the work would have been unrecoverable.
The Checkpoint
Every three to five sessions, stop and ask Claude to account for where the project actually stands — not where you feel it stands. What's been decided. What's locked. What's still open. What's being circled without resolution. The third question is the one that does the real work — it names the thing you already know is there but haven't faced yet.
Before Projects — The Context Doc
Projects require a paid plan. If you're not there yet, the same principles apply — you carry the context manually. Keep a running document: your voice brief, the current state of the work, what's been decided. Paste the essentials at the start of each session. End each session by asking Claude for one paragraph that summarizes where you left off. When you move to Projects, that document becomes your first upload.
Build the Room Before You Need It
Don't wait until you're deep in a project to set up the container. Build it now, while the work is fresh. Create a Project. Write the Custom Instructions as if you're briefing a collaborator who's about to spend the next year with you. Upload one sample that shows what the work sounds like.
Then ask Claude one question: what does it know about this project based on what's already there? The answer shows you what's clear and what's missing. That's your baseline. That's the room before anything goes wrong. The second loss is preventable — but only if you build the room before you need it.