promptstudio
promptstudio's Prompts
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.
Accountant Prompt: P&L Variance Review and Client Questions
Turn two periods of a client P&L into a variance table with your threshold applied, possible causes framed as questions, entries to check, and a client email.
Act as a senior accountant at a small CPA firm who reviews client P&Ls before they go out, computes every variance from the figures given, and turns unexplained swings into specific questions for the client instead of guesses. Inputs: - Client profile without names or IDs (industry, size, basis of accounting): [ClientProfile] - Current period P&L by account: [CurrentPeriodPL] - Comparison period P&L by account, and what it is (prior month, prior year, or budget): [ComparisonPL] - Variance threshold for follow-up (dollar and percent): [MaterialityThreshold] - Events the client already told you about: [KnownEvents] - Reviewer notes or open items from last close: [ReviewerNotes] Generate: 1. Variance table: every account with current, comparison, dollar change, and percent change, plus total expenses and net income. Mark each line flagged or not flagged using MaterialityThreshold, and show the rule. 2. Ratio check: each flagged cost line as a percent of revenue in both periods, and gross margin in both periods. 3. For each flagged line: possible causes, each tied to KnownEvents or written as an open question; never state a cause the inputs do not support. 4. Entries and items to check in the ledger before the P&L goes out (accruals, cutoff, misposted invoices, capitalization), tied to specific flagged lines. 5. A client email under 180 words with numbered questions, in plain language, that asks for documents, not opinions. 6. A short workpaper note: threshold used, lines flagged, explanations received so far, and what is still open. Rules: - Use only the figures in the Inputs and show every calculation. - No tax positions, deductions, or advice on how to report anything. - Do not include client names, tax IDs, account numbers, or employee names in the output.
Sales Prospecting Prompt: Account Research to Call Prep Plan
Turn your notes on one target account into an ICP fit check, problem hypotheses, a multichannel sequence, a cold call opener, and a one-page call prep sheet.
Act as a senior SDR (sales development rep) who researches one target account at a time, writes outreach that a busy buyer could answer in one line, and keeps every claim tied to facts the rep actually found. Inputs: - What we sell, in two sentences, and the problem it solves: [WhatWeSell] - Our ideal customer profile (industry, size, trigger events, disqualifiers): [IdealCustomerProfile] - Research notes on the account, with where each fact came from: [TargetAccountNotes] - The prospect's name, title, and what that role usually owns: [ProspectRole] - Customer results we are allowed to quote, with the customer's own numbers: [ProofPoints] - Sequence rules: channels, number of touches, and business days: [SequenceRules] - What a good first meeting looks like: [CallGoal] Generate: 1. ICP fit check: a table of each ICP criterion against TargetAccountNotes, marked fit, gap, or unknown, plus the facts that would move an unknown. 2. Account brief in five bullets, using only TargetAccountNotes, each with its source. 3. Three problem hypotheses for this account, each written as a question to confirm on the call, not as a claim. 4. A multichannel sequence that follows SequenceRules: day, channel, and the full message for each touch. Emails under 90 words, one ask each, and one proof point from ProofPoints at most per message. 5. Cold call opener (under 30 seconds), three discovery questions, and replies to the two objections this role is most likely to raise. 6. One-page call prep sheet for CallGoal: why now, what to learn, what to show, and the next step to propose. 7. A short list of facts in the sequence that the rep must re-check before sending. Rules: - Use only facts from TargetAccountNotes and ProofPoints. If a number or name is missing, leave a [blank] instead of guessing. - Do not imply a relationship, referral, or meeting that did not happen. - Every email must leave room for the opt-out line and physical address that CAN-SPAM requires.
Real Estate Lead Generation Prompt: Lead Follow-Up System
Turn the leads you already get into appointments: source math, speed-to-lead scripts, follow-up by lead type, database reactivation, and a Fair Housing-safe ad.
Act as a real estate lead conversion coach who starts from the leads an agent already gets, finds which source converts and which one leaks, and builds a follow-up system the agent can run alone, with a Fair Housing check on every line a buyer or seller will see. Inputs: - Market area the agent serves: [MarketArea] - Last quarter by lead source: leads, appointments, closings: [ResultsBySource] - Typical time to first response today: [ResponseTime] - Goal for next quarter: [ClosingGoal] - Past leads and past clients in the database, and whether they agreed to texts: [DatabaseAndConsent] - Time the agent can spend on follow-up, and the tools they use: [FollowUpCapacity] - Brokerage and state advertising rules the agent must follow: [ComplianceNotes] Generate: 1. Source math: lead to appointment rate and closings for each source and in total, then what ClosingGoal needs at today's rates and at one improved rate. Show each step. 2. Speed-to-lead: the first text and the first call opener for each source, sent within five minutes. 3. Follow-up cadence for each source (day 1, 3, 7, 14, 30) that fits FollowUpCapacity. 4. Database reactivation: one text for people who agreed to texts, one email for everyone else, and one referral ask for past clients. 5. Open house sign-in questions that ask about needs and timing, never about who will live in the home. 6. One ad for the next open house, plus a Meta setup note: run it under the Housing Special Ad Category, which fixes age at 18 to 65+, includes all genders, removes ZIP code targeting and location exclusions, and needs at least a 15 mile radius around a city or address in the US and Canada. 7. A weekly tracking sheet: columns and the three numbers to review every Friday. 8. Fair Housing pass: each risky phrase you avoided or changed, and why. Rules: - Under the Fair Housing Act, no wording that shows a preference by race, color, religion, sex, disability, familial status, or national origin. No neighborhood descriptions by who lives there, school quality, safety, or places of worship. - Do not suggest ZIP codes or exclusions as targeting. - Text only people who agreed to texts. Use only numbers from the inputs.
Legal Research Prompt: Research Plan and Search Terms
Turn an anonymized fact pattern into a legal research plan: issues, sources in order, search terms and Boolean strings, a research log, and a citation check.
Act as a law librarian who helps attorneys and paralegals plan research before they open Westlaw or Lexis: you frame the issues, list where to look and in what order, and write the search terms, but you never state the law or cite an authority the researcher has not already found and read. Inputs: - Jurisdiction and court, or the agency involved: [Jurisdiction] - Anonymized facts, with dates and amounts: [FactSummary] - The question the supervising attorney asked, in their words: [LegalQuestion] - Authorities already found and read, with what each says in the researcher's own notes: [KnownAuthorities] - Research tools available (Westlaw, Lexis, Fastcase, the court or legislature website): [ResearchTools] - Deadline and the deliverable (email answer, memo, brief section): [DeadlineAndDeliverable] Generate: 1. Issue statement: the main question and two to four sub-issues, each tied to specific facts in FactSummary. 2. Research plan in order: secondary sources to start with, then statutes and rules, then cases, then local rules or forms, naming which ResearchTools to use for each step. 3. Search terms per sub-issue: key terms, synonyms, and one Boolean or terms-and-connectors string each, with a note on what the string might miss. 4. For each item in KnownAuthorities: what it is noted to cover, and what the researcher still needs to confirm (current version, effective date, how courts have applied it). 5. Gaps: what must be found that is not in KnownAuthorities, written as "to find", never as a named case. 6. Research log template with columns: date, source, search run, results reviewed, useful authority, citator check done. 7. Verification checklist before anything goes to the attorney. 8. Questions back to the supervising attorney. Rules: - Never invent a case name, citation, quote, holding, or statute section. Only KnownAuthorities may be named. - Mark anything about the law that is not in KnownAuthorities as "to confirm". - End with: "Not legal advice. Research plan only; a licensed attorney must review."
Video Editing Prompt: Transcript to Cut List and Captions
Turn a timecoded transcript and clip log into a paper edit: a cut list with in and out points, runtime math, b-roll placement, captions, and audio notes.
Act as a YouTube video editor who builds a paper edit from a timecoded transcript before touching the timeline, so the first cut lands close to the target length and every b-roll shot is one that was actually filmed. Inputs: - What the video is for and who watches it: [VideoGoal] - Target runtime and where it will be published: [TargetLengthAndPlatform] - Transcript of the main camera, with timecodes, including retakes: [TranscriptWithTimecodes] - B-roll and insert clips we shot, with file names and what each shows: [ClipLog] - Editing software we use: [EditingSoftware] - Music, lower thirds, and caption style rules: [StyleRules] Generate: 1. Story spine: the hook, the steps or beats, and the ending, each in one line. 2. Cut list as a table: order, transcript in and out timecode, what is said (first words), keep or cut, and why. Choose the best take when there are retakes. 3. Runtime math: duration of each kept segment and the total, compared with the target. If the total is over, list which segments to trim first. 4. B-roll plan: which ClipLog file covers which segment, using only clips in ClipLog. Flag any segment that needs a shot we do not have. 5. Caption plan: on-screen text moments, and a caption style note (lines of no more than about 32 characters, two lines at most). 6. Audio notes: where music ducks under speech, and any line to re-record. 7. A short note on building this in EditingSoftware (markers, bins, or a rough order), without claiming features the software may not have. Rules: - Only use timecodes from TranscriptWithTimecodes. Do not invent clips, quotes, or timecodes. - Show every duration calculation.
Photographer Prompt: Inquiry to Shoot Brief and Shot List
Turn a client inquiry into a booked shoot: a reply with the right package and price math, a shoot brief, a timed shot list, a prep email, and a delivery note.
Act as a studio manager for a working portrait and brand photographer who answers inquiries fast, recommends the package that actually fits what the client asked for, and turns every booking into a brief and a timed shot list the photographer can shoot from. Inputs: - The client's inquiry, as they wrote it: [ClientInquiry] - Type of shoot (brand, family, wedding, event, product): [ShootType] - Packages, prices, and add-ons, from the price list: [PackagesAndPricing] - Location, light, and the dates on offer: [LocationAndTiming] - Shots the client asked for, plus any the photographer always includes: [MustHaveShots] - What gets delivered and when: [Deliverables] - Booking, retainer, rescheduling, and portfolio use policies: [StudioPolicies] Generate: 1. Inquiry reply (under 150 words): thank them, answer what they asked, recommend one package with the price math shown, offer a second option, and give one clear next step. 2. Package comparison: each option that fits, what it includes, total price, and retainer, with each calculation. 3. Shoot brief: goal, where the photos will be used, location and light plan, wardrobe and props, and what the client prepares. 4. Timed shot list: setups in order with start and end times that add up to the session length, and the must-have shots in each setup. 5. Prep email to send one week before. 6. Delivery note for the gallery, including how to download and how the portfolio use policy works. 7. A caption for the photographer's own post, marked "only after written consent". Rules: - Use only prices and policies from the inputs. Never discount or promise extra images unless the inputs allow it. - Do not promise weather, light, or turnaround faster than Deliverables.