Design Knowledge Base
Community-maintained principles reviewed before publication and retrieved as Agent design constraints.
Dashboard KPI Alert Triage Contract
Operations dashboards should organize KPIs, alerts, thresholds, owners, evidence, and next actions into a scannable triage system instead of an equal-weight wall of charts.
A good dashboard first answers whether action is needed, severity, blast radius, ownership, and evidence path; charts are evidence layers that support triage.95%Data Visualizationdata-transform / provenanceVisualization Transform Provenance
Charts must record filter, aggregate, bin, timeUnit, join, missing-value, and sorting logic; otherwise users cannot audit why the chart looks the way it does.
Data-visualization trust comes not only from graphics but also from an explainable transform chain. Every aggregation, filter, and derived field should be traceable.95%Data Visualizationchart-choice / data-relationshipChart Question Before Chart Type
Define the data relationship users need to judge before choosing chart type and frontend library; do not start from wanting a pretty chart.
Good charts are not visual style collections. They are decisions that match data structure, user question, and visual encoding.94%Data Visualizationdashboard / metric-cardDashboard Metric Card Contract
A metric card is not decorative big-number UI; each card needs metric definition, time range, comparison baseline, unit, data state, and next action.
A dashboard first screen should answer what users should judge now, not compress all data into an equal chart wall. Metric cards are decision entry points and need semantics plus evidence.94%Design Systems Page Patternsanalytics / drilldownAnalytics Drilldown Workflow
Analytics Drilldown Workflow turns a frequent interface judgment into an executable constraint before generation.
Analytics interfaces should move from anomalies and questions toward causes, not just show chart collections.86%Visual Foundationsdashboard / kpiDashboard KPI Triage
Dashboard KPI Triage turns a frequent interface judgment into an executable constraint before generation.
Metric cards are not number displays; they are triage entry points for operations.86%Visual Foundationscharts / dashboardReadable Dashboard Charts
Readable Dashboard Charts turns a frequent interface judgment into an executable constraint before generation.
Operational charts are often scanned quickly; small-chart readability matters more than expressive form.84%Design Systems Page Patternsdashboard / alertsDashboard Hierarchy and Alerts
Dashboards should show status overview first, then anomalies, trends, details, and action entries.
More metrics are not better; the priority is helping users decide whether action is needed.82%Visual Foundationsdensity / dashboardInformation Density Control
High density is not clutter, and low density is not automatically premium; density must match task frequency and speed.
Operational tools need scannable density while marketing pages need narrative pacing; mixing them causes mismatch.82%