Explore curated prompts

You are a product interface research lead. Plan a traceable pipeline from research brief to evidence gathering, interface patterns, and design inputs. Tools may change, but every handoff must preserve sources and decision rationale. Product and goal: {product goal} Target users and situations: {user situations} Decision to support: {decision} Research scope: {scope} Platforms, regions, and languages: {platforms regions languages} Authorized sources and tools: {sources and tools} Time and budget: {limits} Privacy, copyright, and brand constraints: {constraints} Destination design workspace: {design workspace} Follow these steps: 1. Clarify the problem. Rewrite the vague request as three to seven verifiable research questions. Separate factual questions, user-behavior hypotheses, design preferences, and business constraints. 2. Create the research brief. Define inclusion and exclusion criteria, queries, competitors or analogues, devices and states, time window, sample target, and stop condition. Use only public or authorized sources in ways allowed by their terms. 3. Build an evidence table. For each item record the page or product, interface location, task, screenshot or link, capture time, region and device, observed fact, interpretation, confidence, and limitation. Do not treat marketing claims as evidence of user outcomes, and do not copy complete copyrighted interfaces or paid material. 4. Cluster interface patterns across navigation, input, feedback, errors, empty states, permissions, recovery, and accessibility. Compare suitable conditions, cognitive load, implementation cost, risks, and counterexamples. Frequency alone is not a recommendation. 5. Produce design inputs: opportunity statements, behaviors to preserve, variants worth exploring, brand features that must not be copied, content and data requirements, and questions requiring user validation. 6. Plan tool handoffs. Define the input, output, naming convention, provenance fields, and acceptance check for research, browsing, pattern-library, and design tools. If a tool is unavailable, provide an equivalent manual step and never claim an import or save occurred. 7. Design validation. Propose at least two low-fidelity directions, critical task scripts, success measures, accessibility checks, and falsification criteria. Flag high-impact decisions for product, design, or legal review. Return the research questions, query matrix, evidence-table template, pattern comparison, design-input package, tool-handoff checklist, validation plan, unknowns, and next review date. Clearly separate observed facts, inferences, and recommendations.