Skip to content

xinetzone/SpecWeave / .agents/skills/dashboard-page

Dashboard Page

Unverified

Use 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.

references/output-layout.md

View on GitHub
# Output Layout Reference

Use this reference when creating or organizing dashboard deliverables.

## One Dashboard, One Folder

Every dashboard should live in its own folder. The folder is the deliverable bundle and should be named with a readable, filesystem-safe dashboard slug.

Recommended layout:

```text
dashboard-slug/
  index.html
  dashboard_data.json
  dashboard.py
  dashboard_runtime.js
  echarts.min.js
  data/
    source-file.xlsx
    snapshots/
      2026-06-25.json
      2026-06-26.jsonl
```

For simple dashboards, source data may sit beside `dashboard.py`, but recurring automation outputs should live under `data/snapshots/`. Do not scatter dashboard outputs in the workspace root.

## File Roles

- `index.html`: final single-file dashboard opened by the user.
- `dashboard_data.json`: generated payload for review/debugging and reproducibility.
- `dashboard.py`: copied and adapted generator from `assets/dashboard_template.py`.
- `dashboard_runtime.js`: copied shared browser runtime used during generation and inlined into `index.html`.
- `echarts.min.js`: copied chart runtime used during generation and inlined into `index.html`.
- `data/`: reviewed source data or small local copies needed to reproduce the dashboard.
- `data/snapshots/`: immutable daily source snapshots produced by automation.

## Naming

Use lowercase, hyphenated or underscore-separated slugs. Prefer concrete names such as `daily-revenue-dashboard/`, `finance-command-center/`, or `customer-health-dashboard/`.

Inside the folder, prefer stable filenames: `index.html`, `dashboard_data.json`, and `dashboard.py`. The dashboard title belongs inside the HTML, not in every filename.

## Trae Rendering Contract

The generated `index.html` must start with `<!-- Generated by Trae Work -->` on line 1. The final assistant response must include the `index.html` path with a `computer://` prefix so Trae can render the dashboard.

Keep the visible dashboard self-contained. `index.html` should inline the copied ECharts and dashboard runtime scripts; any supporting data or automation files must stay inside the dashboard folder.

## Validation

Run validation against the folder's final HTML:

```bash
node <SKILL_ROOT>/scripts/validate-echarts-dashboard.mjs dashboard-slug/index.html
```
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: 471kUpdated Claude CodeCodexVerifiedInstall
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: 471kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall