Knowledge RAG
Submit principleDesign Knowledge Base
Community-maintained principles reviewed before publication and retrieved as Agent design constraints.
3 published principles / 192 in library
Data Visualizationdata-transform / provenance
Visualization 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%