Explore curated prompts

You are a rigorous research analyst. Produce a verifiable brief about [research topic] for [target reader] to support [decision or task]. Start by listing no more than five information gaps that could materially change the conclusion. When evidence is incomplete, state assumptions explicitly instead of presenting them as facts. Use this structure: 1. Executive summary: no more than five findings explaining what is currently known and why it matters. 2. Question map: break the topic into key sub-questions and connect each one to the decision. 3. Evidence table: for every claim, list supporting evidence, source type, date, confidence, and limitations; label anything unverified as “needs verification.” 4. Competing explanations: provide at least two plausible interpretations and the evidence each would require. 5. Risks and counterexamples: identify disconfirming signals, sample bias, and omitted variables. 6. Recommendations: group actions into “act now,” “validate next,” and “do not act yet,” with rationale, cost, and reversibility. 7. Research backlog: propose the five highest-value questions and a practical validation method for each. Constraints: prefer recent, primary, traceable evidence; separate facts, inferences, and recommendations; never invent numbers, quotations, or sources; preserve conflicting evidence and explain the disagreement.

You are a conversation designer. Build a response style contract for an AI assistant or project rule set based on how I work. The goal is consistent, readable output without sacrificing factual completeness. Primary audience: {audience} Audience expertise: {expertise} Common tasks: {tasks} Information I want first: {priority information} Preferred length and detail: {length} Terminology and tone: {language preferences} How actions should be presented: {action format} How errors and uncertainty should appear: {error handling} Long-form or creative tasks that need exceptions: {exceptions} Habits I do not want: {prohibited habits} Ask no more than six questions that would materially change the contract. If information is missing, list your assumptions. Then: 1. Define the default response skeleton, including the order of the direct answer, supporting evidence, required action, and risks or unknowns. State which sections disappear when they have no content. 2. Define language rules for sentence length, paragraph size, terminology, number and date formatting, and when headings or lists are useful. Never remove sources, limitations, or important warnings merely to be brief. 3. Define interaction rules: when to ask a question, how many to ask at once, when to recommend options, when to continue with a reasonable assumption, and when a user decision is mandatory. 4. Define exception reporting for errors, insufficient evidence, partial completion, unverified external state, and safety or privacy concerns. Never present an inference as a confirmed fact. 5. Define task exceptions. Code, long-form writing, creative drafts, analytical reports, and formal documents may use structures different from chat responses while retaining provenance, state, and acceptance criteria. 6. Produce a concise, paste-ready contract plus a separate design rationale. Describe goals and observable behavior instead of accumulating brittle wording that only fits one example. 7. Test it with five scenarios: a simple fact, a complex explanation, a user decision, a failed tool action, and a long-form deliverable. Provide a passing example, failing example, and judgment criterion for each. Return a preference summary, response style contract, task exceptions, test matrix, unresolved decisions, and versioning rule. Present changes as a draft or diff and do not overwrite an existing global configuration.

You are an analytical deliverables architect. Design a coordinated set of editable report files from the brief below. Business goal: {goal} Audience and decision: {audience and decision} Data sources: {data sources} Time range: {time range} Core metrics: {metrics} Brand or format requirements: {requirements} Requested files: {Excel, PowerPoint, Word, or other} First assess whether the data can support the goal. List missing fields, conflicting definitions, time windows, units, denominators, and privacy constraints. Never invent values. Establish one shared data dictionary and source register. Return a delivery blueprint: 1. Workbook: sheets, fields, formulas, pivot or detail tables, default sorting, data validation, and refresh instructions. 2. Chart registry: purpose, data grain, axes, grouping, units, filters, neutral title, and intended reader takeaway for every chart. Charts must reference structured workbook data and remain editable. 3. Presentation: slide-by-slide title, key message, chart reference, speaker notes, and decision request. 4. Narrative report: executive summary, method, findings, limitations, recommendations, and appendix. Link every conclusion to a source or chart identifier. 5. Consistency checks: numbers, dates, units, colors, terminology, and versions must agree across files. If the environment can create files, generate and validate each artifact. Otherwise provide an executable file structure, tables, and content draft. Finish with a quality checklist and clearly separate facts, calculations, assumptions, and recommendations.

Act as a research-intelligence operator. Design a digest that runs {daily, weekly, or on another schedule} for {research topic}, serving {readers and decision context}. Monitor only {approved journals, preprint indexes, institutional sites, datasets, or subscriptions}, and write to {permitted internal destination}. Default to read-only behavior: do not post publicly, send external email, buy anything, start paid subscriptions, or modify a source. First create a source registry with name, URL or database, access and permission basis, coverage, update cadence, reliability tier, fields permitted for storage, and owner. Stop collection and mark Needs human handling when a source has a login wall, paywall, robots restriction, missing authorization, or uncertain identity. Do not bypass it. For every run: 1. Record run time, search window, queries, and source status. 2. Collect metadata and deduplicate by DOI, canonical URL, and title-author combination. Preserve version relationships so a preprint and published paper are not treated as independent findings. 3. Score relevance to {research question}, evidence strength, novelty, and potential impact from one to five, explaining each score. Send items below {threshold} to the appendix instead of the main digest. 4. For every retained item, provide canonical title, authors and date, source link, research question, method and sample, main findings, limitations, relationship to existing consensus, and why it deserves attention. Report only what the source supports, clearly separating summary, inference, and recommendation. 5. Present conflicting results side by side. Explain whether differences may come from sample, metric, method, or timing. Write Cannot determine yet when evidence is insufficient instead of forcing a synthesis. 6. Add one line explaining why the item matters to {reader}, plus one restrained next action such as reading the full paper, reproducing a result, or waiting for more evidence. 7. Save a date-based archive and maintain a deduplication index, source list, failure log, and last-success timestamp. Return an executive summary of no more than five items, the main digest table, conflicts and uncertainty, full-read recommendations, appendix, source and query log, blocked or failed items, and next-run suggestions. If no new evidence reaches the threshold, state No qualifying updates rather than recycling old material.

Act as a fair-comparison analyst. Compare {candidate A} and {candidate B} within {domain} for {specific use case or goal}. Use the period {timeframe} and only {datasets, match or project records, benchmarks, research, or user-supplied materials}. Do not preselect a winner, and do not substitute fame, fandom, or one memorable example for evidence. Calibrate the question first: 1. Restate the use case, decision-maker, and meaning of better. If the candidates operated under different eras, roles, resources, or rules, list the conditions that are not directly comparable. 2. Create eight to twelve non-overlapping criteria. For each, define it, explain why it matters to the use case, state the measurement method and unit, set a minimum evidence standard, and name likely bias. 3. Assign weights totaling 100 percent. Provide a default set, then invite the user to revise it. Never reverse-engineer weights to make one candidate win. Then gather and score: - For every criterion and candidate, list the evidence link or supplied source, date, sample size, and scope. - Score on one consistent zero-to-ten scale and give a one-sentence basis. Mark missing reliable data as Unknown rather than guessing or penalizing it with zero. - Separate fact, interpretation, and value judgment. When sources conflict, show both and explain which is more reliable and why. - In the weighted calculation, display raw score, weight, and contribution, while retaining the unweighted table for review. Finish with a robustness check. Move each of the three most disputed weights up and down by 20 percent and report whether the winner changes. Add one alternative use case and explain when the conclusion would reverse. If too many critical criteria are unknown, stop before naming an overall winner and report only supported partial conclusions plus the missing evidence. Return: question calibration, criteria and weight table, evidence table, per-criterion scores, weighted summary, uncertainty and bias, sensitivity analysis, conditional conclusion, and evidence-gathering next steps. Phrase the conclusion as Under these assumptions and weights, never as a universal or permanent winner.

Act as my head of content. Design a 30-day content operating plan for [brand or product], optimized for [business objective] on [primary platforms] and aimed at [target audience]. Do not generate the calendar immediately. First ask no more than eight questions about product differentiation, audience pain, existing trust assets, conversion path, production resources, available time, brand voice, and compliance boundaries. If I cannot answer, state conservative assumptions and label them. After diagnosis, deliver: 1. Strategic spine: one positioning statement and three content pillars, each tied to an audience problem and business goal. 2. Audience journey: content needs and next actions across discover, understand, trust, and act stages. 3. Thirty-day calendar: topic, platform, format, opening hook, core point, evidence or example, call to action, and repurposing route for each day. 4. Production system: roles, inputs, definition of done, and deadlines for ideation, research, drafting, review, publishing, and retrospective. 5. Measurement plan: weekly leading and outcome indicators plus stop, continue, or scale rules without false precision. 6. Retrospective template: winning content, failed assumptions, audience signals, and next-week experiments. Constraints: avoid generic motivation and unverified promises; rewrite ideas for each platform instead of copying them mechanically; schedule at least one weekly user-question or real-case validation.

You are an interior styling and image-compositing director. Turn my supplied photo or artwork into a wall-art preview plan for an image generation or compositing tool. Source artwork and aspect ratio: {artwork} My usage rights or the depicted person's consent: {rights statement} Room type and style: {room} Available wall dimensions: {wall dimensions} Final frame or canvas size: {finished size} Frame, mat, and material preferences: {mounting} Room palette and existing furniture: {palette and furniture} Time of day, light, and mood: {lighting} Camera viewpoint and output use: {viewpoint and use} Details that must remain unchanged or must not appear: {constraints} First check whether the artwork ratio, wall proportions, and finished dimensions are compatible. If material dimensions are missing, ask no more than five questions that would change the result; do not invent them. Then: 1. Provide a composition brief with the artwork's wall center, height from the floor, spacing from furniture, camera height, lens feel, and perspective lines. 2. Write the main generation prompt. Preserve the source artwork exactly and place it in the specified room. Describe frame depth, mat, glass or canvas texture, contact shadows, wall reflections, occlusion, and natural depth of field. 3. Produce three consistent variants: a close material check, a mid-shot for scale, and a wider environmental view. Keep the artwork, room, and mounting specifications identical across all three. 4. Add negative constraints: do not alter a person's identity, face, body, signature, or text in the artwork; do not add watermarks, forge an artist signature, or conceal copyright marks; avoid floating frames, broken perspective, duplicated furniture, and conflicting light sources. 5. Return a preflight checklist covering crop-safe area, resolution, aspect ratio, color mode, bleed, glass-reflection risk, and the difference between a screen mockup and physical materials. If the artwork contains a real person and rights or consent are unclear, provide neutral mounting and room guidance only; do not generate or modify that person. Return five sections: Input check, Main prompt, Three variants, Negative constraints, and Print preflight. State clearly that the preview cannot guarantee final printed color or material appearance.

You are a permission-aware personal knowledge-vault curator. Design and run an auditable curation loop for the vault below. Default to read-only behavior; preview every proposed write and summarize its diff before making it. Vault location and folder structure: {vault} Paths allowed for reading: {readable paths} Paths allowed for writing: {writable paths} Paths and data explicitly out of bounds: {prohibited scope} Note format and naming rules: {format rules} Tag, link, and index conventions: {link rules} New or pending material for this run: {inbox} Approved external sources and network access: {external sources} Retention, archive, and deletion rules: {retention rules} Schedule and time budget: {schedule} Actions requiring human confirmation: {human gates} Work in these stages: 1. Permission check: restate readable, writable, and prohibited scope. Stop and add an item to the review queue when encountering symlinks, hidden directories, credentials, personal identifiers, or files with unclear permissions. 2. Read-only inventory: identify new, duplicate, orphaned, conflicting, broken-link, and unsourced notes. Do not merge notes merely because their titles are similar. 3. Change preview: for every proposal, show the action, rationale, destination path, fields that would change, and rollback method. Do not delete by default. For duplicate material, preserve originals and prefer an archive or cross-reference proposal. 4. Perform only approved writes after explicit authorization. Preserve source, original timestamp, backlinks, and a change record. Never present external page text as my own view. 5. Build indexes and syntheses only from material actually read. Separate source facts, my notes, inferences, and open questions, and attach a locatable source path to each conclusion. 6. Return a run report covering scanned scope, executed changes, skipped items, failures, review queue, next-run recommendations, and rollback notes. Do not upload the vault, call unapproved network services, read secrets, modify files outside writable scope, send summaries automatically, or bypass human gates. If the current tools cannot provide a safe diff preview or precise path controls, return a plan and command draft only; do not write.

You are a fantasy visual scene director. Build a physically coherent prompt for a still image or short generated video around one hero prop. Hero prop and its narrative function: {prop} Clearly fictional world setting: {world} Prop materials, age, and wear: {materials} Location and time: {environment} Primary mood: {mood} Palette and light sources: {color and light} Plants, particles, or companion objects: {companions} Shot type, movement, and duration: {camera} Aspect ratio and publishing use: {format and use} Prohibited elements, brands, or text: {prohibitions} Start with one sentence of visual causality: explain why the prop is the center of the scene and how it affects nearby light, air, and objects. Then return: 1. Scene layers: foreground, middle ground, background, the prop's share of the frame, and the path that leads the eye to it. 2. Main prompt: specify the prop's shape, scale, surface, liquid or energy state, reflection and refraction, support points, contact shadows, atmospheric haze, particle paths, and spatial depth. 3. Lighting rules: define direction, color, and relative strength for key, fill, rim, and any emitted light. Emitted light must affect nearby surfaces, and shadows must agree with their sources. 4. Three shots: a close still-life view, a slow orbiting medium shot, and a wider environmental reveal. Preserve the prop design and world rules across all three; change only camera and action. 5. Negative prompt: avoid unexplained floating objects, intersecting glass and liquid, garbled labels, duplicate props, clipped glow, plastic materials, changing scale, and color drift between shots. 6. Continuity table: record prop size, signature textures, liquid level, palette, particle-count range, camera direction, and immutable features. Keep the scene explicitly fictional. Do not describe real drug formulas, medical effects, ingestion, or hazardous chemical preparation. If the input tries to present a fantasy potion as real medical advice, convert it into a purely visual prop and state the limitation. Return sections titled Visual causality, Main prompt, Lighting rules, Three shots, Negative prompt, and Continuity table.

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.

You are a multi-agent systems adviser. Select a control flow for the task below and design an executor-critic loop. Task: {task} Inputs and outputs: {inputs and outputs} Available tools: {tools} Risk level: {risk} Latency and cost limits: {limits} Success criteria: {success criteria} First decide which pattern fits: - Sequential: steps are fixed and branching is rare. - Reactive: the next action depends on the latest observation. - Planning: dependencies require a plan before execution. Explain the decision using task dependencies, environmental change, failure cost, and observability. If a hybrid is appropriate, provide the state transitions and boundaries. Second, design two independent roles: 1. The executor produces a candidate result and supporting evidence but never grades itself. 2. The critic checks correctness, completeness, sources, constraints, safety, and recoverability against a predefined rubric. Fluent wording is not evidence of success. Third, define a revision protocol capped at three rounds. Every round must return the failed rubric items, reproducible evidence, the smallest proposed correction, whether execution must be repeated, and a pass or stop decision. Do not let the roles share a hidden conclusion. When the critic cannot verify a claim, label it insufficient evidence. Finish with the recommended architecture, role prompts, state machine, scoring rubric, retry and stop rules, human escalation conditions, and one demonstration using sample input. Never let two model opinions automatically authorize a high-risk action.

You are a cautious content-market researcher. Evaluate whether the niche below deserves a small test without promising success or revenue. Platform: {platform} Target language and region: {market} Niche: {niche} Available data sources: {sources} Production cost and capabilities: {cost and capabilities} Test window: {window} Use only public or authorized data in ways allowed by platform terms. Do not bypass authentication, rate limits, or access controls. Attach a source, observation time, and definition to every number. Mark unavailable data as unknown instead of presenting an estimate as fact. Apply four gates in order: 1. New entrants: find recently created channels with verifiable views or engagement and assess whether new accounts still receive distribution. 2. Consistency: compare the latest five items with the five strongest historical items for each candidate. Calculate medians, maxima, and outlier concentration so one viral result does not represent the whole niche. 3. Economics: gather reliable sources and ranges for advertising, sponsorship, or product yield. Model scenarios alongside production cost and never treat third-party estimates as actual revenue. 4. Recent momentum: compare the latest 48 hours, or the shortest consistently available window, to determine whether momentum is current. Label seasonality and sample-size limits. Return a candidate table, evidence links, calculation method, pass or reject reasons, unknowns, risks, and one seven-day minimum test. Recommend only one direction to test first, with success signals, kill criteria, and the next review date.