Explore curated prompts

Act as a member-lifecycle email architect. Design a new-member welcome journey for {brand or product} containing {email count, default 12}. The audience is {audience}, the primary goal is {activation, education, first use, repeat purchase, or retention}, the sending platform is {platform}, and the available inputs are {authorized brand guide, product facts, terms, cases, and links}. Begin with an evidence ledger: - Verified: capabilities, prices, rules, and brand statements directly supported by the supplied materials. - Needs verification: claims with missing or stale support. - Do not use: discounts, scarcity, certifications, testimonials, outcomes, revenue, or performance claims that were not supplied. If critical inputs are missing, ask targeted questions first. Do not fill gaps with the conventions or voice of a famous brand. Then plan the journey. Define one north-star behavior, three to five supporting behaviors, exit conditions, frequency caps, timezone handling, unsubscribe behavior, and compliance requirements. Return a table for every email with sequence number, trigger time, audience state, one objective, two subject-line options, preheader, body structure, one primary action, optional secondary action, personalization fields, required evidence, risk, and success metric. Each email must advance the member's state instead of repeating the same benefit under a new headline. For every email, also provide: 1. A 90–140 word draft in {brand voice}. 2. One clear, non-exaggerated CTA. 3. Facts that must be verified before sending. 4. One testable variable and success metric. 5. A skip or branch rule when the member has already completed the target behavior. Finish with a journey overview, event and field requirements, automation logic, prioritized A/B tests, accessibility and mobile checks, failure and stop conditions, and a human pre-launch review checklist. Constraints: use only authorized brand materials. Do not imitate an unauthorized brand voice. Never invent testimonials, numbers, discounts, countdowns, inventory, credentials, or outcomes. Apply the relevant privacy, marketing-consent, and unsubscribe rules, with qualified review where required.

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 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.