xinetzone/SpecWeave / .agents/skills/dashboard-page
Dashboard Page
UnverifiedUse when the user wants to create a stable local/offline ECharts dashboard with KPI panels, time controls, auditable source modals, and optional daily data snapshots produced by automations.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 8.2 KB |
| assets/dashboard_runtime.js | script | 8.6 KB |
| assets/dashboard_template.py | script | 42.7 KB |
| assets/echarts.min.js | script | 1006.7 KB |
| references/dashboard-structure.md | markdown | 2.5 KB |
| references/data-and-automation.md | markdown | 3.2 KB |
| references/output-layout.md | markdown | 2.2 KB |
| references/visual-interactions.md | markdown | 7.3 KB |
| scripts/validate-echarts-dashboard.mjs | script | 3.0 KB |
references/dashboard-structure.md
View on GitHub# Dashboard Structure Reference
Use this reference when planning or modifying the dashboard shell, filters, panel model, or rendered markup.
## Operating Shape
The rendered output should behave like an internal analytics dashboard:
- a sticky top bar with title, data freshness, and primary time controls;
- a constrained but wide workspace around 1180px to 1440px;
- compact KPI tiles near the top, preferably grouped in one outlined strip with internal dividers;
- charts and tables arranged in responsive grids;
- clear panel headings, units, source context, and action menus;
- chart and table data surfaces rendered as thin line-framed modules rather than heavy filled cards;
- no marketing hero, slide canvas, narrative document rail, or card-feed abstractions.
The first viewport should show the dashboard itself, not an explanation of the dashboard.
## Filter Model
The default dashboard must include time selection:
- `range` presets such as 7D, 30D, MTD, QTD, YTD, and All;
- optional explicit start/end dates when the data warrants it;
- visible date coverage and latest refresh timestamp.
Filter controls should operate on a precomputed payload when possible. If a dashboard is too large for full client-side filtering, generate a bounded payload and make the truncation explicit in a visible freshness/source note.
## Block Model
Compose the dashboard with four block kinds:
- `kpi`: compact metric tiles with label, value, unit, delta, comparison basis, sparkline rows, and source context.
- `chart`: ECharts panels rendered as `<section class="dashboard-panel chart-panel">` with panel actions and optional alternate chart types.
- `table`: evidence tables rendered as `<section class="dashboard-panel table-panel">` with stable default sorting.
- `note`: source notes, freshness warnings, caveats, or automation status blocks.
Every block should have a stable `id`. Chart blocks should include chart container id, title, subtitle, unit, allowed chart types, and source key. Table blocks should include table HTML and source context.
## Template Layers
Keep generation layers separate:
- `build_dashboard_blocks(payload)` composes `kpi`, `chart`, `table`, and `note` blocks from analyzed data.
- `render_kpi_block()`, `render_chart_block()`, `render_table_block()`, `render_note_block()`, and `render_dashboard_blocks()` emit the established dashboard markup.
- `build_html(payload)` reads inline assets, calls `build_dashboard_blocks(payload)`, and wraps the final HTML shell.
Dashboard block assembly should not live inside `build_html(payload)`.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |