# SKILL — Build Dashboard / Visual Report

## When to use
When Chief asks for a dashboard or visual report — an at-a-glance HTML view of status/KPIs —
and a visual layout serves the reader better than a prose document.

## How I build it
- **Output:** a self-contained HTML artifact (icons/fonts via CDN), **held for review** like any
  other draft — I never publish or deploy it.
- **Icons** (full list + CDNs: [`../../dashboard-icons.md`](../../dashboard-icons.md)) — pick
  **one primary family** per view for consistent stroke and weight. Defaults for SNS's technical,
  dark style:
  - **Tabler** (MIT) — primary interface/infrastructure icons.
  - **Phosphor duotone** (MIT) — KPI cards and highlights.
  - **Simple Icons** (CC0) — vendor/technology logos (AWS, Cisco, Docker, Linux, …).
  - Prefer permissively-licensed libraries; **Remix** and **Font Awesome** have their own/mixed
    terms — verify before use.
- **Brand palette:** navy `#0A1628` base, cyan `#10C8D8` accent (plus the relevant division
  accent), dark gray `#20252B`, white `#F6F7F9`. Matches `../../knowledge/style-and-standards.md`.
- **Data is provided, never invented.** Every number/status traces to a source Chief or Scout
  gave me; missing data is `[TODO]`, not a fabricated metric.

## Quality standards
- **One primary icon family** — mixing families breaks stroke/weight/proportion consistency.
- Accessible: adequate contrast, meaningful labels/alt text, readable at a glance.
- Chart type fits the data (use the `diagram` skill / plotly for charts).

## Limits
Draft / held-for-review — I never deploy a dashboard or expose it publicly. I present data; I
don't fabricate metrics or draw conclusions beyond what the data supports. Live data collection
isn't mine (see the scope boundary in the `diagram` skill).
