Knowledge RAG
Submit principleDesign Knowledge Base
Community-maintained principles reviewed before publication and retrieved as Agent design constraints.
2 published principles / 192 in library
Design Systems Page Patternspublic-service / trust
Public-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 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%