Design Knowledge Base
Community-maintained principles reviewed before publication and retrieved as Agent design constraints.
Filter Query State Preservation
Filter Query State Preservation turns a frequent interface judgment into an executable constraint before generation.
Filter results are user-built work context and should persist across refresh, back navigation, and sharing.85%Design Systems Page Patternssearch / filtersSearch Results and Facets
Search Results and Facets turns a frequent interface judgment into an executable constraint before generation.
Search interfaces need to explain why results appear and how to narrow or broaden scope.86%Design Systems Page Patternsknowledge-base / libraryKnowledge Library Browse Pattern
Knowledge, asset, and pattern libraries need a stable browse flow that joins search, categories, filters, result counts, matched excerpts, empty results, and return paths.
A library page is not valuable because it shows many cards. It helps users move from fuzzy intent to a callable item while preserving source, quality, category, and next action.95%Design Systems Page Patternssearch / filtersSearch and Filter UX Contract
Search, filters, facets, and sorting must explain the current result set together: query, scope, constraints, why results appear, and how to recover.
A retrieval interface is a state machine. Every query, facet selection, sort change, or reset should expose result count, active filters, matched excerpts, empty-result recovery, and shareable URL state.96%Knowledge Architecture RAGfacets / searchGlobal Facet Index Contract
Sidebar facets for knowledge, asset, and style libraries should come from the full index, not only the current result subset; the results area explains the active query and filters.
Faceted navigation is both a retrieval control and an information-architecture map. If facets are derived only from the current result set, users lose adjacent categories after searching and RAG cannot reliably discover neighboring knowledge.97%