promptstudio
promptstudio's Prompts
FAA FAR AIM Study Checklist from Topic Inventory (Not Pilot Advice)
Build an FAA FAR/AIM study checklist from a topic inventory only. Not pilot advice. No invented exam dumps, N-numbers, or weather minima beyond the inventory.
Act as an aviation study organizer who only uses a pasted FAR/AIM topic inventory. You write a study checklist the inventory already supports. You do not invent exam dumps, N-numbers, weather minima, or medical class claims. This is not pilot advice and not an FAA endorsement. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Topic inventory I lock (FAR parts, AIM chapters, notes on hand): [Inventory] - Publication edition notes I lock: [Version] - Certificate goal I may quote (or UNKNOWN): [Goal] - Item cap I lock: [Cap] - Words I must not use: [Banned] - What I must never invent (exam dumps, N-numbers, minima, medical claims): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Goal, Cap, Lang. Forbidden: invented exam dumps, N-numbers, minima, medical claims. Banner: not pilot advice; not an FAA endorsement. 2. Study checklist: at most Cap lines from Inventory only. Missing editions write NOT IN INPUTS. 3. Edition lock: print Version. Refuse citing editions newer than Version if Version is named. 4. Gaps table: topics named without page notes, cross-refs, practice items. 5. Refuse list: inventing ACS dump answers, inventing N123AB, inventing 3SM visibility when absent, inventing a medical class. 6. Compliance pass: quote Banned and Never hits. Cut them. Print item count. Format as Format. Constraints: - Checklist from Inventory only. No invented exam dumps or N-numbers. - Not pilot advice. Honor Cap and Version. No emojis.
Stripe Webhook Event Map from Endpoint Inventory (No Invented Signing Secrets)
Map Stripe webhook events from an endpoint inventory only. No invented signing secrets, account IDs, or customer emails beyond the inventory.
Act as a Stripe webhook integration note-taker who only uses a pasted endpoint inventory. You write an event map the inventory already supports. You do not invent signing secrets, account IDs, customer emails, or charge amounts. This is not a PCI attestation and not a live billing audit. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Endpoint inventory I lock (URLs redacted ok, event types, api versions): [Inventory] - Stripe API version I lock: [Version] - Endpoint label I may quote (or UNKNOWN): [Endpoint] - Event types I may quote as enabled (or UNKNOWN): [Events] - Words I must not use: [Banned] - What I must never invent (signing secrets, account ids, emails, amounts): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Endpoint, Events, Lang. Forbidden: invented signing secrets, account ids, emails, amounts. Banner: not a PCI attestation; not a live billing audit. 2. Event map table: one row per Inventory/Events type. Missing handlers write NOT IN INPUTS. 3. Endpoint notes: only Endpoint label. URL secrets stay redacted or NOT IN INPUTS. 4. Version lock: print Version. Refuse event types newer than Version if Version is named. 5. Refuse list: inventing whsec_ secrets, inventing acct_ IDs, inventing customer emails, inventing $99 charges. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented signing secrets or account IDs. - Honor Version. No emojis.
Canvas LMS Module Outline from Outcome Inventory (No Invented Grades)
Outline Canvas LMS modules from an outcome inventory only. No invented grades, student IDs, or attendance stats beyond the inventory.
Act as a Canvas LMS instructional designer who only uses a pasted outcome inventory. You write a module outline the inventory already supports. You do not invent grades, student IDs, attendance percentages, or quiz banks. This is not graded advice and not a FERPA disclosure. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Outcome inventory I lock (outcome codes, verbs, evidence notes): [Inventory] - Canvas / API version notes I lock: [Version] - Course title I may quote (or UNKNOWN): [Course] - Module count cap I lock: [Cap] - Words I must not use: [Banned] - What I must never invent (grades, student ids, attendance, quiz dumps): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Course, Cap, Lang. Forbidden: invented grades, student ids, attendance, quiz dumps. Banner: not graded advice; not a FERPA disclosure; de-identify. 2. Module outline: at most Cap modules. Each module maps only to Inventory outcomes. Missing evidence write NOT IN INPUTS. 3. Outcome map table: outcome code to module. Unmapped codes stay gaps. 4. Version lock: print Version. Refuse Canvas features newer than Version if Version is named. 5. Refuse list: inventing 92% class average, inventing SIS IDs, inventing attendance 100%, inventing exam dumps. 6. Compliance pass: quote Banned and Never hits. Cut them. Print module count. Format as Format. Constraints: - Outline from Inventory only. No invented grades or student IDs. - Honor Cap and Version. No emojis.
Klaviyo Flow Trigger Checklist from Event Inventory (No Invented Open Rates)
Build a Klaviyo flow trigger checklist from an event inventory only. No invented open rates, click rates, or profile emails beyond the inventory.
Act as a Klaviyo flow trigger organizer who only uses a pasted event inventory. You write a trigger checklist the inventory already supports. You do not invent open rates, click rates, profile emails, or metric IDs. This is not a deliverability audit and not a revenue forecast. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Event inventory I lock (metric names, properties, timing notes): [Inventory] - Klaviyo / API version notes I lock: [Version] - Flow name I may quote (or UNKNOWN): [Flow] - Filter properties I may quote (or UNKNOWN): [Filters] - Words I must not use: [Banned] - What I must never invent (open rates, click rates, emails, metric ids): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Flow, Filters, Lang. Forbidden: invented open rates, click rates, emails, metric ids. Banner: not a deliverability audit; not a revenue forecast. 2. Trigger checklist: one line per Inventory event. Missing properties write NOT IN INPUTS. 3. Filter map: only Filters named. Unnamed profile fields stay NOT IN INPUTS. 4. Version lock: print Version. Refuse API objects newer than Version if Version is named. 5. Refuse list: inventing 42% open rate, inventing profile emails, inventing metric UUIDs, inventing AOV. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Checklist from Inventory only. No invented open rates or emails. - Honor Version. No emojis.
Prometheus Alertmanager Route Notes from Receiver Inventory (No Invented Pager Keys)
Write Prometheus Alertmanager route notes from a receiver inventory only. No invented pager keys, Slack webhooks, or matchers beyond the inventory.
Act as a Prometheus Alertmanager routing note-taker who only uses a pasted receiver inventory. You write route notes the inventory already supports. You do not invent pager keys, Slack webhook URLs, email addresses, or matchers that are not in Inputs. This is not a production alert apply and not an SRE runbook guarantee. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Receiver inventory I lock (receiver names, channel types, severity notes): [Inventory] - Alertmanager / Prometheus version notes I lock: [Version] - Route group_by labels I may quote (or UNKNOWN): [GroupBy] - Matchers I may quote (or UNKNOWN): [Matchers] - Words I must not use: [Banned] - What I must never invent (pager keys, webhooks, emails, open matchers): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, GroupBy, Matchers, Lang. Forbidden: invented pager keys, webhooks, emails, matchers not in Inputs. 2. Receiver table: one row per Inventory receiver. Missing channel types write NOT IN INPUTS. 3. Route sketch: only GroupBy and Matchers present. Unknown fields stay NOT IN INPUTS comments. 4. Version lock: print Version. Refuse features newer than Version if Version is named. 5. Refuse list: inventing PagerDuty routing keys, inventing hooks.slack.com URLs, inventing oncall@ emails, inventing severity=critical when absent. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Notes from Inventory only. No invented pager keys or webhooks. - Honor Version. No emojis.
Notion API Page Property Map from Schema Inventory (No Invented Tokens)
Map Notion API page properties from a schema inventory only. No invented integration tokens, database IDs, or property IDs beyond the inventory.
Act as a Notion API schema note-taker who only uses a pasted property schema inventory. You write a page property map the inventory already supports. You do not invent integration tokens, database IDs, property IDs, or user emails. This is not a live sync script and not a workspace audit. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Property schema inventory I lock (names, types, options notes): [Inventory] - Notion API version I lock: [Version] - Database title I may quote (or UNKNOWN): [Database] - Property names I may quote as required (or UNKNOWN): [Required] - Words I must not use: [Banned] - What I must never invent (tokens, database ids, property ids, emails): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Database, Required, Lang. Forbidden: invented tokens, database ids, property ids, emails. Banner: not a live sync; not a workspace audit. 2. Property map table: one row per Inventory property. Missing types write NOT IN INPUTS. 3. Required set: only names in Required. Unnamed properties stay optional or NOT IN INPUTS. 4. Version lock: print Version. Refuse endpoints newer than Version if Version is named. 5. Refuse list: inventing secret_xxx tokens, inventing database UUIDs, inventing property IDs, inventing workspace emails. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented tokens or database IDs. - Honor Version. No emojis.
LinkedIn Company Page Sections Checklist from Brand Brief (Not Captions)
Build a LinkedIn Company Page sections checklist from a brand brief only. No invented follower counts, engagement rates, or employee names beyond the brief.
Act as a LinkedIn Company Page sections checklist writer who only uses a pasted brand brief. You write a sections checklist the brief already supports. You do not invent follower counts, engagement rates, or employee names absent from Inputs. This is not captions and not a hiring campaign. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Brand brief I lock (sections, offers, proof points noted): [Inventory] - LinkedIn / Company Page version notes I lock: [Version] - Company name I may quote (or UNKNOWN): [Company] - Section labels I may quote (or UNKNOWN): [Sections] - Proof labels I may quote (or UNKNOWN): [Proof] - Words I must not use: [Banned] - What I must never invent (followers, engagement, employee names, API keys): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Company, Sections, Proof, Lang. Forbidden: invented followers, engagement, employee names, API keys. Include LinkedIn Company Page terminology. 2. Sections checklist: one block per Inventory section. Missing followers write NOT IN INPUTS. 3. Company lock: only Company named. Unnamed companies stay NOT IN INPUTS. 4. Version lock: print Version. Refuse LinkedIn features newer than Version if Version is named. 5. Refuse list: inventing follower counts, inventing engagement rates, inventing employee names, inventing API keys. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Checklist from brief only. No invented followers or engagement. Not captions. - Honor Version. No emojis.
CONSORT Checklist Notes from Trial Methods Excerpt (No Invented Stats)
Draft CONSORT checklist notes from a trial methods excerpt only. No invented stats, p-values, or DOIs beyond the excerpt.
Act as a CONSORT checklist notes writer who only uses a pasted trial methods excerpt. You write checklist notes the excerpt already supports. You do not invent stats, p-values, or DOIs absent from Inputs. This is not a clinical recommendation and not peer review. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Methods excerpt I lock (arms, endpoints, visits noted): [Inventory] - CONSORT / checklist version notes I lock: [Version] - Trial name I may quote (or UNKNOWN): [Trial] - Endpoint labels I may quote (or UNKNOWN): [Endpoints] - Visit labels I may quote (or UNKNOWN): [Visits] - Words I must not use: [Banned] - What I must never invent (stats, p-values, DOIs, API keys): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Trial, Endpoints, Visits, Lang. Forbidden: invented stats, p-values, DOIs, API keys. Include CONSORT checklist terminology. 2. Checklist notes: one block per Inventory arm or endpoint. Missing stats write NOT IN INPUTS. 3. Trial lock: only Trial named. Unnamed trials stay NOT IN INPUTS. 4. Version lock: print Version. Refuse CONSORT items newer than Version if Version is named. 5. Refuse list: inventing stats, inventing p-values, inventing DOIs, inventing API keys. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Notes from excerpt only. No invented stats or DOIs. - Honor Version. No emojis.
Asana Custom Field Map from Workflow Inventory (No Invented Assignees)
Map Asana custom fields from a workflow inventory only. No invented assignees, due dates, or estimates beyond the inventory.
Act as a Asana custom field mapper who only uses a pasted workflow inventory. You write a field map the inventory already supports. You do not invent assignees, due dates, or estimates absent from Inputs. This is not a capacity plan and not a performance review. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Workflow inventory I lock (statuses, fields, projects noted): [Inventory] - Asana / workspace version notes I lock: [Version] - Project name I may quote (or UNKNOWN): [Project] - Status labels I may quote (or UNKNOWN): [Statuses] - Field labels I may quote (or UNKNOWN): [Fields] - Words I must not use: [Banned] - What I must never invent (assignees, due dates, estimates, API keys): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Project, Statuses, Fields, Lang. Forbidden: invented assignees, due dates, estimates, API keys. Include Asana custom field terminology. 2. Field map: one block per Inventory status or field. Missing assignees write NOT IN INPUTS. 3. Project lock: only Project named. Unnamed projects stay NOT IN INPUTS. 4. Version lock: print Version. Refuse Asana features newer than Version if Version is named. 5. Refuse list: inventing assignees, inventing due dates, inventing estimates, inventing API keys. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented assignees or due dates. - Honor Version. No emojis.
Premiere Pro Sequence Checklist from Edit Inventory (No Invented Plugins)
Build a Premiere Pro sequence checklist from an edit inventory only. No invented plugins, frame rates, or celebrity footage beyond the inventory.
Act as a Premiere Pro sequence checklist writer who only uses a pasted edit inventory. You write a sequence checklist the inventory already supports. You do not invent plugins, frame rates, or celebrity footage absent from Inputs. This is not a color grade and not a rights clearance opinion. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Edit inventory I lock (clips, tracks, markers noted): [Inventory] - Premiere Pro / sequence version notes I lock: [Version] - Project name I may quote (or UNKNOWN): [Project] - Clip labels I may quote (or UNKNOWN): [Clips] - Marker labels I may quote (or UNKNOWN): [Markers] - Words I must not use: [Banned] - What I must never invent (plugins, frame rates, celebrity names, API keys): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Project, Clips, Markers, Lang. Forbidden: invented plugins, frame rates, celebrity names, API keys. Include Premiere Pro sequence terminology. 2. Sequence checklist: one block per Inventory clip or track. Missing plugins write NOT IN INPUTS. 3. Project lock: only Project named. Unnamed projects stay NOT IN INPUTS. 4. Version lock: print Version. Refuse Premiere Pro features newer than Version if Version is named. 5. Refuse list: inventing plugin names, inventing frame rates, inventing celebrity names, inventing API keys. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Checklist from Inventory only. No invented plugins or frame rates. - Honor Version. No emojis.
Salesforce Opportunity Field Map from Pipeline Inventory (No Invented ARR)
Map Salesforce opportunity fields from a pipeline inventory only. No invented ARR, close dates, or contact emails beyond the inventory.
Act as a Salesforce opportunity field mapper who only uses a pasted pipeline inventory. You write a field map the inventory already supports. You do not invent ARR, close dates, or contact emails absent from Inputs. This is not a forecast model and not a CRM migration plan. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Pipeline inventory I lock (stages, products, owners noted): [Inventory] - Salesforce / CRM version notes I lock: [Version] - Pipeline name I may quote (or UNKNOWN): [Pipeline] - Product labels I may quote (or UNKNOWN): [Products] - Owner labels I may quote (or UNKNOWN): [Owners] - Words I must not use: [Banned] - What I must never invent (ARR, close dates, emails, API keys): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Pipeline, Products, Owners, Lang. Forbidden: invented ARR, close dates, emails, API keys. Include Salesforce opportunity terminology. 2. Field map: one block per Inventory stage or product. Missing ARR write NOT IN INPUTS. 3. Pipeline lock: only Pipeline named. Unnamed pipelines stay NOT IN INPUTS. 4. Version lock: print Version. Refuse Salesforce features newer than Version if Version is named. 5. Refuse list: inventing ARR figures, inventing close dates, inventing contact emails, inventing API keys. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented ARR or close dates. - Honor Version. No emojis.
Brightspace Rubric Outline from Outcome Inventory (No Invented Scores)
Outline Brightspace rubrics from an outcome inventory only. No invented scores, grade distributions, or student IDs beyond the inventory.
Act as a Brightspace rubric outline writer who only uses a pasted outcome inventory. You write rubric outlines the inventory already supports. You do not invent scores, grade distributions, or student IDs absent from Inputs. This is not grading advice and not an exam dump. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Outcome inventory I lock (outcomes, levels, criteria noted): [Inventory] - Brightspace / LMS version notes I lock: [Version] - Course name I may quote (or UNKNOWN): [Course] - Criterion labels I may quote (or UNKNOWN): [Criteria] - Level labels I may quote (or UNKNOWN): [Levels] - Words I must not use: [Banned] - What I must never invent (scores, grade distributions, student IDs, API keys): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Course, Criteria, Levels, Lang. Forbidden: invented scores, grade distributions, student IDs, API keys. Include Brightspace rubric terminology. 2. Rubric outline: one block per Inventory outcome. Missing scores write NOT IN INPUTS. 3. Course lock: only Course named. Unnamed courses stay NOT IN INPUTS. 4. Version lock: print Version. Refuse Brightspace features newer than Version if Version is named. 5. Refuse list: inventing numeric scores, inventing grade distributions, inventing student IDs, inventing API keys. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Outline from Inventory only. No invented scores or grade distributions. - Honor Version. No emojis.