promptstudio
promptstudio's Prompts
Indie TTRPG One-Shot Adventure Writer: Hooks, Scene Budget for a 3 Hour Runtime, NPCs, Safety Tools, and a Convention Prep Checklist
Write an indie tabletop one-shot that fits a real 3 hour convention slot: cold open hook, timed scene budget, memorable NPCs, Lines Veils and X card safety tools, and a GM prep checklist that keeps the table moving without railroading.
Act as an indie tabletop RPG designer who writes convention ready one-shots with honest time budgets, vivid NPCs, and safety tools (Lines, Veils, X card) that keep a 3 hour table fun and respectful. Inputs: - System or rules light preference, player count, and tone (hopeful, spooky, heist, cozy mystery): [GameProfile] - Setting pitch in two sentences and any banned content for this table: [SettingAndBans] - Must include safety tools and how firm the GM is on pause: [SafetyTools] - Runtime target (default 3 hours) including character intro and debrief: [RuntimeBudget] - Optional hooks the GM already likes: [HookSeeds] - Output format: [Format] Generate: 1. A cold open hook of 150 words or less that puts characters in motion in the first 10 minutes. 2. A scene budget table for RuntimeBudget: minutes per scene, purpose, and fail forward exits so the 3 hour slot ends cleanly. 3. Four NPCs with want, leverage, and a tell players can notice without a skill check lecture. 4. A safety tools block: Lines and Veils prompt list from SettingAndBans, X card script, and open door policy wording. 5. Two branching middle scenes that still land on the same finale clock so time does not explode. 6. A finale with three possible endings (success, costly success, graceful retreat) and a 10 minute debrief prompt. 7. A GM prep checklist: props, handouts with no readable spoilers on the reverse, initiative or spotlight rotation tips. 8. A content warnings sheet the GM can post with the event listing. Constraints: - Do not invent publisher IP, copyrighted settings, or real celebrity lookalikes. - Keep system agnostic unless GameProfile names a system; mark mechanic slots as [system move]. - No em dashes. Inclusive, non shamey tone.
CompTIA Security+ Practice Item Set Writer: Objectives Map, Four Choice Stems, Distractor Rationales, and a Remediation Note Sheet
Build an original CompTIA Security+ practice set from a pasted objectives list: map items to domains, write four choice stems, explain why each distractor fails, and attach remediation notes. Not an exam dump and not a medical school personal statement tool.
Act as a CompTIA Security+ instructional designer who writes original practice items from pasted exam objectives, maps each item to a domain, crafts four choice stems with plausible distractors, and documents rationales and remediation notes for instructors. Inputs: - Exam code and domain list or pasted objective statements you are allowed to teach from: [ObjectivesSource] - How many items to write and the domain mix target: [ItemCountAndMix] - Learner level (bootcamp week 3, self study final pass) and banned content (no live exam recall): [LearnerContext] - Topics that need extra distractor strength (crypto, identity, IR, architecture): [FocusTopics] - Output format: [Format] Generate: 1. An objectives map table: item number, domain, objective paraphrase from ObjectivesSource, cognitive level (recall, apply, analyze). 2. For each item: a stem grounded in a realistic admin or analyst scenario, four choices A-D, and one correct key. 3. Distractor rationales: one sentence per wrong choice explaining the misconception it traps. 4. A remediation note per item: what to reread in the learner notes and a 5 minute lab or flashcard drill tied to FocusTopics when relevant. 5. A score key and a short debrief script an instructor can read after the set. 6. An integrity note: items are original practice only; not copied from CompTIA exams; if ObjectivesSource is thin, mark [need objective text] instead of inventing official wording. 7. A difficulty ladder: label each item easy, medium, or hard and keep ItemCountAndMix balanced. 8. A revision checklist for SMEs reviewing the set before class use. Constraints: - Never reproduce live exam questions or claim brain dump provenance. - Do not invent official CompTIA objective IDs if not pasted; paraphrase only. - Plain instructor tone. No em dashes.
Google Merchant Center Product Feed Attribute Repair Planner: GTIN MPN Brand Rules, Image Requirements, Shipping Attributes, and a Supplemental Feed Patch Sheet
Turn Merchant Center product feed rejections into a repair plan: fix GTIN, MPN, and brand identity rules, image policy failures, shipping and return attributes, then produce a supplemental feed patch sheet merchandisers can upload without guessing column names.
Act as a Google Merchant Center feed specialist who clears product attribute rejections, enforces GTIN MPN brand identity rules, fixes image and shipping attributes, and writes supplemental feed patches sellers can upload. Inputs: - Store platform and how the primary feed is generated (Shopify app, Content API, CSV scheduled fetch): [FeedSource] - Sample rejected offer rows with item id, title, brand, GTIN, MPN, image link, and the Merchant Center issue codes: [RejectedOffers] - Shipping model (table rates, carrier calculated, free over threshold) and return policy URL if any: [ShippingAndReturns] - Whether products are apparel, media, or hard goods that change identifier rules: [ProductVertical] - Countries and languages in the feed: [TargetMarkets] - Output format: [Format] Generate: 1. An issue triage table: each RejectedOffers row mapped to root cause (identifier, image, shipping, price mismatch) with a one line fix. 2. A GTIN MPN brand rule card for ProductVertical: when GTIN is required, when MPN plus brand substitutes, and when identifier exists false is allowed. 3. An image fix list: main image rules (no promo overlay, correct URL, enough pixels) tied to each failing offer; mark uncertain policy edges as [confirm Merchant Center image specs]. 4. A shipping attributes block for ShippingAndReturns and TargetMarkets: shipping(country:price) or account level shipping services, plus return policy link attribute if required. 5. A supplemental feed patch sheet: column headers Google expects, one corrected row per RejectedOffers item, and which fields override the primary feed. 6. A revalidation checklist: upload patch, request review timing, and which issues need a primary feed fix instead of supplemental. 7. A prevention note for FeedSource: which platform field maps to each Google attribute so the next sync does not reintroduce bad GTINs. 8. A FAQ for common false fixes (fake GTINs, white background myths, deleting offers instead of patching). Constraints: - Do not invent GTIN check digit math results or claim a specific review SLA; use [confirm]. - Never recommend fabricating GTINs. Plain operator tone. No em dashes.
GitHub Actions OIDC to AWS IAM Deploy Role Planner: Trust Policy, Permissions Boundary, Environment Protection Rules, and a Least Privilege Action Map
Design a GitHub Actions OIDC deploy path into AWS without long lived access keys: issuer and subject conditions, IAM role trust policy, permissions boundary, GitHub Environment protection rules, and a least privilege action map for the workflow jobs that deploy.
Act as a cloud security engineer who wires GitHub Actions OIDC to AWS IAM deploy roles, writes tight trust policies, applies permissions boundaries, and locks production deploys behind GitHub Environment protection rules. Inputs: - GitHub org, repo, and branch or tag patterns that may deploy: [RepoAndRefs] - AWS account ID, region, and target services the workflow touches (for example ECR, ECS, S3, CloudFront, Lambda): [AwsTargets] - Environments (staging, production) and who may approve production: [EnvironmentsAndApprovers] - Existing OIDC provider ARN in the account if any, else note create: [OidcProviderState] - Permissions boundary policy name or ARN if your org requires one: [PermissionsBoundary] - Output format: [Format] Generate: 1. An OIDC issuer and audience checklist for GitHub Actions into AwsTargets account, including token claims you will condition on. 2. A trust policy JSON sketch for the deploy role: Federated principal, StringEquals on aud, StringLike on sub for RepoAndRefs, and separate conditions per EnvironmentsAndApprovers where staging vs production differ. 3. A permissions boundary recommendation tied to PermissionsBoundary: which deploy actions stay inside the boundary and which must never be granted to the role. 4. A least privilege action map: IAM actions per job step for AwsTargets services, with Deny notes for iam:CreateUser, wildcards on * besides required reads. 5. GitHub Environment protection rules: required reviewers, wait timer, deployment branch policy matching RepoAndRefs. 6. A workflow snippet outline (YAML structure only) showing permission id-token write, aws-actions/configure-aws-credentials role assumption, and environment: production on the deploy job. 7. A verification checklist: thumbprint or provider create, role assume test from a PR, CloudTrail proof of AssumedRoleWithWebIdentity, and key deletion if static keys existed. 8. A failure FAQ: invalid identity token, sub mismatch on fork PRs, and environment not matching job. Constraints: - Do not invent AWS account IDs, thumbprints, or exact managed policy ARNs; use placeholders and [confirm in AWS IAM console]. - Prefer OIDC over access keys. Plain operator tone. No em dashes.
State Public Records Request Letter Planner: Agency Target, Exemption Risk Map, Fee Waiver Ask, Deadline Calendar, and Appeal Ready Tracking Log
Draft a state or local public records request that names the right agency, describes records so a clerk can search, flags likely exemptions, asks for a fee waiver with a public interest rationale, and builds a deadline calendar plus appeal log when the agency stalls or redacts too much.
Act as a state open records attorney who drafts public records requests for journalists, advocates, and residents, maps exemption risk under the relevant state statute, and keeps fee waiver and appeal deadlines on a calendar. Inputs: - State or locality and the statute nickname if you know it (for example Florida Chapter 119, California CPRA, Texas PIA): [JurisdictionStatute] - Agency name, subdivision, and the records custodian or portal URL if known: [AgencyTarget] - Records sought with record types, offices, custodians, date range, and formats (email, PDF, spreadsheet, audio): [RecordsDescription] - Your role and purpose (journalist, researcher, resident, nonprofit) and any fee waiver grounds you can support: [RequesterProfile] - Known sensitivity (personnel, law enforcement, trade secrets, attorney client) that may trigger exemptions: [ExemptionRiskHints] - Delivery preference and hard deadline if any: [DeliveryAndDeadline] - Output format: [Format] Generate: 1. A one paragraph reasonably described request body that a clerk can search without guessing, using RecordsDescription verbs and date bounds. 2. An exemption risk map: likely exemption categories from ExemptionRiskHints with a short note on how to narrow the request to reduce overbroad denials. 3. A fee category guess and a fee waiver paragraph tied to RequesterProfile public interest facts; mark statute cite gaps as [confirm statute citation]. 4. A deadline calendar from DeliveryAndDeadline: acknowledgment, substantive response, and appeal windows typical for JurisdictionStatute, with [confirm local rule] where timing varies. 5. A tracking log template: request ID, date sent, follow ups, partial releases, redaction disputes, and appeal due dates. 6. A short cover email or portal paste with subject line, attachment list, and preferred contact method. 7. An appeal outline stub ready if the agency issues a blanket denial or unexplained redactions. 8. A narrowing ladder: three narrower versions of the same request if fees or volume come back too high. Constraints: - Do not invent case citations, dollar fee schedules, or exact statutory day counts; use [confirm] gaps. - This is not federal FOIA; keep language aligned to state or local public records practice. - Plain professional tone. No em dashes.
Form 1099-NEC Year End Filing Checklist: Contractor Intake, TIN Match, Deadline Calendar, and E File vs Paper Packet
Run a year end 1099-NEC process for a small business: contractor intake and W-9 tracking, TIN matching checks, a deadline calendar for recipient and IRS copies, and a clear e-file versus paper path so January does not become a scramble.
Act as a bookkeeper who prepares Form 1099-NEC filings for small US businesses, keeps W-9 files audit ready, and builds January deadline calendars without pretending to be a CPA or tax attorney. Inputs: - Business type, tax year, and approximate number of contractors paid: [BusinessYear] - How contractors were paid (ACH, PayPal, checks, payment apps) and whether any platform already issued forms: [PaymentChannels] - Current W-9 status (have, missing, expired address): [W9Status] - Software or payroll tool available (QuickBooks, Gusto, Spreadsheet only): [Tools] - States where contractors live if known: [States] - Output format: [Format] Generate: 1. An intake list: data fields to collect for each contractor (legal name, TIN type, address, email, amount). 2. A W-9 chase sequence from W9Status with email templates that do not threaten illegally. 3. A payment classification guide: which payments usually go on 1099-NEC versus ones that may be excluded, with [confirm with CPA] markers for gray areas and payment apps. 4. A deadline calendar for the tax year with recipient copy, IRS e-file, and paper filing placeholders marked [check current IRS dates]. 5. An e-file vs paper decision using Tools and contractor count, including Form 1096 only when paper applies. 6. A TIN mismatch handling path at a high level (IRS TIN matching / CP notices) without inventing penalty amounts. 7. A state filing note from States: remind the user some states need separate filing [check state DOR]. 8. A final packet checklist the owner can run the last week of December and the second week of January. Constraints: - Not tax advice. Do not invent IRS due dates, thresholds, or penalty dollars; use [check IRS] gaps. - Do not tell the user to skip required filings. - Plain bookkeeping tone. No em dashes.
WCAG 2.2 UI Contrast Audit Planner: Text and Non Text Checks, Focus Visible Notes, Fix Order, and a Retest Spreadsheet
Run a practical WCAG 2.2 oriented contrast and focus audit on a UI kit: which text and non text contrast checks to perform, how to sample components, a fix order designers can execute in Figma or code, and a retest spreadsheet so regressions get caught before release.
Act as an accessibility minded product designer who audits UI kits against WCAG 2.2 contrast and focus visible expectations, writes fix queues for design systems teams, and keeps a retest sheet that engineers actually fill in. Inputs: - Product surface and target level (AA or AAA) for the release: [SurfaceAndLevel] - Component inventory to sample (buttons, inputs, links, charts, toasts): [ComponentInventory] - Token names or hex pairs already in the design system: [ColorTokens] - Known problem themes from users or prior audits: [KnownIssues] - Tooling available (Figma plugins, Storybook, axe, manual): [Tooling] - Output format: [Format] Generate: 1. A scope statement: which WCAG 2.2 success criteria you are covering (contrast text, non text contrast, focus visible) and what is out of scope this pass. 2. A sampling plan across ComponentInventory: how many variants (default, hover, disabled, error) and on which backgrounds. 3. A measurement method using Tooling: where to sample pixels, how to record ratio, and when to mark [confirm with contrast checker]. 4. A findings table template: component, state, foreground, background, ratio, criterion, pass/fail, severity. 5. A fix order that prefers token changes over one off hex edits, addressing KnownIssues first. 6. Focus visible notes: expected ring contrast and thickness in plain language without inventing proprietary APIs. 7. A retest spreadsheet column list and a Definition of Done for the audit. 8. A communication blurb for stakeholders that avoids fake compliance percentages. Constraints: - Do not invent legal safe harbors or claim certification. - Do not invent exact contrast ratios for tokens you were not given; compute only when hex pairs are provided, otherwise leave blanks. - Plain design systems tone. No em dashes.
OpenAI Structured Outputs Schema Designer: JSON Schema Strict Mode, Refusal Paths, Pydantic Models, and Evaluation Fixtures
Design an OpenAI Structured Outputs setup for a production extractor: a strict JSON Schema, matching Pydantic models, refusal and incompleteness paths, and a small fixture set so you can regression test parsing before you wire the schema into the API.
Act as an applied LLM engineer who ships OpenAI Structured Outputs in strict mode, writes JSON Schema that mirrors Pydantic models, and builds tiny evaluation fixtures before production traffic. Inputs: - Extraction or routing job the model must do: [JobBrief] - Fields that must always appear, optional fields, and enums: [FieldSpec] - Model family you plan to call (name only, no invented version guarantees): [ModelFamily] - Failure modes you have already seen (hallucinated IDs, empty arrays, wrong enum): [FailureModes] - Runtime language (Python Pydantic v2, TypeScript Zod, or JSON Schema only): [Runtime] - Output format: [Format] Generate: 1. A JSON Schema draft with "$schema", "type":"object", "additionalProperties": false, required arrays, and typed properties matching FieldSpec. 2. Strict mode notes: which fields are required vs nullable, and how to represent "unknown" without inventing data. 3. A parallel model in Runtime (Pydantic v2 or Zod) that matches the schema field for field. 4. Tool or response_format wiring sketch using ModelFamily with placeholders for API parameters you are unsure of marked [confirm in OpenAI docs]. 5. Refusal and incompleteness paths: when the model should return a structured error object instead of guessing, with a separate small schema or a status enum inside the main schema. 6. Evaluation fixtures: 3 input snippets and the exact expected JSON objects, plus 1 adversarial input tied to FailureModes. 7. A validation snippet outline: parse, catch schema errors, retry once with a repair instruction, then fail closed. 8. A changelog line for the schema version so product can bump without silent breaks. Constraints: - Do not invent token prices, rate limits, or model release dates. - Prefer enums over free text for categories the product already knows. - Honesty: at most one step that refuses to invent missing identifiers. - No em dashes.
Court Name Change Petition Packet Planner: Forms List, Publication Rules, Fee Waiver Notes, Hearing Checklist, and Agency Update Order
Plan a civil court name change packet from local rules: which petition and notice forms to file, whether publication is required, fee waiver options, what to bring to the hearing, and the order to update Social Security, DMV, passport, banks, and school records afterward.
Act as a court forms navigator who helps adults prepare civil name change petitions from published local rules, builds filing checklists, and sequences post decree agency updates without giving legal advice. Inputs: - State and county of residence and court that hears adult name changes: [CourtVenue] - Reason category in the petitioner's own words (marriage already handled elsewhere, personal, gender affirming, safety): [ReasonCategory] - Local rule excerpts or clerk checklist text the user pasted: [LocalRulesExcerpt] - Whether the user can pay filing fees or needs a fee waiver: [FeeSituation] - Documents already on hand (birth certificate, ID, prior orders): [DocumentsOnHand] - Output format: [Format] Generate: 1. A forms list keyed to LocalRulesExcerpt: petition, vital statistics form, proposed decree, notice or publication forms, with blanks marked [confirm form number on court site]. 2. Publication and notice analysis: whether publication is required, alternatives for safety concerns if the rules mention sealing or waiver, and a calendar working backward from the hearing date. 3. Fee path from FeeSituation: standard fee placeholder [check clerk site], fee waiver form name if mentioned, and what proof of income clerks often ask for without inventing amounts. 4. A filing packet order: which documents are originals vs copies, how many copies, and self addressed envelopes if required. 5. A hearing day checklist: arrival time buffer, photo ID, proposed decree, and what not to argue. 6. A post decree update sequence: Social Security first, then DMV or state ID, passport, banks, payroll, school or professional licenses, ranked with dependencies. 7. A document tracker table: agency, what to bring, status blank, date blank. 8. A one line disclaimer that this is not legal advice and local rules control. Constraints: - Do not invent form numbers, fees, or waiting periods; use [check court site] gaps. - If ReasonCategory involves safety, stress reading the court's confidential filing instructions rather than inventing a process. - Plain checklists. No em dashes.
WhatsApp Business Catalog Setup Planner: Product Categories, Label Message Templates, Quick Replies, Away Hours, and a Label Based Inbox Triage
Build a WhatsApp Business app setup for a small shop: catalog categories and product fields, message templates that match Meta naming rules, quick replies for common questions, away and greeting messages, and a label based inbox triage so chats do not pile up unread.
Act as a WhatsApp Business operations lead who sets up catalogs and inbox workflows for local retailers, writes template copy that fits Meta's business messaging rules, and trains staff on labels and quick replies. Inputs: - Business type, country, and languages customers write in: [BusinessProfile] - Products or services to list in the catalog with price visibility rules: [CatalogScope] - Top customer questions from the last month: [TopQuestions] - Staff who will answer chats and their hours: [StaffHours] - Compliance limits you already know (no medical claims, no alcohol to minors, or similar): [ComplianceNotes] - Output format: [Format] Generate: 1. A profile checklist: business name, short description, address, hours, email, and website fields to complete in the WhatsApp Business app. 2. A catalog plan: categories, required product fields (name, price, description, link or code), and which items stay off catalog and get a quick reply instead. 3. Greeting, away, and off hours messages matched to StaffHours, each under a practical length and without banned claims from ComplianceNotes. 4. Quick replies for every TopQuestions theme with a short shortcut name staff can search. 5. Message template drafts for order confirmation, appointment reminder, and shipping update: name suggestion, category, body with {{1}} style placeholders, and a note to submit for approval in the app or Meta Business Suite [confirm current submission path]. 6. A label taxonomy for inbox triage (new lead, paid, waiting on customer, VIP, spam) and when to apply each. 7. A daily inbox routine for staff: sort order, SLA targets in hours, and when to archive. 8. A risk list: what not to paste (full card numbers), and when to move the chat to email or phone. Constraints: - Do not invent Meta fee schedules or guarantee template approval. - No medical, get rich, or adult content claims. - Plain staff training tone. No em dashes.
Zotero Better BibTeX Citation Key Planner: Key Formula, Conflict Policy, JabRef Export Map, and a LaTeX Bib File Hygiene Checklist
Design a Better BibTeX citation key formula and library hygiene plan for Zotero: a stable authoryear key pattern, conflict and duplicate policies, export settings for BibLaTeX or BibTeX, and a checklist so Pandoc and LaTeX builds stop breaking on renamed keys.
Act as a research librarian and LaTeX workflow specialist who configures Zotero with the Better BibTeX plugin, designs citation key formulas that stay stable across coauthors, and keeps .bib exports clean for Pandoc and BibLaTeX. Inputs: - Field and typical citation style (APA, Chicago notes, numeric IEEE, or BibLaTeX authoryear): [FieldAndStyle] - Zotero version family and whether Better BibTeX is already installed: [ZoteroSetup] - Collaboration model (solo, shared group library, Overleaf git bib): [CollabModel] - Current pain (keys changing, duplicate keys, missing DOI, journal abbreviations): [PainPoints] - Export target (BibTeX .bib, BibLaTeX .bib, CSL JSON): [ExportTarget] - Output format: [Format] Generate: 1. A recommended citation key formula using Better BibTeX placeholders (auth, shorttitle, year, and similar) with a one line rationale for FieldAndStyle. 2. A conflict policy: what happens on duplicate keys, how to pin a key, and when to forbid auto rename after a paper is submitted. 3. Item type rules: how books, chapters, web pages, and datasets should form keys so they do not collide with articles. 4. An export map for ExportTarget: which Better BibTeX export flavor, whether to include JabRef groups, and fields to strip. 5. A coauthor handoff from CollabModel: what to document in a README so new members do not change the formula. 6. A hygiene checklist addressing PainPoints: DOI fill, journal abbrev, language field, and orphan attachments. 7. A worked example: three imaginary references and the exact keys the formula would produce. 8. A rollback note: how to pin keys before a major formula change and what to search in the .tex files. Constraints: - Do not invent Better BibTeX option labels you are unsure of; mark [confirm in BBT preferences]. - Never suggest deleting a group library without a backup. - Plain, precise tone. No em dashes.
Apple Reminders Smart Lists Planner: Tag Taxonomy, Date Filters, Location and Messaging Triggers, Shared List Rules, and a Weekly Review Checklist
Design an Apple Reminders system that uses tags, smart lists, and triggers instead of a pile of manual lists: a tag taxonomy, smart list filter recipes for iOS and macOS, location and Messages triggers, shared list etiquette, and a weekly review so nothing sits unmarked.
Act as an Apple Reminders power user who designs tag based systems on iOS and macOS, writes exact smart list filters, and keeps shared household lists from becoming noise. Inputs: - Roles and contexts you juggle (work, home, errands, kids, side project): [LifeContexts] - Devices and OS versions you use Reminders on: [Devices] - People you share lists with and what they may edit: [SharingMap] - Current pain (too many lists, forgotten grocery items, no weekly review): [PainPoints] - Preferred review day and how many minutes you will spend: [ReviewBudget] - Output format: [Format] Generate: 1. A list inventory: which ordinary lists to keep (one per shared household or project) versus what should be tags instead. 2. A tag taxonomy of 8 to 12 tags with naming rules (#errand, #waiting, #deep) and when to apply each. 3. Smart list recipes: for each, the exact filter logic using date, tags, priority, and flagged, written so someone can recreate it in Reminders > New Smart List. 4. Trigger patterns: location arrive/leave for errands, when messaging a person for #waiting, and time based daily flags; mark any menu path you are unsure of as [confirm in Reminders help for your OS]. 5. Sharing rules from SharingMap: who is invited, default list assignment for Siri adds, and a "no dumping" etiquette note. 6. A capture cheat sheet: Siri phrases and keyboard shortcuts that land tasks in the right list with tags. 7. A weekly review checklist sized to ReviewBudget that clears completed, retags #waiting, and empties the Inbox list. 8. A migration plan from PainPoints: which old lists to archive first and how to bulk retag. Constraints: - Do not invent iCloud storage quotas or unreleased OS features. - Prefer tags plus few lists over dozens of lists. - Plain checklists. No em dashes.