Design Knowledge Base
Community-maintained principles reviewed before publication and retrieved as Agent design constraints.
Map POI Icon Attribution Boundaries
POI icon sets such as Maki solve map symbols, not map data, tiles, style, basemap providers, place labels, or interaction attribution.
Map symbols are one layer of visual encoding. Agents must govern icon set, sprite, map style, geodata, tile provider, legend, and accessible labels separately instead of treating icon license as map license.95%Data Visualizationmaps / geospatialMap Data Attribution and Alternatives
Map interfaces must separately record runtime library, tiles, styles, glyphs, sprites, geodata, and provider attribution, while providing list/table alternatives and keyboard-reachable paths.
A map is not a background image. It combines complex data visualization, interactive controls, and licensed materials; users must understand location, scope, selected object, data source, update time, and alternate access paths.95%Data Visualizationaccessibility / chartsAccessible Chart Alternatives
Charts need takeaway titles, text summaries, redundant encodings, and data-table alternatives; Canvas or SVG alone is not automatically accessible.
Data visualization is non-text and often interactive content. It must give equivalent conclusions and data paths to people who cannot see the chart, distinguish colors, use a mouse, or read it at default size.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%