open-webui UI Pattern Extraction Prompt

ui generationvery high Token Costadvanced

Prompt provenance

Inspired by open-webui/open-webui.

Reverse-engineered from real GitHub workflow.

Updated 2 weeks ago·0 copies

Reverse-engineer an AI chat workspace UI from open-webui — provider switching, conversation layout, RAG affordances, knowledge/tools/models workspace, channel collaboration, and self-hosted settings — without copying product branding.

What this solves

AI chat workspace UI pattern extraction with provider switching, RAG, tools, knowledge, channels, and self-hosted settings

Best used when

You are designing or rebuilding an AI chat workspace UI and need a source-grounded inventory of layout regions, message states, model selection, RAG/file affordances, and settings surfaces.
You want an agent to map open-webui's chat, sidebar, workspace, admin, and channel components into reusable UI patterns rather than copy product branding.
You need a structured spec for provider/connection switching, knowledge-base attachment, tool servers, citations, code execution, and multi-response comparisons before writing components.

Avoid using when

You only need a generic chatbot mockup with one model and no RAG, tools, or admin surfaces.
You want backend or model-runtime architecture analysis instead of UI pattern extraction.
You intend to publish the generated UI as production prompt rows without maintainer review.

Prompt Variants

Use this when Claude has broad repo-reading access and should produce a source-cited UI specification with per-region component citations and a clear chat-vs-admin separation.