Retrieval Playground

Test retrieval queries against connected knowledge with filters, top-k, reranking, source previews, and relevance feedback. This example brings Query and Sources together so AI product teams can find the next task without losing context.

It includes representative records such as Enterprise permissions policy and Billing edge cases. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Retrieval Playground
Use this template in Figr

Template facts

Screen

Builder

Primary action

Run query

Pattern

Builder

State

Default, loading, empty, error, permission, success

Design system

Configurable product UI theme

What this screen helps users do

Product teams need to run query while keeping top-k, sources and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Query gives users an obvious place to start.
  • Supporting view: Sources keeps the related context close.
  • Primary action: Run query stays visible when people need it.
  • First signal: Top-k shows a useful value (8).
  • Second signal: Sources gives additional context (5).
  • Sample record: Enterprise permissions policy.
  • Next record: Billing edge cases.

States worth designing

  • No configuration selected: say what changed, protect progress, and offer a clear next step.
  • Unsaved changes: say what changed, protect progress, and offer a clear next step.
  • Invalid rule or block: say what changed, protect progress, and offer a clear next step.
  • Preview generated: say what changed, protect progress, and offer a clear next step.
  • Publish blocked: say what changed, protect progress, and offer a clear next step.
  • Version restored: say what changed, protect progress, and offer a clear next step.

Where this screen sits in the flow

Query → Sources → Run query → Review outcome

Patterns used

Builder, Query, Sources, contextual actions, error recovery

Why these choices work

Show constraints before adding blocks, keep a usable preview and protect unsaved changes as people test a different direction.

Pay attention to query and sources. People need to distinguish Enterprise permissions policy from Billing edge cases. Keep top-k visible, especially when a record changes owner or status.

Before this screen reaches handoff, verify keyboard focus, empty and permission states, and what happens after someone chooses “Run query”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Knowledge Source Manager, Prompt Versioning, Tool Connector Setup.

Start from this in Figr

Design a retrieval playground screen inside our existing product. Use our current components, tokens and content language. Include Query and Sources views, credible records like Enterprise permissions policy, and a clear “Run query” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr