promptstudio
promptstudio's Prompts
Product Marketing Prompt: Feature Launch Messaging Brief
Turn release notes, customer quotes, and win/loss notes into a launch messaging brief: claim sources, positioning, message house, launch tier, and channel copy.
Act as a product marketing manager who turns release notes, customer interview quotes, and win/loss notes into a feature launch messaging brief, ties every claim to a source, and picks the launch tier by the team's own rules. Inputs: - Release notes with what ships, who gets it, and the date: [ReleaseNotes] - Target segment and the job they are trying to get done: [TargetSegment] - Customer quotes from beta or interviews, with who said them: [CustomerQuotes] - What customers use today instead: [Alternatives] - Win/loss notes from sales: [WinLossNotes] - Our launch tier rules: [LaunchTierRules] - Channels for this launch: [Channels] - Claims and proof that legal has approved: [ApprovedProof] Generate: 1. Claim inventory: each capability in ReleaseNotes, the customer value it creates, and its source (release note line, quote, or win/loss note). Claims with no source go to a "needs proof" list. 2. Positioning statement: for the TargetSegment, who need the job done, the feature is the one that does X, unlike the Alternatives, built only from the inventory. 3. Message house: one umbrella message and three pillars, each pillar with one proof point from ApprovedProof or the claim inventory. 4. Launch tier: the tier from LaunchTierRules with the rule that decides it, and what that tier includes. 5. Channel copy for each item in Channels, short and specific, using approved proof only. 6. Objection handling: the top objections from WinLossNotes with a two-sentence answer each. 7. Needs proof and open questions: claims that need data, legal review, or product answers before launch. Rules: - No invented metrics, customer names, or competitor claims; a quote from one customer is presented as one customer's experience, not a typical result. - Advertising claims must be truthful and backed by evidence (FTC Act Section 5); flag anything that needs substantiation.
Financial Freedom Prompt: Target Number and Timeline Plan
Turn your own income, spending, debts, and savings into a financial freedom number, a debt payoff order, timeline scenarios, and questions for an advisor.
Act as a personal finance planning coach who turns a household's own numbers into a financial freedom target, a debt payoff order, and timeline scenarios, shows every calculation, and sends the big decisions to a licensed professional. Inputs: - Monthly take-home pay after tax: [TakeHomePay] - Monthly spending by category, not counting debt payments: [MonthlySpending] - Debts with balance, interest rate (APR), and minimum payment: [DebtList] - Savings and investment balances, with which ones count toward the target: [CurrentSavings] - What financial freedom means to me, in monthly dollars: [FreedomDefinition] - The multiple of yearly spending I want to test as my target: [TargetMultiple] - Yearly growth rate I want to test, as my own assumption: [AssumedReturn] - Spending cut I am willing to try: [CutToTest] Generate: 1. Monthly cash flow: take-home pay minus total spending minus debt minimums, with the sum of each list shown, and the monthly surplus. 2. Freedom number: FreedomDefinition times 12 times TargetMultiple, labeled as my assumption, then the gap after the savings that count. 3. Debt order: debts ranked by APR (highest first) and the month each is paid off if the whole surplus goes to the top debt and freed minimums roll down, with interest included and rounded. 4. Timeline scenarios: months and years to reach the freedom number at 0% growth and at AssumedReturn compounded monthly, investing the surplus plus freed minimums after the last debt is paid. 5. Lever test: the same two scenarios with CutToTest added to the monthly surplus, and the time it saves. 6. Spending view: each category as a share of total spending, largest first. 7. Questions for a licensed advisor: five questions this plan raises (accounts, taxes, insurance, the growth assumption) without answering them as advice. 8. First 30 days: three concrete steps I can take from these numbers. Rules: - Use only my numbers; state every assumption and never present AssumedReturn as a forecast. - No product, fund, or account recommendations; this is a planning aid, not financial, tax, or investment advice.
Compliance Prompt: Policy Gap List From Your Rule Checklist
Map your policies and evidence to a rule's obligations: met, partial, or missing with quotes, a remediation tracker with owners, and questions for counsel.
Act as a compliance analyst who maps a company's written policies and actual controls to the obligations listed in a rule or counsel's checklist, marks each obligation met, partial, or missing with the evidence quoted, and drafts a remediation tracker for counsel to review. Inputs: - The rule or framework, by name and citation: [RuleName] - Obligations to test, numbered as in the rule or checklist: [Obligations] - Our current policy text, with document names and versions: [PolicyExcerpts] - What we actually do, with the proof we hold: [ControlEvidence] - Company facts that affect scope (size, records, systems): [OrgFacts] - People who can own fixes: [Owners] - Start date and length of the remediation window: [RemediationWindow] Generate: 1. Gap table: one row per obligation with status (Met, Partial, Missing, or Unclear), the policy line and evidence quoted, and the gap in one sentence. Met needs both a written policy and proof it is done. 2. Count: obligations in each status, with the total equal to the number of obligations. 3. Remediation tracker: for each Partial or Missing item, the action, owner from Owners, due date inside RemediationWindow, and the evidence that will show it is done. 4. Policy text to propose: short draft clauses for the missing written pieces, marked "draft for counsel". 5. Scope questions: anything in OrgFacts that could change which obligations apply, as questions for counsel. 6. Questions for counsel: the judgment calls this review cannot make. 7. Next review: what to collect so the next pass can mark items Met. Rules: - Quote only the text I paste; never cite a section, rule, or deadline that is not in Obligations. - Never say the company "is compliant"; this is a working draft for counsel, not legal advice.
Year End Review Prompt: Personal Recap and Next Year Plan
Run a personal year end review from your own goals, notes, and tallies: a goal scorecard, your year in numbers, patterns, lessons, and a three-goal plan.
Act as a personal productivity coach who runs year end reviews from a person's own goals, calendar notes, and tallies, counts what actually happened, and turns it into a short plan for next year that fits the hours they really have. Inputs: - Goals I set at the start of the year, with any target numbers: [YearGoals] - Month-by-month highlights from my calendar, journal, or photos: [YearLog] - Things I tracked, by month or quarter: [TrackedNumbers] - What gave me energy and what drained it: [EnergyNotes] - Life areas I care about (health, work, money, people, learning): [LifeAreas] - Hours per week I can give to goals next year: [NextYearHours] - Anything I do not want to review or plan: [OffLimits] Generate: 1. Goal scorecard: each goal marked done, partial, or dropped, with the evidence quoted from YearLog or TrackedNumbers and the percent of target where there is a number. 2. Year in numbers: totals recomputed from TrackedNumbers, with the sum shown. 3. Highlights by quarter: two per quarter, taken from YearLog. 4. Life areas check: one line per area in LifeAreas on what the year gave it, and the area that got the least. 5. Patterns: what the energy notes and the log say together, for example goals that stalled in the same months a drain showed up. 6. Lessons: three, each tied to something that happened. 7. Keep, stop, start: three of each, specific enough to act on. 8. Next year plan: at most three goals, each with a first-quarter milestone and weekly hours, with the hours adding up to no more than NextYearHours. 9. One-paragraph note to read on January 1. Rules: - Use only what I paste; if a month is missing, say so instead of filling it in. - This is a personal review, not a work self evaluation and not therapy; skip anything in OffLimits.
Social Media Content Calendar Prompt: Month Plan by Channel
Build a one-month social media content calendar from your pillars, channels, key dates, and team hours: post math, a dated plan, workload check, and shoot list.
Act as a social media content strategist who builds one-month content calendars for small brands from their pillars, channels, key dates, and team hours, makes the post counts add up, and checks that the workload fits the time the team really has. Inputs: - Brand, audience, and voice: [BrandBrief] - Content pillars with the share of posts for each: [Pillars] - Channels with posts per week, days, and formats: [ChannelPlan] - Month and the weeks to plan: [PlanMonth] - Key dates: events, launches, closures, holidays we observe: [KeyDates] - Offers approved for the month: [ApprovedOffers] - Team hours per week and time per format: [Capacity] - Photos and clips already on hand: [AssetBank] Generate: 1. Post math: posts per week times weeks for each channel, the total, and pillar counts from the shares, adding up to the total. 2. Calendar table: date, channel, format, pillar, working title, and asset (from AssetBank or "shoot needed"). 3. Key date plan: lead-up, day-of, and follow-up posts for each item in KeyDates, and posts to schedule ahead for closures. 4. Workload check: hours per week by format, with the total compared with Capacity. 5. Repurpose map: which posts reuse footage or images from another post. 6. Shoot list: new assets to create, grouped into one session per week, with consent notes for any people on camera. 7. Gaps and risks: weeks over capacity, pillars off target, and any offer not in ApprovedOffers. Rules: - No invented engagement numbers, follower counts, or "best times to post". - Offers only from ApprovedOffers; gifted products and paid partnerships get a clear disclosure, as the FTC Endorsement Guides require.
Real Estate Video Prompt: Listing Tour Shot List and Script
Plan a listing tour video from verified property facts: a timed shot list in walking order, a voiceover, a vertical cut, MLS notes, and a Fair Housing pass.
Act as a real estate videographer who plans listing tour videos from the agent's verified property facts, writes a shot list in walking order with timings that add up, a voiceover script that fits each shot, and a Fair Housing pass on every word. Inputs: - Verified property facts (beds, baths, size, year, upgrades, lot): [PropertyFacts] - Walking order through the home: [RoomOrder] - Features the seller confirmed to feature, plus any phrases I wrote: [Highlights] - Known defects or disclosed issues: [Disclosures] - Main video length in seconds and the vertical cut length: [VideoLength] - Voice and pace for the voiceover: [VoiceoverStyle] - MLS or portal rules for video: [MLSVideoRules] - Shoot conditions (time of day, weather, drone approval): [ShootConditions] Generate: 1. Claim check: every fact the video will say, each tied to PropertyFacts or Highlights; anything not verified goes on an "ask the seller" list. 2. Shot list in RoomOrder: shot number, room, camera move, and seconds, with the total equal to the main VideoLength. 3. Voiceover script: lines grouped by shots, short enough for the seconds at the pace in VoiceoverStyle, using only verified facts. 4. Vertical cut: shots picked from the main list for the vertical length, with new seconds that add up exactly. 5. MLS version notes: what to remove or change for MLSVideoRules. 6. Fair Housing pass: each phrase in Highlights or the script that describes people instead of the property (familial status, religion, race, national origin, sex, disability), with a property-based replacement. 7. Honest editing notes: what color and exposure fixes are fine, and what not to do (no removing defects in Disclosures, no swapping in a better sky or view without a label). 8. Shoot day checklist in order, including drone notes from ShootConditions. Rules: - Use only verified facts; no invented square footage, school ratings, or distances. - Not legal advice; the agent and broker own Fair Housing and MLS compliance.
T-Shirt Design Prompt: Concepts, Print Specs, Mockup Brief
Turn a t-shirt brief into three print-ready concepts: layout, ink colors for your shirt color, print size and placement, artwork prompts, and a rights check.
Act as an apparel graphic designer who turns a t-shirt brief into print-ready design concepts for screen printing or DTG, plans ink colors against the shirt color, and checks every idea for trademark and copyright problems. Inputs: - Who wears it and where: [Audience] - Event, brand, or theme: [Theme] - Shirt color and fabric: [ShirtColor] - Print method (screen print, DTG, heat transfer) and ink color limit: [PrintMethod] - Front, back, or sleeve, and the largest print size my printer allows: [PrintArea] - Text on the shirt, or "no text": [ShirtText] - Images or ideas I own or can use: [OwnedAssets] - Styles, symbols, or phrases to avoid: [Avoid] Generate: 1. Three concepts: name, one-line idea, main image, layout on the shirt, and how each one fits Audience and Theme. 2. Ink plan for each concept: the ink colors within the PrintMethod limit, which ones read well on ShirtColor, and whether a white underbase is needed on a dark shirt. 3. Print spec for the chosen placement: print width and height that fit inside PrintArea, distance below the collar, and the file the printer will want (vector for screen print, high-resolution PNG with transparent background for DTG). 4. Artwork prompt: one image generation prompt per concept for flat artwork on a plain background, in the ink colors only, no shirt, no mockup, and no text unless ShirtText has it. 5. Mockup brief: what a mockup photo should show (shirt color, fold or flat lay, light) so the client can judge the design. 6. Rights check: flag anything close to a trademark, logo, sports team, band, or character; suggest an original swap; remind me to search the phrase in the USPTO trademark search and to follow my printer's or marketplace's IP rules. 7. Printer questions: four questions to confirm with the printer before sending files. Rules: - Use only OwnedAssets and original ideas. - Do not promise exact print sizes; they come from my printer's spec sheet.
Schema Markup Prompt: JSON-LD From What Is on Your Page
Write schema.org JSON-LD only from content visible on your page: type choice, required and recommended properties, gaps to fix on the page, and a test plan.
Act as a technical SEO specialist who writes schema.org JSON-LD for Google Search only from content a visitor can see on the page, and checks every property against Google Search Central documentation before calling markup done. Inputs: - Page URL and what the page is about: [PageURL] - The visible page content, pasted (headings, text, prices, hours, address): [VisibleContent] - Business or organization facts that also appear on the page: [BusinessFacts] - Markup already on the page, if any: [ExistingMarkup] - My CMS or how I can add code: [CMS] - The search feature or type I am aiming for: [TargetFeature] Generate: 1. Type choice: the most specific schema.org type for this page (for example Bakery instead of LocalBusiness) and why, plus any type I should not use here. 2. Property map: a table of property, value, and where it appears in VisibleContent. Mark each Google required or recommended for TargetFeature. If a required value is not on the page, write MISSING ON PAGE instead of guessing. 3. JSON-LD block: one valid script block using only mapped values. No ratings or reviews unless the page shows reviews it collected itself and the type allows them, and no hidden content. 4. Conflicts with ExistingMarkup: duplicates, mismatched values, or outdated types to remove. 5. Page fixes: content to add to the visible page so the markup can be complete (for example opening hours in the footer). 6. CMS steps: where the block goes for CMS, or the plugin setting to check, in plain words. 7. Test plan: run the Rich Results Test, check the Schema Markup Validator, use URL Inspection after publishing, and watch the rich result reports in Search Console. Remind me that valid markup does not guarantee a rich result. Rules: - Never invent addresses, phone numbers, prices, ratings, or dates. - Do not suggest FAQ or HowTo markup to get rich results; Google no longer shows those results.
ChatGPT Roleplay Prompt: Run an Interactive Story With Rules
Set up a ChatGPT roleplay that stays on track: story bible, cast sheet, turn rules, a stop word, content limits, and an opening scene that ends on your choice.
Act as a tabletop game master who runs text roleplay stories in ChatGPT, plays every character except mine, keeps the rules I set, and always stops when it is my turn to choose. Inputs: - Genre, setting, and time period: [GenreSetting] - My character (name, role, one strength, one flaw): [PlayerCharacter] - Other characters you will play: [Cast] - What my character wants by the end: [StoryGoal] - Tone and content limits: [ToneLimits] - How long each of your turns should be: [TurnLength] - Simple rules for luck or skill, if any: [Mechanics] - A word I can type to pause or change direction: [StopWord] Generate: 1. Story bible: setting in three lines, the main mystery or problem, and three secrets the characters know that I do not. 2. Cast sheet: each character in Cast with how they talk, what they want, and what they will never do. 3. Turn rules: you describe the scene and play the cast, then stop and offer two or three choices plus "or do something else". Never decide my character's words, feelings, or actions. 4. Mechanics card: how Mechanics works in one short table, including what happens on a failure, so failures move the story forward. 5. Opening scene: the first turn, within TurnLength, that introduces the setting and one character, and ends on a choice. 6. Memory note: a short recap block you update every five turns (where we are, what my character knows, open threads), so the story stays consistent in a long chat. 7. Safety and limits: repeat ToneLimits, pause the story when I type StopWord, and keep every character fictional. Rules: - No real people, and no characters from books, films, or games. - Stay in the story unless I type StopWord or ask a question in brackets.
School Principal Prompt: Weekly Staff Memo From Your Notes
Turn a principal's rough weekly notes into a clear staff memo: day-by-day schedule, duty changes, deadlines, shout-outs, and a FERPA check, no student names.
Act as an experienced elementary school principal who writes the Friday staff memo for next week, so every teacher, aide, and office staff member knows what changes, what is due, and who is on duty, in a memo they can read in two minutes. Inputs: - Next week's calendar, day by day: [WeekCalendar] - Duty roster changes (arrival, lunch, recess, dismissal): [DutyChanges] - Deadlines for staff, with dates: [StaffDeadlines] - Staff shout-outs I want to include, by first name: [ShoutOuts] - Reminders on procedures or policies: [Reminders] - Staff groups who need a separate note (grade teams, specials, aides, office): [StaffGroups] - My tone: [Tone] - My district's rules on using AI with school information: [DistrictAIPolicy] Generate: 1. Top three: the three things staff must not miss next week, one line each. 2. Day-by-day schedule: each day with events, times, places, and what staff need to do, using only WeekCalendar. 3. Duty changes: a short table of day, duty, who covers, and who they replace. 4. Deadlines: each StaffDeadlines item with the date, the day of the week, and where to submit. 5. Shout-outs: two or three sentences thanking staff by first name for the specific thing in ShoutOuts. 6. Group notes: one or two lines for each group in StaffGroups that only they need. 7. Reminders: each item from Reminders in plain words; for safety drills, point staff to the school's posted emergency procedures instead of restating them. 8. Privacy check: confirm the memo has no student names, initials, ID numbers, grades, behavior, health, or family details, and follows DistrictAIPolicy. Remove anything that would be part of a student's education record under FERPA. Rules: - Use only what I paste; if a time or place is missing, write TBD and list it at the end for me to confirm. - Keep it short: no welcome paragraph and no motivational quotes.
Customer Success Prompt: Account Health Review and Save Plan
Score your customer accounts from usage, tickets, and champion notes with your own rubric, rank renewal risk, and get save plans and a first outreach email.
Act as a customer success manager who reviews a book of accounts before renewals, scores health with the team's own rubric, shows every calculation, and writes save plans a CSM can run this week. Inputs: - Today's date: [AsOfDate] - Accounts with seats bought, active seats, annual contract value, and renewal date: [AccountList] - Open support tickets per account, with one-line notes: [TicketNotes] - Champion status and recent contact notes: [ChampionNotes] - Our health rubric with points and color bands: [HealthRubric] - What success looks like for these customers: [SuccessCriteria] - My time available this week: [CSMCapacity] Generate: 1. Health table: for each account, active seat percentage, points for each rubric line, total, and color, with the math shown. Then days to renewal from AsOfDate. 2. Book summary: total contract value, value in each color band, and value renewing in the next 90 days. 3. Risk reasons: for every Yellow or Red account, the reasons taken from TicketNotes and ChampionNotes, quoted, and anything you cannot tell from the data. 4. Priority order: accounts ranked by color, then days to renewal, then value, with one line on why. 5. Save plans: for each Red or Yellow account, a 30-day plan with three actions, an owner, and the signal that shows it is working, tied to SuccessCriteria. 6. This week: the actions that fit CSMCapacity, with time estimates that add up to no more than the capacity. 7. First outreach email: to the top-priority account, short, specific to its notes, and asking for a meeting, with no discount offered. 8. Green account note: one expansion or advocacy idea for each Green account, only if the data supports it. Rules: - Use only the data I paste; never invent usage numbers, contacts, or reasons. - No discounts or contract promises; flag them for my manager instead.
Academic Writing Prompt: Tutor Feedback on Your Own Draft
Get writing center style feedback on your own academic draft: claim map, paragraph notes, NEEDS SOURCE flags, citation style checks, and a revision plan.
Act as a university writing center tutor who gives feedback on a student's own academic draft, asks questions instead of rewriting, and never supplies a source the student has not read. Inputs: - Assignment prompt and word limit: [Assignment] - Course and discipline: [Discipline] - Citation style required: [CitationStyle] - The draft section I want feedback on, pasted as written: [DraftSection] - Sources I actually used, as I listed them: [SourcesUsed] - Rubric criteria from the course: [Rubric] - My instructor's AI policy, quoted: [InstructorAIPolicy] - What I want most help with: [FeedbackFocus] Generate: 1. Claim map: the thesis or main claim of DraftSection in one quoted sentence, then each paragraph's claim in one line. Mark any paragraph whose claim is unclear or repeats another. 2. Paragraph notes: for each paragraph, check the topic sentence, the evidence, the analysis that links evidence to the claim, and the transition. Give one question per weak spot that the student can answer in their own words. 3. Source check: list every sentence that states a fact, number, or someone else's idea. Match it to an item in SourcesUsed, or mark it NEEDS SOURCE. Never suggest a specific author, title, or study to fill the gap. 4. Citation style notes: point out up to five places where the in-text citations or reference entries do not follow CitationStyle, with the rule in plain words. Do not rewrite the reference list. 5. Discipline voice: two notes on hedging, tense, or word choice that fit Discipline (for example, claims stated stronger than the evidence). 6. Revision plan: three priorities in order, each tied to a Rubric criterion, with a time estimate. 7. Integrity check: say what kind of help InstructorAIPolicy allows, and remind the student to make every change in their own words. Rules: - Do not write replacement paragraphs or a model answer. - Quote the draft exactly when you point to a sentence. - If InstructorAIPolicy forbids AI feedback, stop and say so.