Interface Lab
Knowledge RAG

Design Knowledge Base

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

Submit principle
7 published principles / 192 in library
Design Systems Page Patternstokens / settings

Design System Token Settings

Token settings pages must show semantics, aliases, modes, affected components, version diffs, and release risk together, not only color and number inputs.

Design tokens are design decisions that move across design tools, code platforms, and component libraries. A settings page does not only edit values; it explains how a value is referenced, how it changes by mode, and which components and versions it affects.96%
Design Systems Page Patternstokens / theme

Semantic Theme Token Scope

Theme tokens should define scope and hierarchy so components consume semantic roles instead of scattered one-off color values.

A design system's theming power comes from a few predictable semantic controls: accent color, gray scale, panel background, scaling, radius, and component variants.90%
Design Systems Page Patternstokens / editor

Token Editor Pattern

Token Editor Pattern turns a frequent interface judgment into an executable constraint before generation.

Token editors need to make design decisions, references, and impact scope visible.87%
Design Systems Page Patternsdocumentation / design-system

Design System Documentation Page

Design System Documentation Page turns a frequent interface judgment into an executable constraint before generation.

Design system docs must support finding, understanding, copying, and judging suitability.87%
Design Systems Page Patternsgovernance / review

Component Governance Review Flow

Component Governance Review Flow turns a frequent interface judgment into an executable constraint before generation.

A design system needs to record why components are added, how they are reused, and when they are deprecated, not just list components.86%
Design Systems Page Patternscomponents / contract

Component Consistency Contract

Components need clear props, states, sizes, and disallowed combinations to stay consistent across pages.

A component is not a visual screenshot; it is a reusable set of behaviors and constraints.82%
Design Systems Page Patternstokens / design-system

Design Token Governance

Tokens should express roles and constraints, not merely store colors, type, and spacing.

Maintainable tokens need names, scope, defaults, and prohibited uses so humans and agents can share them.82%