Interface Lab
  • Home
  • Agents
  • Community
  • Library
  • Knowledge
  • Docs
ZHLogin
KnowledgeResources and reviewThis resource page is not included in Agent RAG.
All principlesResource MapContribute
Knowledge RAG120 published principles
Knowledge Resource Map

Resource Map

Source tiers, theme coverage, curation standards, and expansion method for the design knowledge base.

Design Knowledge Resource Map

This resource map explains how the Interface Lab design knowledge base is collected, filtered, and expanded. A knowledge item is kept only when it becomes executable design judgment: it can become an Agent directive, change generated UI, has clear apply and avoid contexts, and can be retrieved with English and Chinese queries.

Source Tiers

  • Tier 1: official standards, platform guidelines, and accessibility references. Prioritize W3C WCAG 2.2, Apple Human Interface Guidelines, Apple Accessibility, Material Design, and IBM Carbon Accessibility.
  • Tier 2: mature design systems and product practice. Study GOV.UK Design System, Atlassian Design System, Shopify Polaris, Salesforce Lightning Design System, and Microsoft Fluent.
  • Tier 3: community resources, case indexes, and practice signals. Use them to discover patterns and scenarios, not as unquestioned rules: Design.Systems, Design Systems Repo, Sourcy, Figma Community, Mobbin, Pageflows, UX Collective, and Nielsen Norman Group.

Theme Map

  • Visual Foundations: hierarchy, density, real media, object detail, comparison layouts, chart readability, dashboard triage, and empty-state composition.
  • Typography Color Accessibility: type hierarchy, contrast, semantic color, focus states, form labels, error summaries, status messages, icon accessible names, and reduced redundant entry.
  • Interaction Responsive Motion: keyboard navigation, modal focus, bulk actions, filter state, mobile action bars, skeleton loading, AI generation progress, undo, and drag alternatives.
  • Design Systems Page Patterns: settings pages, list-detail workflows, pricing comparison, search facets, design system docs, token editors, component governance, community contribution, and review flows.

Reading Path

  • Start with accessibility standards: map WCAG principles for perceivable, operable, understandable, and robust interfaces to color, focus, forms, status messages, and keyboard paths.
  • Read platform guidance next: Apple HIG, Material, and Fluent help identify platform habits, touch target expectations, motion purpose, navigation structures, and system control conventions.
  • Study design systems after that: compare how GOV.UK, Carbon, Polaris, Atlassian, and Lightning explain component usage, errors, states, content style, and governance.
  • Use community cases last: Mobbin, Pageflows, Figma Community, and Sourcy help discover real product flows, but only verifiable patterns are summarized. Screenshots, templates, and paid assets are not copied.

Curation Standard

  • The candidate must become an Agent directive, such as “after table row selection, show selected count, scope, risk, and completion feedback.”
  • It must include a positive and negative example or clear apply and avoid contexts.
  • It must affect generation output: layout, interaction, state, copy, accessibility, responsiveness, or component governance.
  • It must be findable through English and Chinese queries that include scenario terms, component terms, and user task terms.
  • Sources are archived as links and summarized as original guidance. Long quotes, screenshots, paid material, and unverifiable trends are rejected.

Reject Rules

  • Do not add pure inspiration images, trend lists, decorative visual fragments, or Dribbble-style effects without use context.
  • Do not add commercial downloads, template packs, icon packs, font packs, or resources that require paid login to verify.
  • Do not add personal preference claims that cannot become executable UI constraints.
  • Do not add this Markdown resource page to Agent RAG. RAG retrieves only reviewed knowledge items and version content.

Expansion Method

  • Fill coverage across the four themes first, then merge near-duplicates so the library does not accumulate the same rule under many names.
  • Use English kebab-case slugs, keep tags to 3 to 5 items, and include principle, design action, examples, apply and avoid contexts, Agent directive, retrieval queries, and source notes.
  • Chinese and English content must be original summarization, not copied or lightly translated external text.
  • Before publishing, run typecheck, seed generation, RAG evaluation, and manual page checks.