Two years into a job I couldn't find my own files. Shortcuts everywhere, untitled documents I'd meant to throw away and never did, and no appetite for fixing any of it by hand. So I asked Gemini to build me a script that would sort it out, with two rules: don't rename anything, and don't delete anything. The folder I was dreading, the one where everything ambiguous would pile up, ended up with about twenty files in it.

A brainstorm about monetizing this blog turned into a realization that I'd never once opened the SEO panel on any of it. So I connected Claude to my Wix site and let it read what was actually there. What followed was fifteen posts fixed, an SEO education I never sat down for, and one moment where I checked the work and found every description had been wiped. The part I keep thinking about isn't the fix. It's that I learned the whole thing while doing it, which is why any of i

Last week's post was about how it felt. This one is about what's actually running underneath it: two scheduled tasks, no code, and the specific guardrails that kept it from falling apart the first two weeks. If you want to build something like this yourself, this is the version with the actual mechanics.

I started a new job about a month ago and braced for the usual rebuild, recreating every script and process I'd relied on before. Instead, I connected a few tools on day one. By week two, someone said a name I didn't recognize, and I already had a profile on them. This is what changed when the context showed up before I did.

I'd made fifteen AI use case videos with no script format, just whatever felt right that day. I transcribed all of them, fed them to NotebookLM, and asked if there was a pattern I couldn't see. There was. Six parts, and I'd been using them the whole time without knowing it.

I used to send my status report after one AI pass and my own read-through. Now five personas argue about it first, the business partner, the executive, the chief of staff, and two more, each built around someone who actually reads the thing. This isn't really about status reports. It's a structure you can point at any output you produce.

I built a Gem in twenty minutes to handle a framing problem I'd been fighting for months. That part worked. What I didn't expect was what happened when I started giving it stakeholder feedback — and asking it to improve its own instructions.

My phone was 96% full and I was leaving for vacation in a few days. The reason I couldn't clear it was an external hard drive I'd been avoiding for years — 25 years of photos, buried in backups of backups, scattered across 30-plus folders. I gave myself the weekend and let AI do the heavy lifting. It recovered 2,101 photos I didn't know I had — including the full Morocco trip I thought was only 304 photos. The number that mattered most: zero deletions.