Lora's Command Center
Last reviewed
IntermediateWhat you'll learn
~60 min- Build a React dashboard that unifies personal finance tracking with game studio planning
- Create a savings rate tracker and investment portfolio summary with founder runway projection
- Integrate IP pipeline status, budget scenarios, prototype progress, and crowdfunding readiness into a single Studio View
- Generate a go/no-go recommendation with confidence score from all available data signals
What you’re building
Nineteen lessons. You have built IP research tools, market analyzers, financial planners, game mechanic specifications, playable prototypes, sound systems, level editors, test harnesses, and a full demo. Each one lives in its own folder. Each one answered a specific question. None of them talk to each other.
This lesson fixes that.
You are building a unified dashboard — Lora’s Command Center — that connects everything you have built into two views and one decision. The Money View tracks your personal financial life: savings rate, investment portfolio, and a projection that tells you exactly when you could afford to quit your job and start the studio. The Studio View tracks the game company: IP pipeline status, budget scenarios, prototype progress, market comparisons, and a crowdfunding readiness score. Between them, a bridge calculation answers the question that actually matters: “Based on my savings rate and the studio’s estimated burn rate, when can I realistically start?”
This is the capstone. Not because it is the most technically complex thing you have built — the playable demo was harder. This is the capstone because it is the cockpit. Every decision you make about the game company starts here. Every financial milestone you hit shows up here. The dashboard does not build the game for you. It tells you whether you are ready to build it.
You have a day job and a dream. The day job pays rent and fills investment accounts. The dream costs money and takes time. Most people keep these in separate mental buckets — “my finances” over here, “my game studio idea” over there — and never connect them. The Command Center forces the connection. Your savings rate is not just a personal finance metric. It is the clock counting down to the day you can afford to start. That reframe changes everything.
By the end of this lesson you will have a React application with localStorage persistence, two tabbed views (Money and Studio), a bridge calculation that connects personal finance to founder readiness, a crowdfunding kit section, and a go/no-go decision integrator that pulls every signal from the entire module into a single recommendation with a confidence score.
Multiple data domains (personal finance, project management, market analysis) rendered in a unified interface with cross-domain calculations. This pattern appears in executive dashboards, operations centers, and any context where decisions require synthesizing signals from multiple independent systems. The key technique is defining a shared data model that bridges domains without coupling them.
The showcase
Here is what the finished Command Center gives you:
Money View tab:
- Savings Rate Tracker: Monthly income, monthly expenses, savings rate percentage, trend over time (Chart.js sparkline). Pre-filled with editable defaults.
- Investment Portfolio Summary: Account balances by type (401k, Roth IRA, brokerage), total portfolio value, asset allocation pie chart, estimated annual return.
- Founder Runway Projection: “At your current savings rate of X% and estimated studio burn rate of $Y/month, you can self-fund for Z months starting [date].” Editable target date. Shows how much you need saved by that date.
Studio View tab:
- IP Pipeline Status: Where you stand on rights acquisition (from the patterns in the Source Availability Scanner, BloodRayne Rights Map, Remake Deal Structure Advisor and Remake Strategy Decider). Status indicators: research complete, contact initiated, terms proposed, deal signed.
- Budget Scenarios: Summary cards from the Studio Runway Planner’s data — self-funded, Kickstarter, publisher. Monthly burn, runway months, funding gap.
- Prototype Progress Checklist: Every prototype from the Combat Loop to the Playable Demo with completion status. Percentage complete bar.
- Market Comp Summary: Key metrics from the Retro Remake Market Tracker and the Storefront Revenue Simulator: comparable titles, revenue estimates, market positioning.
- Crowdfunding Readiness Score: Calculated from checklist completion (demo built? trailer beat sheet done? landing page copy ready? press kit assembled?).
Bridge section (visible on both tabs):
- “Based on your savings rate and estimated studio burn rate, here’s when you could realistically start”
- Timeline visualization showing savings growth, target start date, and runway from that point
- Adjustable parameters: savings rate, target start date, studio burn rate, initial funding source
Go/No-Go Decision Integrator:
- Pulls all signals: IP availability, market viability, financial readiness, prototype completeness, crowdfunding readiness
- Each signal scored 0-100 with a weight
- Weighted composite score with confidence level
- Final recommendation: GO, CONDITIONAL GO, or NOT YET with specific blockers listed
Plan this build in plan mode, as every build in this module runs. The plan will be long, so before you approve it, send:
Split this plan into chunks I can check one at a time. Build the first chunk,run it, and stop so I can look before you start the next one.That is the rule of one from Breaking Down Tasks (one feature per step, the next only after the last one works), applied to a full dashboard build. When the build works, keep the facts later messages repeat in a one-screen brief the tool reads at the start of every session:
Write AGENTS.md, one screen long, recording how to start the dev server, the dark theme,how browser state persistence works, and the runway figures from the StudioRunway Planner lesson, copied from that lesson's output, not retyped.Codex, Antigravity and Copilot read AGENTS.md on their own. Claude Code reads it directly when the project has no CLAUDE.md (v2.1.277 and later); if it has one, add the line @AGENTS.md to it so it loads too. Before each commit, run the tool’s built-in review on what changed: /code-review in Claude Code, /review in Codex and Copilot, or /diff in Antigravity followed by a request to review that diff.
Before you start
If your AI tool is open from the previous lesson, leave it (/exit, or Ctrl+D in Antigravity) so you are back at your terminal prompt. Create a folder for Lora’s Command Center and step into it:
mkdir -p ~/retro-remake/20-command-center && cd ~/retro-remake/20-command-centerIn Windows PowerShell, run mkdir ~/retro-remake/20-command-center; cd ~/retro-remake/20-command-center. In a desktop agent app, open ~/retro-remake/20-command-center as your workspace folder. Then start your AI tool the way Workbench Setup showed.
Switch to plan mode
Switch into Plan mode (Shift+Tab, /plan, or the mode picker) so your agent clarifies the Money View, Studio View, Bridge calculation, and Go/No-Go weights before generating files.
The conversation
Each message below is an example. Say it in your own words.
Say what you want
Ask for a browser dashboard that connects personal finances, studio runway planning, prototype progress, and a Go/No-Go decision tool:
Build a browser dashboard called Lora's Command Center with a Money View, a Studio View, a founder runway bridge calculation, and a Go/No-Go decision score that saves my edits automatically. Ask me what you need first.Answer its questions
Your agent will ask about the Money View inputs, the Studio View sections, the bridge calculation between savings and studio burn, and the Go/No-Go scoring weights:
| If it asks | You might say |
|---|---|
| What belongs in the Money View tab? | Editable take-home pay ($6,500), expenses ($3,435), 47.2% savings rate sparkline, portfolio summary ($65,700), and founder runway projection. |
| How should cash savings versus retirement accounts be treated? | Exclude the $625/month Roth IRA contribution from studio self-funding; use the $2,440/month cash savings and $28,000 cash balance. |
| What belongs in the Studio View tab? | IP pipeline tracker, three budget scenarios ($85K/mo burn), 10/10 prototype checklist, market comps, and a 7-item crowdfunding kit. |
| How should the Bridge section connect both tabs? | Keep it visible on both tabs showing target start date, self-fund months, and when Kickstarter or publisher cash runs short. |
| How should the Go/No-Go decision score work? | Weight IP Availability (25%), Financial Readiness (25%), Market Viability (20%), Prototypes (15%), and Crowdfunding (15%) with blockers below 50. |
Read the plan
Before approving the build, check the agent’s plan for these four details:
- Money View and retirement separation (
src/components/money/*.jsx,src/data/defaults.js, React with Vite): pre-fills $6,500 take-home pay, $3,435 monthly expenses, $3,065 total savings (47.2% savings rate), $28,000 cash savings balance, and a $65,700 investment portfolio ($45,000 401k, $12,500 Roth IRA at the 2026 IRS $7,500/year limit = $625/month, $8,200 brokerage), and counts only the $2,440/month non-retirement cash savings toward studio self-funding. - Studio View and realistic scenario checks (
src/components/studio/*.jsx): tracks IP pipeline stages (Research= 20 up toSigned= 100), three budget scenarios against an editable $85,000/month studio burn (Self-funded $250K, Kickstarter $800K goal = $736K net after 8% platform and payment fees arriving in month 3 plus $50K personal capital, and Publisher $2M advance across months 1, 12, 18, and 24), all 10 prototypes complete, 3 placeholder market comps ($30M, $50M, $5M), and a 7-item crowdfunding checklist (1/7 done = 14%) with expandable landing page copy, feature matrix, and trailer beat sheet templates. - Always-visible Bridge and Timeline (
src/components/bridge/*.jsx): stays visible across both tabs, projectingsavings at target date = current cash + (monthly cash savings * months)divided bystudio burn rate(e.g., 18 months at $2,440/mo adds to $28,000 for $71,920, or ~0.8 months at $85K/mo burn) and plotting a multi-scenario timeline withchart.js@4andreact-chartjs-2@5(callingChart.register()). - Five-signal Go/No-Go integrator (
src/components/decision/GoNoGo.jsx): computes the weighted composite (IP25%,Market20%,Financial25%,Prototypes15%,Crowdfunding15%), recommendsGO(80+),CONDITIONAL GO(50-79), orNOT YET(under 50), lists every signal under 50 as an explicit blocker, and persists all edits inlocalStorageunder"lora-command-center"with a"Reset to Defaults"button.
If the plan counts retirement contributions (401k or Roth IRA) as spendable studio cash or caches the Go/No-Go score instead of deriving it live from state, steer it before approving:
Count only the $2,440/month non-retirement cash savings toward studio self-fund runway, and derive the Go/No-Go score live whenever any checklist or financial input changes.Once the plan covers all four points, ask the agent to split it into chunks (as shown in the callout above) or approve it to build. After testing tab switching, editing income, checking off crowdfunding items, and reloading to confirm localStorage persistence, ask your agent to save a Git checkpoint.
You do not need the actual output files from previous lessons to build the Command Center — defaults.js pre-fills realistic sample figures so every chart and score works immediately. Once it runs, swap in your own numbers from earlier lessons after going through the data check.
What you get
After the AI tool generates the application, the project folder structure looks like this:
REFERENCE PROJECT LAYOUT 20-command-center/ generated React dashboard folder tree open reference hide reference Reference example of the folder layout your agent creates for the Money View, Studio View, Bridge, and Go/No-Go sections.
20-command-center/ package.json index.html src/ App.jsx components/ TabBar.jsx money/ SavingsTracker.jsx PortfolioSummary.jsx FounderRunway.jsx studio/ IPPipeline.jsx BudgetScenarios.jsx PrototypeChecklist.jsx MarketComps.jsx CrowdfundingKit.jsx bridge/ BridgeCalculation.jsx Timeline.jsx decision/ GoNoGo.jsx SignalCard.jsx data/ defaults.js styles/ dashboard.cssFire it up
Ask your agent to install what is needed, start the local server, and open the dashboard:
Install the packages, start the local server, and open Lora's Command Center in my browser.Or run it from a terminal:
cd ~/retro-remake/20-command-centernpm installnpm run devOpen the dev server URL. You should see the Money View tab active with your savings tracker, portfolio summary, and founder runway projection. The bridge calculation at the bottom shows the connection between your savings and the studio start date. Switch to Studio View to see IP pipeline, budget scenarios, prototype checklist, market comps, crowdfunding kit, and the go/no-go decision integrator.
If something is off
| Problem | Follow-up prompt |
|---|---|
| Changes disappear on reload | My edits reset to the default values whenever I refresh the browser. Save every change automatically in the browser and reload my saved numbers when the dashboard opens, while keeping a Reset to Defaults button. |
| Charts not rendering on tab switch | The charts on the Studio View tab look blank or squished until I resize my browser window. Make sure every chart redraws at full size whenever I switch between Money View and Studio View. |
| Go/No-Go score not updating | Checking off crowdfunding items or changing the IP status does not change the Go/No-Go composite score. Recalculate all five signal scores, the weighted total, and the blockers list live whenever any input changes. |
| Bridge calculation shows NaN | The founder runway projection displays NaN months when I edit my income or studio burn rate. Treat every financial input as a number and guard against empty inputs or a zero burn rate. |
| Tabs don’t switch | Clicking Money View or Studio View in the header does not switch the main panel. Make the tab bar update the active view while keeping the Bridge section and Go/No-Go summary visible. |
Deep dive
Two domains, one decision
The Command Center does something unusual: it puts personal finance and business planning in the same interface. Most dashboard tools are single-domain. A budgeting app tracks your money. Jira tracks your project. Pitch decks track your market. Nobody puts them together because they serve different audiences.
But you are not a corporation with departments. You are one person. Your savings rate directly determines when you can start the studio. Your studio burn rate directly determines how much you need saved. The prototype completion directly determines whether you have something to show investors. These are not separate concerns. They are the same concern viewed from different angles.
The bridge calculation makes this explicit. It takes a number from the Money View (savings rate) and a number from the Studio View (burn rate) and produces the answer to the question you actually care about: when can I start?
The go/no-go integrator is not a magic 8-ball
The composite score is a weighted average of five signals. It is not artificial intelligence. It is arithmetic. An IP score of 20 drags the composite down. A crowdfunding readiness score of 14 drags it down further. Prototype completeness at 100% pulls it up. The weights reflect judgment calls about what matters most — IP and financial readiness are weighted higher because they are hard blockers.
The value is not in the number. The value is in the blockers list. When the dashboard says “CONDITIONAL GO — address IP Availability (20/100) and Crowdfunding Readiness (14/100),” it is telling you exactly what to work on next. Not in vague terms. In specific, scored terms with a clear path to improvement.
🔍Why localStorage instead of a backendclick to expand
The Command Center stores everything in the browser’s localStorage. No server, no database, no authentication. This is a deliberate choice for three reasons:
Privacy. This dashboard contains your real financial data — income, savings, investment balances. That data should not leave your machine unless you choose to share it. localStorage keeps it in your browser and nowhere else.
Simplicity. Adding a backend means a server, a database, deployment, and authentication. For a personal dashboard used by one person, that is overhead with no benefit. The data model fits comfortably in localStorage (browsers allow up to 5 MiB per site; your data is under 100KB).
Portability. Export your state as a JSON file (add this customization if you want). Import it on another machine. Back it up to a USB drive. You own the data in a format you can read.
The tradeoff: if you clear your browser data, the dashboard resets. The “Reset to Defaults” button does this intentionally. If you want persistence beyond the browser, the customization section below covers adding a JSON export/import feature.
Customize it
Add JSON export and import
Back up your dashboard data:
Add Export Data and Import Data buttons in the footer to download the full dashboard state as command-center-backup-YYYY-MM-DD.json and restore it from a file upload after confirmation.Add a monthly review mode
Track your progress over time:
Add a Save Monthly Snapshot footer button that records timestamped progress snapshots and a History tab plotting savings rate, portfolio value, Go/No-Go score, and crowdfunding readiness over time.Add a scenario comparison calculator
Model different life decisions:
Add a What If panel to Money View comparing baseline runway against cheaper rent, extra freelance income, maxing out the 401k, or delaying studio launch by 6 months.Try it yourself
- Walk through the plan-mode conversation above and let your agent build the dashboard.
- Ask your agent to start the dashboard (or run
npm install && npm run dev) and open the Money View. Look at your savings rate. Look at your portfolio. Look at the founder runway number. That number — the self-fund months — is the most important number on the entire dashboard. - Switch to the Studio View. All 10 prototypes should show complete. The crowdfunding readiness score should be low (14%) because you have a demo but no marketing materials. Look at the go/no-go score. It should say CONDITIONAL GO with clear blockers.
- Edit your monthly income upward by $1,000 (maybe you picked up freelance consulting). Watch the savings rate recalculate. Watch the bridge calculation update. Watch the founder runway extend. Every dollar you save is a day closer to starting.
- Check off “Trailer beat sheet” and “Landing page copy” in the crowdfunding kit. Watch the readiness score jump. Watch the go/no-go composite score tick upward. This is progress made visible.
- Go to the bridge calculation. Adjust the target start date. See how much you need saved by then. See how many months of self-funding that buys. Now try different funding scenarios — does Kickstarter change the equation? Does a publisher deal make the start date irrelevant?
- Close the browser tab. Reopen it. Everything should still be there. localStorage is doing its job.
- Look at the go/no-go blockers list. That list is your to-do list. Not in the abstract. In specific, scored, prioritized terms.
Key takeaways
- Personal finance and startup planning are the same problem. Your savings rate is your studio’s pre-funding runway. Separating them is a mental convenience that hides the real timeline.
- The bridge calculation is the most important number. Not the portfolio value. Not the prototype count. The bridge: “At your savings rate and the studio’s burn rate, you can self-fund for X months starting [date].” That is the number that determines when you start.
- The go/no-go integrator turns scattered signals into a decision. Five independent metrics combined into one score with explicit blockers. You stop wondering “am I ready?” and start looking at “what specifically is blocking me?”
- Crowdfunding readiness is often the biggest gap. You built the prototype. You did the market research. You modeled the finances. But the trailer, landing page, press kit, and community channels take real work, and they are easy to underestimate.
- localStorage is enough for a personal dashboard. No server, no database, no auth. Your financial data stays on your machine. Export to JSON for backup. Import on another machine. You own it.
What’s next
Look at what you have. A market tracker that proves cult revivals are profitable. A financial model that shows what each funding path looks like. A mechanics specification that documents every system in the game. Ten working prototypes culminating in a playable demo. And now a dashboard that connects your personal financial life to your studio dream with a single number: when can you start?
That is not a lesson plan. That is a business plan with working software behind it.
The next step is yours. The Command Center will tell you when you are ready. The blockers list will tell you what to work on. The bridge calculation will tell you when the numbers line up. And when they do — when the go/no-go score hits 80 and the recommendation says GO — you will know it is not a gut feeling. It is data.
Rayne did not wait for permission. Neither should you. But she also did not charge in blind. She assessed the situation, picked her moment, and struck. The Command Center is your aura vision. Use it.