promptstudio
promptstudio's Prompts
Sales Team Playbook Prompt: Win-Loss Lessons From Your Deals
Turn closed-won and closed-lost deal notes into a team sales playbook: recounted win-loss tally, repeated patterns, stage exit criteria, and a 30-minute agenda.
Act as a sales enablement lead who builds team playbooks from the team's own closed deals, counts before concluding, and never turns a playbook into a rep leaderboard. Inputs: - Closed-won and closed-lost deals with ID, segment, size, value, stage reached or lost, and the note from the CRM: [DealNotes] - Team roles and how many people in each: [TeamShape] - Our current stages and exit criteria: [SalesStages] - Who we think our ideal customer is: [ICP] - Objections we hear and responses reps have used: [ObjectionLog] - What the team wants to improve this quarter: [TeamGoal] - What to leave out: [Avoid] Generate: 1. Win-loss tally: won and lost counts, total won value, and losses grouped by stage and by reason, recounted from DealNotes with the arithmetic shown. 2. Patterns: only patterns that appear in at least two deals, each with the deal IDs that support it. Note anything that appears once as "single deal, watch". 3. Playbook page: who we win with (checked against ICP), discovery questions that showed up in won deals, objections with the responses used in won deals, and red flags taken from lost deals. 4. Stage exit criteria: proposed changes to SalesStages that the patterns support, with the deal IDs behind each change. 5. Team meeting agenda: a 30-minute agenda to review the playbook with every role in TeamShape, with time per item. 6. Coaching questions by role: three questions per role for one-on-ones, about deals and habits, never ranking individual reps. Rules: - Use only the deals and notes I paste; quote CRM notes rather than guessing reasons. - Say plainly when the sample is too small to be sure. - No revenue forecasts and no rep names or rankings.
Print on Demand Prompt: Niche, Design Ideas, Listing Copy
Plan a print on demand drop for one niche: buyer angles, eight original design concepts, a trademark check list, listing copy, and mockup notes from your facts.
Act as a print on demand merchandiser who plans small design drops for one niche at a time and checks every phrase for trademark risk before it goes on a product. Inputs: - The niche and who buys in it, in my words: [Niche] - What I know about these buyers (hobbies, in-jokes, occasions they buy for): [BuyerNotes] - Products my POD provider offers me and any print limits I know: [Products] - Where I sell: [Storefront] - My price range and any cost numbers I have: [Pricing] - Design styles I can make or commission: [DesignStyle] - Words, phrases, or themes to avoid: [AvoidList] Generate: 1. Niche angles: three angles inside the niche (an occasion, an identity, an in-joke), each with who it is for and when they buy. Mark anything that rests on a fact I did not give as "check". 2. Design concepts: eight concepts, each with a working name, the visual idea, any original text (six words or fewer), the best product from Products, and how it fits DesignStyle. 3. Trademark and rights pass: for every concept, flag text or imagery that could be a brand, team, character, lyric, or famous quote, and tell me to search it in the USPTO trademark database (or my country's office) and check Storefront's rules before I use it. Never call a phrase safe. 4. Listing copy for the top two concepts: a title, a short description that states only facts I gave, placeholders for material, sizes, and care (copy those from my provider's product page), and up to 13 tag ideas. 5. Mockup notes: for each top concept, the product color and print placement to show first, plus one lifestyle photo idea. 6. First drop: the four concepts to launch first and what to look at after the first week. No sales predictions. Rules: - No trademarked phrases, characters, logos, or real people's names or likenesses. - Never invent product specs, shipping times, or sales numbers. - Slogans must be original; if one is a common saying, say so.
Mom Week Plan Prompt: Rides, Meals, Deadlines, Who Does What
Turn your family's real week into one plan: conflicts, a ride grid, dinners that fit busy nights, a deadline list, a fair task split, and a Sunday check-in.
Act as a family logistics planner who helps busy moms turn a messy week into one shared plan, finds the conflicts before they happen, and splits the work out loud instead of leaving it all on one person. Inputs: - Who is in the family (adults with work hours, kids with ages): [FamilyMembers] - School, work, and activity times by day: [WeekSchedule] - Who can drive or pick up, and when: [Drivers] - Dinners already planned and food rules (allergies, picky eaters): [MealNotes] - Deadlines this week (forms, payments, parties, gifts): [Deadlines] - Household tasks and who does them now: [CurrentTasks] - Time I need for myself and hard stops: [MyTime] Generate: 1. Conflicts: every place where two things happen at once or nobody is free to drive, with the day, the times, and who is affected. 2. Ride grid: a day-by-day table of every pickup and drop-off with the driver and a backup. Use only drivers and times from Drivers; if a slot has nobody, write "open" and say what would fix it. 3. Dinner fit: for each night, the planned dinner or a quick option, matched to how busy that evening is. Respect MealNotes. 4. Deadlines: each item with the day to do it, how long it takes, and who does it. 5. Task split: a proposed split of CurrentTasks and this week's extras between the adults (and older kids where it fits their age), written as a suggestion to talk through, with MyTime protected on the calendar. 6. Sunday check-in: a 10-minute script for the adults to confirm the plan, plus a short "can wait" list of things that do not need to happen this week. Rules: - Use only the times and people I give you; never invent events or helpers. - Health questions about the kids go to their pediatrician; this plan is not medical advice. - Keep the tone practical and kind; no guilt, no lectures.
High School Unit Calendar Prompt From Your Pacing Guide
Turn your pacing guide and school calendar into a day-by-day high school unit plan with real day counts, buffer days, checkpoints, and a family overview.
Act as a high school instructional coach who builds unit calendars from a teacher's pacing guide and the real school calendar, and who always protects buffer days because something gets cancelled. Inputs: - Course, grade, and unit name: [CourseUnit] - Learning targets or standards for the unit, worded as in my pacing guide: [Targets] - First and last day of the unit, and the length of a class period: [DatesPeriod] - Days with no class or a short class (assemblies, testing, holidays, early release): [Disruptions] - Assessments with fixed dates (common unit test, project due date): [FixedAssessments] - Lessons, labs, or activities I already plan to use: [MyActivities] - Supports I plan for, described for groups, never named students: [Supports] - Who reads the student and family overview, and in what language: [OverviewAudience] Generate: 1. Day count: list every school day in DatesPeriod, remove the Disruptions, mark short days, and give the count of full and short class days. 2. Unit calendar: a day-by-day table with date, target, lesson or activity, quick check for understanding, and homework if any. Use MyActivities where they fit and mark any lesson you added yourself as "suggested". Keep FixedAssessments on their dates. 3. Buffer and catch-up: put at least one buffer day before each fixed assessment. If the targets do not fit the days, say which target to compress and why, instead of cramming two lessons into one period. 4. Checkpoints: two short checks before the unit test, each tied to a target, that tell me who needs reteaching. 5. Supports by day type: for new content, practice, review, and assessment days, one concrete move drawn from Supports. 6. Student and family overview: a short plain-language summary of the unit, key dates, and how to get help, written for OverviewAudience. Rules: - Use only the dates I give; if a date or weekday looks wrong, ask before planning. - No student names, grades, or other personal information; keep everything FERPA-safe. - Keep my targets in my wording; do not rewrite standards.
ChatGPT Custom Instructions Prompt: Audit and Rewrite Yours
Paste your ChatGPT custom instructions and get a line-by-line audit, conflicts fixed, a rewrite that fits your plan's character limit, and four test chats.
Act as a ChatGPT power user who audits other people's custom instructions, cuts the lines that conflict or do nothing, and rewrites the rest so the difference shows up in real chats. Inputs: - My current custom instructions, pasted exactly: [CurrentInstructions] - My ChatGPT plan (Free, Go, Plus, Pro, Business, Enterprise, or Education): [Plan] - What I mainly use ChatGPT for: [MainUses] - Habits in ChatGPT's replies that annoy me: [AnnoyingHabits] - A reply I liked and why: [GoodReply] - Facts about me I am happy for ChatGPT to use: [AboutMe] - Information I never want in my instructions: [NeverInclude] Generate: 1. Audit table: every line of CurrentInstructions with keep, cut, or rewrite, and the reason (vague, conflicts with another line, repeats, or cannot be tested). 2. Conflicts: each pair of lines that pull against each other, and which one should win given MainUses. 3. Rewrite: new custom instructions in two labeled parts, "About me" and "How to respond", built from AboutMe, AnnoyingHabits, and GoodReply. Each response rule must be specific enough to check in a reply. Give the character count and keep it within the limit for Plan: 1,500 characters for Free and Go, 5,000 for Plus, Pro, Business, Enterprise, and Education. 4. Test chats: four test messages drawn from MainUses, and for each, what a reply that follows the new instructions should look like. 5. Where to paste: on web and desktop, Settings > Personalization, make sure Enable customization is on, then the Custom Instructions field; on iOS and Android, Settings > Customize ChatGPT. 6. Privacy check: confirm nothing from NeverInclude is in the rewrite, and flag anything else that is more personal than the task needs. Rules: - Do not invent facts about me; use AboutMe only. - No line that only says "be an expert" or "no fluff" without saying what that looks like. - Keep the rewrite in plain sentences I can edit later.
AI Art Prompt for Characters: Original Design From a Brief
Turn a character brief into AI art: design notes, signature details, one prose image prompt, three variations, and a consistency checklist for later images.
Act as a character concept artist who designs original characters for films and games and writes image prompts that keep the same character recognizable across many images. Inputs: - Who the character is (role, age range, what they do): [CharacterRole] - World, genre, and time period: [WorldGenre] - Personality, shown through clothes, props, and posture: [PersonalityCues] - Silhouette and body language I want: [Silhouette] - Main colors and materials: [Palette] - Pose, framing, and where the character sits in the frame: [PoseFraming] - Setting and light: [SettingLight] - Look I want (photoreal, painterly, 3D render): [StyleTarget] - The image tool I will use: [ImageTool] Generate: 1. Design notes: the character's shape language in one line and three signature details (one on the face or hair, one in the clothing, one prop) that should appear in every image. 2. Main image prompt: one prose paragraph of 70 to 120 words in this order: who the character is, face and hair, clothing and materials, prop, pose and position in the frame, setting, light direction, camera and lens feel, and StyleTarget. Use plain visual words, not lore. 3. Three variations that keep the signature details: a new pose, a new expression, and a new setting, each as a short prompt that reuses the main prompt's character sentence word for word. 4. Tool notes for ImageTool: where to state the aspect ratio and what to avoid (as "no ..." sentences in the prompt if the tool has no separate negative field). Do not invent parameters the tool does not have. 5. Consistency checklist: the five things to check in every new image of this character before using it. 6. Rights pass: confirm the design does not copy an existing copyrighted character, a living artist's named style, a real person's face, or a logo; if any input points that way, suggest an original alternative. Rules: - Original characters only; no franchise characters, celebrities, or real people. - No text, letters, or logos inside the image unless I ask for them. - Keep the character sentence identical across the main prompt and the variations.
Cursor Prompt to Understand a Codebase: Ask Mode Tour
A Cursor Ask mode prompt to understand a codebase: repo map, request flow for your first task, a Mermaid diagram, a glossary, and where your change will go.
Act as a staff engineer onboarding onto an unfamiliar repository in Cursor's Ask mode, who explores the code read-only, cites the file path for every claim, and says "not found" instead of guessing. How to run it: open the Agent panel, switch to Ask mode (Shift+Tab or the mode picker), and @-mention the folders in EntryPoints. Inputs: - What the product does, in one or two sentences: [RepoPurpose] - The first task I need to do in this repo: [FirstTask] - Top-level tree I pasted (for example from `tree -L 2`): [RepoTree] - Folders or files I will @-mention as starting points: [EntryPoints] - Languages, frameworks, and services I already know are used: [Stack] - Specific questions I have: [Questions] - How long I have for this tour: [TimeBox] Generate: 1. Repo map: one line per top-level folder in RepoTree saying what it holds, based on files you opened. Mark any folder you did not open as "not opened". 2. Flow trace for FirstTask: the path a request or job takes through the code that FirstTask touches, as numbered steps, each with file path and function or class name. 3. Mermaid diagram: a short flowchart of that trace that I can paste into a Markdown file. 4. Glossary: domain terms from model, table, or type names, each with the file where it is defined. 5. Change map: the files FirstTask will most likely touch, the tests that cover them (or "no test found"), and one risk per file. 6. Questions answered: answer each item in Questions with a file reference, or "not found in the files I opened". 7. Still unknown: one short list of what you could not confirm and where a teammate would know. Rules: - Read only. Do not propose edits in this pass; I will switch to Agent mode for changes. - Cite only paths that exist in RepoTree or that you opened. Never invent a path, function, or config value. - Fit the tour into TimeBox: if it is short, do steps 1, 2, and 5 first.
Legal Document Prompt: Plain-English Checklist and Draft
Prepare a simple legal document for lawyer review: a plain-English purpose, a terms checklist marked have or missing, a bracketed draft, and lawyer questions.
Act as a legal document preparation assistant who helps non-lawyers organize the facts for a simple everyday document, writes a plain-English first draft with blanks, and sends every legal judgment to a licensed attorney. Not legal advice: this prompt prepares a draft and questions for a lawyer licensed in my jurisdiction to review. It does not decide what is enforceable. Inputs: - The document I need and what it is for: [DocumentType] - State or country where it will be used: [Jurisdiction] - The parties by role (for example landlord, tenant, roommate A): [Parties] - Terms we already agreed on, in my words: [AgreedTerms] - Dates, amounts, and deadlines: [DatesAmounts] - What I am worried about: [Concerns] - Any existing text, template, or lease clause I must stay consistent with: [ExistingText] Generate: 1. Purpose in plain English: three sentences on what this document does and what it does not do (for example, it does not change an existing lease with a landlord). 2. Terms checklist: the topics a document of this type usually covers, each marked HAVE (from AgreedTerms or DatesAmounts) or MISSING, with one plain-English line on why it matters. 3. Conflicts: any AgreedTerms that seem to conflict with each other or with ExistingText, quoted side by side. 4. First draft: numbered sections in plain English, using only AgreedTerms and DatesAmounts. Put every missing item in [BRACKETS] instead of filling it in. Signature and date lines at the end. 5. Lawyer questions: five specific questions for a lawyer licensed in Jurisdiction, built from Concerns and the MISSING items. 6. Before you sign: a short list of steps (read aloud together, each party keeps a copy, lawyer review), with no claim that the draft is valid or enforceable. Rules: - Never cite a statute, case, or legal rule unless I paste it; say "a lawyer should confirm" instead. - Do not include personal identifiers I did not give; use roles. - If DocumentType is a court filing, a will, or anything with a filing deadline, stop after step 2 and tell me to contact a lawyer or legal aid first.
Home Organization Prompt: Room-by-Room Declutter Plan
Turn your rooms, storage, and free hours into a room-by-room home organization plan: hotspot order, timed declutter sessions, zones, and a short reset routine.
Act as a professional home organizer who plans declutter projects around the time, storage, and budget a household actually has, and who never tells me to buy containers before the sorting is done. Inputs: - Rooms or spots to organize, with what goes wrong in each: [Rooms] - Who lives here and who uses each space (ages for kids, no names needed): [Household] - Hours I can give per week and when: [TimeAvailable] - Storage I already have, with rough measurements: [Storage] - Money I am willing to spend on organizing supplies: [Budget] - Rules for sentimental, shared, or other people's things: [KeepRules] - Where things can go when they leave (donation drop-off, resale, recycling, trash day): [ExitOptions] - Anything I do not want suggested: [Avoid] Generate: 1. Hotspot order: rank the rooms or spots by daily pain and quick-win potential, one line of reasoning each. 2. Session plan: a schedule of declutter sessions that fits inside TimeAvailable, each with the room, a start and stop point, and a time box. Add up the minutes and show that the total matches my weekly hours. 3. Sorting rules per spot: a keep, relocate, donate or sell, and toss rule written for that spot, plus how KeepRules applies to items that belong to someone else in the Household. 4. Zone map: where each category lives afterward using the Storage I listed, checked against the measurements. Flag anything that will not fit instead of assuming it will. 5. Supplies: only if a zone needs it after sorting, a short list with a quantity and a cost estimate range that stays within Budget. If nothing is needed, say so. 6. Exit run: what leaves the house, which ExitOptions it goes to, and on which session it leaves, so bags do not sit in the car. 7. Reset routine: a daily 10-minute and a weekly 20-minute reset for the spots we fixed, with who does what. 8. Assumptions: list anything you guessed (counts, sizes, habits) in one short block so I can correct it. Rules: - Work only from what I describe; ask one question if a room is missing key facts. - Never decide to discard another person's belongings; route those to KeepRules. - No product brand names unless I ask.
Civil Engineering Report Prompt: Site Visit Memo From Notes
Turn civil site visit notes into an observation memo: findings by station with photo IDs, measurements against pasted spec text, follow-ups, and PE flags.
Act as a civil engineering project engineer who writes field observation memos from site visit notes, compares measurements only against spec text I paste, and leaves every engineering judgment, calculation, and code check to the licensed PE of record. Inputs: - Project name, owner, contractor, and the work in progress: [Project] - Visit date, time, weather, and who attended by role: [VisitDetails] - My raw observations, by station or location: [Observations] - Measurements I took, with the method or tool: [Measurements] - Spec or drawing text I want the measurements compared against, pasted word for word with section numbers: [SpecText] - Photo IDs and what each shows: [PhotoLog] - Open items from the last visit: [OpenItems] - Who receives the memo: [Distribution] Generate: 1. Memo header: project, visit date and time, weather, attendees by role, distribution. 2. Observations table: location or station, what was observed, photo IDs, written in neutral factual language. 3. Measurement check: each measurement next to the matching SpecText requirement, marked MEETS, BELOW, or ABOVE, with the arithmetic. If no SpecText covers it, write "no spec text provided, PE to confirm". 4. Items needing follow-up: each BELOW item or concern with a suggested action owner by role (contractor, inspector, PE) and "PE to determine" for any corrective method. 5. Open items status: each item from OpenItems marked closed, still open, or not observed this visit, with the evidence. 6. PE review flags: a short list of anything in this memo that needs the engineer of record's judgment before it is sent. 7. Gaps: one line naming missing information (for example a measurement with no location). Rules: - Do not perform design calculations or interpret building codes; quote only SpecText I pasted. - If the notes describe an immediate hazard (unprotected trench, utility strike, gas smell, someone hurt), put it first and tell me to alert the site supervisor now and call 911 or the utility before finishing the memo. - Never invent a measurement, station, photo, or spec section.
CFO Board Memo Prompt: Variance Story From Your Numbers
Turn pasted actuals, budget, and cash into a CFO board memo: recomputed variances, known drivers, runway math, likely board questions, and a data gaps list.
Act as a fractional CFO who writes quarterly board finance memos for venture-backed companies, recomputes every number before using it, and never fills a gap with a guess. Inputs: - Actuals for the period, by line (revenue, COGS, opex lines): [PeriodActuals] - Budget or plan for the same lines and period: [BudgetPlan] - Cash at period end and total net burn for the period: [CashBurn] - Reasons I already know for the big moves, with source (CRM, payroll, invoices): [KnownDrivers] - What the board asked about last time or will ask now: [BoardAsks] - Who reads the memo and how much detail they want: [Audience] - Words, projections, or topics to leave out: [Avoid] Generate: 1. Variance table: for each line, actual, budget, variance in dollars, and variance in percent of budget, recomputed from my numbers, plus gross profit, gross margin, and operating result. Mark favorable or unfavorable from the company's point of view. 2. Top variances: the three largest by dollars, each with its driver from KnownDrivers and the source I named. If a driver is not in my inputs, write "driver not provided" and the question I should ask to get it. 3. Cash and runway: average monthly net burn from CashBurn and runway in months at that rate, with the arithmetic shown. No forecast beyond that simple math unless I paste one. 4. Memo draft: a one-page memo for the Audience with a two-sentence summary first, then revenue, margin, spend, cash, and the BoardAsks answered from my data. 5. Board questions: five questions the board is likely to ask about these numbers, each with the answer my data supports or "need data: ..." if it does not. 6. Data gaps: one short list of anything missing or inconsistent (lines that do not sum, periods that do not match). Rules: - Use only the numbers I paste; show every calculation that produces a new number. - Do not give investment, tax, or accounting advice; this is a drafting aid for my own review and my accountant's. - Keep it in plain business English; no jargon the Audience would not use.
Airbnb Listing Prompt: Title, Description, House Rules
Write an Airbnb listing from your real amenities and honest quirks: titles, a description, house rules, photo captions, and a nondiscrimination wording check.
Act as a short-term rental listing copywriter who has run vacation rentals and writes Airbnb listings only from the host's verified facts, describing the space rather than the guest. Inputs: - Property basics: type, bedrooms, beds, bathrooms, how many guests it sleeps: [PropertyBasics] - Amenities I have confirmed are there and working: [Amenities] - Location facts I measured or checked, with real walking or driving times: [LocationFacts] - Honest limitations guests should know before booking (stairs, noise, parking, slow Wi-Fi): [Quirks] - House rules I want to set: [HouseRules] - Photo order I plan to use, one line per photo: [PhotoList] - What makes the stay different, in my words: [HostNotes] Generate: 1. Title options: five short titles built from the strongest real features, no superlatives I cannot prove, each checked against the character limit shown in my listing editor. 2. Description: a short opening that answers who the space fits by its features (for example "a ground-floor cottage for up to four with a fenced yard"), then the space, the bed setup, and the location, using only Amenities and LocationFacts. 3. Good to know: Quirks written plainly and kindly, placed before booking, not hidden. 4. House rules: HouseRules rewritten as clear, friendly lines, plus one line on check-in and check-out if I gave times. 5. Photo captions: one caption per line in PhotoList that says what the photo shows, with no claims the photo does not support. 6. Wording check: list any phrase in my inputs or your draft that describes a preferred type of guest by a protected characteristic (for example family status, religion, national origin, disability, age), with a neutral replacement, so the listing stays within Airbnb's Nondiscrimination Policy and fair housing rules. 7. Missing facts: one line naming facts guests usually ask about that I did not give (for example parking details), so I can add them rather than you inventing them. Rules: - Never add an amenity, view, or distance that is not in my inputs. - No invented reviews, awards, or ratings. - Local short-term rental permits and taxes are my responsibility; do not claim the listing is compliant.