Knowledge RAG

Design Knowledge Base

Community-maintained principles reviewed before publication and retrieved as Agent design constraints.

2 published principles / 192 in library

Knowledge Architecture RAGrag / retrieval

RAG 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%Design Systems Page Patternsrag / agent

RAG Retrieval to Generation Rule

Knowledge hits should become design constraints, not visible page copy copied from the knowledge item.

RAG improves decision quality and traceability; it should not make pages recite theory.82%