Code Dashboard

The Code Dashboard is your personal code health check — a live panel that shows you the one thing most worth fixing in your project right now, and makes it a single click to ask Claude for help.

It replaces the “Teach me something” placeholder screen once you've finished onboarding.

What you're looking at

The dashboard scans your project across four areas:

• Working Hygiene — uncommitted files, building on main, large files in git
• Code Shape — files that have grown so large Claude struggles to read them
• Project Health — npm vulnerabilities, outdated packages, missing .gitignore
• Cleanup Queue — console logs, stale branches

At the top, a priority banner surfaces the single most important issue in plain English. Everything else stacks below it.

The three states

All clear.“Nothing urgent to fix right now.” Your project is in good shape. Keep building.

Housekeeping only.“Nothing urgent. Ship when you're ready.” You've got some low-priority items — console logs, a stale branch — but nothing blocking. They show up in a “When you get a chance” section so they're easy to find later without getting in your way now.

Urgent issues.The priority banner appears with one sentence describing the problem and an “Ask Claude →” button. Clicking it drops a pre-written claude "..." command in your terminal, already loaded with real data from your project.

For example, if you have a god file:

claude "My file src/handlers/setup-flow.ts is 847 lines. Help me break it into smaller modules."

Or for uncommitted changes before deploying:

claude "I have 12 uncommitted files. Walk me through committing them cleanly before I deploy."

You don't write the prompt. The dashboard reads your project and writes it for you.

Why some checks are locked

The dashboard unlocks checks progressively as you complete lessons. If you haven't learned about git branching yet, the branching check won't surface — there's no point flagging something you don't have context for.

Hover any locked check to see which lesson unlocks it. Once you complete the lesson, the check activates and the dashboard rescans automatically.

Where it goes during a lesson

When you start a lesson, the dashboard steps aside so it's not competing for your attention. Once you finish, it comes back with fresh data — sometimes showing you a check that just unlocked.

Refreshing

Hit the ↻ button in the top-right corner to rescan anytime. Takes a few seconds. You'll see rotating messages while it works (“Checking your branches…”, “Scanning for large files…”).

Why the tooltips exist

Every check has a tooltip explaining why it matters — not to lecture you, but so you're not staring at a warning that means nothing to you. Each one includes a “Learn more →” link to the relevant lesson if you want to go deeper.

The goal is a dashboard that feels like a smart friend glancing at your project and saying “hey, this one thing is worth fixing before you ship” — not a wall of red flags.