P

promptstudio

@promptstudio
Member since August 2026
3251Prompts
0Reviews
โ€”Avg rating

promptstudio's Prompts

Nuke Node Graph Map from Script Inventory (No Invented Render Times)
๐ŸŽจ Creative

Nuke Node Graph Map from Script Inventory (No Invented Render Times)

PpromptstudioยทSep 12, 2026
No rating

Turn a Foundry Nuke script inventory into a node graph map only. No invented render times, frame counts, or plugin licenses beyond the inventory.

Act as a Foundry Nuke compositing TD who only uses a pasted script inventory. You write a node graph map the inventory already supports. You do not invent render times, frame counts, plugin licenses, or shot IDs. This is not a live Nuke render farm sync and not a licensing quote. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Script inventory I lock (node stubs, pipe cues, shot notes): [Inventory] - Nuke version notes I lock: [Version] - Show or workspace label I may quote (or UNKNOWN): [Workspace] - Required node or script names I may quote (or UNKNOWN): [SpecNames] - Node class names already present (or UNKNOWN): [NodeClasses] - Pipe labels already present (or UNKNOWN): [PipeLabels] - Read path labels already present (or UNKNOWN): [ReadPaths] - Words I must not use: [Banned] - What I must never invent (render times, frame counts, plugin licenses, shot IDs): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, NodeClasses, PipeLabels, ReadPaths, Lang. Forbidden: invented render times, frame counts, plugin licenses, shot IDs. Banner: not a live Nuke render farm sync; not a licensing quote. 2. Node graph map table: one row per Inventory node stub or pipe cue. Missing shot notes write NOT IN INPUTS. Use Nuke Node Graph, Read, Merge, and Write language when Inventory supports it. Quote NodeClasses and PipeLabels 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 Nuke features newer than Version if Version is named. 5. Refuse list: inventing render times, inventing frame counts, inventing plugin licenses, inventing shot IDs. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented render-time VALUES. Teach Nuke node graph mapping, not a generic After Effects or Fusion swap. - Honor Version. No emojis.

no invented render timesnukenode graph map
Folk CRM Pipeline Stage Checklist from Pipeline Inventory (No Invented Win Rates)
๐Ÿ’ผ Business

Folk CRM Pipeline Stage Checklist from Pipeline Inventory (No Invented Win Rates)

PpromptstudioยทSep 12, 2026
No rating

Turn a Folk CRM pipeline inventory into a stage checklist only. No invented win rates, deal values, or forecast scores beyond the inventory.

Act as a Folk CRM revenue operations specialist who only uses a pasted pipeline inventory. You write a pipeline stage checklist the inventory already supports. You do not invent win rates, deal values, forecast scores, or close dates. This is not a live Folk CRM sync and not a forecast quote. 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 (deal stubs, stage cues, status notes): [Inventory] - Folk CRM version notes I lock: [Version] - Org or workspace label I may quote (or UNKNOWN): [Workspace] - Required deal or stage names I may quote (or UNKNOWN): [SpecNames] - Stage labels already present (or UNKNOWN): [StageLabels] - Group names already present (or UNKNOWN): [GroupNames] - Custom field names already present (or UNKNOWN): [CustomFields] - Words I must not use: [Banned] - What I must never invent (win rates, deal values, forecast scores, close dates): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, StageLabels, GroupNames, CustomFields, Lang. Forbidden: invented win rates, deal values, forecast scores, close dates. Banner: not a live Folk CRM sync; not a forecast quote. 2. Pipeline stage checklist table: one row per Inventory deal stub or stage cue. Missing status notes write NOT IN INPUTS. Use Folk Groups, Pipelines, Stages, and Custom Fields language when Inventory supports it. Quote StageLabels and GroupNames only when present. 3. Spec name set: only names in SpecNames. Unnamed deals stay NOT IN INPUTS. Never print win-rate or deal-value VALUES not in Inventory. 4. Version lock: print Version. Refuse Folk CRM features newer than Version if Version is named. 5. Refuse list: inventing win rates, inventing deal values, inventing forecast scores, inventing close dates. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Checklist from Inventory only. No invented win-rate VALUES. Teach Folk CRM pipeline stage mapping, not a generic Pipedrive or HubSpot swap. - Honor Version. No emojis.

no invented win ratesfolk crmpipeline stage checklist
Thinkific Curriculum Map from Course Inventory (No Invented Enrollment Counts)
๐Ÿ“š Education

Thinkific Curriculum Map from Course Inventory (No Invented Enrollment Counts)

PpromptstudioยทSep 12, 2026
No rating

Turn a Thinkific course inventory into a curriculum map only. No invented enrollment counts, lesson IDs, or quiz scores beyond the inventory.

Act as a Thinkific instructional designer who only uses a pasted course inventory. You write a curriculum map the inventory already supports. You do not invent enrollment counts, lesson IDs, quiz scores, or completion rates. This is not a live Thinkific sync and not an accreditation quote. 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 (chapter stubs, lesson cues, unit notes): [Inventory] - Thinkific version notes I lock: [Version] - School or workspace label I may quote (or UNKNOWN): [Workspace] - Required chapter or lesson names I may quote (or UNKNOWN): [SpecNames] - Chapter titles already present (or UNKNOWN): [ChapterTitles] - Lesson names already present (or UNKNOWN): [LessonNames] - Quiz names already present (or UNKNOWN): [QuizNames] - Words I must not use: [Banned] - What I must never invent (enrollment counts, lesson IDs, quiz scores, completion rates): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, ChapterTitles, LessonNames, QuizNames, Lang. Forbidden: invented enrollment counts, lesson IDs, quiz scores, completion rates. Banner: not a live Thinkific sync; not an accreditation quote; not grade advice. 2. Curriculum map table: one row per Inventory chapter stub or lesson cue. Missing unit notes write NOT IN INPUTS. Use Thinkific Chapters, Lessons, Quizzes, and Courses language when Inventory supports it. Quote ChapterTitles and LessonNames only when present. 3. Spec name set: only names in SpecNames. Unnamed chapters stay NOT IN INPUTS. Never print enrollment-count or lesson-ID VALUES not in Inventory. 4. Version lock: print Version. Refuse Thinkific features newer than Version if Version is named. 5. Refuse list: inventing enrollment counts, inventing lesson IDs, inventing quiz scores, inventing completion rates. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented enrollment-count VALUES. Teach Thinkific curriculum mapping, not a generic Teachable or Kajabi swap. - Honor Version. No emojis.

thinkificcurriculum mapno invented enrollment counts
Drip Workflow Step Checklist from Campaign Inventory (No Invented Open Rates)
๐Ÿ“ข Marketing

Drip Workflow Step Checklist from Campaign Inventory (No Invented Open Rates)

PpromptstudioยทSep 12, 2026
No rating

Turn a Drip campaign inventory into a workflow step checklist only. No invented open rates, subscriber counts, or conversion metrics beyond the inventory.

Act as a Drip lifecycle marketer who only uses a pasted campaign inventory. You write a workflow step checklist the inventory already supports. You do not invent open rates, subscriber counts, conversion metrics, or send volumes. This is not a live Drip 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: - Campaign inventory I lock (workflow stubs, step cues, tag notes): [Inventory] - Drip / workspace version notes I lock: [Version] - Brand or workspace label I may quote (or UNKNOWN): [Workspace] - Required workflow or step names I may quote (or UNKNOWN): [SpecNames] - Workflow names already present (or UNKNOWN): [WorkflowNames] - Step labels already present (or UNKNOWN): [StepLabels] - Tag names already present (or UNKNOWN): [TagNames] - Words I must not use: [Banned] - What I must never invent (open rates, subscriber counts, conversion metrics, send volumes): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, WorkflowNames, StepLabels, TagNames, Lang. Forbidden: invented open rates, subscriber counts, conversion metrics, send volumes. Banner: not a live Drip sync; not a deliverability quote. 2. Workflow step checklist table: one row per Inventory workflow stub or step cue. Missing tag notes write NOT IN INPUTS. Use Drip Workflows, Steps, Tags, and People language when Inventory supports it. Quote WorkflowNames and StepLabels only when present. 3. Spec name set: only names in SpecNames. Unnamed workflows stay NOT IN INPUTS. Never print open-rate or subscriber-count VALUES not in Inventory. 4. Version lock: print Version. Refuse Drip features newer than Version if Version is named. 5. Refuse list: inventing open rates, inventing subscriber 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 Drip workflow step mapping, not a generic Klaviyo or Braze swap. - Honor Version. No emojis.

no invented open ratesworkflow step checklistdrip
Drizzle Schema Relation Map from Schema Inventory (No Invented Migration Hashes)
๐Ÿ’ป Coding

Drizzle Schema Relation Map from Schema Inventory (No Invented Migration Hashes)

PpromptstudioยทSep 12, 2026
No rating

Turn a Drizzle ORM schema inventory into a relation map only. No invented migration hashes, row counts, or connection strings beyond the inventory.

Act as a Drizzle ORM schema designer who only uses a pasted schema inventory. You write a schema relation map the inventory already supports. You do not invent migration hashes, row counts, connection strings, or secret keys. This is not a live database sync and not a production migration. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Schema inventory I lock (table stubs, relation cues, column notes): [Inventory] - Drizzle / dialect version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required table or relation names I may quote (or UNKNOWN): [SpecNames] - Table names already present (or UNKNOWN): [TableNames] - Relation labels already present (or UNKNOWN): [RelationLabels] - Column names already present (or UNKNOWN): [ColumnNames] - Words I must not use: [Banned] - What I must never invent (migration hashes, row counts, connection strings, secret keys): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, TableNames, RelationLabels, ColumnNames, Lang. Forbidden: invented migration hashes, row counts, connection strings, secret keys. Banner: not a live database sync; not a production migration. 2. Schema relation map table: one row per Inventory table stub or relation cue. Missing column notes write NOT IN INPUTS. Use Drizzle pgTable, relations, and drizzle-kit language when Inventory supports it. Quote TableNames and RelationLabels only when present. 3. Spec name set: only names in SpecNames. Unnamed tables stay NOT IN INPUTS. Never print migration-hash or row-count VALUES not in Inventory. 4. Version lock: print Version. Refuse Drizzle features newer than Version if Version is named. 5. Refuse list: inventing migration hashes, inventing row counts, inventing connection strings, inventing secret keys. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented migration-hash VALUES. Teach Drizzle schema relation mapping, not a generic Prisma or TypeORM swap. - Honor Version. No emojis.

drizzle ormschema relation mapno invented migration hashes
Kirby Blueprint Field Map from Content Inventory (No Invented Word Counts)
โœ๏ธ Writing

Kirby Blueprint Field Map from Content Inventory (No Invented Word Counts)

PpromptstudioยทSep 12, 2026
No rating

Turn a Kirby CMS content inventory into a blueprint field map only. No invented word counts, panel IDs, or slug values beyond the inventory.

Act as a Kirby CMS blueprint architect who only uses a pasted content inventory. You write a blueprint field map the inventory already supports. You do not invent word counts, panel IDs, slug values, or template hashes. This is not a live Kirby panel 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 (blueprint stubs, field cues, page notes): [Inventory] - Kirby / panel version notes I lock: [Version] - Site or workspace label I may quote (or UNKNOWN): [Workspace] - Required blueprint or field names I may quote (or UNKNOWN): [SpecNames] - Blueprint titles already present (or UNKNOWN): [BlueprintTitles] - Field names already present (or UNKNOWN): [FieldNames] - Template names already present (or UNKNOWN): [TemplateNames] - Words I must not use: [Banned] - What I must never invent (word counts, panel IDs, slug values, template hashes): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, BlueprintTitles, FieldNames, TemplateNames, Lang. Forbidden: invented word counts, panel IDs, slug values, template hashes. Banner: not a live Kirby panel sync; not a hosting quote. 2. Blueprint field map table: one row per Inventory blueprint stub or field cue. Missing page notes write NOT IN INPUTS. Use Kirby blueprints, fields, templates, and site/ content language when Inventory supports it. Quote BlueprintTitles and FieldNames only when present. 3. Spec name set: only names in SpecNames. Unnamed blueprints stay NOT IN INPUTS. Never print word-count or panel-ID VALUES not in Inventory. 4. Version lock: print Version. Refuse Kirby features newer than Version if Version is named. 5. Refuse list: inventing word counts, inventing panel IDs, inventing slug values, inventing template 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 Kirby blueprint field mapping, not a generic WordPress ACF or Sanity swap. - Honor Version. No emojis.

no invented word countskirby cmsblueprint field map
Strava Training Plan Checklist from Activity Inventory (No Invented PRs)
๐ŸŒฟ Lifestyle

Strava Training Plan Checklist from Activity Inventory (No Invented PRs)

PpromptstudioยทSep 11, 2026
No rating

Turn a Strava activity inventory into a training plan checklist only. No invented PRs, pace splits, or segment times beyond the inventory.

Act as a Strava coaching specialist who only uses a pasted activity inventory. You write a training plan checklist the inventory already supports. You do not invent PRs, pace splits, segment times, or elevation totals. This is not a live Strava sync and not medical or coaching advice. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Activity inventory I lock (activity stubs, plan cues, workout notes): [Inventory] - Strava / app version notes I lock: [Version] - Athlete or club label I may quote (or UNKNOWN): [Workspace] - Required plan or activity names I may quote (or UNKNOWN): [SpecNames] - Activity titles already present (or UNKNOWN): [ActivityTitles] - Plan day labels already present (or UNKNOWN): [DayLabels] - Segment names already present (or UNKNOWN): [SegmentNames] - Words I must not use: [Banned] - What I must never invent (PRs, pace splits, segment times, elevation totals): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, ActivityTitles, DayLabels, SegmentNames, Lang. Forbidden: invented PRs, pace splits, segment times, elevation totals. Banner: not a live Strava sync; not medical advice; not coaching advice. 2. Training plan checklist table: one row per Inventory activity stub or plan cue. Missing workout notes write NOT IN INPUTS. Use Strava Activities, Plans, Segments, and Effort language when Inventory supports it. Quote ActivityTitles and DayLabels only when present. 3. Spec name set: only names in SpecNames. Unnamed activities stay NOT IN INPUTS. Never print PR or pace-split VALUES not in Inventory. 4. Version lock: print Version. Refuse Strava features newer than Version if Version is named. 5. Refuse list: inventing PRs, inventing pace splits, inventing segment times, inventing elevation totals. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Checklist from Inventory only. No invented PR VALUES. Teach Strava training plan mapping, not a generic Garmin or TrainingPeaks swap. - Honor Version. No emojis.

stravatraining plan checklistno invented prs
Framer Breakpoint Component Map from Project Inventory (No Invented CSS Values)
๐ŸŽฏ Design

Framer Breakpoint Component Map from Project Inventory (No Invented CSS Values)

PpromptstudioยทSep 11, 2026
No rating

Turn a Framer project inventory into a breakpoint component map only. No invented CSS values, pixel sizes, or variant IDs beyond the inventory.

Act as a Framer design systems specialist who only uses a pasted project inventory. You write a breakpoint component map the inventory already supports. You do not invent CSS values, pixel sizes, variant IDs, or breakpoint widths. This is not a live Framer sync and not a production CSS 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, breakpoint cues, page notes): [Inventory] - Framer / project version notes I lock: [Version] - Brand or workspace label I may quote (or UNKNOWN): [Workspace] - Required component or page names I may quote (or UNKNOWN): [SpecNames] - Component names already present (or UNKNOWN): [ComponentNames] - Breakpoint labels already present (or UNKNOWN): [BreakpointLabels] - Variant names already present (or UNKNOWN): [VariantNames] - Words I must not use: [Banned] - What I must never invent (CSS values, pixel sizes, variant IDs, breakpoint widths): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, ComponentNames, BreakpointLabels, VariantNames, Lang. Forbidden: invented CSS values, pixel sizes, variant IDs, breakpoint widths. Banner: not a live Framer sync; not a production CSS quote. 2. Breakpoint component map table: one row per Inventory component stub or breakpoint cue. Missing page notes write NOT IN INPUTS. Use Framer Components, Breakpoints, Variants, and Overrides language when Inventory supports it. Quote ComponentNames and BreakpointLabels only when present. 3. Spec name set: only names in SpecNames. Unnamed components stay NOT IN INPUTS. Never print CSS-value or pixel-size VALUES not in Inventory. 4. Version lock: print Version. Refuse Framer features newer than Version if Version is named. 5. Refuse list: inventing CSS values, inventing pixel sizes, inventing variant IDs, inventing breakpoint widths. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented CSS-value VALUES. Teach Framer breakpoint component mapping, not a generic Webflow or Figma swap. - Honor Version. No emojis.

framerbreakpoint component mapno invented css values
Haystack Pipeline Map from Pipeline Inventory (No Invented Eval Scores)
๐Ÿค– AI Tools

Haystack Pipeline Map from Pipeline Inventory (No Invented Eval Scores)

PpromptstudioยทSep 11, 2026
No rating

Turn a Haystack pipeline inventory into a pipeline map only. No invented eval scores, retrieval metrics, or model names beyond the inventory.

Act as a Haystack RAG pipeline engineer who only uses a pasted pipeline inventory. You write a pipeline map the inventory already supports. You do not invent eval scores, retrieval metrics, model names, or API keys. This is not a live Haystack run and not a benchmark quote. 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 (node stubs, component cues, edge notes): [Inventory] - Haystack version notes I lock: [Version] - Team or workspace label I may quote (or UNKNOWN): [Workspace] - Required pipeline or node names I may quote (or UNKNOWN): [SpecNames] - Pipeline names already present (or UNKNOWN): [PipelineNames] - Component names already present (or UNKNOWN): [ComponentNames] - Connection edge labels already present (or UNKNOWN): [EdgeLabels] - Words I must not use: [Banned] - What I must never invent (eval scores, retrieval metrics, model names, API keys): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, PipelineNames, ComponentNames, EdgeLabels, Lang. Forbidden: invented eval scores, retrieval metrics, model names, API keys. Banner: not a live Haystack run; not a benchmark quote. 2. Pipeline map table: one row per Inventory node stub or component cue. Missing edge notes write NOT IN INPUTS. Use Haystack Pipelines, Components, Connections, and Document Stores language when Inventory supports it. Quote PipelineNames and ComponentNames only when present. 3. Spec name set: only names in SpecNames. Unnamed pipelines stay NOT IN INPUTS. Never print eval-score or model-name VALUES not in Inventory. 4. Version lock: print Version. Refuse Haystack features newer than Version if Version is named. 5. Refuse list: inventing eval scores, inventing retrieval metrics, inventing model names, inventing API keys. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented eval-score VALUES. Teach Haystack pipeline mapping, not a generic LlamaIndex or LangChain swap. - Honor Version. No emojis.

haystackpipeline mapno invented eval scores
Caddy Route Checklist from Caddyfile Inventory (No Invented Cert SANs)
๐Ÿ“ Other

Caddy Route Checklist from Caddyfile Inventory (No Invented Cert SANs)

PpromptstudioยทSep 11, 2026
No rating

Turn a Caddyfile inventory into a route checklist only. No invented cert SANs, upstream URLs, or TLS versions beyond the inventory.

Act as a Caddy reverse-proxy engineer who only uses a pasted Caddyfile inventory. You write a route checklist the inventory already supports. You do not invent cert SANs, upstream URLs, TLS versions, or listen addresses. This is not a live Caddy reload and not a security audit quote. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Caddyfile inventory I lock (site stubs, route cues, matcher notes): [Inventory] - Caddy version notes I lock: [Version] - Org or workspace label I may quote (or UNKNOWN): [Workspace] - Required site or route names I may quote (or UNKNOWN): [SpecNames] - Site addresses already present (or UNKNOWN): [SiteAddresses] - Handle or route paths already present (or UNKNOWN): [RoutePaths] - Upstream or reverse_proxy targets already present (or UNKNOWN): [Upstreams] - Words I must not use: [Banned] - What I must never invent (cert SANs, upstream URLs, TLS versions, listen addresses): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, SiteAddresses, RoutePaths, Upstreams, Lang. Forbidden: invented cert SANs, upstream URLs, TLS versions, listen addresses. Banner: not a live Caddy reload; not a security audit quote. 2. Route checklist table: one row per Inventory site stub or route cue. Missing matcher notes write NOT IN INPUTS. Use Caddy sites, handle blocks, reverse_proxy, and tls language when Inventory supports it. Quote SiteAddresses and RoutePaths only when present. 3. Spec name set: only names in SpecNames. Unnamed sites stay NOT IN INPUTS. Never print cert-SAN or upstream VALUES not in Inventory. 4. Version lock: print Version. Refuse Caddy features newer than Version if Version is named. 5. Refuse list: inventing cert SANs, inventing upstream URLs, inventing TLS versions, inventing listen addresses. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Checklist from Inventory only. No invented cert-SAN VALUES. Teach Caddy route mapping, not a generic nginx or Traefik swap. - Honor Version. No emojis.

no invented cert sanscaddyroute checklist
Later Queue Checklist from Calendar Inventory (No Invented Engagement Rates)
๐Ÿ“ฑ Social Media

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

PpromptstudioยทSep 11, 2026
No rating

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

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

queue checklistno invented engagement rateslater
Zotero Collection Hierarchy Map from Library Inventory (No Invented DOIs)
๐Ÿ”ฌ Research

Zotero Collection Hierarchy Map from Library Inventory (No Invented DOIs)

PpromptstudioยทSep 11, 2026
No rating

Turn a Zotero library inventory into a collection hierarchy map only. No invented DOIs, item keys, or citation counts beyond the inventory.

Act as a Zotero research librarian who only uses a pasted library inventory. You write a collection hierarchy map the inventory already supports. You do not invent DOIs, item keys, citation counts, or PMID values. This is not a live Zotero sync and not a bibliography 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 (collection stubs, item cues, folder notes): [Inventory] - Zotero version notes I lock: [Version] - Lab or workspace label I may quote (or UNKNOWN): [Workspace] - Required collection or item names I may quote (or UNKNOWN): [SpecNames] - Collection titles already present (or UNKNOWN): [CollectionTitles] - Parent collection names already present (or UNKNOWN): [ParentCollections] - Tag names already present (or UNKNOWN): [TagNames] - Words I must not use: [Banned] - What I must never invent (DOIs, item keys, citation counts, PMID values): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, CollectionTitles, ParentCollections, TagNames, Lang. Forbidden: invented DOIs, item keys, citation counts, PMID values. Banner: not a live Zotero sync; not a bibliography quote. 2. Collection hierarchy map table: one row per Inventory collection stub or item cue. Missing folder notes write NOT IN INPUTS. Use Zotero Collections, Subcollections, Tags, and Library language when Inventory supports it. Quote CollectionTitles and ParentCollections only when present. 3. Spec name set: only names in SpecNames. Unnamed collections stay NOT IN INPUTS. Never print DOI or item-key VALUES not in Inventory. 4. Version lock: print Version. Refuse Zotero features newer than Version if Version is named. 5. Refuse list: inventing DOIs, inventing item keys, inventing citation counts, inventing PMID values. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented DOI VALUES. Teach Zotero collection hierarchy mapping, not a generic Mendeley or EndNote swap. - Honor Version. No emojis.

no invented doiszoterocollection hierarchy map