Whether a dashboard answers its question in one glance — the metric that matters winning the top-left, signal over decoration, and density chosen, not accidental.
Free & open · no signup · read-only — it ends by asking · nothing leaves your machine
You are working inside this repo. Mission: judge whether each dashboard and data-dense screen answers its core question at a glance — or forces the reader to hunt, scroll, and interpret before they learn anything.
Read-only pass. Walk the dashboards in the running app or read their layouts, widgets, and queries; your only write is the report file.
Phase 2 sweeps the codebase through every one of these, citing file and line for each finding.
does the primary question resolve in the first few seconds and the top-left, or is it buried among peers
widget prominence matches importance; the vanity metric outsizing the one people act on
every tile pays rent in decisions; the widget nobody uses taking prime space
dense where scanning rewards it (ops, tables), airy where focus does; density chosen, not accidental
consistent units, time ranges, and scales across tiles so numbers can be compared, not just displayed
a value with its trend, target, or baseline, versus a bare figure with no "good or bad"
layout guiding the eye in a deliberate order; the grid that reads as noise with no path
partial-data, still-loading, and no-data states; the dashboard that is useless until every query returns
One structured report at the repo root — or in reports/, if you keep one — the same shape every time, ready for a teammate — or the optional Studio — to act on.
Every Goal Prompt follows the same four steps, so results are consistent and repeatable — no matter which one you run.
List the dashboards and dense screens (overviews, admin panels, reports, big tables).
Cite the screen and widget for every finding.
Rank by decisions-per-screen.
Create DASHBOARD.md at repo root.
Copy it and paste it into your agent inside the repo you want checked.
Install the goal plugin once — two commands — then just type /goal:dashboard-density.
/plugin marketplace add GhostlyGawd/goal-prompts/plugin install goal@goal-promptsOr install only this Goal Prompt as /goal-dashboard-density:
curl -fsSL https://goal-prompts.vercel.app/install | BRIEF=132 shLet an agent fetch it mid-conversation, or pull the raw Goal Prompt by URL.
https://goal-prompts.vercel.app/raw/132.mdNothing hidden — this is the whole Goal Prompt, verbatim. Read it in a minute, edit it, or copy it as-is.
# Goal: Dashboard & Density Audit You are working inside this repo. Mission: judge whether each dashboard and data-dense screen answers its core question at a glance — or forces the reader to hunt, scroll, and interpret before they learn anything. Read-only pass. Walk the dashboards in the running app or read their layouts, widgets, and queries; your only write is the report file. ## Phase 1 — Frame each dashboard - List the dashboards and dense screens (overviews, admin panels, reports, big tables). - For each, write the one question it exists to answer and who reads it, before auditing — so the audit can disagree. - Inventory the widgets, the reading order, and what sits above the fold. ## Phase 2 — Audit through 8 lenses Cite the screen and widget for every finding. 1. **One-glance answer** — does the primary question resolve in the first few seconds and the top-left, or is it buried among peers 2. **Signal ranking** — widget prominence matches importance; the vanity metric outsizing the one people act on 3. **Earns its place** — every tile pays rent in decisions; the widget nobody uses taking prime space 4. **Density fit** — dense where scanning rewards it (ops, tables), airy where focus does; density chosen, not accidental 5. **Comparability** — consistent units, time ranges, and scales across tiles so numbers can be compared, not just displayed 6. **Context for numbers** — a value with its trend, target, or baseline, versus a bare figure with no "good or bad" 7. **Scan pattern** — layout guiding the eye in a deliberate order; the grid that reads as noise with no path 8. **Load & empty** — partial-data, still-loading, and no-data states; the dashboard that is useless until every query returns ## Phase 3 — Curate - Rank by decisions-per-screen: fixing the primary question's visibility beats rearranging secondary tiles. - Separate "wrong priority", "over/under-dense", and "no context"; fix priority first. - For each, name the screen and the move — promote, demote, merge, or cut. ## Phase 4 — Report Create `DASHBOARD.md` at repo root: 1. **Dashboard table** — screen · the question it answers · read in one glance? · what wins the eye 2. **Findings** — each: lens · screen/widget · what the reader cannot learn fast · the fix 3. **Cut list** — the tiles that do not earn their space 4. **The one rule** — the density and layout convention this codebase should adopt Start the report with today's date. If `DASHBOARD.md` already exists from a previous run, read it first and lead with what changed since. ## Rules - Every finding names the screen and widget, with the query or data behind it where it matters - A number without a baseline is decoration; context is what makes it a signal - No dashboards in this repo? Say so in a one-paragraph null report and stop — a null result is a valid finding. - If a `reports/` directory exists at the repo root, write the report there instead of the root. - Before asking, present the top findings as a ranked list in plain words - Report only — end by asking which dashboard fixes to make
reports/ directory exists at the repo root, write the report there instead of the root.Where the eye actually goes versus where it should — focal points, size and weight and contrast doing real work, and the screens where everything shouts at once.
The type scale, or the lack of one — sizes, weights, line lengths and heights, font loading, and every place text is asked to do a job at the wrong size.
The palette as it actually ships — every hex in the codebase, contrast ratios computed, semantic drift named, and whether dark mode is a theme or an apology.
The spacing scale nobody wrote down — margins and paddings inventoried, grid discipline checked, alignment breaks found, and density judged screen by screen.
Runs inside these playbooks — curated sequences you can launch with one paste: