Knowledge RAG
Submit principleDesign Knowledge Base
Community-maintained principles reviewed before publication and retrieved as Agent design constraints.
4 published principles / 192 in library
Design Systems Page Patternstokens / settings
Design System Token Settings
Token settings pages must show semantics, aliases, modes, affected components, version diffs, and release risk together, not only color and number inputs.
Design tokens are design decisions that move across design tools, code platforms, and component libraries. A settings page does not only edit values; it explains how a value is referenced, how it changes by mode, and which components and versions it affects.96%Design Systems Page Patternspublic-service / trustPublic-Service Trust Rails and Recovery
Public-service interfaces must make official identity, responsible organization, legal links, task title, form semantics, error summaries, and recovery paths into verifiable page structure instead of merely applying blue-white civic styling.
Trust in public services comes from an inspectable responsibility chain and recoverable task flow: users need to know whether the service is official, who is responsible, whether the connection is safe, why information is needed, how to fix mistakes, and where privacy/accessibility/oversight information lives.95%Design Systems Page Patternsgovernance / reviewComponent Governance Review Flow
Component Governance Review Flow turns a frequent interface judgment into an executable constraint before generation.
A design system needs to record why components are added, how they are reused, and when they are deprecated, not just list components.86%Design Systems Page Patternstokens / design-systemDesign Token Governance
Tokens should express roles and constraints, not merely store colors, type, and spacing.
Maintainable tokens need names, scope, defaults, and prohibited uses so humans and agents can share them.82%