Design Principle
Search interfaces need to explain why results appear and how to narrow or broaden scope.
Principle
Search interfaces need to explain why results appear and how to narrow or broaden scope.
Design action
Show query, count, sort, facets, active filters, and no-result suggestions; result cards show matched field or excerpt.
Examples
Positive example: Knowledge bases, libraries, ecommerce, docs, user management, and template marketplaces. Counterexample: Search only refreshes the list without count or filter state.
Apply when
Knowledge bases, libraries, ecommerce, docs, user management, and template marketplaces. Users need to judge state, scope, risk, or next action quickly.
Source notes
Source note: Synthesized from GOV.UK, Carbon, Polaris, Atlassian, Design.Systems, Design Systems Repo, and product-pattern libraries. GOV.UK Design System Patterns: https://design-system.service.gov.uk/patterns/ Carbon Patterns: https://carbondesignsystem.com/patterns/ Shopify Polaris: https://polaris-react.shopify.com/ Atlassian Design System: https://atlassian.design/ Design Systems Repo: https://designsystemsrepo.com/
Agent Directive
Show query, count, sort, facets, active filters, and no-result suggestions; result cards show matched field or excerpt.