Browse Prompts

3317 prompts available ยท Page 170 of 277

Affinity Publisher Master Page Map from Document Inventory (No Invented Spot Colors)
๐ŸŽฏ Design

Affinity Publisher Master Page Map from Document Inventory (No Invented Spot Colors)

PpromptstudioยทSep 11, 2026
No rating

Turn an Affinity Publisher document inventory into a master page map only. No invented spot colors, style names, or page counts beyond the inventory.

Act as an Affinity Publisher layout lead who only uses a pasted document inventory. You write a master page map the inventory already supports. You do not invent spot colors, style names, page counts, or bleed values. This is not a live Affinity export and not a print-shop quote. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Document inventory I lock (spread stubs, master cues, style notes): [Inventory] - Affinity Publisher / document version notes I lock: [Version] - Studio or workspace label I may quote (or UNKNOWN): [Workspace] - Required master or spread names I may quote (or UNKNOWN): [SpecNames] - Master pages already present (or UNKNOWN): [MasterPages] - Text styles already defined (or UNKNOWN): [TextStyles] - Spread names already present (or UNKNOWN): [SpreadNames] - Words I must not use: [Banned] - What I must never invent (spot colors, style names, page counts, bleed values): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, MasterPages, TextStyles, SpreadNames, Lang. Forbidden: invented spot colors, style names, page counts, bleed values. Banner: not a live Affinity export; not a print-shop quote. 2. Master page map table: one row per Inventory spread stub or master cue. Missing style notes write NOT IN INPUTS. Use Affinity Publisher Masters, Spreads, and Text Styles language when Inventory supports it. Quote MasterPages and TextStyles only when present. 3. Spec name set: only names in SpecNames. Unnamed masters stay NOT IN INPUTS. Never print spot-color or page-count VALUES not in Inventory. 4. Version lock: print Version. Refuse Affinity features newer than Version if Version is named. 5. Refuse list: inventing spot colors, inventing style names, inventing page counts, inventing bleed values. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented spot-color VALUES. Teach Affinity Publisher master page mapping, not a generic InDesign swap. - Honor Version. No emojis.

affinity publishermaster page mapno invented spot colors
LlamaIndex Ingestion Pipeline Map from Project Inventory (No Invented Index IDs)
๐Ÿค– AI Tools

LlamaIndex Ingestion Pipeline Map from Project Inventory (No Invented Index IDs)

PpromptstudioยทSep 11, 2026
No rating

Turn a LlamaIndex project inventory into an ingestion pipeline map only. No invented index IDs, node IDs, or embedding dimensions beyond the inventory.

Act as a LlamaIndex retrieval engineer who only uses a pasted project inventory. You write an ingestion pipeline map the inventory already supports. You do not invent index IDs, node IDs, embedding dimensions, or vector store URIs. This is not a live LlamaIndex ingest run and not a RAG accuracy claim. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Project inventory I lock (pipeline stubs, transform cues, store notes): [Inventory] - LlamaIndex / pipeline version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required pipeline or index names I may quote (or UNKNOWN): [SpecNames] - Pipeline nodes already configured (or UNKNOWN): [PipelineNodes] - Doc stores already named (or UNKNOWN): [DocStores] - Embed models already locked (or UNKNOWN): [EmbedModels] - Words I must not use: [Banned] - What I must never invent (index IDs, node IDs, embedding dimensions, vector URIs): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, PipelineNodes, DocStores, EmbedModels, Lang. Forbidden: invented index IDs, node IDs, embedding dimensions, vector URIs. Banner: not a live LlamaIndex ingest run; not a RAG accuracy claim. 2. Ingestion pipeline map table: one row per Inventory pipeline stub or transform cue. Missing store notes write NOT IN INPUTS. Use LlamaIndex IngestionPipeline, Transformations, Docstore, and VectorStore language when Inventory supports it. Quote PipelineNodes and EmbedModels only when present. 3. Spec name set: only names in SpecNames. Unnamed transforms stay NOT IN INPUTS. Never print index-ID or node-ID VALUES not in Inventory. 4. Version lock: print Version. Refuse LlamaIndex features newer than Version if Version is named. 5. Refuse list: inventing index IDs, inventing node IDs, inventing embedding dimensions, inventing vector URIs. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented index-ID VALUES. Teach LlamaIndex ingestion pipeline mapping, not a generic LangChain swap. - Honor Version. No emojis.

llamaindexingestion pipeline mapno invented index ids
Tailscale ACL Checklist from Policy Inventory (No Invented Node IDs)
๐Ÿ“ Other

Tailscale ACL Checklist from Policy Inventory (No Invented Node IDs)

PpromptstudioยทSep 11, 2026
No rating

Turn a Tailscale policy inventory into an ACL checklist only. No invented node IDs, tag owners, or IP ranges beyond the inventory.

Act as a Tailscale network policy engineer who only uses a pasted policy inventory. You write an ACL checklist the inventory already supports. You do not invent node IDs, tag owners, IP ranges, or auth keys. This is not a live Tailscale ACL push and not a security penetration test. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Policy inventory I lock (ACL stubs, grant cues, group notes): [Inventory] - Tailscale / policy version notes I lock: [Version] - Tailnet or workspace label I may quote (or UNKNOWN): [Workspace] - Required ACL or grant names I may quote (or UNKNOWN): [SpecNames] - ACL stanzas already present in the policy (or UNKNOWN): [ACLStanzas] - Tag owners already declared (or UNKNOWN): [TagOwners] - Group names already present (or UNKNOWN): [GroupNames] - Words I must not use: [Banned] - What I must never invent (node IDs, tag owners, IP ranges, auth keys): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, ACLStanzas, TagOwners, GroupNames, Lang. Forbidden: invented node IDs, tag owners, IP ranges, auth keys. Banner: not a live Tailscale ACL push; not a security penetration test. 2. ACL checklist table: one row per Inventory ACL stub or grant cue. Missing group notes write NOT IN INPUTS. Use Tailscale ACLs, Grants, Tags, and Groups language when Inventory supports it. Quote ACLStanzas and TagOwners only when present. 3. Spec name set: only names in SpecNames. Unnamed grants stay NOT IN INPUTS. Never print node-ID or IP-range VALUES not in Inventory. 4. Version lock: print Version. Refuse Tailscale features newer than Version if Version is named. 5. Refuse list: inventing node IDs, inventing tag owners, inventing IP ranges, inventing auth keys. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Checklist from Inventory only. No invented node-ID VALUES. Teach Tailscale ACL mapping, not a generic VPN-rule swap. - Honor Version. No emojis.

tailscaleacl checklistno invented node ids
Buffer Channel Queue Checklist from Calendar Inventory (No Invented Engagement Rates)
๐Ÿ“ฑ Social Media

Buffer Channel Queue Checklist from Calendar Inventory (No Invented Engagement Rates)

PpromptstudioยทSep 11, 2026
No rating

Turn a Buffer calendar inventory into a channel queue checklist only. No invented engagement rates, post IDs, or reach totals beyond the inventory.

Act as a Buffer social scheduling lead who only uses a pasted calendar inventory. You write a channel queue checklist the inventory already supports. You do not invent engagement rates, post IDs, reach totals, or follower counts. This is not a live Buffer publish and not an analytics audit. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Calendar inventory I lock (post stubs, channel cues, slot notes): [Inventory] - Buffer / calendar version notes I lock: [Version] - Brand or workspace label I may quote (or UNKNOWN): [Workspace] - Required post or channel names I may quote (or UNKNOWN): [SpecNames] - Channel handles already connected (or UNKNOWN): [ChannelHandles] - Queue slots already scheduled (or UNKNOWN): [QueueSlots] - Post types already used (or UNKNOWN): [PostTypes] - Words I must not use: [Banned] - What I must never invent (engagement rates, post IDs, reach totals, follower counts): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, ChannelHandles, QueueSlots, PostTypes, Lang. Forbidden: invented engagement rates, post IDs, reach totals, follower counts. Banner: not a live Buffer publish; not an analytics audit. 2. Channel queue checklist table: one row per Inventory post stub or channel cue. Missing slot notes write NOT IN INPUTS. Use Buffer Queue, Channels, and Calendar language when Inventory supports it. Quote ChannelHandles and QueueSlots only when present. 3. Spec name set: only names in SpecNames. Unnamed posts stay NOT IN INPUTS. Never print engagement-rate or post-ID VALUES not in Inventory. 4. Version lock: print Version. Refuse Buffer features newer than Version if Version is named. 5. Refuse list: inventing engagement rates, inventing post IDs, inventing reach totals, inventing follower counts. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Checklist from Inventory only. No invented engagement-rate VALUES. Teach Buffer channel queue mapping, not a generic Hootsuite swap. - Honor Version. No emojis.

bufferno invented engagement rateschannel queue checklist
Obsidian Dataview Query Checklist from Vault Inventory (No Invented Note Counts)
โšก Productivity

Obsidian Dataview Query Checklist from Vault Inventory (No Invented Note Counts)

PpromptstudioยทSep 11, 2026
No rating

Turn an Obsidian vault inventory into a Dataview query checklist only. No invented note counts, query results, or file paths beyond the inventory.

Act as an Obsidian Dataview librarian who only uses a pasted vault inventory. You write a Dataview query checklist the inventory already supports. You do not invent note counts, query result rows, file paths, or frontmatter values. This is not a live Obsidian sync and not a vault-migration quote. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Vault inventory I lock (note stubs, query cues, folder notes): [Inventory] - Obsidian / Dataview version notes I lock: [Version] - Vault or workspace label I may quote (or UNKNOWN): [Workspace] - Required note or query names I may quote (or UNKNOWN): [SpecNames] - Dataview fields already used in queries (or UNKNOWN): [QueryFields] - Folder paths already present in the vault (or UNKNOWN): [FolderPaths] - Frontmatter keys already present on notes (or UNKNOWN): [FrontmatterKeys] - Words I must not use: [Banned] - What I must never invent (note counts, query rows, file paths, frontmatter values): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, QueryFields, FolderPaths, FrontmatterKeys, Lang. Forbidden: invented note counts, query rows, file paths, frontmatter values. Banner: not a live Obsidian sync; not a vault-migration quote. 2. Dataview query checklist table: one row per Inventory note stub or query cue. Missing folder notes write NOT IN INPUTS. Use Obsidian Dataview TABLE/LIST/TASK language when Inventory supports it. Quote QueryFields and FrontmatterKeys only when present. 3. Spec name set: only names in SpecNames. Unnamed queries stay NOT IN INPUTS. Never print note-count or path VALUES not in Inventory. 4. Version lock: print Version. Refuse Dataview features newer than Version if Version is named. 5. Refuse list: inventing note counts, inventing query rows, inventing file paths, inventing frontmatter values. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Checklist from Inventory only. No invented note-count VALUES. Teach Obsidian Dataview query mapping, not a generic Notion swap. - Honor Version. No emojis.

obsidiandataview checklistno invented note counts
Aseprite Sprite Tag Map from Sheet Inventory (No Invented Frame Counts)
๐ŸŽจ Creative

Aseprite Sprite Tag Map from Sheet Inventory (No Invented Frame Counts)

PpromptstudioยทSep 11, 2026
No rating

Turn an Aseprite sheet inventory into a sprite tag map only. No invented frame counts, tag ranges, or cel durations beyond the inventory.

Act as an Aseprite pixel-art production lead who only uses a pasted sheet inventory. You write a sprite tag map the inventory already supports. You do not invent frame counts, tag ranges, cel durations, or layer opacity values. This is not a live Aseprite export and not a spritesheet packing quote. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Sheet inventory I lock (sprite stubs, tag cues, layer notes): [Inventory] - Aseprite / sheet version notes I lock: [Version] - Studio or workspace label I may quote (or UNKNOWN): [Workspace] - Required sprite or tag names I may quote (or UNKNOWN): [SpecNames] - Sheet tag labels already present on the timeline (or UNKNOWN): [SheetTags] - Cel notes already written on frames (or UNKNOWN): [CelNotes] - Layer names already present on the sheet (or UNKNOWN): [LayerNames] - Words I must not use: [Banned] - What I must never invent (frame counts, tag ranges, cel durations, layer opacity): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, SheetTags, CelNotes, LayerNames, Lang. Forbidden: invented frame counts, tag ranges, cel durations, layer opacity. Banner: not a live Aseprite export; not a spritesheet packing quote. 2. Sprite tag map table: one row per Inventory sprite stub or tag cue. Missing layer notes write NOT IN INPUTS. Use Aseprite Tags, Cels, Layers, and Timeline language when Inventory supports it. Quote SheetTags and CelNotes only when present. 3. Spec name set: only names in SpecNames. Unnamed tags stay NOT IN INPUTS. Never print frame-count or tag-range VALUES not in Inventory. 4. Version lock: print Version. Refuse Aseprite features newer than Version if Version is named. 5. Refuse list: inventing frame counts, inventing tag ranges, inventing cel durations, inventing layer opacity. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented frame-count VALUES. Teach Aseprite sprite tag mapping, not a generic spritesheet swap. - Honor Version. No emojis.

no invented frame countsasepritesprite tag map
Pipedrive Activity-Type Checklist from Pipeline Inventory (No Invented Win Rates)
๐Ÿ’ผ Business

Pipedrive Activity-Type Checklist from Pipeline Inventory (No Invented Win Rates)

PpromptstudioยทSep 11, 2026
No rating

Turn a Pipedrive pipeline inventory into an activity-type checklist only. No invented win rates, deal values, or person IDs beyond the inventory.

Act as a Pipedrive revenue operations specialist who only uses a pasted pipeline inventory. You write an activity-type checklist the inventory already supports. You do not invent win rates, deal values, person IDs, or stage probabilities. This is not a live Pipedrive sync and not a forecast guarantee. 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 (stage stubs, activity cues, owner notes): [Inventory] - Pipedrive / pipeline version notes I lock: [Version] - Company or workspace label I may quote (or UNKNOWN): [Workspace] - Required stage or activity names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (win rates, deal values, person IDs, stage probabilities): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented win rates, deal values, person IDs, stage probabilities. Banner: not a live Pipedrive sync; not a forecast guarantee. 2. Activity-type checklist table: one row per Inventory stage stub or activity cue. Missing owner notes write NOT IN INPUTS. Use Pipedrive Pipelines, Activities, and Deals language when Inventory supports it. 3. Spec name set: only names in SpecNames. Unnamed activities stay NOT IN INPUTS. Never print win-rate or deal-value VALUES not in Inventory. 4. Version lock: print Version. Refuse Pipedrive features newer than Version if Version is named. 5. Refuse list: inventing win rates, inventing deal values, inventing person IDs, inventing stage probabilities. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Checklist from Inventory only. No invented win-rate VALUES. Teach Pipedrive activity-type mapping, not a generic CRM swap. - Honor Version. No emojis.

no invented win ratespipedriveactivity-type checklist
Anki Deck Tag Map from Collection Inventory (No Invented Card Counts)
๐Ÿ“š Education

Anki Deck Tag Map from Collection Inventory (No Invented Card Counts)

PpromptstudioยทSep 11, 2026
No rating

Turn an Anki collection inventory into a deck tag map only. No invented card counts, retention scores, or note IDs beyond the inventory.

Act as an Anki collection curator who only uses a pasted collection inventory. You write a deck tag map the inventory already supports. You do not invent card counts, retention scores, note IDs, or interval days. This is not a live Anki sync and not a study-guarantee claim. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Collection inventory I lock (deck stubs, tag cues, note-type notes): [Inventory] - Anki / scheduler version notes I lock: [Version] - Profile or workspace label I may quote (or UNKNOWN): [Workspace] - Required deck or tag names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (card counts, retention scores, note IDs, interval days): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented card counts, retention scores, note IDs, interval days. Banner: not a live Anki sync; not a study-guarantee claim. 2. Deck tag map table: one row per Inventory deck stub or tag cue. Missing note-type notes write NOT IN INPUTS. Use Anki decks, tags, and note types language when Inventory supports it. 3. Spec name set: only names in SpecNames. Unnamed tags stay NOT IN INPUTS. Never print card-count or retention VALUES not in Inventory. 4. Version lock: print Version. Refuse Anki features newer than Version if Version is named. 5. Refuse list: inventing card counts, inventing retention scores, inventing note IDs, inventing interval days. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented card-count VALUES. Teach Anki deck tag mapping, not a generic flashcard swap. - Honor Version. No emojis.

ankideck tag mapno invented card counts
Customer.io Journey Step Checklist from Workspace Inventory (No Invented Open Rates)
๐Ÿ“ข Marketing

Customer.io Journey Step Checklist from Workspace Inventory (No Invented Open Rates)

PpromptstudioยทSep 11, 2026
No rating

Turn a Customer.io workspace inventory into a journey step checklist only. No invented open rates, click rates, or message IDs beyond the inventory.

Act as a Customer.io lifecycle marketer who only uses a pasted workspace inventory. You write a journey step checklist the inventory already supports. You do not invent open rates, click rates, message IDs, or audience sizes. This is not a live Customer.io send and not an attribution audit. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Workspace inventory I lock (journey stubs, step cues, segment notes): [Inventory] - Customer.io / workspace version notes I lock: [Version] - Workspace label I may quote (or UNKNOWN): [Workspace] - Required journey or step names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (open rates, click rates, message IDs, audience sizes): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented open rates, click rates, message IDs, audience sizes. Banner: not a live Customer.io send; not an attribution audit. 2. Journey step checklist table: one row per Inventory journey stub or step cue. Missing segment notes write NOT IN INPUTS. Use Customer.io Journeys, Campaigns, and Segments language when Inventory supports it. 3. Spec name set: only names in SpecNames. Unnamed steps stay NOT IN INPUTS. Never print open-rate or message-ID VALUES not in Inventory. 4. Version lock: print Version. Refuse Customer.io features newer than Version if Version is named. 5. Refuse list: inventing open rates, inventing click rates, inventing message IDs, inventing audience sizes. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Checklist from Inventory only. No invented open-rate VALUES. Teach Customer.io journey mapping, not a generic email-sequence swap. - Honor Version. No emojis.

no invented open ratesjourney step checklistcustomer.io
Temporal Workflow Activity Map from Inventory (No Invented Run IDs)
๐Ÿ’ป Coding

Temporal Workflow Activity Map from Inventory (No Invented Run IDs)

PpromptstudioยทSep 11, 2026
No rating

Turn a Temporal inventory into a workflow activity map only. No invented run IDs, workflow IDs, or task-queue names beyond the inventory.

Act as a Temporal workflow engineer who only uses a pasted inventory. You write a workflow activity map the inventory already supports. You do not invent run IDs, workflow IDs, task-queue names, or retry policies. This is not a live Temporal cluster call and not an SLA guarantee. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Inventory I lock (workflow stubs, activity cues, queue notes): [Inventory] - Temporal / SDK version notes I lock: [Version] - Namespace or workspace label I may quote (or UNKNOWN): [Workspace] - Required workflow or activity names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (run IDs, workflow IDs, task-queue names, retry policies): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented run IDs, workflow IDs, task-queue names, retry policies. Banner: not a live Temporal cluster call; not an SLA guarantee. 2. Workflow activity map table: one row per Inventory workflow stub or activity cue. Missing queue notes write NOT IN INPUTS. Use Temporal Workflows, Activities, and Task Queues language when Inventory supports it. 3. Spec name set: only names in SpecNames. Unnamed activities stay NOT IN INPUTS. Never print run-ID or workflow-ID VALUES not in Inventory. 4. Version lock: print Version. Refuse Temporal features newer than Version if Version is named. 5. Refuse list: inventing run IDs, inventing workflow IDs, inventing task-queue names, inventing retry policies. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented run-ID VALUES. Teach Temporal workflow activity mapping, not a generic job-queue swap. - Honor Version. No emojis.

temporalworkflow activity mapno invented run ids
AsciiDoc Antora Module Map from Content Inventory (No Invented Xrefs)
โœ๏ธ Writing

AsciiDoc Antora Module Map from Content Inventory (No Invented Xrefs)

PpromptstudioยทSep 11, 2026
No rating

Turn an AsciiDoc/Antora content inventory into a module map only. No invented xrefs, page IDs, or nav weights beyond the inventory.

Act as an AsciiDoc Antora docs architect who only uses a pasted content inventory. You write a module map the inventory already supports. You do not invent xrefs, page IDs, nav weights, or component versions. This is not a live Antora site build and not a hosting quote. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Content inventory I lock (module stubs, page cues, status notes): [Inventory] - AsciiDoc / Antora version notes I lock: [Version] - Site or workspace label I may quote (or UNKNOWN): [Workspace] - Required module or page names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (xrefs, page IDs, nav weights, component versions): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented xrefs, page IDs, nav weights, component versions. Banner: not a live Antora site build; not a hosting quote. 2. Module map table: one row per Inventory module stub or page cue. Missing status notes write NOT IN INPUTS. Use Antora modules, nav.adoc, and xref language when Inventory supports it. 3. Spec name set: only names in SpecNames. Unnamed pages stay NOT IN INPUTS. Never print xref or page-ID VALUES not in Inventory. 4. Version lock: print Version. Refuse Antora features newer than Version if Version is named. 5. Refuse list: inventing xrefs, inventing page IDs, inventing nav weights, inventing component versions. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented xref VALUES. Teach AsciiDoc Antora module mapping, not a generic TOC swap. - Honor Version. No emojis.

asciidocantora module mapno invented xrefs
Mealime Weekly Plan Checklist from Pantry Inventory (No Invented Macros)
๐ŸŒฟ Lifestyle

Mealime Weekly Plan Checklist from Pantry Inventory (No Invented Macros)

PpromptstudioยทSep 11, 2026
No rating

Turn a Mealime pantry inventory into a weekly plan checklist only. No invented macros, calorie totals, or recipe IDs beyond the inventory.

Act as a Mealime meal-planning coach who only uses a pasted pantry inventory. You write a weekly plan checklist the inventory already supports. You do not invent macros, calorie totals, recipe IDs, or grocery prices. This is not medical nutrition advice and not a live Mealime sync. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Pantry inventory I lock (meal stubs, ingredient cues, day notes): [Inventory] - Mealime / plan version notes I lock: [Version] - Household or workspace label I may quote (or UNKNOWN): [Workspace] - Required meal or day names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (macros, calorie totals, recipe IDs, grocery prices): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented macros, calorie totals, recipe IDs, grocery prices. Banner: not medical nutrition advice; not a live Mealime sync. 2. Weekly plan checklist table: one row per Inventory meal stub or ingredient cue. Missing day notes write NOT IN INPUTS. Use Mealime plan, grocery list, and pantry language when Inventory supports it. 3. Spec name set: only names in SpecNames. Unnamed meals stay NOT IN INPUTS. Never print macro or calorie VALUES not in Inventory. 4. Version lock: print Version. Refuse Mealime features newer than Version if Version is named. 5. Refuse list: inventing macros, inventing calorie totals, inventing recipe IDs, inventing grocery prices. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Checklist from Inventory only. No invented macro VALUES. Teach Mealime weekly plan mapping, not a generic diet-swap template. - Honor Version. No emojis.

mealimeweekly planno invented macros