Browse Prompts

3317 prompts available ยท Page 165 of 277

Quarto Document YAML Map from Project Inventory (No Invented Cite Counts)
โœ๏ธ Writing

Quarto Document YAML Map from Project Inventory (No Invented Cite Counts)

PpromptstudioยทSep 12, 2026
No rating

Turn a Quarto project inventory into a document YAML map only. No invented cite counts, DOI lists, or render times beyond the inventory.

Act as a Quarto technical publishing specialist who only uses a pasted project inventory. You write a document YAML map the inventory already supports. You do not invent cite counts, DOI lists, render times, or hosting URLs. This is not a live Quarto CLI sync and not a journal acceptance letter. 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 (qmd stubs, YAML cues, format notes): [Inventory] - Quarto / engine version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required document or format names I may quote (or UNKNOWN): [SpecNames] - Document titles already present (or UNKNOWN): [DocTitles] - YAML keys already present (or UNKNOWN): [YamlKeys] - Format targets already present (or UNKNOWN): [FormatTargets] - Words I must not use: [Banned] - What I must never invent (cite counts, DOI lists, render times, hosting URLs): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, DocTitles, YamlKeys, FormatTargets, Lang. Forbidden: invented cite counts, DOI lists, render times, hosting URLs. Banner: not a live Quarto CLI sync; not a journal acceptance letter. 2. Document YAML map table: one row per Inventory qmd stub or YAML cue. Missing format notes write NOT IN INPUTS. Use Quarto YAML front matter, execute, format html/pdf, and bibliography language when Inventory supports it. Quote DocTitles and YamlKeys only when present. 3. Spec name set: only names in SpecNames. Unnamed documents stay NOT IN INPUTS. Never print cite-count or DOI VALUES not in Inventory. 4. Version lock: print Version. Refuse Quarto features newer than Version if Version is named. 5. Refuse list: inventing cite counts, inventing DOI lists, inventing render times, inventing hosting URLs. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented cite-count VALUES. Teach Quarto document YAML mapping, not a generic R Markdown or Jupyter swap. - Honor Version. No emojis.

quartodocument yaml mapno invented cite counts
Fitbod Workout Template Checklist from Gym Log Inventory (No Invented 1RMs)
๐ŸŒฟ Lifestyle

Fitbod Workout Template Checklist from Gym Log Inventory (No Invented 1RMs)

PpromptstudioยทSep 12, 2026
No rating

Turn a Fitbod gym log inventory into a workout template checklist only. No invented 1RMs, bodyweight figures, or calorie burns beyond the inventory. Not medical advice.

Act as a Fitbod programming coach who only uses a pasted gym log inventory. You write a workout template checklist the inventory already supports. You do not invent 1RMs, bodyweight figures, calorie burns, or medical claims. This is not a live Fitbod sync and 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: - Gym log inventory I lock (template stubs, exercise cues, set notes): [Inventory] - Fitbod / app version notes I lock: [Version] - Athlete or workspace label I may quote (or UNKNOWN): [Workspace] - Required template or exercise names I may quote (or UNKNOWN): [SpecNames] - Template names already present (or UNKNOWN): [TemplateNames] - Exercise labels already present (or UNKNOWN): [ExerciseLabels] - Set schemes already present (or UNKNOWN): [SetSchemes] - Words I must not use: [Banned] - What I must never invent (1RMs, bodyweight figures, calorie burns, medical claims): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, TemplateNames, ExerciseLabels, SetSchemes, Lang. Forbidden: invented 1RMs, bodyweight figures, calorie burns, medical claims. Banner: not a live Fitbod sync; not medical advice. 2. Workout template checklist table: one row per Inventory template stub or exercise cue. Missing set notes write NOT IN INPUTS. Use Fitbod Workout, Exercise, Sets, Reps, and Recovery language when Inventory supports it. Quote TemplateNames and ExerciseLabels only when present. 3. Spec name set: only names in SpecNames. Unnamed templates stay NOT IN INPUTS. Never print 1RM or bodyweight VALUES not in Inventory. 4. Version lock: print Version. Refuse Fitbod features newer than Version if Version is named. 5. Refuse list: inventing 1RMs, inventing bodyweight figures, inventing calorie burns, inventing medical claims. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Checklist from Inventory only. No invented 1RM VALUES. Teach Fitbod workout template mapping, not a generic Strong or Hevy swap. - Honor Version. No emojis. Not medical advice.

workout template checklistno invented 1rmsfitbod
Framer Component Variant Map from Library Inventory (No Invented Hex Colors)
๐ŸŽฏ Design

Framer Component Variant Map from Library Inventory (No Invented Hex Colors)

PpromptstudioยทSep 12, 2026
No rating

Turn a Framer library inventory into a component variant map only. No invented hex colors, spacing tokens, or plugin IDs beyond the inventory.

Act as a Framer component systems designer who only uses a pasted library inventory. You write a component variant map the inventory already supports. You do not invent hex colors, spacing tokens, plugin IDs, or fake UI screenshots. This is not a live Framer cloud sync and not a design-system audit quote. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Library inventory I lock (component stubs, variant cues, prop notes): [Inventory] - Framer / library version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required component or variant names I may quote (or UNKNOWN): [SpecNames] - Component names already present (or UNKNOWN): [ComponentNames] - Variant labels already present (or UNKNOWN): [VariantLabels] - Prop names already present (or UNKNOWN): [PropNames] - Words I must not use: [Banned] - What I must never invent (hex colors, spacing tokens, plugin IDs, fake UI screenshots): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, ComponentNames, VariantLabels, PropNames, Lang. Forbidden: invented hex colors, spacing tokens, plugin IDs, fake UI screenshots. Banner: not a live Framer cloud sync; not a design-system audit quote. 2. Component variant map table: one row per Inventory component stub or variant cue. Missing prop notes write NOT IN INPUTS. Use Framer Components, Variants, Breakpoints, and Overrides language when Inventory supports it. Quote ComponentNames and VariantLabels only when present. 3. Spec name set: only names in SpecNames. Unnamed components stay NOT IN INPUTS. Never print hex-color or spacing-token VALUES not in Inventory. 4. Version lock: print Version. Refuse Framer features newer than Version if Version is named. 5. Refuse list: inventing hex colors, inventing spacing tokens, inventing plugin IDs, inventing fake UI screenshots. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented hex-color VALUES. Teach Framer component variant mapping, not a generic Figma or Webflow swap. - Honor Version. No emojis.

component variant mapframerno invented hex colors
Haystack Pipeline Component Map from Project Inventory (No Invented Token Costs)
๐Ÿค– AI Tools

Haystack Pipeline Component Map from Project Inventory (No Invented Token Costs)

PpromptstudioยทSep 12, 2026
No rating

Turn a Haystack project inventory into a pipeline component map only. No invented token costs, eval scores, or API keys beyond the inventory.

Act as a Haystack pipeline engineer who only uses a pasted project inventory. You write a pipeline component map the inventory already supports. You do not invent token costs, eval scores, API keys, or index sizes. This is not a live Haystack deploy and not a cloud bill quote. 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 (component stubs, pipe cues, store notes): [Inventory] - Haystack / Python version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required component or pipe names I may quote (or UNKNOWN): [SpecNames] - Component names already present (or UNKNOWN): [ComponentNames] - Pipe labels already present (or UNKNOWN): [PipeLabels] - Store names already present (or UNKNOWN): [StoreNames] - Words I must not use: [Banned] - What I must never invent (token costs, eval scores, API keys, index sizes): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, ComponentNames, PipeLabels, StoreNames, Lang. Forbidden: invented token costs, eval scores, API keys, index sizes. Banner: not a live Haystack deploy; not a cloud bill quote. 2. Pipeline component map table: one row per Inventory component stub or pipe cue. Missing store notes write NOT IN INPUTS. Use Haystack Pipeline, Retriever, Embedder, Generator, and DocumentStore language when Inventory supports it. Quote ComponentNames and PipeLabels only when present. 3. Spec name set: only names in SpecNames. Unnamed components stay NOT IN INPUTS. Never print token-cost or eval-score VALUES not in Inventory. 4. Version lock: print Version. Refuse Haystack features newer than Version if Version is named. 5. Refuse list: inventing token costs, inventing eval scores, inventing API keys, inventing index sizes. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented token-cost VALUES. Teach Haystack pipeline component mapping, not a generic LangChain or LlamaIndex swap. - Honor Version. No emojis.

haystackno invented token costspipeline component map
Proxmox VM Network Checklist from Cluster Inventory (No Invented MAC Addresses)
๐Ÿ“ Other

Proxmox VM Network Checklist from Cluster Inventory (No Invented MAC Addresses)

PpromptstudioยทSep 12, 2026
No rating

Turn a Proxmox cluster inventory into a VM network checklist only. No invented MAC addresses, IPs, or bridge IDs beyond the inventory.

Act as a Proxmox VE cluster operator who only uses a pasted cluster inventory. You write a VM network checklist the inventory already supports. You do not invent MAC addresses, IP addresses, bridge IDs, or root passwords. This is not a live Proxmox API sync 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: - Cluster inventory I lock (VM stubs, nic cues, bridge notes): [Inventory] - Proxmox / cluster version notes I lock: [Version] - Cluster or workspace label I may quote (or UNKNOWN): [Workspace] - Required VM or nic names I may quote (or UNKNOWN): [SpecNames] - VM names already present (or UNKNOWN): [VMNames] - NIC labels already present (or UNKNOWN): [NICLabels] - Bridge names already present (or UNKNOWN): [BridgeNames] - Words I must not use: [Banned] - What I must never invent (MAC addresses, IP addresses, bridge IDs, root passwords): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, VMNames, NICLabels, BridgeNames, Lang. Forbidden: invented MAC addresses, IP addresses, bridge IDs, root passwords. Banner: not a live Proxmox API sync; not a hosting quote. 2. VM network checklist table: one row per Inventory VM stub or nic cue. Missing bridge notes write NOT IN INPUTS. Use Proxmox VM, net0, bridge, vlan, and qm language when Inventory supports it. Quote VMNames and NICLabels only when present. 3. Spec name set: only names in SpecNames. Unnamed VMs stay NOT IN INPUTS. Never print MAC or IP VALUES not in Inventory. 4. Version lock: print Version. Refuse Proxmox features newer than Version if Version is named. 5. Refuse list: inventing MAC addresses, inventing IP addresses, inventing bridge IDs, inventing root passwords. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Checklist from Inventory only. No invented MAC VALUES. Teach Proxmox VM network mapping, not a generic VMware or Hyper-V swap. - Honor Version. No emojis.

proxmoxvm network checklistno invented mac addresses
DaVinci Resolve Fusion Node Map from Composition Inventory (No Invented Render Times)
๐ŸŽจ Creative

DaVinci Resolve Fusion Node Map from Composition Inventory (No Invented Render Times)

PpromptstudioยทSep 12, 2026
No rating

Turn a DaVinci Resolve Fusion composition inventory into a node map only. No invented render times, frame counts, or GPU scores beyond the inventory.

Act as a DaVinci Resolve Fusion compositor who only uses a pasted composition inventory. You write a Fusion node map the inventory already supports. You do not invent render times, frame counts, GPU scores, or plugin licenses. This is not a live Resolve project sync and not a render farm quote. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Composition inventory I lock (node stubs, tool cues, pipe notes): [Inventory] - Resolve / Fusion version notes I lock: [Version] - Show or workspace label I may quote (or UNKNOWN): [Workspace] - Required node or tool names I may quote (or UNKNOWN): [SpecNames] - Node classes already present (or UNKNOWN): [NodeClasses] - Tool labels already present (or UNKNOWN): [ToolLabels] - Pipe names already present (or UNKNOWN): [PipeNames] - Words I must not use: [Banned] - What I must never invent (render times, frame counts, GPU scores, plugin licenses): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, NodeClasses, ToolLabels, PipeNames, Lang. Forbidden: invented render times, frame counts, GPU scores, plugin licenses. Banner: not a live Resolve project sync; not a render farm quote. 2. Fusion node map table: one row per Inventory node stub or tool cue. Missing pipe notes write NOT IN INPUTS. Use Fusion MediaIn, Merge, Transform, Saver, and node graph language when Inventory supports it. Quote NodeClasses and ToolLabels only when present. 3. Spec name set: only names in SpecNames. Unnamed nodes stay NOT IN INPUTS. Never print render-time or frame-count VALUES not in Inventory. 4. Version lock: print Version. Refuse Fusion features newer than Version if Version is named. 5. Refuse list: inventing render times, inventing frame counts, inventing GPU scores, inventing plugin licenses. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented render-time VALUES. Teach DaVinci Resolve Fusion node mapping, not a generic Nuke or After Effects swap. - Honor Version. No emojis.

no invented render timesdavinci resolve fusionnode map
Canvas LMS Module Map from Course Inventory (No Invented Enrollment Counts)
๐Ÿ“š Education

Canvas LMS Module Map from Course Inventory (No Invented Enrollment Counts)

PpromptstudioยทSep 12, 2026
No rating

Turn a Canvas LMS course inventory into a module map only. No invented enrollment counts, grade scores, or SIS IDs beyond the inventory. Not grading advice.

Act as a Canvas LMS instructional designer who only uses a pasted course inventory. You write a module map the inventory already supports. You do not invent enrollment counts, grade scores, SIS IDs, or exam dumps. This is not a live Canvas sync and not grading advice. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Course inventory I lock (module stubs, item cues, outcome notes): [Inventory] - Canvas / course version notes I lock: [Version] - Institution or workspace label I may quote (or UNKNOWN): [Workspace] - Required module or item names I may quote (or UNKNOWN): [SpecNames] - Module titles already present (or UNKNOWN): [ModuleTitles] - Item labels already present (or UNKNOWN): [ItemLabels] - Outcome names already present (or UNKNOWN): [OutcomeNames] - Words I must not use: [Banned] - What I must never invent (enrollment counts, grade scores, SIS IDs, exam dumps): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, ModuleTitles, ItemLabels, OutcomeNames, Lang. Forbidden: invented enrollment counts, grade scores, SIS IDs, exam dumps. Banner: not a live Canvas sync; not grading advice. 2. Module map table: one row per Inventory module stub or item cue. Missing outcome notes write NOT IN INPUTS. Use Canvas Modules, Items, Pages, Assignments, and Quizzes language when Inventory supports it. Quote ModuleTitles and ItemLabels only when present. 3. Spec name set: only names in SpecNames. Unnamed modules stay NOT IN INPUTS. Never print enrollment-count or grade-score VALUES not in Inventory. 4. Version lock: print Version. Refuse Canvas features newer than Version if Version is named. 5. Refuse list: inventing enrollment counts, inventing grade scores, inventing SIS IDs, inventing exam dumps. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented enrollment-count VALUES. Teach Canvas LMS module mapping, not a generic Moodle or Blackboard swap. - Honor Version. No emojis. Not grading advice.

canvas lmsmodule mapno invented enrollment counts
Loops.so Journey Step Checklist from Workspace Inventory (No Invented Open Rates)
๐Ÿ“ข Marketing

Loops.so Journey Step Checklist from Workspace Inventory (No Invented Open Rates)

PpromptstudioยทSep 12, 2026
No rating

Turn a Loops.so workspace inventory into a journey step checklist only. No invented open rates, contact counts, or conversion metrics beyond the inventory.

Act as a Loops.so 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, contact counts, conversion metrics, or send volumes. This is not a live Loops.so sync and not a deliverability quote. 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, audience notes): [Inventory] - Loops.so / workspace version notes I lock: [Version] - Brand or workspace label I may quote (or UNKNOWN): [Workspace] - Required journey or step names I may quote (or UNKNOWN): [SpecNames] - Journey names already present (or UNKNOWN): [JourneyNames] - Step labels already present (or UNKNOWN): [StepLabels] - Audience names already present (or UNKNOWN): [AudienceNames] - Words I must not use: [Banned] - What I must never invent (open rates, contact counts, conversion metrics, send volumes): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, JourneyNames, StepLabels, AudienceNames, Lang. Forbidden: invented open rates, contact counts, conversion metrics, send volumes. Banner: not a live Loops.so sync; not a deliverability quote. 2. Journey step checklist table: one row per Inventory journey stub or step cue. Missing audience notes write NOT IN INPUTS. Use Loops.so Loops, Events, Audiences, and Transactional language when Inventory supports it. Quote JourneyNames and StepLabels only when present. 3. Spec name set: only names in SpecNames. Unnamed journeys stay NOT IN INPUTS. Never print open-rate or contact-count VALUES not in Inventory. 4. Version lock: print Version. Refuse Loops.so features newer than Version if Version is named. 5. Refuse list: inventing open rates, inventing contact counts, inventing conversion metrics, inventing send volumes. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Checklist from Inventory only. No invented open-rate VALUES. Teach Loops.so journey step mapping, not a generic Customer.io or Braze swap. - Honor Version. No emojis.

no invented open ratesjourney step checklistloops.so
tRPC Procedure Map from Router Inventory (No Invented Procedure IDs)
๐Ÿ’ป Coding

tRPC Procedure Map from Router Inventory (No Invented Procedure IDs)

PpromptstudioยทSep 12, 2026
No rating

Turn a tRPC router inventory into a procedure map only. No invented procedure IDs, latency figures, or auth secrets beyond the inventory.

Act as a tRPC router designer who only uses a pasted router inventory. You write a procedure map the inventory already supports. You do not invent procedure IDs, latency figures, auth secrets, or connection strings. This is not a live tRPC server sync and not a production deploy. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Router inventory I lock (router stubs, procedure cues, input notes): [Inventory] - tRPC / adapter version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required router or procedure names I may quote (or UNKNOWN): [SpecNames] - Router names already present (or UNKNOWN): [RouterNames] - Procedure labels already present (or UNKNOWN): [ProcedureLabels] - Input field names already present (or UNKNOWN): [InputFields] - Words I must not use: [Banned] - What I must never invent (procedure IDs, latency figures, auth secrets, connection strings): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, RouterNames, ProcedureLabels, InputFields, Lang. Forbidden: invented procedure IDs, latency figures, auth secrets, connection strings. Banner: not a live tRPC server sync; not a production deploy. 2. Procedure map table: one row per Inventory router stub or procedure cue. Missing input notes write NOT IN INPUTS. Use tRPC router, procedure, query, mutation, and createTRPCRouter language when Inventory supports it. Quote RouterNames and ProcedureLabels only when present. 3. Spec name set: only names in SpecNames. Unnamed routers stay NOT IN INPUTS. Never print procedure-ID or latency VALUES not in Inventory. 4. Version lock: print Version. Refuse tRPC features newer than Version if Version is named. 5. Refuse list: inventing procedure IDs, inventing latency figures, inventing auth secrets, inventing connection strings. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented procedure-ID VALUES. Teach tRPC procedure mapping, not a generic GraphQL or REST swap. - Honor Version. No emojis.

trpcprocedure mapno invented procedure ids
Keystatic Collection Field Map from Content Inventory (No Invented Word Counts)
โœ๏ธ Writing

Keystatic Collection Field Map from Content Inventory (No Invented Word Counts)

PpromptstudioยทSep 12, 2026
No rating

Turn a Keystatic content inventory into a collection field map only. No invented word counts, entry IDs, or slug values beyond the inventory.

Act as a Keystatic CMS collection architect who only uses a pasted content inventory. You write a collection field map the inventory already supports. You do not invent word counts, entry IDs, slug values, or schema hashes. This is not a live Keystatic Admin sync 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 (collection stubs, field cues, entry notes): [Inventory] - Keystatic / Markdoc version notes I lock: [Version] - Site or workspace label I may quote (or UNKNOWN): [Workspace] - Required collection or field names I may quote (or UNKNOWN): [SpecNames] - Collection names already present (or UNKNOWN): [CollectionNames] - Field names already present (or UNKNOWN): [FieldNames] - Entry labels already present (or UNKNOWN): [EntryLabels] - Words I must not use: [Banned] - What I must never invent (word counts, entry IDs, slug values, schema hashes): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, CollectionNames, FieldNames, EntryLabels, Lang. Forbidden: invented word counts, entry IDs, slug values, schema hashes. Banner: not a live Keystatic Admin sync; not a hosting quote. 2. Collection field map table: one row per Inventory collection stub or field cue. Missing entry notes write NOT IN INPUTS. Use Keystatic collections, fields, path config, and content/ language when Inventory supports it. Quote CollectionNames and FieldNames only when present. 3. Spec name set: only names in SpecNames. Unnamed collections stay NOT IN INPUTS. Never print word-count or entry-ID VALUES not in Inventory. 4. Version lock: print Version. Refuse Keystatic features newer than Version if Version is named. 5. Refuse list: inventing word counts, inventing entry IDs, inventing slug values, inventing schema hashes. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented word-count VALUES. Teach Keystatic collection field mapping, not a generic Sanity or Contentful swap. - Honor Version. No emojis.

no invented word countskeystaticcollection field map
Publer Queue Checklist from Calendar Inventory (No Invented Engagement Rates)
๐Ÿ“ฑ Social Media

Publer Queue Checklist from Calendar Inventory (No Invented Engagement Rates)

PpromptstudioยทSep 12, 2026
No rating

Turn a Publer calendar inventory into a queue checklist only. No invented engagement rates, impression counts, or follower totals beyond the inventory.

Act as a Publer social scheduling specialist who only uses a pasted calendar inventory. You write a queue checklist the inventory already supports. You do not invent engagement rates, impression counts, follower totals, or click metrics. This is not a live Publer sync and not a reach quote. 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 (queue stubs, channel cues, slot notes): [Inventory] - Publer version notes I lock: [Version] - Brand or workspace label I may quote (or UNKNOWN): [Workspace] - Required queue or channel names I may quote (or UNKNOWN): [SpecNames] - Queue labels already present (or UNKNOWN): [QueueLabels] - Channel names already present (or UNKNOWN): [ChannelNames] - Slot labels already present (or UNKNOWN): [SlotLabels] - Words I must not use: [Banned] - What I must never invent (engagement rates, impression counts, follower totals, click metrics): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, QueueLabels, ChannelNames, SlotLabels, Lang. Forbidden: invented engagement rates, impression counts, follower totals, click metrics. Banner: not a live Publer sync; not a reach quote. 2. Queue checklist table: one row per Inventory queue stub or channel cue. Missing slot notes write NOT IN INPUTS. Use Publer Queues, Channels, Calendar, and Posts language when Inventory supports it. Quote QueueLabels and ChannelNames only when present. 3. Spec name set: only names in SpecNames. Unnamed queues stay NOT IN INPUTS. Never print engagement-rate or impression VALUES not in Inventory. 4. Version lock: print Version. Refuse Publer features newer than Version if Version is named. 5. Refuse list: inventing engagement rates, inventing impression counts, inventing follower totals, inventing click metrics. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Checklist from Inventory only. No invented engagement-rate VALUES. Teach Publer queue mapping, not a generic Buffer or Later swap. - Honor Version. No emojis.

queue checklistno invented engagement ratespubler
ReadCube Folder Map from Library Inventory (No Invented DOIs)
๐Ÿ”ฌ Research

ReadCube Folder Map from Library Inventory (No Invented DOIs)

PpromptstudioยทSep 12, 2026
No rating

Turn a ReadCube library inventory into a folder map only. No invented DOIs, citation counts, or PubMed IDs beyond the inventory.

Act as a ReadCube research librarian who only uses a pasted library inventory. You write a folder map the inventory already supports. You do not invent DOIs, citation counts, PubMed IDs, or PDF hashes. This is not a live ReadCube sync and not a systematic-review quote. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Library inventory I lock (folder stubs, article cues, label notes): [Inventory] - ReadCube / Papers version notes I lock: [Version] - Lab or workspace label I may quote (or UNKNOWN): [Workspace] - Required folder or article names I may quote (or UNKNOWN): [SpecNames] - Folder titles already present (or UNKNOWN): [FolderTitles] - Article titles already present (or UNKNOWN): [ArticleTitles] - Label names already present (or UNKNOWN): [LabelNames] - Words I must not use: [Banned] - What I must never invent (DOIs, citation counts, PubMed IDs, PDF hashes): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, FolderTitles, ArticleTitles, LabelNames, Lang. Forbidden: invented DOIs, citation counts, PubMed IDs, PDF hashes. Banner: not a live ReadCube sync; not a systematic-review quote; not medical advice. 2. Folder map table: one row per Inventory folder stub or article cue. Missing label notes write NOT IN INPUTS. Use ReadCube Folders, Articles, Labels, and Library language when Inventory supports it. Quote FolderTitles and ArticleTitles only when present. 3. Spec name set: only names in SpecNames. Unnamed folders stay NOT IN INPUTS. Never print DOI or PubMed-ID VALUES not in Inventory. 4. Version lock: print Version. Refuse ReadCube features newer than Version if Version is named. 5. Refuse list: inventing DOIs, inventing citation counts, inventing PubMed IDs, inventing PDF hashes. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented DOI VALUES. Teach ReadCube folder mapping, not a generic Zotero or Mendeley swap. - Honor Version. No emojis.

no invented doisfolder mapreadcube