Skill LibraryPrompt Skill1 DesignsTop Views

Dashboard KPI Alert Triage

Prioritize KPIs, alert severity, thresholds, owners, evidence paths, acknowledge/mute/resolved states, and next actions for operations dashboards, monitoring consoles, status pages, and admin analytics.

Skill Uses0

Recorded selections across prompt workflows.

Public Designs1

Ranked by views, then community favorites.

Prompt Lines10

Reusable instruction lines for generation.

Author@Interface Lab

Data Visualization

Skill Directive

Description

TagsData Visualization

Skill Prompt

- Use for dashboard KPI hierarchy, alert triage, status dashboards, incident boards, monitoring consoles, admin analytics, metric cards, severity states, thresholds, and turning raw metrics into actionable React/CSS interfaces.
- Write the triage question first: what changed, how bad is it, where is it, who owns it, and what should happen next; do not arrange widgets or add charts first.
- Classify metrics into four groups: primary KPIs answer the triage question, diagnostic metrics explain why change happened, context metrics compare time/region/segment, and decorative metrics are removed or demoted.
- The top row contains only 3-5 decision KPIs; each KPI includes value, unit, period, baseline, delta/trend, threshold, freshness, severity label, explanation, and evidence/drill-down entry.
- Severity cannot rely only on color: critical/warning/info/success/neutral states use text labels, icons or shapes, borders/semantic color, trend, and helper copy; record whether thresholds come from SLA, percentile, anomaly, manual, or static rules.
- The alert rail is sorted by severity, recency, blast radius, owner, and acknowledged/resolved/muted state; critical alerts need owner, next action, escalation, and evidence link.
- Acknowledge, mute, and resolve do not hide alerts: acknowledged alerts are visually settled but visible, muted alerts show reason and expiry, and resolved alerts move to history/audit trail.
- Layout contract: page title states system and time scope, top area shows critical state, side or main column carries alert rail, analysis region only explains the top signal with trend/table/map/logs, and detail drawer/route carries evidence and actions.
- Frontend implementation uses tabular numbers, stable card/grid dimensions, URL-reproducible filters/time range, data freshness/timezone, semantic CSS variables, and accessible names that include metric/value/unit/state.
- QA covers desktop scan order, mobile alert-first ordering, sticky headers, keyboard focus, color-independent state, loading/empty/error/stale/partial data, no chart clipping, and mobile labels without overflow. Sources: NN/g dashboards, Grafana alerting, Carbon status indicators/notifications, and Atlassian badge/lozenge/flag.

Public directive summary shown; Pro unlocks the full prompt.

Layout Info

Designs below are ordered by views. Top items use live previews; the rest stay fast thumbnail cards.

Unlock Pro All Skills

Dashboard KPI Alert Triage

More pages using Dashboard KPI Alert Triage