A free step-by-step guide for ambitious leaders. Stand up a personal AI Chief of Staff that knows your goals, calendar, and relationships. Four steps. No engineering background needed.
Most people use AI like a search box. Type, answer, close tab. A personal Command Center is different. Your AI knows your goals, your calendar, your relationships, your week. It writes you a morning brief that says what actually matters today.
Models are getting smarter every quarter. The people getting outsized returns aren't the ones prompting better. They're the ones who built a system that lets more AI capability land on the things they care about. You're shipping an MVP, not a perfect product. 30 minutes from now, something is running. You iterate from there.
Steps 1 through 3 are your MVP. 30 minutes, end to end. Step 4 is the rest of your life with the system, getting sharper every week. Each step gives you a prompt to paste into Claude Code. Claude Code handles the setup. You bring the context.
A Command Center is only as good as what it knows about you. Start here.
Gather these into a folder. Don't worry about formatting. Claude Code sorts it.
That's enough. This alone changes every conversation you have with your AI from here on.
I want to start building my personal Command Center. I'm going to give you the basics about me, and I want you to organize them into a context folder you can read at the start of every session. Create a folder called ~/CommandCenter/ and inside it create a MEMORY.md file. Then walk me through what to drop in. I'll have my resume, my LinkedIn, a one-pager about me, a few writing samples, and my professional bio. Once we have the basics, set up a session-start hook so this context loads automatically every time I open a Claude Code session. I shouldn't have to re-explain who I am.
A great brief in a place you never read is worth nothing. Tell your AI how you work before you build anything.
Before you start, enable voice mode in Claude Code and answer these out loud. You'll move twice as fast, and the answers will be more honest. Less editing, more truth.
I want to define how my Command Center should communicate with me. Walk me through the questions in Step 2 of the guide, one section at a time. As I answer (I'll probably use voice mode), take notes in ~/CommandCenter/MEMORY.md under a section called "How to work with me." Then write a one-paragraph voice and cadence summary at the top of that section. This is what every future brief should follow.
Write a one-page picture of your life one year from today, in present tense, as if it's already that day. Where you live. What you're working on. What a Tuesday looks like. What you stopped doing.
Mine sits at the top of my Command Center. Every real decision maps back to whether it gets me closer to that document. Talk it into a voice recorder. Describe the day.
One prompt. Claude Code sets up the rest.
Every morning at the time you chose, an email lands in your inbox. It reads your context and your calendar, and tells you what matters today, what to drop, and what to watch out for. Paste the prompt below and answer the follow-ups.
Set up my daily morning brief. The brief should fire at the time I prefer (ask me) and land in my inbox as an email. It should read my Command Center context (the MEMORY.md and the one-page vision I wrote), my calendar for today and the week ahead, and any recent activity logs. It should then synthesize a 200 to 400 word brief that names: - What today actually is (calendar shape, energy state, what's load-bearing) - One or two things that matter most - What to drop - What pattern to watch out for in myself Use my voice preferences from MEMORY.md. No corporate hedging. No prescribed counts. To make this work, you'll need to: 1. Set up a daily scheduled job on my Mac 2. Stand up a small local server that reads my context 3. Wire the brief into my email Walk me through each step. Pause for my input when you need information from me (calendar access, email setup). Make it run by tomorrow morning.
Claude Code will ask a few things along the way: calendar access, where to send the email, your preferred time. Answer each one.
Your MVP is running. Now you make it sharper. A Command Center compounds because you keep teaching it.
Audit my Command Center. Tell me: - Which scheduled jobs are firing, and which are stale or silent - Which briefings are actually reaching me and which I'm ignoring - What context in MEMORY.md is out of date - Three small improvements I could make this week Be direct. Don't pad. I'd rather hear what's broken than what's working.
Once your daily brief is solid, you can add a weekly relationship digest, a pre-meeting briefing, a content-prompt that reads your last month of activity. None of these need to exist on day one. They earn their place when the daily brief is working.
Most leaders eventually build a second Command Center for work. Different machine, different rules, hard firewall. It holds client templates, brand styling, organizational context, the language of your team. Same pattern as this guide, different context. Build the personal one first.
Your MVP works. Now the real leverage. Three directions for your next stage, in roughly the order most people take them.
A Command Center gets exponentially more useful when it can read from the places your life already lives. Most of these connect through the command line or a small local server that runs on your machine.
Once real data flows, get the security right. Five rules cover most of what matters.
The same brain can power more than the morning email. The pattern is identical: a scheduled trigger, a synthesis call, a place the answer lands.
Each of the stages above is becoming its own module: connections, the brain, security, custom surfaces. If you want the full course when it ships, drop me a line.
If you want a partner to ship your MVP in one working session, I do this with leaders one-on-one. You leave with something running.
See how it works