Design Knowledge Base
Community-maintained principles reviewed before publication and retrieved as Agent design constraints.
Progressive 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 Patternsaudit-log / evidenceAudit Log Evidence Chain
An audit log UI should support investigation, filtering, details, JSON/CSV export, and evidence explanation rather than only showing a chronological activity stream.
The value of an audit log is traceability and proof. Each record should answer who did what, when, from where, to which object, with what result, and where supporting evidence lives.95%Design Systems Page Patternspermissions / rolesPermission Matrix Inheritance Preview
Permission interfaces must explain who gets which capability through which path, and preview inheritance, overrides, dangerous permissions, and bulk-change impact before saving.
A permission matrix is not an ordinary settings table. It joins security, organizational structure, resource scope, and audit responsibility; users must distinguish direct grants, role grants, team or group inheritance, defaults, external guests, and explicit denies.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 Patternsaudit-log / timelineAudit Log Timeline
Audit Log Timeline turns a frequent interface judgment into an executable constraint before generation.
Audit logs need to answer who, when, what object, what action, and what impact.86%Design Systems Page Patternsadmin / list-detailAdmin List Detail Pattern
Admin List Detail Pattern turns a frequent interface judgment into an executable constraint before generation.
Admin work often moves from filtered lists into detail handling, and both views must share state and action semantics.86%