What problem does it solve? Developers embedding or modifying the QwkSearch chat/search UI need to navigate a large React package with two entry points, a provider stack, dependency-injected API handlers, and subtle pitfalls like editor code leaking into chat-only bundles. ## Core Features & Use Cases - Entry Point Selection: Choose between the chat-only root entry and the /workspace entry that adds the REASON editor, keeping Tiptap/Plate out of chat-only bundles. - Provider & Config Wiring: Mount QwkSearchApp or compose SessionProvider, ChatProvider, and ExtractPanelProvider with configureResearchAgentUI for branding, callbacks, and Google Drive picker setup. - Server Route Handlers: Add dependency-injected API route factories (chats, messages, search, rewrite, voice) that run in any Next.js host. - Use Case: A host app wants a branded chat UI with a Ctrl-Space spotlight palette and streaming rewrite endpoint; this Skill explains which providers to mount, which config callbacks return true to handle navigation in place, and how the rewrite handler falls back across model providers. ## Quick Start Ask the assistant to mount QwkSearchApp from research-agent-ui with a custom authClient and appName config in your Next.js app.