Last week I wrote about being messy, not sloppy. About stopping to reorganize before pushing forward. About the boring, unsexy work of building systems.
This week I built on top of those systems. And something clicked.
I spent a morning watching Internet Vin’s breakdown of how he uses Obsidian with Claude Code. Slash commands. Custom prompts that read your entire vault: your notes, your thinking, your backlinks, and give you real output. Not generic AI stuff. Output that knows who you are because it’s reading your words back to you.
So I built five of them. Adapted to my vault, my workflow, my life.
/today reads my last week of notes, figures out what matters, builds a plan, generates a dashboard I can actually look at. It doesn’t just summarize. It pulls threads. It connects yesterday’s idea with last week’s project. It shows me what I said I’d do versus what I actually did. Then it builds a realistic plan for today based on my patterns, not my wishful thinking.
/close-day runs at the end of the day. It pulls out everything I captured: the notes, the ideas, the half-formed thoughts I dumped into the daily note. Then it suggests where to file each piece. It catches contradictions in my own thinking. It tells me what to carry into tomorrow and what to let go. It’s like having a closing shift manager for my brain.
/drift is the brutal one. It compares what I say matters against what I actually do over 30 to 60 days. Shows me where I’m avoiding things. Where I keep saying “I should work on X” but never actually touch it. Honest assessment, no sugarcoating. This one stings. It’s supposed to.
I built all five in one morning. And they work. Not because the AI is magic, because I spent last week organizing my vault so the AI has something real to read.
That’s the compounding. The boring work from last week made this week’s tools possible.
The Best Tools Are the Ones You Build Yourself
Here’s the thing nobody tells you about AI tools: the best ones are the ones you build yourself.
Not because you’re a better engineer than the people building products. You’re not. I’m not. But because the tool has to fit your brain. Your workflow. Your weird combination of a day job and a side business and a personal project and a family and a hundred ideas you can’t stop thinking about.
No off-the-shelf tool knows all that. But your notes do. Your vault does. And an AI that can read your vault can build tools that fit you like a glove.
I’ve tried every productivity app. Every task manager. Every dashboard tool. They all have the same problem: they’re built for someone else’s brain. Someone who thinks linearly. Someone who works on one thing at a time. Someone who doesn’t have three kids, two jobs, plumbing school, client work, side projects, and a brain that won’t stop generating ideas.
That’s not me. And I’m guessing it’s not you either.
So I stopped looking for the perfect tool and started building my own. Not from scratch. I’m not writing code. I’m writing prompts. I’m building workflows. I’m using the tools that already exist (Obsidian, Claude, OpenClaw) but I’m assembling them in a way that matches how I actually work instead of how I think I should work.
The difference is everything.
When a tool understands your context, it stops feeling like a tool. It starts feeling like a teammate who gets you. Who knows what you’re working on. Who knows what you care about. Who doesn’t need everything explained from scratch every single time.
That’s what these slash commands are. They’re not just shortcuts. They’re context-aware workflows that operate on my data, my priorities, my mess.
The Dashboard Pattern
Something else happened this week that I didn’t plan. I started seeing dashboards everywhere.
I’m building a workflow dashboard for my Obsidian setup. I’m prototyping a client dashboard for my agency. I’m thinking about a personal dashboard to track everything that matters to me. I’m looking at a client’s business and thinking “they need a dashboard too.”
I didn’t sit down and decide “dashboards are my thing.” It emerged. From the work. From trying to solve the same problem in different contexts: how do I see what matters without drowning in noise?
That’s a pattern worth paying attention to. When you keep solving the same problem in different places, that’s not repetition, that’s a signal.
The /today command builds a dashboard. Every morning. Fresh. Based on what actually matters right now, not what I set up three months ago and forgot to update. It changes as my priorities change. It reflects reality instead of aspirations.
And I realized: this is what I need for everything. Not static tools that get stale. Dynamic dashboards that rebuild themselves based on current data. That show me the truth, not what I want to see.
This applies to my business. Show me which clients are active, which are stalled, which haven’t heard from me in three weeks. Not a CRM I have to manually update. A dashboard that pulls from my notes, my calendar, my email, and tells me the truth.
This applies to my personal life. Show me how much time I’m actually spending with my kids versus how much I think I am. Show me if I’m working evenings when I said I wouldn’t. Show me the gap between intention and reality.
The dashboard isn’t about more information. It’s about the right information. At the right time. Without me having to hunt for it.
The System That Catches Things
I’m going a million miles an hour right now. Thinking of things faster than I can do them. Ideas evaporating before I can act on them. That’s not new. That’s just how my brain works.
But the difference between now and three months ago is that I have a system that catches things. The brain dump goes into Obsidian. Claude sorts it. The /close-day command makes sure nothing falls through the cracks. The /drift command holds me accountable when I’m avoiding something.
I’m still messy. But the mess has a floor now. Things land somewhere instead of disappearing.
Three months ago an idea would pop into my head at 10 PM and I’d think “I should remember that” and by morning it was gone. Or I’d capture it in a note somewhere and never see it again because I forgot where I put it.
Now? Idea hits. I dump it into today’s note. Doesn’t matter if it’s coherent. Doesn’t matter if it’s a full thought or just three words. At the end of the day, /close-day reads it, understands it, and files it somewhere I’ll actually find it when it matters.
I’m not trying to remember everything anymore. I’m trying to capture everything and trust the system to surface it when it’s relevant.
That’s a completely different way of working. And it only works because I built the system to match my brain instead of forcing my brain to match someone else’s system.
What This Means for You
If you’re building with AI right now, here’s what I’d tell you: stop looking for the perfect tool and start building your own.
It doesn’t have to be complex. A markdown file with a good prompt. A slash command that reads your notes and tells you what to focus on. A script that exports your website content so you can actually read it without clicking through an admin panel.
Small tools. Your tools. Built on your data, your workflow, your context.
That’s where the real leverage is. Not in the model. In the system you build around it.
The AI is just an engine. It’s powerful, but it’s generic. It becomes your tool when you give it your context. Your notes. Your priorities. Your weird way of thinking about things.
And here’s the thing: once you start building tools that fit you, you see opportunities everywhere. You start solving problems you didn’t even realize were problems. You start automating things you thought had to be manual. You start trusting the system to handle things you used to white-knuckle through memory.
You stop fighting your tools and start working with them.
That’s the shift. That’s what happened this week. And it only happened because I did the boring work last week to build a foundation worth building on.
Messy, not sloppy. Then build on top of the mess.
