It also knows not to use em dashes. I hate em dashes.

This didn’t happen by accident. I built it that way. And today I’m packaging the whole thing so you can use it too.

The Problem With AI Assistants

Every AI tool you’ve used has the same flaw: it forgets you the moment the conversation ends.

You spend five minutes giving it context. It gives you a great answer. You close the window. Next session, you’re a stranger again.

The productivity community’s solution to this has been prompt templates and custom instructions. Paste your context at the top of every conversation. It works, barely. It’s also exhausting and still doesn’t account for anything that changes day to day.

I wanted something different. I wanted an assistant that actually knows me and gets smarter about me over time without me having to repeat myself constantly.

Obsidian as the Brain

I already lived in Obsidian. My notes, my journals, my health log, my media library. All of it was there. The problem was it was static. I could find things, but nothing was connected to action.

The insight was simple: what if I gave Claude a folder in my vault and told it to treat that as its memory?

That’s the whole idea. Claude doesn’t “remember” me but it reads files that do. Every session it boots up and reads:

• A file about who I am (family, job, health conditions, preferences, communication style)

• A running log of every session we’ve ever had

• A list of active projects and where they stand

• A set of skill files that tell it exactly how to handle specific tasks

That last part is the key. The skills aren’t prompts. They’re documented workflows that are step-by-step instructions for recurring tasks, stored as plain markdown files in the vault. There’s one for morning briefings. One for logging health data. One for processing my inbox. One for logging movies and TV. One for weekly reviews. One for shutdowns.

When I say “log a movie,” Claude reads the media-log skill, pulls metadata from the web, creates a properly formatted note in my /Movies folder, and moves on. No fumbling, no clarifying questions, no “as an AI language model.” It just does it.

What This Looks Like in Practice

My mornings start the same way. I open Cowork (Claude’s desktop app), type “good morning,” and within about thirty seconds I have:

• Current weather and what’s coming later in the day

• Everything on my calendar pulled from all my Google calendars in parallel

• A quote worth reading

• Any open loops from the last session I need to know about

• An inbox count

Then it asks if I watched anything last night that needs logging. If I say yes, it handles the whole thing (title, cast, gene, cover image, rating, my notes) and files it in the right place.

Why This Works When Other Setups Don’t

I’ve tried the custom instructions approach. I’ve tried pasting context blocks. I’ve tried dedicated AI apps that promise memory features.

The difference here is that the memory lives in a place I already control, in a format I already use, and it’s updated automatically as part of the workflow itself or I can go into the .md file and edit it myself.

I don’t have to use tokens if I want to make a change.

When I log something, the log gets updated. When a project changes status, projects.md gets updated. When I shut down, a session summary gets written. The system maintains itself because maintaining it is built into every skill.

It also means I can read my own logs. I can see what Cog (that’s what I call my robot) did two weeks ago. I can search my vault for any decision I made or any task that came up. It’s not locked in some proprietary memory system I can’t inspect or export.

The Magpie Vault

I’ve been running this system for a while now. It’s become the thing I use more than anything else on my computer.

So I packaged it all up.

The Magpie Vault is an Obsidian starter pack built around this exact setup. It includes:

• The full Robot Assistant skeleton CLAUDE.md, all the core skill files (morning, journal, health, media log, weekly review, inbox, shutdown, and more), and the memory file structure

• A health tracker template pre-built for daily logging

• A media log template for movies and TV

• Weekly and monthly review templates

• A full README walking you through setup step by step

You bring your own Claude account. Everything else is in the vault.

It’s $19. One time. You own it.

Get the Magpie Vault →

If you’ve been wanting to use AI more intentionally and not just for one-off questions but as an actual part of how you work, this is the place to start. The skeleton is already built. You just have to fill in the details about yourself and let it run.

That’s the Magpie Method. Steal what works, leave the rest. This one works.

Questions? Hit reply. I read everything.

When the doctor told us she was allowed 4,000mg of acetaminophen every 24 hours and not to exceed that, I went and asked it to keep track of how much acetaminophen was in each of her medicines. I was able to put that in, and then it gave me a graph at the top showing how much she had taken in the past rolling 24 hours and how much she was allowed to take.

Once things calmed down, I was able to look around on the App Store to see if there was something on the market that gave me this level of customization and I found nothing. There were no apps that met everything I needed, yet this application that took me 30 minutes to get started and 20 minutes here and there to customize was exactly what I needed when I needed it. Her surgery went well and pain management was phenomenal, so she was able to get off the pain medicines within a week. I just didn’t open the web app anymore.

I didn’t have to uninstall anything, didn’t have to unsubscribe, didn’t have to pay for any of it (other than my Claude subscription). Had I downloaded an app, there more than likely would’ve been a subscription, a one-time fee, or some kind of payment for something I only used for one week.

I don’t know what that means for app development and what it means for the future of software, but I was blown away by how easy it was to get it going, customize it to exactly what I needed, and use it for when I needed it.

Before this, my default move was opening the App Store and searching until I found something that was close enough to what I needed (and then paying for it anyway). Now my default move is opening Claude and just building it. I wonder how many of you are still searching the App Store when you could just build exactly what you want in 30 minutes. Are you still doing it the old way?

I am still in the early stages of the Productive Magpie concept. I have learned not to hoard tools but to build systems that reinforce who I am and how I work. After finishing Atomic Habits by James Clear, this concept was further fleshed out as I looked to build in those systems into my magpie approach.

Identity Over Goals

On…

Read more

Watch a magpie build its nest and you’ll see a creature that refuses to be loyal. Magpies are thieves with taste. They don’t commit to one tree or one yard. Instead, they scavenge, hopping from fence post to garden to parking lot, select…

Read more

My heart sank as I realized I had forgotten to set up the room. I was driving to work when my boss called about a meeting with physicians that morning. The details were in my work calendar, humming away on my office PC, completely useless to me in the car. That’s the moment I beca…

Read more