Skip to content
Sign in
Artwork for Master Claude Chat, Cowork, Code
Master Claude Chat, Cowork, Code · Yesterday · 46 min

4. Projects and Persistent Context (Curing AI Amnesia)

In Episode 4 of Beyond Prompting, we tackle the most frustrating bottleneck in AI collaboration: starting every conversation from a clean slate. If you find yourself repeatedly re-explaining your organizational domain, terminology, and conventions, Claude Projects provide a persistent container to turn disposable chats into an ongoing working relationship. In this episode, we break down the core mechanics of context persistence: The Three-Layer Architecture: How Projects separate Custom Instructions and the Knowledge Base (which persist across sessions) from Conversations (which remain disposable and unshared). Instructions That Earn Their Place: How to draft high-impact custom instructions that focus on non-derivable rules, target audience descriptions, and standing conventions without wasting context on generic filler. Curating the Knowledge Base: Why uploading pattern-defining specifications beats dumping entire document trees, and how to prune superseded files so conflicting context doesn't confuse the model. Diagnosing Project Failures: Recognizing the failure modes of Projects that are either too broad or too fragmented, using the "5-minute re-explanation test" to know when your setup needs refactoring. Shared Institutional Memory: How shared Projects serve as automated onboarding for new team members, establishing consistent organizational context without manual runbooks. (Note for listeners: This episode covers Chapter 4 of Sho Shimoda's book RUNNING CLAUDE: The Operator’s Guide to Chat, Cowork and Claude Code, available on Amazon as the successor book to Master Claude: Chat, Cowork and Code).

0:00-46:14
Play in

transcript

No transcript — this publisher did not publish one.

show notes

In Episode 4 of Beyond Prompting, we tackle the most frustrating bottleneck in AI collaboration: starting every conversation from a clean slate. If you find yourself repeatedly re-explaining your organizational domain, terminology, and conventions, Claude Projects provide a persistent container to turn disposable chats into an ongoing working relationship. In this episode, we break down the core mechanics of context persistence:

    • The Three-Layer Architecture: How Projects separate Custom Instructions and the Knowledge Base (which persist across sessions) from Conversations (which remain disposable and unshared).
    • Instructions That Earn Their Place: How to draft high-impact custom instructions that focus on non-derivable rules, target audience descriptions, and standing conventions without wasting context on generic filler.
    • Curating the Knowledge Base: Why uploading pattern-defining specifications beats dumping entire document trees, and how to prune superseded files so conflicting context doesn't confuse the model.
    • Diagnosing Project Failures: Recognizing the failure modes of Projects that are either too broad or too fragmented, using the "5-minute re-explanation test" to know when your setup needs refactoring.
    • Shared Institutional Memory: How shared Projects serve as automated onboarding for new team members, establishing consistent organizational context without manual runbooks.

(Note for listeners: This episode covers Chapter 4 of Sho Shimoda's book RUNNING CLAUDE: The Operator’s Guide to Chat, Cowork and Claude Code, available on Amazon as the successor book to Master Claude: Chat, Cowork and Code).

links1

more episodes

All episodes