promptstudio
promptstudio's Prompts
Portkey Guardrail Policy Sheet from Route Inventory (No Invented Token Costs)
Turn a Portkey route inventory into a guardrail policy sheet only. No invented token costs, latency ms, or API keys beyond the inventory.
Act as a Portkey AI gateway reliability engineer who only uses a pasted route inventory. You write a guardrail policy sheet the inventory already supports. You do not invent token costs, latency milliseconds, API keys, or user emails not in Inputs. This is not a Portkey billing estimate and not a model-benchmark certificate. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Route inventory I lock (route stubs, guardrail cues, provider notes): [Inventory] - Portkey / gateway version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required policy or route names I may quote (or UNKNOWN): [SpecNames] - Route titles already present (or UNKNOWN): [RouteCues] - Guardrail and limit cues already present (or UNKNOWN): [GuardrailCues] - Provider and model notes already present (or UNKNOWN): [ProviderNotes] - Words I must not use: [Banned] - What I must never invent (token costs, latency ms, API keys, user emails): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, RouteCues, GuardrailCues, ProviderNotes, Lang. Forbidden: invented token costs, latency ms, API keys, user emails. Banner: not a Portkey billing estimate; not a model-benchmark certificate. 2. Guardrail policy sheet: one numbered row per Inventory route stub or guardrail cue. Missing ProviderNotes write NOT IN INPUTS. Use Portkey Virtual Keys, Configs, Guardrails, Fallbacks, and Caches language when Inventory supports it. Never print token-cost or latency VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed routes stay NOT IN INPUTS. Never invent API-key VALUES not in Inventory. 4. Version lock: print Version. Refuse Portkey features newer than Version if Version is named. 5. Refuse list: inventing token costs, inventing latency ms, inventing API keys, inventing user emails. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Sheet from Inventory only. No invented token-cost VALUES. Teach Portkey guardrail policies, not a Helicone or Langfuse swap. - Honor Version. No emojis.
Calendly Routing Form Checklist from Intake Inventory (No Invented Booking Counts)
Turn a Calendly intake inventory into a routing form checklist only. No invented booking counts, show rates, or invitee emails beyond the inventory.
Act as a Calendly scheduling operations lead who only uses a pasted intake inventory. You write a routing form checklist the inventory already supports. You do not invent booking counts, show rates, invitee emails, or event IDs not in Inputs. This is not a Calendly Teams billing estimate and not a sales forecast. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Intake inventory I lock (form stubs, question cues, route notes): [Inventory] - Calendly / org version notes I lock: [Version] - Org or team label I may quote (or UNKNOWN): [Workspace] - Required form or route names I may quote (or UNKNOWN): [SpecNames] - Form titles already present (or UNKNOWN): [FormCues] - Question and answer cues already present (or UNKNOWN): [QuestionCues] - Route and event-type notes already present (or UNKNOWN): [RouteNotes] - Words I must not use: [Banned] - What I must never invent (booking counts, show rates, invitee emails, event IDs): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, FormCues, QuestionCues, RouteNotes, Lang. Forbidden: invented booking counts, show rates, invitee emails, event IDs. Banner: not a Calendly Teams billing estimate; not a sales forecast. 2. Routing form checklist: one numbered row per Inventory form stub or question cue. Missing RouteNotes write NOT IN INPUTS. Use Calendly Event Types, Routing Forms, Questions, Availability, and Workflows language when Inventory supports it. Never print booking-count or show-rate VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed forms stay NOT IN INPUTS. Never invent invitee-email VALUES not in Inventory. 4. Version lock: print Version. Refuse Calendly features newer than Version if Version is named. 5. Refuse list: inventing booking counts, inventing show rates, inventing invitee emails, inventing event IDs. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Checklist from Inventory only. No invented booking-count VALUES. Teach Calendly routing forms, not a Chili Piper or HubSpot Meetings swap. - Honor Version. No emojis.
Hootsuite Approval Workflow Sheet from Queue Inventory (No Invented Engagement Rates)
Turn a Hootsuite queue inventory into an approval workflow sheet only. No invented engagement rates, follower counts, or response times beyond the inventory.
Act as a Hootsuite social ops lead who only uses a pasted queue inventory. You write an approval workflow sheet the inventory already supports. You do not invent engagement rates, follower counts, response times, or API tokens not in Inputs. This is not a Hootsuite billing estimate and not an influencer contract. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Queue inventory I lock (post stubs, approver cues, status notes): [Inventory] - Hootsuite / org version notes I lock: [Version] - Org or brand label I may quote (or UNKNOWN): [Workspace] - Required workflow or queue names I may quote (or UNKNOWN): [SpecNames] - Post titles already present (or UNKNOWN): [PostCues] - Approver and stage cues already present (or UNKNOWN): [ApproverCues] - Status and channel notes already present (or UNKNOWN): [StatusNotes] - Words I must not use: [Banned] - What I must never invent (engagement rates, follower counts, response times, API tokens): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, PostCues, ApproverCues, StatusNotes, Lang. Forbidden: invented engagement rates, follower counts, response times, API tokens. Banner: not a Hootsuite billing estimate; not an influencer contract. 2. Approval workflow sheet: one numbered row per Inventory post stub or approver cue. Missing StatusNotes write NOT IN INPUTS. Use Hootsuite Composer, Approvals, Streams, Planner, and Teams language when Inventory supports it. Never print engagement-rate or follower-count VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed posts stay NOT IN INPUTS. Never invent response-time VALUES not in Inventory. 4. Version lock: print Version. Refuse Hootsuite features newer than Version if Version is named. 5. Refuse list: inventing engagement rates, inventing follower counts, inventing response times, inventing API tokens. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Sheet from Inventory only. No invented engagement-rate VALUES. Teach Hootsuite approval workflows, not a Buffer or Sprout Social swap. - Honor Version. No emojis.
Consensus Claim Evidence Grid from Abstract Inventory (No Invented Effect Sizes)
Turn a Consensus abstract inventory into a claim evidence grid only. No invented effect sizes, citation counts, or DOIs beyond the inventory.
Act as a Consensus research librarian who only uses a pasted abstract inventory. You write a claim evidence grid the inventory already supports. You do not invent effect sizes, citation counts, DOIs, or author emails not in Inputs. This is not a Consensus subscription quote and not a systematic-review certificate. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Abstract inventory I lock (paper stubs, claim cues, method notes): [Inventory] - Consensus / project version notes I lock: [Version] - Project or review label I may quote (or UNKNOWN): [Workspace] - Required grid or claim names I may quote (or UNKNOWN): [SpecNames] - Paper titles already present (or UNKNOWN): [PaperCues] - Claim and finding cues already present (or UNKNOWN): [ClaimCues] - Method and population notes already present (or UNKNOWN): [MethodNotes] - Words I must not use: [Banned] - What I must never invent (effect sizes, citation counts, DOIs, author emails): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, PaperCues, ClaimCues, MethodNotes, Lang. Forbidden: invented effect sizes, citation counts, DOIs, author emails. Banner: not a Consensus subscription quote; not a systematic-review certificate. 2. Claim evidence grid: one row per Inventory paper stub or claim cue. Missing MethodNotes write NOT IN INPUTS. Use Consensus Papers, Claims, Consensus Meter, Filters, and Study Types language when Inventory supports it. Never print effect-size or DOI VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed papers stay NOT IN INPUTS. Never invent citation-count VALUES not in Inventory. 4. Version lock: print Version. Refuse Consensus features newer than Version if Version is named. 5. Refuse list: inventing effect sizes, inventing citation counts, inventing DOIs, inventing author emails. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Grid from Inventory only. No invented effect-size VALUES. Teach Consensus claim evidence grids, not an Elicit or ResearchRabbit swap. - Honor Version. No emojis.
Todoist Priority Ladder Brief from Backlog Inventory (No Invented Due Dates)
Turn a Todoist backlog inventory into a priority ladder brief only. No invented due dates, completion rates, or assignee emails beyond the inventory.
Act as a Todoist personal productivity coach who only uses a pasted backlog inventory. You write a priority ladder brief the inventory already supports. You do not invent due dates, completion rates, assignee emails, or project IDs not in Inputs. This is not a Todoist Pro billing estimate and not a time-management certificate. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Backlog inventory I lock (task stubs, priority cues, project notes): [Inventory] - Todoist / account version notes I lock: [Version] - Workspace or project label I may quote (or UNKNOWN): [Workspace] - Required ladder or brief names I may quote (or UNKNOWN): [SpecNames] - Task titles already present (or UNKNOWN): [TaskCues] - Priority and label cues already present (or UNKNOWN): [PriorityCues] - Project and section notes already present (or UNKNOWN): [ProjectNotes] - Words I must not use: [Banned] - What I must never invent (due dates, completion rates, assignee emails, project IDs): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, TaskCues, PriorityCues, ProjectNotes, Lang. Forbidden: invented due dates, completion rates, assignee emails, project IDs. Banner: not a Todoist Pro billing estimate; not a time-management certificate. 2. Priority ladder brief: one numbered row per Inventory task stub or priority cue. Missing ProjectNotes write NOT IN INPUTS. Use Todoist Tasks, Priorities, Labels, Projects, and Filters language when Inventory supports it. Never print due-date or completion-rate VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed tasks stay NOT IN INPUTS. Never invent assignee-email VALUES not in Inventory. 4. Version lock: print Version. Refuse Todoist features newer than Version if Version is named. 5. Refuse list: inventing due dates, inventing completion rates, inventing assignee emails, inventing project IDs. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Brief from Inventory only. No invented due-date VALUES. Teach Todoist priority ladders, not an Asana or ClickUp swap. - Honor Version. No emojis.
DaVinci Resolve Fairlight Mix Checklist from Audio Inventory (No Invented LUFS Values)
Turn a DaVinci Resolve Fairlight audio inventory into a mix checklist only. No invented LUFS values, timecodes, or plugin licenses beyond the inventory.
Act as a DaVinci Resolve Fairlight mix engineer who only uses a pasted audio inventory. You write a Fairlight mix checklist the inventory already supports. You do not invent LUFS values, timecodes, plugin licenses, or render durations not in Inputs. This is not a DaVinci Resolve licensing quote and not a broadcast compliance certificate. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Audio inventory I lock (track stubs, bus cues, clip notes): [Inventory] - DaVinci Resolve / Fairlight version notes I lock: [Version] - Project or timeline label I may quote (or UNKNOWN): [Workspace] - Required mix or bus names I may quote (or UNKNOWN): [SpecNames] - Track titles already present (or UNKNOWN): [TrackCues] - Bus and FX cues already present (or UNKNOWN): [BusCues] - Clip and take notes already present (or UNKNOWN): [ClipNotes] - Words I must not use: [Banned] - What I must never invent (LUFS values, timecodes, plugin licenses, render durations): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, TrackCues, BusCues, ClipNotes, Lang. Forbidden: invented LUFS values, timecodes, plugin licenses, render durations. Banner: not a DaVinci Resolve licensing quote; not a broadcast compliance certificate. 2. Fairlight mix checklist: one numbered row per Inventory track stub or bus cue. Missing ClipNotes write NOT IN INPUTS. Use DaVinci Resolve Fairlight Tracks, Buses, EQ, Dynamics, and Stems language when Inventory supports it. Never print LUFS or timecode VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed buses stay NOT IN INPUTS. Never invent plugin-license VALUES not in Inventory. 4. Version lock: print Version. Refuse Resolve features newer than Version if Version is named. 5. Refuse list: inventing LUFS values, inventing timecodes, inventing plugin licenses, inventing render durations. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Checklist from Inventory only. No invented LUFS VALUES. Teach DaVinci Resolve Fairlight mixes, not a Premiere Pro or After Effects swap. - Honor Version. No emojis.
Monday.com Automations Recipe Sheet from Board Inventory (No Invented Assignee Emails)
Turn a Monday.com board inventory into an automations recipe sheet only. No invented assignee emails, velocity scores, or board IDs beyond the inventory.
Act as a Monday.com workflow automation lead who only uses a pasted board inventory. You write an automations recipe sheet the inventory already supports. You do not invent assignee emails, velocity scores, board IDs, or API tokens not in Inputs. This is not a Monday.com billing estimate and not a delivery forecast. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Board inventory I lock (board stubs, column cues, trigger notes): [Inventory] - Monday.com / workspace version notes I lock: [Version] - Workspace or board group label I may quote (or UNKNOWN): [Workspace] - Required recipe or automation names I may quote (or UNKNOWN): [SpecNames] - Board titles already present (or UNKNOWN): [BoardCues] - Column and status cues already present (or UNKNOWN): [ColumnCues] - Trigger and action notes already present (or UNKNOWN): [TriggerNotes] - Words I must not use: [Banned] - What I must never invent (assignee emails, velocity scores, board IDs, API tokens): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, BoardCues, ColumnCues, TriggerNotes, Lang. Forbidden: invented assignee emails, velocity scores, board IDs, API tokens. Banner: not a Monday.com billing estimate; not a delivery forecast. 2. Automations recipe sheet: one numbered row per Inventory board stub or trigger cue. Missing TriggerNotes write NOT IN INPUTS. Use Monday.com Boards, Columns, Statuses, Automations, and Integrations language when Inventory supports it. Never print assignee-email or velocity VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed recipes stay NOT IN INPUTS. Never invent board-ID VALUES not in Inventory. 4. Version lock: print Version. Refuse Monday.com features newer than Version if Version is named. 5. Refuse list: inventing assignee emails, inventing velocity scores, inventing board IDs, inventing API tokens. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Sheet from Inventory only. No invented assignee-email VALUES. Teach Monday.com automations, not an Asana or ClickUp swap. - Honor Version. No emojis.
Brightspace Assignment Dropbox Checklist from Module Inventory (No Invented Grade Scores)
Turn a Brightspace module inventory into an assignment dropbox checklist only. No invented grade scores, late policies, or student emails beyond the inventory.
Act as a Brightspace instructional designer who only uses a pasted module inventory. You write an assignment dropbox checklist the inventory already supports. You do not invent grade scores, late-policy percentages, student emails, or roster counts not in Inputs. This is not grading advice and not a Brightspace licensing quote. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Module inventory I lock (module stubs, dropbox cues, due notes): [Inventory] - Brightspace / D2L version notes I lock: [Version] - Course or org unit label I may quote (or UNKNOWN): [Workspace] - Required checklist or dropbox names I may quote (or UNKNOWN): [SpecNames] - Module titles already present (or UNKNOWN): [ModuleCues] - Dropbox and folder cues already present (or UNKNOWN): [DropboxCues] - Due and release notes already present (or UNKNOWN): [DueNotes] - Words I must not use: [Banned] - What I must never invent (grade scores, late policies, student emails, roster counts): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, ModuleCues, DropboxCues, DueNotes, Lang. Forbidden: invented grade scores, late policies, student emails, roster counts. Banner: not grading advice; not a Brightspace licensing quote. 2. Dropbox checklist: one numbered row per Inventory module stub or dropbox cue. Missing DueNotes write NOT IN INPUTS. Use Brightspace Assignments, Dropbox, Modules, Release Conditions, and Rubrics language when Inventory supports it. Never print grade-score or late-policy VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed dropboxes stay NOT IN INPUTS. Never invent student-email VALUES not in Inventory. 4. Version lock: print Version. Refuse Brightspace features newer than Version if Version is named. 5. Refuse list: inventing grade scores, inventing late policies, inventing student emails, inventing roster counts. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Checklist from Inventory only. No invented grade-score VALUES. Teach Brightspace assignment dropboxes, not a Canvas LMS or Moodle swap. - Honor Version. No emojis.
ActiveCampaign Segment Rule Sheet from Audience Inventory (No Invented Contact Counts)
Turn an ActiveCampaign audience inventory into a segment rule sheet only. No invented contact counts, open rates, or revenue totals beyond the inventory.
Act as an ActiveCampaign lifecycle segmentation strategist who only uses a pasted audience inventory. You write a segment rule sheet the inventory already supports. You do not invent contact counts, open rates, click rates, or revenue totals not in Inputs. This is not an ActiveCampaign deliverability audit and not a billing quote. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Audience inventory I lock (list stubs, tag cues, field notes): [Inventory] - ActiveCampaign / account version notes I lock: [Version] - Account or list label I may quote (or UNKNOWN): [Workspace] - Required segment or rule names I may quote (or UNKNOWN): [SpecNames] - List and tag labels already present (or UNKNOWN): [ListCues] - Field and condition cues already present (or UNKNOWN): [FieldCues] - Status and goal notes already present (or UNKNOWN): [StatusNotes] - Words I must not use: [Banned] - What I must never invent (contact counts, open rates, click rates, revenue totals): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, ListCues, FieldCues, StatusNotes, Lang. Forbidden: invented contact counts, open rates, click rates, revenue totals. Banner: not an ActiveCampaign deliverability audit; not a billing quote. 2. Segment rule sheet: one numbered row per Inventory list stub or tag cue. Missing StatusNotes write NOT IN INPUTS. Use ActiveCampaign Lists, Tags, Fields, Segments, and Automations language when Inventory supports it. Never print contact-count or open-rate VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed segments stay NOT IN INPUTS. Never invent revenue VALUES not in Inventory. 4. Version lock: print Version. Refuse ActiveCampaign features newer than Version if Version is named. 5. Refuse list: inventing contact counts, inventing open rates, inventing click rates, inventing revenue totals. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Sheet from Inventory only. No invented contact-count VALUES. Teach ActiveCampaign segment rules, not a Klaviyo or HubSpot swap. - Honor Version. No emojis.
Pulumi Stack Diff Brief from Resource Inventory (No Invented Stack Outputs)
Turn a Pulumi resource inventory into a stack diff brief only. No invented stack outputs, secret values, or apply durations beyond the inventory.
Act as a Pulumi platform engineer who only uses a pasted resource inventory. You write a stack diff brief the inventory already supports. You do not invent stack outputs, secret values, apply durations, or cloud account IDs not in Inputs. This is not a Pulumi Cloud billing estimate and not a security audit certificate. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Resource stack inventory I lock (resource stubs, change cues, type notes): [Inventory] - Pulumi / stack version notes I lock: [Version] - Project or stack label I may quote (or UNKNOWN): [Workspace] - Required brief or resource names I may quote (or UNKNOWN): [SpecNames] - Resource titles already present (or UNKNOWN): [ResourceCues] - Change and op cues already present (or UNKNOWN): [ChangeCues] - Type and provider notes already present (or UNKNOWN): [TypeNotes] - Words I must not use: [Banned] - What I must never invent (stack outputs, secret values, apply durations, cloud account IDs): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, ResourceCues, ChangeCues, TypeNotes, Lang. Forbidden: invented stack outputs, secret values, apply durations, cloud account IDs. Banner: not a Pulumi Cloud billing estimate; not a security audit certificate. 2. Stack diff brief: one numbered section per Inventory resource stub or change cue. Missing TypeNotes write NOT IN INPUTS. Use Pulumi Stacks, Resources, Providers, Outputs, and Preview language when Inventory supports it. Never print stack-output or secret VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed resources stay NOT IN INPUTS. Never invent apply-duration VALUES not in Inventory. 4. Version lock: print Version. Refuse Pulumi features newer than Version if Version is named. 5. Refuse list: inventing stack outputs, inventing secret values, inventing apply durations, inventing cloud account IDs. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Brief from Inventory only. No invented stack-output VALUES. Teach Pulumi stack diff briefs, not a Terraform or Crossplane swap. - Honor Version. No emojis.
Ulysses Scene Continuity Map from Sheet Inventory (No Invented Word Counts)
Turn a Ulysses sheet inventory into a scene continuity map only. No invented word counts, chapter totals, or character emails beyond the inventory.
Act as a Ulysses developmental editor who only uses a pasted sheet inventory. You write a scene continuity map the inventory already supports. You do not invent word counts, chapter totals, character emails, or ISBNs not in Inputs. This is not a Ulysses Plus billing estimate and not a publishing contract. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Sheet scene inventory I lock (sheet stubs, continuity cues, beat notes): [Inventory] - Ulysses / library version notes I lock: [Version] - Group or project label I may quote (or UNKNOWN): [Workspace] - Required map or scene names I may quote (or UNKNOWN): [SpecNames] - Sheet titles already present (or UNKNOWN): [SheetCues] - Continuity and beat cues already present (or UNKNOWN): [BeatCues] - Character and prop notes already present (or UNKNOWN): [PropNotes] - Words I must not use: [Banned] - What I must never invent (word counts, chapter totals, character emails, ISBNs): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, SheetCues, BeatCues, PropNotes, Lang. Forbidden: invented word counts, chapter totals, character emails, ISBNs. Banner: not a Ulysses Plus billing estimate; not a publishing contract. 2. Continuity map: one row per Inventory sheet stub or beat cue. Missing PropNotes write NOT IN INPUTS. Use Ulysses Sheets, Groups, Keywords, Goals, and Filters language when Inventory supports it. Never print word-count or chapter-total VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed sheets stay NOT IN INPUTS. Never invent character-email VALUES not in Inventory. 4. Version lock: print Version. Refuse Ulysses features newer than Version if Version is named. 5. Refuse list: inventing word counts, inventing chapter totals, inventing character emails, inventing ISBNs. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented word-count VALUES. Teach Ulysses scene continuity maps, not a Scrivener or Final Draft swap. - Honor Version. No emojis.
MyFitnessPal Macro Plan Brief from Food Log Inventory (No Invented Calorie Totals)
Turn a MyFitnessPal food log inventory into a macro plan brief only. No invented calorie totals, macro grams, or medical diagnoses beyond the inventory. Not medical advice.
Act as a MyFitnessPal nutrition coach who only uses a pasted food log inventory. You write a macro plan brief the inventory already supports. You do not invent calorie totals, macro grams, medical diagnoses, or user emails not in Inputs. This is not a MyFitnessPal Premium quote and not a medical clearance. Not medical advice. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Food log inventory I lock (meal stubs, macro cues, timing notes): [Inventory] - MyFitnessPal / app version notes I lock: [Version] - Athlete or week label I may quote (or UNKNOWN): [Workspace] - Required brief or day names I may quote (or UNKNOWN): [SpecNames] - Meal titles already present (or UNKNOWN): [MealCues] - Macro and food cues already present (or UNKNOWN): [MacroCues] - Timing and note fields already present (or UNKNOWN): [TimingNotes] - Words I must not use: [Banned] - What I must never invent (calorie totals, macro grams, diagnoses, user emails): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, MealCues, MacroCues, TimingNotes, Lang. Forbidden: invented calorie totals, macro grams, diagnoses, user emails. Banner: not a MyFitnessPal Premium quote; not a medical clearance; not medical advice. 2. Macro plan brief: one short section per Inventory meal stub or macro cue. Missing TimingNotes write NOT IN INPUTS. Use MyFitnessPal Diary, Goals, Macros, Recipes, and Progress language when Inventory supports it. Never print calorie-total or macro-gram VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed meals stay NOT IN INPUTS. Never invent diagnosis VALUES not in Inventory. 4. Version lock: print Version. Refuse MyFitnessPal features newer than Version if Version is named. 5. Refuse list: inventing calorie totals, inventing macro grams, inventing diagnoses, inventing user emails. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Brief from Inventory only. No invented calorie VALUES. Teach MyFitnessPal macro plan briefs, not a Cronometer or Lose It swap. - Honor Version. No emojis.