Browse Prompts
3315 prompts available · Page 25 of 277
Marketing Campaign Prompt: One Brief to a Full Launch Plan
Turn one campaign brief into a launch plan: core message, channel and budget split, asset list with counts, weekly timeline, UTM names, and a claims check.
Act as a campaign manager at a small marketing agency who turns one client brief into a launch plan the team can execute, splits the budget so it adds up to the cent, and checks every claim against the client's proof points before any asset is written. Inputs: - The offer, price, dates, and what success looks like: [CampaignBrief] - Who it is for and what they care about: [TargetAudience] - Facts the client can prove (no superlatives without proof): [ProofPoints] - Channels available, with what already exists (email list size, social accounts, partners): [ChannelMix] - Total budget and any fixed costs: [Budget] - Campaign start and end dates, and any hard deadlines: [Timeline] - The one number the campaign is judged on, and its target: [SuccessMetric] Generate: 1. Campaign idea: one sentence, plus a message house (one core message and three supporting points, each tied to a line in ProofPoints). 2. Channel plan: each channel's job in the funnel and its share of Budget, in a table whose rows add up exactly to the total. 3. Cost check: the budget divided by the SuccessMetric target, so the client sees the cost per result needed to hit it. 4. Asset list: every asset with its count, format, and owner (ads, emails, posts, print, landing page). 5. Week-by-week timeline from the Timeline start to end, with dates, and what launches, runs, and gets reviewed each week. 6. Tracking: a UTM naming pattern (source, medium, campaign) with one filled example per channel. 7. Claims and compliance check: every claim in the plan matched to a ProofPoints line, plus the disclosure and email rules that apply to these channels. 8. Mid-campaign review: the date, the three numbers to check, and what to change if the SuccessMetric is behind. Rules: - Use only the facts given; mark any missing number as a question for the client. - No invented benchmarks, conversion rates, or audience sizes. - Dates must fall on the right weekdays; recheck every sum.
High School Assignment Coach: Rubric to Plan and Self-Check
Paste a high school assignment, rubric, and your own draft: get a dated work plan, a rubric checklist, questions for your teacher, and feedback, not rewrites.
Act as a high school academic coach and former classroom teacher who helps a student plan one graded assignment from the teacher's own rubric, coaches with questions and quoted feedback, and never writes the assignment for the student. Inputs: - The assignment sheet, as the teacher gave it: [AssignmentSheet] - The rubric, with criteria and points: [Rubric] - Today's date, the due date, and the evenings I can work, with minutes: [DatesAndTime] - My notes, data, or draft so far, in my own words: [MyNotesOrDraft] - What my school or teacher allows for AI use: [SchoolAIPolicy] - The part I find hardest: [StuckPoint] Generate: 1. The task in plain words: three sentences on what the teacher is asking for and what a finished version contains. 2. Rubric checklist: each criterion turned into yes or no checks I can tick, with its points, and the total points recomputed from Rubric. 3. Work plan: one line per available session from DatesAndTime with its date, minutes, and one job, ending before the due date; total minutes added up. 4. Questions for my teacher: up to three, only where the AssignmentSheet or Rubric is unclear. 5. Draft self-check: for each criterion, quote one line from MyNotesOrDraft and ask one question that helps me improve it myself. Point out anything my own data contradicts. Do not rewrite my sentences. 6. StuckPoint help: a short explanation of the idea with one "what if" example, then one practice question I answer myself. 7. AI use note: what I may and may not use this chat for under SchoolAIPolicy, and a one-sentence disclosure I can add if my teacher asks for one. 8. Next session: the first 10 minutes of my next session, step by step. Rules: - Coach, do not ghostwrite: no full paragraphs, conclusions, or answers I could hand in. - Use only the assignment, rubric, and notes given; if something is missing, say what to ask the teacher. - Keep dates and minutes exact, and check the arithmetic.
Business Card Design Prompt: Layout Spec and Clean Mockup
Turn brand colors, card text, and printer details into a business card layout spec, a text-free photoreal mockup prompt, and a print proof checklist in ChatGPT.
Act as a print graphic designer who designs small-business cards, writes a front and back layout spec a printer can follow, and briefs ChatGPT's image generation for a text-free photoreal mockup, because tiny type is where image models fail. Inputs: - Business name, what it does, and any existing mark: [BrandFacts] - Colors with HEX codes, and type style (serif, sans serif, script): [ColorsAndType] - Every line that must be on the card, exactly as it should read: [CardText] - Card size, printer, and whether the printer supplies a template: [SizeAndPrinter] - Paper, finish, and special effects (foil, spot gloss, rounded corners): [PaperAndFinish] - Look and feel in three words, plus what to avoid: [StyleDirection] - Surface, props, and light for the mockup photo: [MockupScene] Generate: 1. Card concept: two sentences on how the design reflects BrandFacts and StyleDirection. 2. Layout spec, front and back: what goes on each side, alignment, the order of CardText lines, suggested type sizes and weights, and which color each element uses from ColorsAndType. 3. Contrast check: each text and background color pair, with a note if it may be hard to read in print. 4. Print setup: use the printer's template for size, bleed, and safe area; keep text inside the safe area; how to supply special effects from PaperAndFinish (ask the printer for their file rules). 5. Mockup image prompt for ChatGPT's image generation: photorealistic photo of the cards in MockupScene, exact count of cards, which side faces up, colors, finish and effect, light direction, and every text area left blank. 6. A "leave out" line: readable text, letters, numbers, QR codes, logos other than the described mark, watermarks, hands. 7. Proof checklist: eight yes or no checks for the real print file (spelling of every CardText line, phone and email tested, safe area, color mode, foil layer, size, test print at 100%, back side). 8. Two alternate directions in one line each, using the same CardText and colors. Rules: - Put CardText only in the layout spec and the print file, never in the image prompt. - Do not state paper weights, bleed sizes, or prices; the printer's template decides. - No logos except the user's own mark as described.
Christmas Photo Prompt: Holiday Portrait From Your Own Photo
Turn your own photo of a person, family, or pet into a Christmas portrait in ChatGPT: keep the likeness, set the tree, lights, props, and room for a greeting.
Act as a holiday portrait photographer and retoucher who restyles a client's own photo into a Christmas portrait in ChatGPT, keeps the subject's face, build, coat, and markings unchanged, and plans the set the way a studio would before a December shoot. Inputs: - Who or what is in the uploaded photo, and what must stay exactly the same: [SubjectAndLikeness] - What the subject wears or holds in the new photo: [WardrobeOrAccessory] - The Christmas set: tree, lights, ornaments, fireplace, window, with counts: [HolidaySet] - Gifts and props with exact numbers and positions: [PropsAndCounts] - Light and mood (warm lamp glow, morning snow light, candlelight): [LightAndMood] - Where it will be shared, with the aspect ratio: [ShareFormatAndRatio] - Where the greeting goes, and how much of the frame to keep empty: [GreetingSpace] Generate: 1. Likeness lock: one paragraph to put first in the request that names what must not change in SubjectAndLikeness (face shape, eyes, expression, hair or coat color, markings, body size) and says to change only the setting, clothing, and light. 2. The Christmas photo prompt: photorealistic portrait, the subject from the uploaded photo, WardrobeOrAccessory, the HolidaySet and PropsAndCounts with every number, LightAndMood, camera height and lens feel, the GreetingSpace kept empty, and the ratio from ShareFormatAndRatio. 3. Two alternate sets for the same subject (for example snowy porch, Christmas morning by the window), one line each, keeping the likeness lock. 4. A "leave out" line: text, letters, logos, licensed characters, extra people or animals, changes to the face or markings. 5. Likeness and set checklist: six yes or no questions comparing the result with the uploaded photo and the counts. 6. A one-line follow-up for the most likely miss (the face or markings drift). 7. Greeting note: where the greeting and names go in the design tool, and a short greeting line written from GreetingSpace. Rules: - Edit only a photo the user owns or has permission to use. - Every prop gets a number. Keep the set simple enough to count. - No words in the image; the greeting is added afterward.
Birthday Image Prompt: ChatGPT Party Scene From Your Brief
Turn a birthday brief into a ChatGPT image prompt: cake and candle count, decor with exact numbers, palette, light, and blank space for the invitation text.
Act as a party stylist and tabletop food photographer who writes ChatGPT image prompts for birthday invitations, cards, and story posts, counts every candle and balloon, and keeps the birthday message out of the picture so it can be typeset later. Inputs: - Whose birthday, the age or milestone, and the theme (no names needed): [BirthdayOccasion] - The cake exactly: shape, tiers, frosting, toppings, candle number and color: [CakeDetails] - Decorations and props, each with an exact number and position: [DecorAndCounts] - Three to five colors for the whole scene: [ColorPalette] - Setting, time of day, and light direction: [SettingAndLight] - Where it will be used, with the aspect ratio: [UseAndRatio] - Which part of the frame stays empty for the message: [MessageSpace] - Anything that must not appear: [AvoidList] Generate: 1. The birthday image prompt, ready for ChatGPT's image generation: photorealistic party scene, the cake from CakeDetails with the candle count written as a number and in words, every item in DecorAndCounts with its count and position, the ColorPalette, the SettingAndLight, camera height and lens feel, the MessageSpace kept empty, and the ratio from UseAndRatio. 2. A candle and count line that repeats every number in the scene (candles, tiers, balloons, gifts) so the model is told twice. 3. A card version and a story version (vertical) of the same scene, saying where the cake and the empty message area move. 4. A "leave out" line from AvoidList plus: letters, numbers, cake toppers with words, banners with words, logos, licensed characters, people, hands. 5. Image checklist: six yes or no questions to answer by looking at the result (candle count, balloon count and colors, cake details, empty message area, no text, ratio). 6. A one-line follow-up to fix the most likely miss (wrong candle count). 7. Message layout note: where the birthday line, date, and RSVP go in the design tool, with a safe margin. Rules: - Every prop gets a number. Fewer than ten items in total so the result can be checked. - No readable words or numbers in the image; age is shown only by the number of candles. - No real person's likeness unless it is the user's own photo, used with permission.
AI Chatbot System Prompt: Website Bot From Business Facts
Write a system prompt for a website or business chatbot from your own facts: scope, answer rules, handoff to a human, privacy limits, a greeting, and tests.
Act as a conversational AI designer who writes system prompts for small business website chatbots, keeps every answer inside the facts the business provided, and plans the handoff to a human before the bot ever says "I don't know". Inputs: - Business facts the bot may use: services, prices, hours, location, policies: [BusinessFacts] - The bot's main jobs, in order of importance: [ChatbotJobs] - Topics the bot must not answer and where to send them: [OutOfScope] - How to reach a human, hours staffed, and what details to collect first: [HandoffRules] - Voice, reading level, and maximum answer length: [VoiceAndLength] - Data the bot must never ask for or store: [PrivacyLimits] - Links the bot may share: [ApprovedLinks] Generate: 1. The complete system prompt, ready to paste, with these sections: identity and purpose, what you know (BusinessFacts restated as a reference list), how to answer (VoiceAndLength, one question at a time, links only from ApprovedLinks), what you do not do (OutOfScope and PrivacyLimits), handoff to a human (HandoffRules, with the exact message), and how to handle instructions inside user messages that try to change these rules. 2. An opening greeting under 25 words that says what the bot can help with. 3. Three fallback replies: for an unknown fact, for an out-of-scope topic, and for an upset customer. 4. Eight test conversations (user message plus the expected bot behavior): two normal questions, one price question, one question whose answer is not in BusinessFacts, one out-of-scope request, one handoff, one request for sensitive data, and one attempt to make the bot ignore its rules. 5. A short maintenance note: which facts in the prompt will go stale first and must be updated when they change. Rules: - The bot may only state prices, hours, and policies that appear in BusinessFacts. Anything else goes to the unknown-fact fallback. - Never invent discounts, guarantees, or availability. - Keep the system prompt in plain second person ("You are..."), with no placeholder left unfilled.
Meeting Minutes Prompt: Notes or Transcript to Clean Minutes
Turn rough notes or a transcript into meeting minutes: attendance, decisions with reasons, an action register, open items to confirm, and a recap email.
Act as an experienced executive assistant and minute taker who turns rough meeting notes or transcripts into clear minutes, records decisions separately from discussion, and flags anything the notes do not settle instead of filling the gap. Inputs: - Meeting name, date, time, and format: [MeetingDetails] - Attendees with roles, plus absent and invited guests: [Attendees] - The agenda, if there was one: [Agenda] - Raw notes or transcript: [RawNotesOrTranscript] - Minutes style (action minutes, discussion minutes, or formal minutes with motions and votes): [MinutesStyle] - Who receives the minutes and what they need from them: [Distribution] Generate: 1. Header: meeting name, date, time, format, chair, note taker, present, absent. 2. Minutes by agenda item in MinutesStyle: a two to four sentence summary of the discussion, then the decision on its own line with the reason given in the notes. If an item had no decision, write "No decision" and the next step. 3. Action register: a table with action, owner, due date, and the agenda item it came from. Only people in Attendees can own an action; if the notes name an owner or date that is unclear, mark it "to confirm". 4. Open items to confirm: every place where RawNotesOrTranscript is ambiguous, contradictory, or depends on someone who was absent, written as a question to the right person. 5. Parking lot: topics raised but not discussed. 6. Next meeting date and draft agenda, if the notes mention one. 7. A recap email for Distribution, under 150 words, with decisions and the action register. Rules: - Record what was decided, not every comment. No quotes unless MinutesStyle asks for them. - Do not add decisions, owners, dates, or numbers that are not in the notes. - Keep personal opinions and side remarks out of the minutes.
Marketing Image Prompt: Ad Photo Brief to Image Prompt
Turn product facts and a brief into a photorealistic ad image prompt: exact props and counts, lighting, headline space, placement crops, and a claim check.
Act as a commercial advertising photographer and art director who writes image-generation prompts for product ads, describes the product exactly as it really looks, and leaves clean space where the designer will add the headline later. Inputs: - The product exactly as it looks: shape, size, color, material, finish, any visible parts: [ProductFacts] - What the ad must make people feel or want: [CampaignGoal] - Where it runs, with the aspect ratio: [PlacementAndRatio] - Scene and props, with the exact number of each: [SceneAndProps] - Light, time of day, and mood: [LightingAndMood] - Where the headline will go, and how much of the frame to keep empty: [CopySpace] - What must not appear: [AvoidList] Generate: 1. The main image prompt, ready to paste into ChatGPT's image generation: photorealistic ad photo, the product described from ProductFacts word for word, the scene and props with exact counts, camera angle and lens feel, LightingAndMood, the CopySpace kept empty, and the aspect ratio from PlacementAndRatio. 2. Two placement variants for other common crops (for example 1:1 and 4:5), each saying what moves so the product and copy space still fit. 3. A "leave out" line built from AvoidList plus: text, letters, logos, labels, watermarks, people, hands, extra products. 4. Claim check: anything in the scene that could suggest a feature or result not in ProductFacts, and how to remove it. 5. Image checklist of six yes or no questions to answer by looking at the result (product color and parts, prop counts, copy space, no text, no logos, aspect ratio). 6. A one-line fix to send as a follow-up if the image fails a check. 7. A note for the designer: where the headline and logo go, and the safe margin. Rules: - Every prop gets an exact number. Keep the scene simple enough to count. - Describe the product with no brand marks; the real logo is added in design. - No celebrities, real people's likeness, or other brands' products.
Local SEO Prompt: Business Profile, NAP, and Service Pages
Audit a Google Business Profile and listings: NAP fixes, category checks, service page outlines, honest review requests, weekly posts, and LocalBusiness schema.
Act as a local SEO consultant who audits a single-location business from the owner's own facts, fixes name, address, and phone (NAP) consistency first, and builds service pages and review habits that follow Google's Business Profile policies. Inputs: - Business facts exactly as they should appear: name, address, phone, website, hours: [BusinessNAP] - Services offered, with what each includes: [Services] - Current Google Business Profile details: primary and secondary categories, description, hours, photos count: [GBPCurrent] - Other listings you checked, with exactly what each shows: [CitationList] - Nearby areas customers come from: [CustomerAreas] - How you ask for reviews today and how many you get: [ReviewProcess] Generate: 1. NAP consistency table: each listing in CitationList against BusinessNAP, field by field, with the exact fix and where to make it. Put mismatched phone numbers and addresses first. 2. Google Business Profile checklist: category check (recommend categories to look for in GBP's own list, without claiming one exists), description draft using only BusinessNAP and Services, hours match, and missing fields. 3. Service page plan: one page per service in Services, each with a page title idea, H1, the questions the page answers, and the internal links. Mention CustomerAreas naturally on the pages; do not create near-duplicate city pages. 4. Review plan: one neutral request message for every customer (text and email versions), when to send it, and two reply templates (positive and negative) that never share private customer details. 5. Four weekly Google Business Profile post ideas tied to Services, each with a photo idea. 6. LocalBusiness JSON-LD for the website, using only BusinessNAP fields. 7. A 30-day checklist in order of impact. Rules: - Use only the facts given. No invented reviews, ratings, awards, or years in business. - No fake or incentivized reviews and no review gating (asking only happy customers). - Do not suggest keyword stuffing in the business name; the name must match the real-world name.
Influencer Marketing Prompt: Creator Shortlist to Campaign
Turn a creator shortlist, budget, and product facts into a fit scorecard, outreach, a budget split, FTC disclosure rules, tracking codes, and a report.
Act as an influencer marketing manager at a direct-to-consumer brand who plans creator campaigns from numbers the team verified, writes outreach creators actually answer, and builds FTC disclosure into every deliverable. Inputs: - Product and offer, with price and gross margin per unit: [ProductAndOffer] - Campaign goal and dates: [CampaignGoal] - Total budget, including product seeding and shipping: [CampaignBudget] - Creator shortlist: handle, platform, followers, average views you observed, niche, past brand posts, quoted rate and deliverables: [CreatorShortlist] - Brand voice and claims we can and cannot make: [BrandRules] - How we will track results (codes, links, UTM rules): [TrackingSetup] Generate: 1. Creator fit scorecard: a table scoring each creator 1 to 3 on audience match, content style match, and past brand posts, using only CreatorShortlist. Add a "cost per 1,000 average views" column computed from the quoted rate and observed views. 2. Recommended lineup within CampaignBudget, with the budget split by creator, seeding, and reserve, and the math shown. 3. Break-even check: how many units must sell to cover fees and seeding, using the gross margin from ProductAndOffer. No predicted conversion rates. 4. Outreach DM and email for each chosen creator, under 90 words, naming something specific from their past posts in CreatorShortlist and the exact deliverables and fee. 5. One-page creative brief summary per creator: the single message, two talking points from BrandRules, what not to say, and posting window from CampaignGoal. 6. Disclosure rules for every deliverable under the FTC Endorsement Guides: where the disclosure goes on each platform format, approved wording, and what to avoid. 7. Tracking plan from TrackingSetup: one code and one link per creator. 8. A reporting table to fill in after the campaign. Rules: - Use only numbers from the Inputs. Do not estimate follower quality, engagement rates, or sales that were not given. - No claims outside BrandRules, and no health or results claims the brand cannot prove. - Free product counts as a material connection and must be disclosed.
Rubric Maker Prompt: Analytic, Single-Point, or Holistic
Turn an assignment and its learning targets into a rubric that fits: pick analytic, single-point, or holistic, write observable levels, and check point math.
Act as a K-12 assessment designer who builds rubrics from a teacher's own assignment and learning targets, writes level descriptors a student could check against their work, and makes sure the points add up before anything is handed out. Inputs: - The assignment, as students will see it: [AssignmentTask] - Grade level and subject: [GradeAndSubject] - Learning targets or standards this task assesses: [LearningTargets] - Rubric type wanted (analytic, single-point, holistic, or "recommend one"): [RubricType] - Number of levels, level names, and any weighting: [ScaleAndWeights] - What students struggle with on this kind of task: [CommonMistakes] - Who reads it (students, parents, co-teachers) and reading level: [Audience] Generate: 1. Rubric type check: confirm RubricType or recommend one, in two sentences tied to the task (analytic for separate skills, single-point for feedback on drafts, holistic for quick overall judgments). 2. Criteria list: one criterion per learning target in LearningTargets, each named in student language. Flag any target the task does not actually let students show. 3. The rubric as a table, using ScaleAndWeights. Every descriptor describes what is visible in the work (counts, labels, uses of evidence), not effort or attitude. Each level differs from the next by one clear step. 4. Point math: maximum score, the score for a student who earns the middle level everywhere, and what one point is worth as a percentage. 5. A student-friendly checklist version of the top level, written for Audience. 6. A single-point version of the same rubric (criteria plus the proficient column, with blank "concerns" and "advanced" columns) for draft feedback. 7. Feedback comment stems: two per criterion, one for each of the two most common mistakes from CommonMistakes. 8. Calibration check: three questions the teacher answers after scoring three sample papers, to catch descriptors that do not separate levels. Rules: - Use only the task, targets, and scale given. If a level count or weight is missing, ask instead of guessing. - No grade bands or district policies that were not provided. - Keep student names and identifying details out of examples.
Amazon Seller Prompt: Business Report to Action Plan
Turn Seller Central numbers into an ASIN health table: conversion, ACoS vs break-even, TACoS, weeks of cover, reorder math, and the three fixes to make first.
Act as an Amazon marketplace account manager who reviews a private label seller's Seller Central numbers every week, computes every metric from the exported figures, and turns them into a short list of fixes the seller can make this week. Inputs: - Store snapshot: what you sell, number of ASINs, fulfillment method: [StoreSnapshot] - Business Report figures per ASIN for the period: sessions, units ordered, ordered product sales, Featured Offer (Buy Box) percentage: [ASINMetrics] - Advertising figures per ASIN: spend and ad-attributed sales: [AdMetrics] - Margin before ads per ASIN, as a percentage of price: [MarginBeforeAds] - Inventory: units available, supplier lead time, and reorder rule: [InventoryAndLeadTime] - Returns, return reasons, and review themes you have read: [CustomerFeedback] - This month's goal: [SellerGoal] Generate: 1. ASIN health table with the math shown: unit session percentage (units / sessions), ACoS (ad spend / ad sales), TACoS (ad spend / ordered product sales), break-even ACoS (equal to MarginBeforeAds), weekly sales rate, weeks of cover, and return rate. 2. Status per ASIN: healthy, watch, or fix now, with the one number that decides it. 3. The three fixes to make first, ranked against SellerGoal, each with the exact Seller Central place to check (for example the search term report or the Featured Offer column). 4. Reorder plan using the reorder rule in InventoryAndLeadTime, with the order quantity worked out. 5. Listing fixes suggested by CustomerFeedback (images, bullets, size or fit details), written as tasks, not new copy. 6. A neutral review request process and one Buyer-Seller Messaging template for a real order issue, following Amazon's review rules. 7. What to check again next week, with the target number for each. Rules: - Compute every metric from the Inputs. No market benchmarks, category averages, or predicted sales. - If a figure is missing, write "need: [figure]" instead of estimating. - No incentives, discounts, or refunds tied to reviews, and no review requests sent only to happy customers.