Key takeaways
- The cold-start tax is real. A new chat forgets where you were, so you burn time re-explaining before any real work happens.
- Leave a bookmark when you stop. Ask Claude to write a short project log: what you did, where you stopped, and the next steps. It takes 20 seconds.
- Open to the bookmark when you return. Have it read the log and tell you where you left off and what to do first. You're back in context in under a minute.
- A file beats scrolling old chats. Your decisions and next steps live in 1 short file you control, not buried across a long transcript.
- It scales across projects. Each project folder keeps its own log, so many clients never blur together.
- The log, memory, and a second brain stack. The log holds 1 project's live state; memory holds your standing rules; a second brain holds your archive.
The Solo Creators AI Studio
Get this skill, and every one I build.
The whole vaultA new drop monthlyBuild live with meYours to keep, forever
See inside the Studio
30-day money-back guarantee. Cancel anytime.
Questions people ask
Why does Claude Code forget my project between sessions?
Each new conversation in the Claude desktop app starts clean on purpose, so old context does not muddy new work. That is a feature, but it also means a fresh chat does not know where you left off. The fix is a short note you leave before you stop and read when you return.
How do I save where I left off?
Ask, in plain English, before you close the app: 'update my project log with what we did, where we stopped, any decisions, and the next steps, and save it to the project folder.' Claude writes a short status file and keeps it in your folder. Do it every time you stop, while the context is fresh in the conversation.
How do I get back up to speed the next day?
Point Claude at the log first instead of diving in cold: 'read my project log, tell me where we left off, what is still open, and what you would do first today.' In 1 message you are fully back in context, with the current state and a plan, usually in under a minute.
How is a project log different from memory?
A project log holds the live state of 1 project: what is done, what is half-finished, what comes next. Memory holds your standing rules and voice that apply to every task. The log is narrower and more urgent, a bookmark for 1 job in progress, while memory makes everything sound like you. You want both.
Why not just scroll back through the old chat?
Because the important decisions are buried between 100 small messages, so re-reading is slow and unreliable. A project log flips it: the decisions and next steps live in 1 short file you control, so you read a paragraph instead of an afternoon of history. It also survives a closed or lost chat.
What exactly goes in a project log?
4 short things: what you did (the current state), where you stopped (the exact resume point), any decisions you locked in, and the next 3 steps. That is it. Decisions and next steps are the 2 lines people skip and the most valuable, because they are what gets buried in a long chat. Keep it to a few lines, not a transcript, so the restart stays fast.
How is a project log different from a to-do app?
A to-do app holds your next steps but not the state of the work or the decisions you made, and it sits in a separate tool Claude is not looking at when it briefs you. A project log sits in the project folder, so Claude reads it and briefs you from it, and it captures state and decisions as well as next steps. It is the 1 note that both you and the assistant can actually use.
Written by Ronnie Nijmeh
Ronnie spent 18 years building a SaaS with a team of 20 that served over 650,000 customers, generated over $14M in sales, and sent over 550M emails. Now he's solo, solving real business bottlenecks and turning them into working AI skills, workflows, and automations. He teaches all of it, with direct access to him, inside the Solo Creators AI Studio Skool community. See what he's built →
“I completely rebuilt my site using the Website Launch Builder. If you've ever built a website, you'll really appreciate this skill. I'm blessed to be a member.”
Michael HattawayFounder, Iron Strengthens Iron