Knowledge RAG
Submit principleDesign Knowledge Base
Community-maintained principles reviewed before publication and retrieved as Agent design constraints.
3 published principles / 192 in library
Knowledge Architecture RAGscroll / overflow
Scroll Container Ownership Contract
Long pages, libraries, and workbenches must define one primary scroll owner; declare scroll ownership before combining nested `height: 100vh`, `overflow: hidden/auto`, and sticky panels.
Scrolling is not incidental browser behavior; it is a layout contract. Decide who owns page scroll, who owns local scroll, which panels are sticky, and how mobile reflows before implementation.97%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%Knowledge Architecture RAGrag / retrievalRAG Retrieval Intent Coverage Contract
Every skill, knowledge, style, and asset entry should cover user phrasing, design-theory terms, component/state terms, implementation-risk terms, and source terms instead of relying only on the title.
RAG quality depends not only on content depth but on whether entries can be recalled. Retrieval queries are signposts for future agents and must cover multiple phrasings and task intents.96%