Command Center reference guide

Want to build the first version now? The Command Center Quickstart turns your businesses, current tools, and preferred dashboard sections into one guided Claude Code setup.

This is the thing you came for: one page that answers, at a glance, what is done, what is in progress, what is waiting on you, and what happens next, across every project you run. You do not check five apps to reconstruct it. You open one page and you know. This chapter builds it.

By now Claude knows your business (Win 1), sounds like you (Win 2), sees your work (Win 3), and files your meetings (Win 4). Your command center is what turns all of that into a single view you actually look at.

What a command center is

Picture the dashboard a pilot has: not every gauge in the plane, just the handful that tell them whether they are on course. Your command center is that, for your business. It pulls from the files Claude already maintains and answers four questions:

What is done? Finished work, so you can see momentum.
What is in progress? Live work and where it stands.
What is waiting on you? The things stuck until you decide, approve, or reply.
What is next? The most important thing to move forward.

You already have all of this information scattered across your projects. The command center just gathers it into one place, in your words, and keeps it current.

Level 1 - the page anyone can build (no code)

The simplest command center is a single markdown file, COMMAND-CENTER.md, at the top of your ~/hub folder. Claude writes it and rewrites it by reading your projects. You read it.

Here is the shape:

# Command Center - [your name]
_Last updated: [date] by Claude_

## Waiting on you
- [ ] Approve the new pricing page (ready since Tue)
- [ ] Reply to the supplier quote before Friday

## In progress
| Project | Status | Next step |
|---|---|---|
| Online store restock | Photos done, copy in draft | Claude finishes copy, you approve |
| Client onboarding (Acme) | Kickoff call filed | Send the welcome pack |

## Done this week
- Shipped the fall newsletter
- Closed the books for last month

## What's next (most important first)
1. Launch the restocked products
2. Draft next week's content

How Claude fills it in. Ask, in plain words:

read my hub folder and update COMMAND-CENTER.md. Look at each project,
figure out what's done, what's in progress, what's waiting on me, and
what's next. Write it in the four sections. Keep it short.

Claude reads your project files, your meeting notes, your decisions, and your task lists, then writes the page. Because it reads the real files, the page reflects reality, not what you remembered to type.

Make it refresh on its own. A dashboard you have to remember to update goes stale, and a stale dashboard is worse than none. So wire the refresh into the end of every work session. Add one line to your ~/.claude/CLAUDE.md:

## End of session
When I'm wrapping up, update COMMAND-CENTER.md before we finish.

Now the page rewrites itself as a byproduct of working, and it is current every time you open it. That is the difference between a dashboard you use and one you abandon.

Level 2 - the web version (optional, later)

The markdown page is genuinely useful, and most people are happy there for a long time. When you want something more visual, a web page you can pull up on your phone with real boards and status colors, that is Level 2.

Be honest with yourself about what it is: Level 2 is a small software build. It reads the same files you already have and renders them as a live web dashboard. If you enjoy tinkering, budget a weekend. If you do not, this is exactly the kind of thing worth having done with you rather than fighting alone. Either way, nothing about Level 2 changes your files; it just gives them a nicer window.

Do not start here. Level 1 first. The web view renders a well-kept command center; it cannot fix a messy one. Get the markdown page working and refreshing, then decide if you want the glossier version.

A worked version - Maya’s command center

Maya runs an online store and a small service business on the side, plus a content channel. Her command center has the same four sections, shaped to her world:

Waiting on Maya: approve product photos, reply to a wholesale inquiry, sign off on a video thumbnail.
In progress: store restock, a client’s project, this week’s videos, each with its next step.
Done this week: momentum she can actually see, which on a hard week is the whole point.
What’s next: the one launch that matters most, at the top, so a busy morning still starts in the right place.

She never types this up. She works, Claude updates the page at the end of each session, and every morning she opens one file and knows exactly where all three parts of her business stand. The morning scramble of “what was I doing, what am I forgetting” is just gone.

You’ve got it when

COMMAND-CENTER.md exists at the top of your ~/hub folder
It has the four sections: waiting on you, in progress, done, what’s next
Claude filled it in by reading your real projects, not by asking you
It refreshes at the end of a session without you asking
You opened it one morning and knew the state of everything in ten seconds

That last one is the whole game. When it happens, you have the outcome this guide was built to deliver.

Where this can go

You have now built, by hand, the thing most people imagine when they picture “AI running my business”: a single, always-current view of everything, that both you and your AI read from. Keep it simple and it will serve you for a long time.

If you want the web version, or you want this same command center to cover a whole team instead of just you, that is a bigger build. The next chapter is honest about where the do-it-yourself path ends and where having a partner starts to make sense.

→ Next: 99-where-this-goes-next.md