insight-dashboard
Insight Dashboard
Build a data view that helps the reader answer a recurring question or choose an action. Make the useful comparison visible in the initial view, then provide a clear path to the details that explain it. Let data and the reader's task determine the layout.
This skill decides what the view compares, its metrics and denominators, how selections change the results, and its explanatory text. frontend-design builds and reviews the interface that carries those decisions in the project's UI stack: components, layout, states, responsive behavior, and accessibility. Use both when building or redesigning a view; an interface-only change that alters no value, ranking, or sentence the reader sees needs only frontend-design.
Preserve the project's data model, terminology, and requested medium. Inspect supplied data before choosing claims. Use authorized real results; mark development fixtures as synthetic. If a missing input prevents the main comparison, identify that input and build only the supported views. Review requests return findings rather than changing the application.
Choose the first useful view
- Communicate a finding: lead with the supported finding and decisive comparison, then the factors, exceptions, and observations that explain it. Add exploration for a concrete follow-up question.
- Investigate: start with a meaningful baseline, visible selections, and enough context to choose a population. Link overview, breakdown, and record detail so the reader can narrow a question.
- Monitor: prioritize affected services, severity, freshness, and the next operational action. Keep severity separate from investigation status; distinguish unavailable telemetry from healthy service.
- Review periodically: connect previous actions to current measures and the next proposed action. Associate human commentary with its period and evidence. Add explanations where judgment matters rather than requiring a comment on every card.
- Answer a small recurring question: show the answer and the useful next link. A current-version page can be complete without a KPI grid or trend chart.
- Rank candidates: rank only rows measured under the same comparison, show each row's comparability, and keep the ranking claim true under the reader's filters. The ranking pattern covers ties, missing cells, and metrics with opposite directions.