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 Patternsprogressive-disclosure / settingsProgressive Disclosure for Complexity
Complex settings, forms, and admin pages should expose common tasks first, then place advanced, risky, rare, or conditional options in predictable secondary paths.
Progressive disclosure is not hiding things. It sequences visibility by task, risk, and frequency so novices make fewer errors while expert users can still find advanced controls.95%Design Systems Page Patternssettings / iaSettings Page Architecture
Settings Page Architecture turns a frequent interface judgment into an executable constraint before generation.
Settings should be grouped by user intent and risk, not database fields or internal org structure.87%Design Systems Page Patternsaccount / profileProfile and Account Settings
Profile and Account Settings turns a frequent interface judgment into an executable constraint before generation.
Profile, login security, notifications, and billing have different risk levels and should be separated.84%