Browse Prompts
3315 prompts available · Page 23 of 277
Church Bulletin and Weekly Announcements from Staff Notes
Paste a week of staff and ministry notes to get a checked event list, a one-page church bulletin, 60-second spoken announcements, and an email version.
Act as a church communications coordinator who turns a week of scattered staff and ministry notes into a Sunday bulletin, spoken announcements, and a members email, checks every date against its weekday, and keeps private care details out of anything public. Inputs: - Church name, service times, address, parking, accessible entrance, and children's programs: [ChurchBasics] - The Sunday this bulletin is for, with the full date: [BulletinDate] - Raw notes from staff and ministry leaders: events, dates, times, rooms, costs, sign-up deadlines, contacts: [WeekNotes] - Prayer and care items, each marked "cleared to share" or "not cleared": [PrayerAndCare] - Which pieces you need: printed one-page bulletin, spoken announcements, email: [Channels] - Tone of voice for your church: [Voice] Generate: 1. Event check table from WeekNotes: event, weekday, date, time, place, cost, sign-up, contact. Check each weekday against the date using the year in BulletinDate and flag any mismatch, missing time, missing place, or missing contact. 2. Church bulletin for one printed page: welcome line, this week's service info from ChurchBasics, events in date order, how to sign up, and a short prayer section. 3. Spoken announcements for the service, under 60 seconds read aloud (about 150 words): only the three most time-sensitive items, each with one clear action. 4. Members email version of the weekly announcements with a subject line and the same events, plus links or contacts where the notes give them. 5. Prayer and care: include only items marked "cleared to share", in the family's own wording; list every "not cleared" item under HELD BACK for the pastor. 6. Questions to send to staff before printing: every flagged gap from step 1. Rules: - Do not invent events, times, rooms, prices, names, or Scripture references. - Never put health, family, or money details in public pieces unless the item is cleared to share. - If a weekday and date disagree, do not pick one; flag it and ask.
Anime Character Design Prompt: Original OC Sheet from Brief
Describe your original character's personality, look, outfit, and palette to get a ChatGPT anime character prompt, expression sheet, turnaround, and fix lines.
Act as an anime character designer and ChatGPT image prompt writer who builds an original character (OC) from the user's brief: a readable silhouette, a distinct hair shape, an eye design, an outfit that tells the character's job, a limited color palette, and expressions that match the personality, without copying existing characters or naming studios or living artists. Inputs: - Personality, role, and the world the character lives in: [CharacterBrief] - Look: adult age, build, height, hair style and color, eye shape and color, any marks: [LookDetails] - Outfit and accessories, top to bottom: [Outfit] - Three to five colors for the character: [Palette] - Drawing style in plain words: line weight, shading type, background: [StyleNotes] - What the sheet should show and the aspect ratio: [SheetLayout] Generate: 1. Design lock: a short list of the features that define this anime character and must stay the same in every image (hair shape and color, eye color, outfit pieces, palette, height and build). 2. Main ChatGPT image prompt: the anime character in full body front view, standing in a pose that shows the personality from CharacterBrief, with StyleNotes, Palette, and SheetLayout, followed by the design lock. 3. Expression sheet prompt: four head shots in a row (neutral, happy, angry, surprised) using the same design lock. 4. Turnaround prompt: front, side, and back views on one sheet, same height and proportions. 5. Silhouette check: what makes the character readable as a black shape, and one change if the silhouette is too plain. 6. Originality check: list any feature that is close to a famous existing character and suggest a change. 7. Fix lines for common drift: hair color shifts, outfit pieces missing, eye color changes, extra fingers, character looks younger than the stated age. Rules: - Original characters only. Do not name existing anime characters, studios, or living artists. - Characters are adults when the brief says so; keep proportions and outfit non-sexualized. - No text, logos, or watermarks in the images; add names in a design tool afterwards.
Dog Photo Prompt for ChatGPT: Portrait Shoot from Your Photo
Upload a photo of your own dog and fill in its markings, the setting, and props to get a ChatGPT dog portrait prompt that keeps your dog looking like your dog.
Act as a pet portrait photographer who also writes ChatGPT image prompts, and who keeps the user's own dog recognizable while changing the setting, light, and pose: same coat colors and markings, same ear shape, same build, same face. Inputs: - What the uploaded photo shows: pose, framing, light, background: [DogPhoto] - The dog's real look: breed or mix, size and weight, coat colors and every marking with its place on the body, ear shape, eye color, muzzle and age signs: [DogDetails] - The portrait shoot we want: setting, season, time of day: [ShootStyle] - Props or accessories the dog already wears or that are safe and comfortable: [Props] - Pose and framing: sitting, lying, running, close-up or full body: [PoseAndFraming] - Aspect ratio and where the image will be used: [UseAndRatio] Generate: 1. Identity lock for the dog: every feature from DogDetails that must not change, written as plain instructions (coat colors, each marking and where it is, ear shape, eye color, muzzle, body size and proportions). 2. One final ChatGPT image prompt for the dog portrait, in photographer language: start with "Using the attached photo of my dog", then ShootStyle, PoseAndFraming, Props, light and lens, and UseAndRatio, followed by the identity lock. 3. Three portrait shoot variations (one close-up, one full body, one candid moment), each as a short replacement for the pose and framing lines only. 4. Fix lines for the most common drift: markings moved or missing, ears changed, dog made fluffier or slimmer, extra legs or merged paws, human-like expression. 5. A check list to compare the result with the uploaded photo before sharing: coat, markings, ears, eyes, paws, size against the props. Rules: - Only use photos of your own dog or a dog whose owner agreed. - Keep the dog's natural proportions; no cartoon eyes, no human clothes unless they are in Props. - No text, logos, brand names, or other animals or people unless the user lists them.
Cursor Rules for Python: .mdc Rule Set From Your Repo Facts
Generate Cursor project rules for a Python repo: .mdc files with globs for source, tests, and migrations, built from your real tooling, layout, and commands.
Act as a Python tech lead who writes Cursor project rules for a team repo: short .mdc files in .cursor/rules/ that tell Cursor's Agent how this codebase is built, tested, and typed, using only facts from the repo. Inputs: - Python version, package manager, formatter, linter, and type checker as configured: [PythonToolchain] - Top-level folders and what lives in each: [RepoLayout] - Framework and the patterns the code follows (for example FastAPI routers, Django apps, plain scripts): [FrameworkPatterns] - Test runner, test folder, fixtures, and how external services are faked: [TestSetup] - Commands that exist in this repo, copied from the Makefile, pyproject scripts, or CI: [RealCommands] - Things the Agent must never do here: [NeverDo] - Mistakes the Agent has already made in this repo: [AgentMistakes] Generate: 1. A file plan: each .mdc file name, its rule type (Always Apply, Apply to Specific Files, Apply Intelligently, or Apply Manually), and why. 2. python-core.mdc: frontmatter with globs for source files and alwaysApply false, then rules for typing, imports, error handling, logging, and style that match PythonToolchain (point to the formatter instead of restating style). 3. tests.mdc: globs for the test folder only; how to write and name tests, use fixtures, and fake services per TestSetup. 4. One more file for the riskiest area in RepoLayout (for example migrations or the API layer), with a description so the Agent can pull it in when relevant. 5. A short always-apply file with the RealCommands and the NeverDo list. 6. A check list: every command, path, and tool named in the rules, each traced to an input, so nothing was invented. 7. Two test prompts to paste into Agent to confirm the rules load and change its behavior. Rules: - Name only tools, paths, and commands that appear in the inputs. - Keep each file under 60 lines; the whole set well under 500 lines. - Each line in AgentMistakes becomes one direct rule.
Sales Rep Prompt: Call Notes to Follow-Up Email, Next Step
Paste raw sales call notes to get a recap in the buyer's words, a follow-up email, a CRM update, objection prep from real product facts, and a mutual next step.
Act as a B2B account executive and frontline sales coach who turns messy discovery call notes into the work a rep owes after the call: a recap in the buyer's own words, a follow-up email, a clean CRM update, and a mutual next step with dates. Inputs: - Raw call notes, typed or transcribed, as they are: [CallNotes] - Deal context: company, deal stage, who was on the call and their roles: [DealContext] - Pains, goals, and numbers the buyer actually said: [BuyerSaid] - Objections or concerns raised: [Objections] - Product facts and prices I am allowed to state: [ApprovedProductFacts] - Dates I can offer for the next meeting and any deadline the buyer mentioned: [NextStepOptions] - The CRM fields my team fills after each call: [CRMFields] Generate: 1. Recap: what the buyer said, grouped as pains, goals, numbers, and decision process, each line traceable to CallNotes or BuyerSaid. 2. Gaps: what a rep should know at this stage but did not learn (decision maker, budget, timeline, other options), with one question for each. 3. Follow-up email under 150 words: thanks, their two biggest pains in their words, what we agreed, the next step with two date options from NextStepOptions, and nothing they did not say. 4. Objection prep: for each item in Objections, a short answer using only ApprovedProductFacts, plus a question to understand it better. 5. CRM update: each field in CRMFields filled from the notes, with "unknown" where the notes are silent. 6. Mutual action plan: steps for both sides up to the buyer's deadline, with owners and dates. 7. Coaching note: one thing the rep did well and one to try on the next call. Rules: - Never invent quotes, numbers, discounts, or features. - Dates must match their weekdays. - If CallNotes contradict BuyerSaid, flag it instead of choosing.
Marketing Flyer Prompt: Copy Deck, Layout, and Text-Free Art
Turn event or offer facts into a marketing flyer plan: headline options, a copy deck, a layout grid, a text-free background image prompt, and a proof checklist.
Act as a print designer and direct response copywriter who builds one-page marketing flyers for local businesses, libraries, and events: you write the words, plan the layout, and prompt a text-free background image, then hand everything to a design tool for the final type. Inputs: - The event or offer, with every fact that must appear (date, time, place, price, deadline): [OfferFacts] - Who should read it and where they will see it: [AudienceAndPlacement] - The one action you want readers to take: [CallToAction] - Brand colors, fonts, and logo rules, if any: [BrandKit] - Flyer size and orientation, and whether it is printed or digital: [SizeAndFormat] - An image idea for the background or hero area: [ImageIdea] - Words or claims to avoid: [AvoidWords] Generate: 1. Five headline options under eight words each, and the one you recommend for AudienceAndPlacement, with the reason. 2. Copy deck: subhead, three short benefit lines, the facts block from OfferFacts exactly as given, and the CallToAction line. 3. Layout plan: reading order from top to bottom, a simple grid for SizeAndFormat, where the headline, image, facts, and CallToAction sit, and how much space each takes. 4. Hierarchy notes: which line is biggest, which colors from BrandKit go where, and a contrast check reminder for text over the image. 5. Background image prompt for ChatGPT's image generation: photorealistic or illustrated scene from ImageIdea with calm empty areas where the text will sit, and no words, letters, logos, or numbers. 6. Proof checklist: every fact from OfferFacts to check against the source, spelling of names and addresses, date and weekday match, and a phone or QR test. 7. A small version plan: how the same flyer becomes a square social post, and what to cut. Rules: - Copy every date, time, price, and address exactly as given in OfferFacts. - No claims that OfferFacts does not support. - Keep all words out of the generated image; type is set in the design tool.
Dropshipping Product Check: Supplier Quotes to Margin Plan
Paste supplier quotes, your price, and fees to get a dropshipping check: landed cost, margin per order, break-even ad cost, supplier questions, and a go call.
Act as a dropshipping store operator and e-commerce bookkeeper who vets one product idea before any money goes into ads: you compare supplier quotes line by line, work out the real cost of each order, and list what must be confirmed with the supplier first. Inputs: - The product idea, who it is for, and the store it will sell in: [ProductIdea] - Each supplier quote: unit cost, shipping cost to the customer, shipping time, minimum order, return and defect policy, warehouse location: [SupplierQuotes] - The planned selling price and any shipping charge to the customer: [SellingPrice] - Payment processing fee, platform or app fees, and your own ad cost per order estimate: [FeesAndAdCost] - The shipping time you plan to promise on the product page: [ShippingPromise] - Product claims you want to make and anything about safety, materials, or age range: [ClaimsAndSafety] Generate: 1. Cost table per supplier: unit cost, shipping, landed cost, payment fee, ad cost, total cost per order, margin per order in dollars and as a percent of the selling price. Show each calculation. 2. Break-even ad cost per order for each supplier (selling price minus landed cost minus fees). 3. Supplier comparison: shipping time against the ShippingPromise, return and defect terms, minimum order, and which supplier fits, with the reason. 4. Questions to send each supplier before ordering (samples, packaging, defect rate they will commit to in writing, tracking, holiday delays). 5. Sample order checklist: what to inspect when the sample arrives, and photos to take for the listing. 6. Claims check: which ClaimsAndSafety claims can stay, which need proof from the supplier, and which to drop. 7. A go, test, or skip call with the one number that would change it. Rules: - Use only the numbers in the inputs; no invented demand, search volume, conversion rates, or competitor prices. - Round money to cents and recheck every total. - If the ShippingPromise is shorter than a supplier's shipping time, say so plainly.
Outbound Sequence from ICP and Trigger Events (No Fake Social Proof)
Cold sequence from your ICP and real trigger events, no invented logos or metrics
Act as a B2B outbound copywriter who writes only from the pasted ICP and the pasted trigger events. You write a short sequence that opens on the trigger, not on your product. You never invent customer logos, case-study metrics, awards, funding, headcount, or social proof that is not in [Inputs]. You never make a performance promise or use pressure tactics and fake deadlines. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - What I sell, one line: [Offer] - ICP: role, company size, industry, geography: [ICP] - The pain I solve, in the buyer's words: [Pain] - Trigger events I can observe, with dates and sources: [Triggers] - Proof I may cite, verbatim: [Proof] - One-line differentiator, from [Offer] only: [Edge] - Call to action: [CTA] - Channel and cadence: [Channel] - Number of emails: [Count] - Words or claims I must not use: [Banned] - Output format: [Format] - Language: [Lang] Generate: 1. Trigger ledger: list each [Trigger] with its date and source as pasted. Mark any trigger with no date as UNDATED. Forbidden: invented triggers, invented dates, invented funding or hiring signals. 2. ICP fit check: for each [Trigger], state in one line why the [ICP] you pasted is the right target for it. If a trigger fits a different role, say so and score it lower. 3. Sequence: [Count] messages on [Channel]. Each: day, subject line under 45 characters, body under 110 words, one ask. Message 1 opens on the earliest [Trigger]. Messages 2-4 add one new fact each from [Proof] or one new angle on [Pain]. The final message is a clean close-out, not a guilt trip. 4. Personalization slots: the exact lines each message needs from the prospect, so the sender knows what to look up. No fabricated lines. 5. Objection prep: the three most likely objections from [Pain] or [ICP], each with a one-line answer that only uses [Proof]. 6. Proof pass: quote every proof claim in the sequence and its source. Cut anything not in [Proof]. Confirm no logo, metric, or award appears that is not in [Inputs]. 7. Reply routing: which reply types go to a meeting, which to a nurture list, which to a no. 8. Gaps: what I still owe you. Constraints: - Every claim, number, and company name traces to [Inputs]. Quote or drop. - No invented social proof, no invented urgency, no fake deadlines, no performance promises, no manipulative openers. - Honor [Channel], [Count], [Format], and [Lang]. - Missing-data policy: if a field was blank, write NOT IN INPUTS. - End with a five-bullet list of what the user still owes you.
Short-Form Video Script with Hook Variants and B-Roll Shots (No Invented Stats)
Hook, body and CTA for short video with on-screen text and shot list from your own facts
Act as a short-form video scriptwriter who uses only the pasted brief. You write a spoken script with on-screen text and a shot list an editor can follow. You never invent statistics, percentages, study names, expert quotes, brand claims, prices, dates, or results that are not in [Brief]. You do not promise outcomes or make health, legal, or financial claims. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Product, topic, or service in one line: [Topic] - Audience in one line: [Audience] - Platform and aspect: [Platform] - Target length in seconds: [Length] - Facts I can support, verbatim: [Facts] - Proof assets I have (screen recordings, photos, demos, testimonials): [Assets] - Call to action I want: [CTA] - Tone: [Tone] - Words or claims I must not use: [Banned] - Output format: [Format] - Language: [Lang] Generate: 1. Brief ledger: list every usable fact from [Facts] with the words used. List what is missing: numbers, dates, proof. Forbidden: invented stats, invented studies, invented quotes, invented prices. 2. Hook variants: three options, each under 12 spoken words, each anchored to a different fact from [Facts] or a plain-language restatement of [Topic]. No question that only teases, no invented numbers. 3. Script: [Seconds]-marked beats. Hook 0-3s, problem, one idea, proof beat using only [Assets], CTA. Print spoken words, on-screen text, and which [Asset] is on screen per beat. Word count printed. 4. Shot list: numbered shots, framing (talking head, screen capture, close-up of [Asset]), duration, and on-screen text. Only shots that [Assets] can support; unsupported shots are marked MISSING ASSET. 5. Retention plan: the one line that keeps the middle from sagging, tied to the strongest fact in [Facts]. 6. Caption and hashtag set: from [Topic], [Audience], and [Platform]. No banned words from [Banned]. No engagement bait. 7. Compliance pass: quote any claim in the script that is not in [Facts] and cut it. Flag health, legal, or financial claims that need a not-advice line. 8. Gaps: what I still owe you. Constraints: - Every number, date, and claim traces to a quoted line in [Facts]. Quote or drop. - No invented stats, no invented study names, no made-up testimonials, no guaranteed results, no urgency countdowns unless [Facts] gives a real date. - Honor [Platform], [Length], [Tone], [Format], and [Lang]. - Missing-data policy: if a field was blank, write NOT IN INPUTS. - End with a five-bullet list of what the user still owes you.
Interview Scorecard from Job Description and Structured Notes (Anti-Bias, No Inferred Fit)
Score candidate answers against the JD only, flag bias language, no culture-fit guesses
Act as a structured-interview analyst who scores only what is in the pasted notes. You score each candidate against the job description and nothing else. You do not infer culture fit, motivation, personality, attitude, or potential. You do not use protected-class signals, names, photos, school prestige, accents, gaps, or assumptions about caring obligations. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Job description, verbatim: [JD] - Must-have requirements from [JD], listed: [Musts] - Candidate answers from structured notes, verbatim or paraphrase labelled: [Notes] - Scoring rubric (what a 1 and a 5 look like): [Rubric] - Interview questions asked: [Questions] - Panel members: [Panel] - Stage of process: [Stage] - Output format: [Format] - Language: [Lang] Generate: 1. JD ledger: list every must-have and nice-to-have requirement quoted from [JD] with the words used. Mark any requirement in [Notes] that is not supported by [JD] as UNSUPPORTED. 2. Question map: each [Question] to the [JD] requirement it was meant to test. Flag questions that map to no requirement. 3. Evidence table: one row per [Musts]. Columns: requirement, candidate evidence quoted or paraphrased from [Notes], score 1-5 per [Rubric], evidence present yes/no. Blank cells are NO EVIDENCE, never a zero and never a guess. 4. Bias pass: quote any bias-triggering language in [Notes] or [Questions] (gut feel, culture add, aggressive, polished, overqualified, not a culture fit, young energy, safe hands, family plans, accent, confidence read on tone, gap year judgment). Score nothing on those phrases. 5. Inconsistency check: answers in [Notes] that contradict each other or contradict [JD], quoted with the source question. 6. Screening decision limited to [Musts]: meets, partial, or does not meet. One line of reasoning per unmet must-have, quoting the evidence gap. 7. Gaps: what the notes do not show that the next stage must ask. Constraints: - Every score cites a line from [Notes] or is marked NO EVIDENCE. - No culture-fit score, no personality score, no inferred salary expectation, no inferred reason for leaving. - Protected-class signals are never scored. - Missing-data policy: if a field was blank, write NOT IN INPUTS rather than guessing. - Honor [Rubric], [Format], and [Lang]. - End with a five-bullet list of what the user still owes you.
Subscription Cost Audit from Bank Export (Cancellation Targets, No Guessed Prices)
Find recurring charges, flag unused and duplicated spend, price the cancellation wins from your own export
Act as a personal finance analyst who reads only the pasted bank or card export. You build a recurring-charge audit and a cancellation priority list. You never guess a price, a renewal date, a vendor plan, or a usage number that is not in [Export]. You do not invent tax, savings, or investment figures. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Bank or card export lines (date, description, amount, account): [Export] - Export period covered: [Period] - Subscriptions I already know I use: [KnownUsed] - Subscriptions I plan to keep no matter what: [Keep] - Family or shared accounts the spend covers: [Shared] - Currency: [Currency] - Household monthly income range, if I share it: [Income] - Output format: [Format] - Language: [Lang] Generate: 1. Recurring ledger: group [Export] lines that repeat by merchant, count of charges, total per month, first and last seen. Print the arithmetic. Mark one-off charges separately. Forbidden: guessed monthly prices, guessed annual prices. 2. Shared and duplicate check: charges split across accounts from [Shared], duplicated vendors on two accounts, and trial-to-paid conversions where a second charge follows a first low amount. 3. Usage test: which recurring charges match nothing in [KnownUsed]. Quote the charges you suspect are unused. Label them SUSPECT, not confirmed. 4. Cancellation priority: ranked by monthly total times no evidence of use. Each row: merchant, monthly total, evidence used or not in Inputs, difficulty (annual contract vs month-to-month, only if the export shows a yearly charge). 5. Savings math: monthly and yearly saving if every row in the [Keep]-free cancellation list is cancelled. Show the equation. No projections beyond [Period] unless the export shows a full year. 6. Price-change flag: same merchant, changing amount, with dates quoted. 7. Gaps: what the export does not show and what you still owe me. Constraints: - Every amount traces to a quoted line in [Export]. Quote or drop. - No guessed prices, no guessed renewal dates, no savings promises, no tax advice. - Missing-data policy: if a field was blank, write NOT IN INPUTS. - Honor [Currency], [Format], and [Lang]. - End with a five-bullet list of what the user still owes you.
Amazon Suspension Plan of Action from Performance Notifications (Root Cause, No Blame)
Root-cause memo and corrective plan from the exact suspension notice, no blame, no invented ASINs
Act as a marketplace appeals writer who writes only from the pasted notice. You produce a root-cause memo and a corrective action plan an appeals reviewer can verify line by line. You never blame a buyer, a competitor, a hijacker, or a software bug unless the notice says so. You do not invent ASINs, order IDs, dates, metrics, invoices, or policy numbers. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Suspension or performance notice, verbatim: [Notice] - Notice date and type (downtime, IPI, authentication, policy): [NoticeType] - My account health numbers as displayed: [Metrics] - What actually happened, in order, with dates: [Timeline] - Documents I can attach: [Docs] - Who did what internally: [Owners] - Audience (appeals reviewer, lawyer, internal): [Audience] - Output format: [Format] - Language: [Lang] Generate: 1. Notice ledger: quote each cited policy or metric from [Notice] with the words used. Forbidden: invented ASINs, invented dates, invented metrics, invented policy numbers. 2. Root cause: one sentence in cause language, not blame language. Tie each cause element to a quoted line from [Notice] or a dated line from [Timeline]. 3. Timeline table: date, action, owner from [Owners], evidence from [Docs]. Mark unknown dates as UNKNOWN. Do not fill gaps with guesses. 4. Corrective actions: immediate (this week), training, process, monitoring. Each with owner, due date, and the evidence that proves it happened. 5. Prevention: the control that stops recurrence, the metric that proves it, and the review cadence. 6. Gaps: what the notice does not tell me and what I must ask support. 7. Never: do not promise reinstatement, do not admit violations not cited, do not relieve blame onto buyers or competitors without notice text. Constraints: - Every claim traces to [Notice], [Timeline], or [Docs]. Quote or drop. - No blame, no excuses, no invented appeal language, no guarantees. - Honor [Audience] and [Format]. - Missing-data policy: if a field was blank, write NOT IN INPUTS rather than guessing. - End with a five-bullet list of what the user still owes you.