UI DESIGN LAB
  • Home
  • Community
  • Library
  • Knowledge
  • Docs
ZHLogin

Docs

Platform
Site OverviewDevelopment LogCollaboration Guide
Template Library
Prompt BoardStyle Board
Agent Workflow
Agent Deep DiveProject Workflow AgentAgent Output PathPrompt Agent EvalsDesign System PanelsKnowledge Base GuideDeepSeek Agent Incident Notes
UI DESIGN LABDocumentation

Read public Markdown docs; admins can maintain them in editor pages.

Knowledge Base Guide

Knowledge Base Guide

Explains the independent knowledge base, community review, and Agent RAG integration rules.

Back to docs

Chapter preview

Product BoundaryKnowledge Entry ShapeRAG FlowGeneration RuleAdmin WorkflowConfiguration

Knowledge Base Guide

The real community knowledge base lives at /knowledge. Docs keeps this guide only so product, engineering, and admin users can understand how knowledge entries flow into Agent generation.

Product Boundary

  • /knowledge stores community-submitted design principles, page patterns, accessibility guidance, and Agent directives.
  • /docs stores platform documentation, operating notes, and usage guidance.
  • Draft, review, private, rejected, and archived knowledge never enters public Agent generation context.
  • Only published public knowledge can be retrieved by RAG.

Knowledge Entry Shape

Each knowledge entry has:

  • Title, slug, category, tags, status, visibility, author, quality score, and published timestamp.
  • A versioned body with bilingual summary, principle, apply/avoid scenarios, Agent directive, and retrieval queries.
  • Published chunks used for full-text and embedding retrieval.
  • RAG event logs that record which chunks were used by which workflow stage.

    • RAG Flow

    1. A user starts a workflow from the creation page.
    2. The workflow loads selected Skills.
    3. Sable also acts as the knowledge retrieval manager.
    4. The retrieval query is built from the user brief, requirement summary, selected Skills, page type, and asset summaries.
    5. If embedding is configured, pgvector retrieves top matching published chunks.
    6. If embedding is unavailable or fails, the system falls back to full-text and keyword scoring.
    7. The workflow keeps 4-8 compact hits with title, summary, principle, Agent directive, and source ID.
    8. Cleo, Isolde, Sable, and Orson read those constraints during planning and QA.

    Generation Rule

    Knowledge is not page copy. Agents must transform retrieved principles into layout, component, interaction, accessibility, and responsive constraints. The visible page should never quote agent_directive verbatim unless the user explicitly asks to build a knowledge/detail surface.

    Admin Workflow

    • Community users save drafts and submit review.
    • Admins publish, reject, archive, or rebuild chunks.
    • Publishing syncs the current version into knowledge_chunks.
    • Rebuilding chunks refreshes retrieval material and optionally embeddings.

    Configuration

    Embedding is optional for the first version.

    • EMBEDDING_API_KEY
    • EMBEDDING_BASE_URL
    • EMBEDDING_MODEL

    When these are missing, published knowledge remains searchable through the fallback retrieval path.