Mission_Control

A visual project dashboard that replaces walls of Claude Code text with a glanceable interface. One central dashboard, every project you own as a dropdown, a motherboard-style cutaway showing each project's internal engine.

Why this exists

If you build with Claude Code, you spend a lot of your day scrolling through long technical messages just to remember what each of your projects does and where each one is stuck. Mission_Control is the visual antidote: open the dashboard and immediately see what runs, what's broken, what's blocking which phase, and what to fix next — without reading.

It's designed for solo builders and small teams who run several projects in parallel and use Claude Code as their primary dev partner.

How it works

1. You run /mc adopt inside any project that has Claude Code wired up.
2. Claude scans the project, proposes 5–12 components, asks you to confirm via a short multiple-choice prompt, then writes mission-control.config.json to the project root — and mirrors it to the central dashboard.
3. You open the dashboard. Your project is now in the dropdown.
4. As you work, /mc audit finds real issues and appends them as findings. /mc reconcile syncs APPLY / SKIP clicks back into the code.

The config file is the source of truth. The dashboard is read-only of it. There's no backend, no database, no auth.

Quickstart

1. Clone

git clone https://github.com/mcin93/Mission_Control.git
cd Mission_Control

2. Start the dashboard

cd mission-control
./start.sh       # macOS / Linux
start.bat        # Windows

…or just open mission-control/index.html directly in a browser.

You should see the bundled Deal Tracker demo project. The dropdown lets you switch to Daily Digest and Docs Portal — two more bundled demos that show the linear-flow badges and drill-down respectively.

3. Wire up the /mc skill (optional, requires Claude Code)

If you use Claude Code, the .claude/commands/mc*.md files in this repo give you a /mc command and four subcommands. Each subcommand is reachable two equivalent ways:

Spaced form	Hyphenated form
/mc adopt	/mc-adopt
/mc audit	/mc-audit
/mc reconcile	/mc-reconcile
/mc status	/mc-status
/mc publish	/mc-publish

Both forms do the same thing — the spaced form goes through the mc dispatcher; the hyphenated form jumps straight to the subcommand. Pick whichever you prefer. To make them available, copy .claude/commands/mc*.md and mission-control/skills/*.md into your global Claude Code dirs (~/.claude/commands/ and ~/.claude/skills/), or just drop them under .claude/ inside each project where you want /mc available.

Set the env var MC_ROOT to the absolute path of this checkout (e.g. ~/Mission_Control or C:\Mission_Control). /mc publish reads it to know where to mirror configs. If unset, Claude will ask you for it on first use and remember the answer for the conversation.

If you don't use Claude Code, you can still hand-author mission-control.config.json files and use the dashboard as a static viewer.

What you get

The dashboard surface:

• Project picker (top-left) — switch projects without leaving the page
• LOOK dropdown (top-right of each look's header) — flip between 5 visual styles
• Info-band (right under the tabs) — plain-language "what is this · right now" panel, readiness scorecard pills, tag filters
• Engine (the big central area) — chips for components, traces for connections, particle flow for live edges
• Audit panel (right column) — open findings as actionable cards (APPLY / SKIP)
• TOOLS bar (bottom-left, alt looks only) — FIT / SAVE VIEW / RESET LAYOUT + AUDIT / RECONCILE / ROOT / PUBLISH

Five visual looks share the same data and the same feature set; only the chrome changes:

Look	Vibe
Motherboard	Original PCB / BIOS aesthetic
Terminal	Bloomberg-dense JetBrains Mono on dark
Linear	Modern dark dev tool, rounded cards
Blueprint	Cream paper, serif type, brick dashed traces
Crisp	White cards on white, electric blue accent

Bundled demo projects

Three fictional configs ship with the repo so the dashboard looks like something on first load. They are not used as starting templates — /mc adopt builds a config from your actual project, not from a copy of a demo.

Demo	Shape	Showcases
Deal Tracker (example.config.json)	Mixed graph: scrapers, store, ranker, API, frontend, external	Every component type, mixed statuses
Daily Digest (configs/newsletter_pipeline.json)	Linear pipeline: fetcher → store → summarizer → builder → sender	START / OUTPUT flow badges
Docs Portal (configs/docs_portal.json)	Frontend with children and child_connections	Drill-down nested engine

Where to learn more

• docs/manual.md — the whole story (~20-minute read). Concepts, every /mc command, dashboard features, schema reference, troubleshooting, roadmap.
• CLAUDE.md — project spec, canonical config schema reference, hard rules.
• CONTRIBUTING.md — how to send a PR, what's in scope, what isn't.

License

MIT. Use it however you like.