promptstudio
promptstudio's Prompts
Port a Custom GPT Brief into a Gemini Gem
Port instructions; map never-list; do not invent Gemini-only features.
Act as an AI tools engineer porting GPT briefs to Gemini Gems. Port instructions; map never-list; do not invent Gemini-only features. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Tool and version: [Tool] - Job to automate: [Job] - Inputs/outputs: [IO] - Guardrails: [Guardrails] - Eval or retry needs: [Eval] - Forbidden: [Forbidden] Generate: 1. Job decomposition. 2. Tool-specific artifact (command, OpenAPI, Gem, scorer, n8n node). 3. Guardrails and retry. 4. Eval cases (5). 5. Gaps. Constraints: - No em dashes. - Never invent stats, citations, social proof, DOIs, or IDs. - If Inputs are thin, list gaps instead of filling. - Version-lock named tools; else write unknown. - De-identify and add not-advice for legal, clinical, insurance, HR, veterinary, or education-plan content. - Stay on brief for: Port a Custom GPT Brief into a Gemini Gem
GPT Actions OpenAPI Stub from a Job Description
OpenAPI stub for GPT Actions from a job description; no fake auth secrets.
Act as a Custom GPT Actions engineer. OpenAPI stub for GPT Actions from a job description; no fake auth secrets. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Tool and version: [Tool] - Job to automate: [Job] - Inputs/outputs: [IO] - Guardrails: [Guardrails] - Eval or retry needs: [Eval] - Forbidden: [Forbidden] Generate: 1. Job decomposition. 2. Tool-specific artifact (command, OpenAPI, Gem, scorer, n8n node). 3. Guardrails and retry. 4. Eval cases (5). 5. Gaps. Constraints: - No em dashes. - Never invent stats, citations, social proof, DOIs, or IDs. - If Inputs are thin, list gaps instead of filling. - Version-lock named tools; else write unknown. - De-identify and add not-advice for legal, clinical, insurance, HR, veterinary, or education-plan content. - Stay on brief for: GPT Actions OpenAPI Stub from a Job Description
Claude Code Slash Command from a Repeatable Job
Design a slash command for a repeatable job; no invented CLI flags.
Act as a Claude Code power user. Design a slash command for a repeatable job; no invented CLI flags. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Tool and version: [Tool] - Job to automate: [Job] - Inputs/outputs: [IO] - Guardrails: [Guardrails] - Eval or retry needs: [Eval] - Forbidden: [Forbidden] Generate: 1. Job decomposition. 2. Tool-specific artifact (command, OpenAPI, Gem, scorer, n8n node). 3. Guardrails and retry. 4. Eval cases (5). 5. Gaps. Constraints: - No em dashes. - Never invent stats, citations, social proof, DOIs, or IDs. - If Inputs are thin, list gaps instead of filling. - Version-lock named tools; else write unknown. - De-identify and add not-advice for legal, clinical, insurance, HR, veterinary, or education-plan content. - Stay on brief for: Claude Code Slash Command from a Repeatable Job
App Store and Google Play Listing Copy with Limits
Write App Store and Google Play listing copy with hard character counts, screenshot captions, and a compliance pass that refuses invented ratings.
Act as an app store listing copywriter who counts characters. Write for Apple App Store and Google Play. Do not invent ratings, download counts, awards, or competitor ranks. Inputs: - App name: [Name] - Platform mix: [iOS / Android / both] - Category: [Category] - Who it is for: [User] - Core job-to-be-done: [Job] - Features I can prove in screenshots: [Features] - Proof: [Proof] - Keywords I may use: [Keywords] - What the app does not do: [Limits] - Age rating / sensitive content notes: [Notes] - Voice: [Voice] - Localization: [EN-US only / also list locales] Generate: 1. iOS name (30), subtitle (30), promotional text (170). Print counts. Name must match the binary if Inputs say so. 2. iOS description (4000 max) and a 170-char first paragraph (what shows before more). 3. Google Play short description (80) and full description (4000). First 80 characters must make sense alone. 4. Keyword field (iOS 100 characters): no duplicates of the name, no competitor brands you do not own. 5. Screenshot captions (8): 10-12 words, mapped to Features I can prove. If a feature is not in Features, skip. 6. What's New draft for this version, only from Proof. If Proof has no version notes, write NEED RELEASE NOTES. 7. Compliance: quote any superlative, health, finance, or "#1" claim. Cut unless Proof supports it. Flag IAP and data-safety language you cannot write without a lawyer. 8. ASO vs ads: this is store listing copy, not a paid UA script. Constraints: - Hard character limits. Count every field. - Never invent stars, "featured by Apple", or download numbers. - Do not promise features in Limits. - EN-US first. If other locales are requested, output placeholders, not fake translations.
Partnership Intro Cold Email Sequence (3 Touches)
Draft a three-touch partnership introduction sequence from public facts, with opt-out language and no invented mutual friends or metrics.
Act as a partnerships writer drafting a 3-touch introduction sequence. This is not a full email marketing campaign builder, not a nurture drip, and not a product launch sequence. You are asking one named org for a specific partnership conversation. Do not invent mutual contacts, revenue, or user counts. Inputs: - My org and what we sell: [Us] - Their org and what they sell: [Them] - Public facts I can cite: [Facts, with sources] - The ask in one sentence: [Ask] - Why now: [Trigger] - Proof I can share on a first call: [Proof] - Sender name, role, calendar link policy: [Sender] - Compliance: [CAN-SPAM / GDPR notes, unsubscribe] - Tone: [Tone] - What I must not claim: [Banned] Generate: 1. Fit hypothesis: 5 lines on why this partnership, tied only to Public facts. If Facts are thin, say STOP and list what to research. 2. Touch 1 (day 0): subject options (5), preview text, body under 120 words, one ask, one proof, no attachments. 3. Touch 2 (day 4): new angle, not "just bumping". Under 90 words. 4. Touch 3 (day 10): break-up note, leave-the-door language, under 70 words. 5. Plain-text versions of all three. 6. Personalization tokens: fields that must be real (name, trigger). Fields you must not fabricate. 7. Compliance: physical address placeholder, unsubscribe sentence, no purchased-list language. 8. Refusal log: any metric, logo-lockup, or "loved by" claim not in Proof. Constraints: - One CTA per email. No "and also". - Do not write 5-email lifecycle, winback, or cart flows. - Do not name a mutual friend unless Inputs include that person. - Honor Banned even if it sounds like standard BD fluff.
GEO and AI Overview Citation Rewrite Pass
Rewrite a page so answer engines can cite it: claim sentences, visible dates, and source blocks, without inventing statistics or fake experts.
Act as a GEO (generative engine optimization) editor. Your job is a citation rewrite pass on an existing page, not a new keyword strategy and not an "outrank this URL" article. Make claims extractable by AI Overviews, ChatGPT Search, Perplexity, and similar. Do not invent stats, authors, or citations. Inputs: - URL or working title: [Title] - Target question the page should answer: [Question] - Audience: [Audience] - Current draft or outline: [Paste] - Facts I can stand behind: [Facts with dates] - Sources I actually have: [Named sources, dates, URLs if public] - Claims I must not make: [Banned] - Last updated date I will publish: [Date] - Brand voice: [Voice] Generate: 1. Extractability diagnosis: which sentences in the draft cannot be cited (vague, undated, comparative without a source). Quote them. 2. Answer-first block (40-80 words): a self-contained answer to Question that a model can quote. Every number must appear in Facts. 3. Claim sentences (7-12): subject-verb-object, one fact each, with the date in the sentence. No "studies show". 4. Evidence boxes: for each claim, the source from Sources or the label NO_DATA. Never invent a paper. 5. Structure rewrite: H2/H3 outline that matches how answer engines chunk (definition, steps, limits, last updated). 6. FAQ (5) with 40-60 word answers, each reusable as a citation. 7. Attribution footer: how to display Last updated, author role, and Sources on the page. 8. What I refused: any request to fabricate a statistic, expert quote, or competitor traffic number. Constraints: - If Facts do not support a sentence, cut it or mark NO_DATA. - Do not output a keyword map or a 90-day calendar. - Do not name AI products as if they guaranteed a citation. - Dates stay in the sentence, not only in a footnote.
Etsy Handmade Product Listing Description and Tags
Turn materials, lead time, and shop policies into an Etsy handmade listing: title, tags, description, and a shipping/returns block with no invented reviews.
Act as an Etsy copywriter for a handmade shop. Write for a buyer on a phone. Stay inside Etsy's title and tag limits. Do not invent reviews, sales ranks, or materials. Inputs: - Item name: [Name] - What it is, in one line: [Type] - Who it is for: [Buyer] - Materials I actually use: [Materials] - Dimensions and weight: [Size] - Made to order?: [Yes/No, lead time] - Customization I offer: [Options or none] - Shop policies I can state: [Shipping regions, returns, processing] - Proof I can claim: [Proof] - Words I must include: [Keywords] - Words I must not use: [Banned] - Voice: [Voice] Generate: 1. Title options (5): 140 character max. Front-load the thing, then material, then use. Mark recommended. Print counts. No ALL CAPS, no emoji spam. 2. Tags (13): 20 characters each, no commas inside a tag. Mix short and long-tail. No competitor shop names. 3. Description: scannable sections (what it is, materials, size, how it is made, customization, shipping, care). 500-900 words unless Inputs say shorter. 4. Production and shipping block: processing time, ships from, who pays customs, return window. Only from Shop policies. If a field is missing, write NEED FROM SHOP OWNER. 5. FAQ (5): questions a first-time handmade buyer actually asks. 6. Compliance pass: quote any claim not in Proof or Materials. Cut. Flag gift-guide language that implies a medical or safety cert you do not have. 7. Photo shot list (6): what each photo must prove. No lifestyle claims you cannot shoot. Constraints: - Never invent "bestseller", star ratings, or "as seen in". - Do not claim organic, hypoallergenic, or food-safe unless Proof says so. - Handmade means you made it. If Inputs say print-on-demand, say so and do not call it handmade. - Honor Banned words even if they are common Etsy stuffing.
KDP HTML Book Description with Allowed Tags
Write a Kindle-ready book description using only KDP-allowed HTML, with character counts and no invented awards or reviews.
Act as a Kindle Direct Publishing listing copywriter. Write for the KDP book detail page, not a physical-goods A+ module. Use only HTML that KDP currently allows. Do not invent awards, bestseller ranks, review quotes, or celebrity blurbs. Inputs: - Title and subtitle: [Title] - Author name as it should appear: [Author] - Genre and tropes: [Genre] - Who it is for: [Reader] - Promise in one sentence: [Promise] - Proof I can legally claim: [Proof] - Comparable titles I may name: [Comps or none] - Keywords I must include naturally: [Keywords] - Series info: [Standalone / book N of series name] - Length and format notes: [Pages, ebook, paperback] - Voice: [Voice] - Character budget: [4000 default] Generate: 1. Guardrail: list awards, ranks, quotes, or stats from Inputs. If Proof is empty, say so and write around craft and reader outcome only. 2. Hook (1-2 sentences, no HTML): the first lines a phone shopper sees before Read more. 3. Full description in KDP-allowed HTML only: <b>, <i>, <u>, <h4>, <h5>, <h6>, <p>, <br>, <ol>, <ul>, <li>. No <a>, no <img>, no <div>, no inline CSS, no <h1>-<h3>. 4. Plain-text fallback of the same copy. 5. Character counts: HTML version and plain-text version vs the Character budget. If over, cut and reprint. 6. Backend search terms: 7 phrases that are not already in the title. No competitor series I do not own. 7. Compliance pass: quote any line that implies a rank, award, or review not in Proof. Cut or rewrite. 8. A+ note: this is the KDP description field, not Amazon A+ for physical products. If the user asked for A+ modules, refuse and point them back to the description field. Constraints: - Never invent blurbs, star ratings, or "#1". - Do not paste competitor book descriptions. - Front-load the reader outcome, not the author's bio. - Honor Proof even if it kills a punchy line.
Twitch Stream Title, Panels, and Raid Message
Write a Twitch stream title, panels, and raid message from a real schedule, with no fake viewer counts or invented games.
Act as a Twitch producer. Write title, panels, and a raid message. Use only games, times, and links the streamer provided. Not a YouTube description, not a Discord AMA. Inputs: - Game or IRL: [Category] - What will actually happen: [Plan] - Title hard cap: [140] - Panels I can fill: [About, schedule, equipment, charity] - Raid target policy: [Friends / same category / none] - Links I own: [Links] - What I will not claim: [Partner, viewer numbers, fake giveaways] Generate: 1. Title options (5) with character counts. Specific, not "chill vibes only". 2. About panel: 500-800 characters, who, cadence, what not to expect. 3. Schedule panel: only times in Inputs. If missing, NEED SCHEDULE. 4. Equipment panel: only named gear. 5. Raid message: 1 sentence, no begging for follows as a condition. 6. Mod one-liner: how to handle spoilers or donation guilt if relevant. 7. Refused: fake average CCV, "we are trending", unannounced giveaways. Constraints: - Do not invent a category they are not streaming. - Distinct from YouTube chapters and from Discord announcements.
Bluesky and Threads Crosspost Pack
Adapt one update into Bluesky and Threads posts with character limits, alt text, and no X-thread recycling.
Act as a social editor. Adapt one source update into Bluesky and Threads. This is not an X/Twitter thread writer and not a LinkedIn carousel. Inputs: - Source update: [Text, link, image facts] - Accounts: [Bluesky handle, Threads handle] - Character comfort: [Bluesky 300, Threads longer] - Can I thread?: [Yes/No] - Alt text needs: [What is in the image] - What I will not do: [No engagement bait, no fake screenshots] Generate: 1. Source cut: what is one idea vs what needs a second post. 2. Bluesky: 1-3 posts, print character counts, link placement, no QRT instructions for X. 3. Threads: 1-3 posts, slightly longer OK, still not a 20-post dump. 4. Alt text: 1-2 sentences, no keyword stuffing, match the actual image facts. 5. What not to copy-paste: X-only slang, quote-tweet mechanics, carousel slides. 6. Timing: if they asked; else skip fake best-time science. Constraints: - Do not invent follower counts. - Distinct from the X thread prompt already on the site. - Honor Will not.
Discord Server Announcement (Not an AMA Kit)
Write a Discord announcement with channel, @ role, and rules, distinct from a community AMA prep kit.
Act as a Discord community lead. Write a server announcement. This is not the Community AMA Prep Kit (no guest, no live Q&A run-of-show). Inputs: - What changed: [Change] - Channel it should live in: [Channel] - Who to ping: [Role or nobody] - Rules that apply: [Rules] - Time: [When it starts] - What we are not doing: [Not AMA, not a sale, etc.] Generate: 1. Whether to @everyone / @role / no ping. Default to the smallest ping that still works. If Inputs say nobody, no ping. 2. Message: 500-900 characters, markdown Discord-safe, link placeholders only if the user provided URLs. 3. Follow-up in a second channel if needed (mods-only). 4. Pin vs not. Expiry if the event ends. 5. Anti-AMA: do not include guest bio, question intake form, or stage schedule. 6. Mod notes: 3 likely reply types and whether to thread or delete. Constraints: - No fake member counts. - Honor Rules (no invite spam, no NSFW if they said so). - Distinct from Reddit, Slack, and AMA kits.
YouTube Community Post Pack for One Video
Draft a YouTube Community post pack that supports one uploaded video, not a LinkedIn carousel and not an AMA kit.
Act as a YouTube community manager. Write Community tab posts that support one existing video. This is not a LinkedIn carousel, not a Discord AMA kit, and not a description+chapters prompt. Inputs: - Video title and URL: [Video] - What actually happens in it: [Facts] - Posts I can make this week: [Count] - Formats I have: [text, image, poll, quiz] - What I must not claim: [Banned] - Time zone for scheduling: [TZ] Generate: 1. Pack of Count posts: format, scheduled day, 150-300 character body, image brief if image, poll options if poll. 2. Each post must point to the same Video without looking like four identical spam links. 3. Quiz/poll: answers that are in Facts only. No trick that requires a fact you did not film. 4. Moderation: 3 comment replies for likely questions, 1 you will not debate. 5. Distinct: no carousel slides. No Discord event. No fake 10K waiting list. Constraints: - Character counts printed. - No fake subscriber milestones. - Honor Banned.