Everyone knows Anthropic models are incredible for coding, but when you’re deep in a large codebase, Claude Code can still lose focus over long context and forget steps you gave it earlier. In this video, I show a simple fix: pair Claude Code with Obsidian (completely free) to create persistent, structured project memory. Because Obsidian stores everything as plain Markdown files inside a local folder (your “vault”), Claude can directly read, search, reference, and even update the notes over time. I walk through creating a vault, what to put in it (project overviews, coding rules, architecture decisions, bugs, session summaries, meeting transcripts, PRDs—anything that matters), and why this becomes a “second brain” for your codebase. I also recommend installing the Obsidian Skills/agent skills so Claude interacts with the vault more cleanly—reading and writing notes, searching prior context, and generating session logs automatically. To prove it works, I demo referencing an existing CRM dashboard project and having Claude pull the correct context (Prisma schema, component architecture, ShadCN UI patterns) to build a deals Kanban board that stays consistent with the existing stack. The big takeaway: stop re-explaining your project every session—use a vault so Claude stays aligned with your original vision across weeks or months.