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 Visualizationmap / poi
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%