UI & UX
AuraScore 79/100

Academic Discovery Engine Interaction Design Brief

Generate a detailed UX brief to redesign scholarly search, filtering, and citation preview workflows in academic repositories.

Use this template when redesigning search facets, citation interactions, or metadata exploration for university research portals. It helps product teams deliver clear, evidence-based interaction specifications.

Template

Role: Staff Product Designer specializing in Academic Discovery Interfaces

Context

  • Institution: {{institution_name}}
  • Primary user base: {{target_researcher_cohort}}
  • Current interaction issues: {{current_search_pain_points}}
  • Underlying schema and metadata: {{metadata_standards}}
  • Success benchmarks: {{primary_discovery_metrics}}
  • Engineering limitations: {{technical_integration_constraints}}

Task

Draft a comprehensive interaction design brief that establishes the visual hierarchy, faceted query mechanics, and inline citation preview workflows for the institutional research repository, driving higher citation capture and reduced query abandonment.

Method

  1. Analyze {{current_search_pain_points}} against the search behaviors common to {{target_researcher_cohort}}.
  2. Map the data attributes from {{metadata_standards}} into a clear progressive disclosure hierarchy for search result cards.
  3. Define multi-attribute filtering logic (e.g., peer-review status, open access tiers, publication date brackets) that minimizes zero-result states.
  4. Design the micro-interactions for rapid abstract previewing, inline citation copying, and bibliography export workflows.
  5. Establish layout patterns for complex Boolean querying that remain accessible to non-technical users while supporting advanced researchers.
  6. Specify the responsive behavior of the discovery canvas across mobile, tablet, and widescreen desktop monitors within {{technical_integration_constraints}}.
  7. Detail empty, loading, and error states with clear recovery actions tailored to scholarly search queries.
  8. Align user interface requirements with the target goals defined in {{primary_discovery_metrics}}.

Constraints

  • MUST integrate all mandatory data fields from {{metadata_standards}} into primary or secondary card views.
  • MUST NOT require full-page reloads for facet selection or citation snippet previews.
  • Interface wireframe recommendations must respect {{technical_integration_constraints}}.
  • Maintain minimum WCAG 2.1 AA target contrast for all metadata badges and tag components.

Output format

Provide the design brief using the following structure:

  1. Executive Summary & Design Objectives (max 150 words)
  2. User Persona & Mental Model Mapping
  3. Faceted Search & Filtering Interaction Architecture
  4. Result Card Anatomy & Progressive Disclosure Rules
  5. Micro-interactions & Export Workflows
  6. Responsive Layout & State Matrix (Empty, Loading, Partial, Error)
  7. Measurement & Validation Protocol

Self-review

  • Did I resolve every item listed in {{current_search_pain_points}}?
  • Are the interaction states compliant with {{technical_integration_constraints}}?
  • Is the progressive disclosure model intuitive for {{target_researcher_cohort}} without hiding critical metadata?
AuraScore breakdown
79/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering10/12 · Adequate

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency5/10 · Thin

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness3/5 · Adequate

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

design-visual
design-ui-ux
education-research
ui-ux
academic-research
search-ux