generate-dashboardlisted

# Generate dashboard Turn a described need into a new dashboard page for *this* project — added to the dashboard's own navigation, rendered by the dashboard's own components, so it looks and behaves like it shipped with the framework, not like a plugin bolted on. ## When to use Whenever the user asks (from the Customize page, or directly in chat) to **add a dashboard** — "I want a dashboard that shows my architecture", "add a page tracking API endpoint coverage", "show me a dashboard of open security findings" — or when `propose-customizations` proposed a dashboard candidate the user picked. ## Method ### 1. Never generate raw markup — only the declarative block vocabulary The dashboard renders a custom page from a **JSON block spec**, using the exact same components the built-in Board uses (`kpiCard`, `ocard`, `bars`, `donut`, a table builder, `mdLite` for markdown — see `dashboard/public/app.js`). This is not a stylistic preference: it is the mechanism that makes the result correct. - Every block type is styled entirely through the active design's CSS custom properties (`--signal`, `--surface`, `--line`, `--s-done`, …). Nothing in a block spec ever sets a literal color, font, radius, or shadow. - Because of that, a dashboard generated under one design (say, the default Spectral Console) renders correctly, unmodified, under every other shipped design (Orbit, Control Room, Obsidian Ops, Neon Command, Mission Control) — including any the user switches to **after