Building My Own AI Command Center

Why I built it

I spent one evening building a personal AI command center, and it now writes me one short briefing every weekday at 9 AM. Not a productivity system for a business. A briefing for my life.

I'm a frontend developer, a writer, and an Enneagram Type 9. Type 9s are great at keeping the peace and terrible at remembering their own priorities. My days fill up with other people's asks, and the things I care about quietly slide.

The spark came from Erika Stanley's AI Queens episode, "Claude Command Center: Stop Drowning in Email, Slack, and To-Do Lists." Hearing her walk through her setup made me realize I could build one around my own life.

So I wanted one place that puts my priorities first, every morning, in five things or fewer. October gave me the perfect test: Hacktoberfest, a reading habit I'm trying to build, and recovering from ankle surgery, all at once.

What lands every weekday morning

Every weekday at 8:59 AM, a scheduled Claude task reads my email, calendar, podcasts, and daily log, then sends me one briefing. The rule I gave it: five things that matter beat twenty that don't.

It always starts the same way:

1. What's still open from yesterday, at the very top
2. Quick wins: up to five things I can finish in about 10 minutes, with time estimates
3. The one most important thing today
4. Weather, energy, recovery, reading, and one awareness line
5. Hacktoberfest progress, emails worth answering, what's due
6. One or two focus ideas, offered as options, never orders

Each day has its own mode, so the week has a rhythm:

The pieces under the hood

The whole system runs on three simple parts: a plain-text log, a few trackers, and some ground rules about tone.

A daily log I talk to. A file called carryover.md has a dated entry for each day with four sections: Done, Didn't get to, Came up today, and Carry forward. At night I just say what happened ("read 12 pages, got the DevRelay sticker") and Claude sorts it into the right place. It only ever adds, never deletes. The morning briefing reads it, so nothing I said slips through the cracks.

Trackers that fit this season of life. Right now it tracks my ankle recovery, a 10-pages-a-day reading habit, what I'm learning, and my Hacktoberfest stickers. Habit tracking like water and steps is paused until I'm healed. A tracker that makes me feel behind is worse than no tracker.

Frameworks as options, not rules. I use Human Design, the Enneagram, and my INFJ-T type as self-reflection tools. Each briefing gets exactly one awareness sentence from them, written fresh. Every suggestion is framed as something I can respond to. Big decisions get "sleep on it, then decide by ___." And one hard rule: no guilt, no "you should have."

Hacktoberfest 2026: chasing 15 stickers

My top priority this month is Hacktoberfest, and I'm aiming for 15 stickers, the maximum prize tier. By the end of day one I had 5.

I've done Hacktoberfest before, back when it was all about pull requests, so I was surprised by how much changed this year. Pull requests no longer count toward rewards. Instead you collect virtual stickers in a sticker book by doing things: DEV Challenge posts, livestream check-ins, Global Hack Week, connecting tools, and surveys. There are 24 in total. Two are in-person, which I'm skipping while I recover, so 22 is my real maximum.

The command center made this easy to plan:

• It mapped every sticker to its deadline and picked a path to 15 by mid-October.
• It flags each DEV Challenge the day before it closes. They close at 2:59 AM on Mondays, which is really Sunday night.
• It filters 33 livestreams down to the evening and weekend ones I can actually catch live, since check-ins need the code on screen.
• It turned the four "do it anytime" stickers into quick wins. I knocked out all four on day one.

Next up: the Launch Weekend DEV Challenge. Build something small, write it up, post it by Sunday night.

What I learned in one evening

The biggest lesson: a good system says no more than it says yes.

• Fewer trackers win. I was tempted to track everything. Every tracker is something I have to log at night, so I kept only what matters this month and paused the rest.
• Check the rules before you plan. I almost set a pull-request goal. Reading the actual Hacktoberfest site showed PRs don't count anymore, and the whole plan changed.
• Keep work and personal separate. I skipped connecting my work calendar and sprint board, and I used my personal Claude account, not my work one, for my Hacktoberfest tools. My open-source work should be clearly mine.
• Tone is a feature. "Options, not orders" and "no guilt" do more for me than any clever automation. If the briefing made me feel behind, I'd stop reading it.
• Start small and imperfect. My first book is 10 pages a day. My first DEV post will be something quick. Done beats perfect.

What's next

Tomorrow is the first real briefing, and it happens to be Fun Friday. Over October I'll find out whether a calmer, shorter morning actually changes what I get done.

Here's what I'll report back on at the end of the month:

• [ ] Did I reach 15 Hacktoberfest stickers?
• [ ] Did 10 pages a day turn into a finished book?
• [ ] Which parts of the briefing did I actually use, and which did I skip?

If you build something like this, start with one question: what are the five things you'd want to know before 9 AM? Everything else can wait.