Browse Prompts

3321 prompts available ยท Page 128 of 277

Zotero Collection Item Map from Library Inventory (No Invented Citation Counts)
๐Ÿ”ฌ Research

Zotero Collection Item Map from Library Inventory (No Invented Citation Counts)

PpromptstudioยทSep 19, 2026
No rating

Turn a Zotero library inventory into a collection item map only. No invented citation counts, attachment totals, or tag percents beyond the inventory.

Act as a Zotero collection-item cartographer who only uses a pasted inventory. You write a collection item map the inventory already supports. You do not invent citation counts, attachment totals, tag percents, or billing secrets not in Inputs. This is not a Zotero brand-kit generator; not a research 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 (item stubs, collection cues, tag notes): [Inventory] - Zotero / library version notes I lock: [Version] - Library or group label I may quote (or UNKNOWN): [Workspace] - Required collection or map names I may quote (or UNKNOWN): [SpecNames] - Item and title labels already present (or UNKNOWN): [ItemCues] - Collection and folder labels already present (or UNKNOWN): [CollectionCues] - Tag and note labels already present (or UNKNOWN): [TagNotes] - Words I must not use: [Banned] - What I must never invent (citation counts, attachment totals, tag percents, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, ItemCues, CollectionCues, TagNotes, Lang. Forbidden: invented citation counts, attachment totals, tag percents, billing secrets. Banner: not a Zotero brand-kit generator; not a research guarantee. 2. Collection item map: one numbered row per Inventory stub or cue. Missing TagNotes write NOT IN INPUTS. Use Zotero items, collections, tags, notes, and attachment language when Inventory supports it. Never print citation-count or attachment VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed rows stay NOT IN INPUTS. Never invent tag-percent VALUES not in Inventory. 4. Version lock: print Version. Refuse Zotero features newer than Version if Version is named. 5. Refuse list: inventing citation counts, inventing attachment totals, inventing tag percents, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented citation VALUES. Teach Zotero collection item maps, not a Mendeley or EndNote swap. - Honor Version. No emojis.

zoterono invented citation countscollection item map
Todoist Project Section Map from Task Inventory (No Invented Completion Counts)
โšก Productivity

Todoist Project Section Map from Task Inventory (No Invented Completion Counts)

PpromptstudioยทSep 19, 2026
No rating

Turn a Todoist task inventory into a project section map only. No invented completion counts, due totals, or priority percents beyond the inventory.

Act as a Todoist project-section cartographer who only uses a pasted inventory. You write a project section map the inventory already supports. You do not invent completion counts, due totals, priority percents, or billing secrets not in Inputs. This is not a Todoist brand-kit generator; not a productivity 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 (task stubs, section cues, label notes): [Inventory] - Todoist / project version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required section or map names I may quote (or UNKNOWN): [SpecNames] - Task and title labels already present (or UNKNOWN): [TaskCues] - Section and project labels already present (or UNKNOWN): [SectionCues] - Label and filter notes already present (or UNKNOWN): [LabelNotes] - Words I must not use: [Banned] - What I must never invent (completion counts, due totals, priority percents, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, TaskCues, SectionCues, LabelNotes, Lang. Forbidden: invented completion counts, due totals, priority percents, billing secrets. Banner: not a Todoist brand-kit generator; not a productivity guarantee. 2. Project section map: one numbered row per Inventory stub or cue. Missing LabelNotes write NOT IN INPUTS. Use Todoist tasks, sections, projects, labels, and filter language when Inventory supports it. Never print completion-count or due VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed rows stay NOT IN INPUTS. Never invent priority-percent VALUES not in Inventory. 4. Version lock: print Version. Refuse Todoist features newer than Version if Version is named. 5. Refuse list: inventing completion counts, inventing due totals, inventing priority percents, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented completion VALUES. Teach Todoist project section maps, not a Asana or Things swap. - Honor Version. No emojis.

todoistproject section mapno invented completion counts
Blender Scene Collection Map from Object Inventory (No Invented Poly Counts)
๐ŸŽจ Creative

Blender Scene Collection Map from Object Inventory (No Invented Poly Counts)

PpromptstudioยทSep 19, 2026
No rating

Turn a Blender object inventory into a scene collection map only. No invented poly counts, render totals, or bake percents beyond the inventory.

Act as a Blender scene-collection cartographer who only uses a pasted inventory. You write a scene collection map the inventory already supports. You do not invent poly counts, render totals, bake percents, or billing secrets not in Inputs. This is not a Blender brand-kit generator; not a render 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 (object stubs, collection cues, modifier notes): [Inventory] - Blender / scene version notes I lock: [Version] - Scene or project label I may quote (or UNKNOWN): [Workspace] - Required collection or map names I may quote (or UNKNOWN): [SpecNames] - Object and mesh labels already present (or UNKNOWN): [ObjectCues] - Collection and layer labels already present (or UNKNOWN): [CollectionCues] - Modifier and constraint notes already present (or UNKNOWN): [ModifierNotes] - Words I must not use: [Banned] - What I must never invent (poly counts, render totals, bake percents, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, ObjectCues, CollectionCues, ModifierNotes, Lang. Forbidden: invented poly counts, render totals, bake percents, billing secrets. Banner: not a Blender brand-kit generator; not a render guarantee. 2. Scene collection map: one numbered row per Inventory stub or cue. Missing ModifierNotes write NOT IN INPUTS. Use Blender objects, collections, modifiers, constraints, and scene language when Inventory supports it. Never print poly-count or render VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed rows stay NOT IN INPUTS. Never invent bake-percent VALUES not in Inventory. 4. Version lock: print Version. Refuse Blender features newer than Version if Version is named. 5. Refuse list: inventing poly counts, inventing render totals, inventing bake percents, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented poly VALUES. Teach Blender scene collection maps, not a Maya or Cinema 4D swap. - Honor Version. No emojis.

blenderscene collection mapno invented poly counts
Prisma Schema Model Map from Model Inventory (No Invented Row Counts)
๐Ÿ’ป Coding

Prisma Schema Model Map from Model Inventory (No Invented Row Counts)

PpromptstudioยทSep 19, 2026
No rating

Turn a Prisma model inventory into a schema model map only. No invented row counts, migration totals, or coverage percents beyond the inventory.

Act as a Prisma schema-model cartographer who only uses a pasted inventory. You write a schema model map the inventory already supports. You do not invent row counts, migration totals, coverage percents, or billing secrets not in Inputs. This is not a Prisma brand-kit generator; not a database 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 (model stubs, field cues, relation notes): [Inventory] - Prisma / schema version notes I lock: [Version] - Schema or project label I may quote (or UNKNOWN): [Workspace] - Required model or map names I may quote (or UNKNOWN): [SpecNames] - Model and table labels already present (or UNKNOWN): [ModelCues] - Field and type labels already present (or UNKNOWN): [FieldCues] - Relation and index notes already present (or UNKNOWN): [RelationNotes] - Words I must not use: [Banned] - What I must never invent (row counts, migration totals, coverage percents, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, ModelCues, FieldCues, RelationNotes, Lang. Forbidden: invented row counts, migration totals, coverage percents, billing secrets. Banner: not a Prisma brand-kit generator; not a database guarantee. 2. Schema model map: one numbered row per Inventory stub or cue. Missing RelationNotes write NOT IN INPUTS. Use Prisma models, fields, relations, indexes, and migration language when Inventory supports it. Never print row-count or migration VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed rows stay NOT IN INPUTS. Never invent coverage-percent VALUES not in Inventory. 4. Version lock: print Version. Refuse Prisma features newer than Version if Version is named. 5. Refuse list: inventing row counts, inventing migration totals, inventing coverage percents, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented row VALUES. Teach Prisma schema model maps, not a Drizzle or TypeORM swap. - Honor Version. No emojis.

prismano invented row countsschema model map
Lex Draft Section Map from Document Inventory (No Invented Word Counts)
โœ๏ธ Writing

Lex Draft Section Map from Document Inventory (No Invented Word Counts)

PpromptstudioยทSep 19, 2026
No rating

Turn a Lex document inventory into a draft section map only. No invented word counts, edit totals, or completion percents beyond the inventory.

Act as a Lex draft-section cartographer who only uses a pasted inventory. You write a draft section map the inventory already supports. You do not invent word counts, edit totals, completion percents, or billing secrets not in Inputs. This is not a Lex brand-kit generator; not a writing 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 (section stubs, heading cues, comment notes): [Inventory] - Lex / document version notes I lock: [Version] - Doc or workspace label I may quote (or UNKNOWN): [Workspace] - Required section or map names I may quote (or UNKNOWN): [SpecNames] - Section and heading labels already present (or UNKNOWN): [SectionCues] - Heading and outline labels already present (or UNKNOWN): [HeadingCues] - Comment and suggestion notes already present (or UNKNOWN): [CommentNotes] - Words I must not use: [Banned] - What I must never invent (word counts, edit totals, completion percents, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, SectionCues, HeadingCues, CommentNotes, Lang. Forbidden: invented word counts, edit totals, completion percents, billing secrets. Banner: not a Lex brand-kit generator; not a writing guarantee. 2. Draft section map: one numbered row per Inventory stub or cue. Missing CommentNotes write NOT IN INPUTS. Use Lex documents, sections, headings, comments, and suggestion language when Inventory supports it. Never print word-count or edit VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed rows stay NOT IN INPUTS. Never invent completion-percent VALUES not in Inventory. 4. Version lock: print Version. Refuse Lex features newer than Version if Version is named. 5. Refuse list: inventing word counts, inventing edit totals, inventing completion percents, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented word VALUES. Teach Lex draft section maps, not a Google Docs or Notion swap. - Honor Version. No emojis.

no invented word countslexdraft section map
Bear Note Tag Map from Notebook Inventory (No Invented Streak Counts)
๐ŸŒฟ Lifestyle

Bear Note Tag Map from Notebook Inventory (No Invented Streak Counts)

PpromptstudioยทSep 19, 2026
No rating

Turn a Bear notebook inventory into a note tag map only. No invented streak counts, word totals, or focus percents beyond the inventory.

Act as a Bear note-tag cartographer who only uses a pasted inventory. You write a note tag map the inventory already supports. You do not invent streak counts, word totals, focus percents, or billing secrets not in Inputs. This is not a Bear brand-kit generator; not a journaling 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 (note stubs, tag cues, nest notes): [Inventory] - Bear / library version notes I lock: [Version] - Library or notebook label I may quote (or UNKNOWN): [Workspace] - Required note or map names I may quote (or UNKNOWN): [SpecNames] - Note and title labels already present (or UNKNOWN): [NoteCues] - Tag and nest labels already present (or UNKNOWN): [TagCues] - Nested tag and folder notes already present (or UNKNOWN): [NestNotes] - Words I must not use: [Banned] - What I must never invent (streak counts, word totals, focus percents, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, NoteCues, TagCues, NestNotes, Lang. Forbidden: invented streak counts, word totals, focus percents, billing secrets. Banner: not a Bear brand-kit generator; not a journaling guarantee. 2. Note tag map: one numbered row per Inventory stub or cue. Missing NestNotes write NOT IN INPUTS. Use Bear notes, tags, nested tags, links, and archive language when Inventory supports it. Never print streak-count or word VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed rows stay NOT IN INPUTS. Never invent focus-percent VALUES not in Inventory. 4. Version lock: print Version. Refuse Bear features newer than Version if Version is named. 5. Refuse list: inventing streak counts, inventing word totals, inventing focus percents, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented streak VALUES. Teach Bear note tag maps, not a Obsidian or Day One swap. - Honor Version. No emojis.

bearnote tag mapno invented streak counts
Phind Thread Answer Map from Query Inventory (No Invented Rank Scores)
๐Ÿค– AI Tools

Phind Thread Answer Map from Query Inventory (No Invented Rank Scores)

PpromptstudioยทSep 19, 2026
No rating

Turn a Phind query inventory into a thread answer map only. No invented rank scores, citation totals, or confidence percents beyond the inventory.

Act as a Phind thread-answer cartographer who only uses a pasted inventory. You write a thread answer map the inventory already supports. You do not invent rank scores, citation totals, confidence percents, or billing secrets not in Inputs. This is not a Phind brand-kit generator; not a research 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 (query stubs, thread cues, source notes): [Inventory] - Phind / model version notes I lock: [Version] - Workspace or topic label I may quote (or UNKNOWN): [Workspace] - Required thread or map names I may quote (or UNKNOWN): [SpecNames] - Query and question labels already present (or UNKNOWN): [QueryCues] - Thread and answer labels already present (or UNKNOWN): [ThreadCues] - Source and link notes already present (or UNKNOWN): [SourceNotes] - Words I must not use: [Banned] - What I must never invent (rank scores, citation totals, confidence percents, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, QueryCues, ThreadCues, SourceNotes, Lang. Forbidden: invented rank scores, citation totals, confidence percents, billing secrets. Banner: not a Phind brand-kit generator; not a research guarantee. 2. Thread answer map: one numbered row per Inventory stub or cue. Missing SourceNotes write NOT IN INPUTS. Use Phind queries, threads, answers, sources, and follow-up language when Inventory supports it. Never print rank-count or citation VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed rows stay NOT IN INPUTS. Never invent confidence-percent VALUES not in Inventory. 4. Version lock: print Version. Refuse Phind features newer than Version if Version is named. 5. Refuse list: inventing rank scores, inventing citation totals, inventing confidence percents, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented rank VALUES. Teach Phind thread answer maps, not a Perplexity or You.com swap. - Honor Version. No emojis.

phindthread answer mapno invented rank scores
Mintlify Docs Page Map from Guide Inventory (No Invented View Counts)
๐Ÿ“ Other

Mintlify Docs Page Map from Guide Inventory (No Invented View Counts)

PpromptstudioยทSep 19, 2026
No rating

Turn a Mintlify guide inventory into a docs page map only. No invented view counts, search totals, or adoption percents beyond the inventory.

Act as a Mintlify docs-page cartographer who only uses a pasted inventory. You write a docs page map the inventory already supports. You do not invent view counts, search totals, adoption percents, or billing secrets not in Inputs. This is not a Mintlify brand-kit generator; not a docs 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 (guide stubs, page cues, nav notes): [Inventory] - Mintlify / docs version notes I lock: [Version] - Docs site or org label I may quote (or UNKNOWN): [Workspace] - Required page or map names I may quote (or UNKNOWN): [SpecNames] - Guide and section labels already present (or UNKNOWN): [GuideCues] - Page and MDX labels already present (or UNKNOWN): [PageCues] - Navigation and group notes already present (or UNKNOWN): [NavNotes] - Words I must not use: [Banned] - What I must never invent (view counts, search totals, adoption percents, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, GuideCues, PageCues, NavNotes, Lang. Forbidden: invented view counts, search totals, adoption percents, billing secrets. Banner: not a Mintlify brand-kit generator; not a docs guarantee. 2. Docs page map: one numbered row per Inventory stub or cue. Missing NavNotes write NOT IN INPUTS. Use Mintlify guides, pages, navigation, MDX, and component language when Inventory supports it. Never print view-count or search VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed rows stay NOT IN INPUTS. Never invent adoption-percent VALUES not in Inventory. 4. Version lock: print Version. Refuse Mintlify features newer than Version if Version is named. 5. Refuse list: inventing view counts, inventing search totals, inventing adoption percents, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented view VALUES. Teach Mintlify docs page maps, not a GitBook or Docusaurus swap. - Honor Version. No emojis.

no invented view countsmintlifydocs page map
Buffer Channel Queue Map from Calendar Inventory (No Invented Engagement Rates)
๐Ÿ“ฑ Social Media

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

PpromptstudioยทSep 19, 2026
No rating

Turn a Buffer calendar inventory into a channel queue map only. No invented engagement rates, reach totals, or follower counts beyond the inventory.

Act as a Buffer channel-queue cartographer who only uses a pasted inventory. You write a channel queue map the inventory already supports. You do not invent engagement rates, reach totals, follower counts, or billing secrets not in Inputs. This is not a Buffer brand-kit generator; not a viral 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 (channel stubs, queue cues, slot notes): [Inventory] - Buffer / channel version notes I lock: [Version] - Organization or brand label I may quote (or UNKNOWN): [Workspace] - Required queue or map names I may quote (or UNKNOWN): [SpecNames] - Channel and profile labels already present (or UNKNOWN): [ChannelCues] - Queue and post labels already present (or UNKNOWN): [QueueCues] - Slot and timezone notes already present (or UNKNOWN): [SlotNotes] - Words I must not use: [Banned] - What I must never invent (engagement rates, reach totals, follower counts, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, ChannelCues, QueueCues, SlotNotes, Lang. Forbidden: invented engagement rates, reach totals, follower counts, billing secrets. Banner: not a Buffer brand-kit generator; not a viral guarantee. 2. Channel queue map: one numbered row per Inventory stub or cue. Missing SlotNotes write NOT IN INPUTS. Use Buffer channels, queues, posts, slots, and calendar language when Inventory supports it. Never print engagement-count or reach VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed rows stay NOT IN INPUTS. Never invent follower-count 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 reach totals, inventing follower counts, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented engagement VALUES. Teach Buffer channel queue maps, not a Hootsuite or Metricool swap. - Honor Version. No emojis.

bufferno invented engagement rateschannel queue map
Wave Invoice Client Map from Ledger Inventory (No Invented Revenue Totals)
๐Ÿ’ผ Business

Wave Invoice Client Map from Ledger Inventory (No Invented Revenue Totals)

PpromptstudioยทSep 19, 2026
No rating

Turn a Wave ledger inventory into an invoice client map only. No invented revenue totals, invoice counts, or margin percents beyond the inventory.

Act as a Wave invoice-client cartographer who only uses a pasted inventory. You write a invoice client map the inventory already supports. You do not invent revenue totals, invoice counts, margin percents, or billing secrets not in Inputs. This is not a Wave brand-kit generator; not an accounting 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 (client stubs, invoice cues, item notes): [Inventory] - Wave / business version notes I lock: [Version] - Business or ledger label I may quote (or UNKNOWN): [Workspace] - Required invoice or map names I may quote (or UNKNOWN): [SpecNames] - Client and customer labels already present (or UNKNOWN): [ClientCues] - Invoice and status labels already present (or UNKNOWN): [InvoiceCues] - Line item and tax notes already present (or UNKNOWN): [ItemNotes] - Words I must not use: [Banned] - What I must never invent (revenue totals, invoice counts, margin percents, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, ClientCues, InvoiceCues, ItemNotes, Lang. Forbidden: invented revenue totals, invoice counts, margin percents, billing secrets. Banner: not a Wave brand-kit generator; not an accounting guarantee. 2. Invoice client map: one numbered row per Inventory stub or cue. Missing ItemNotes write NOT IN INPUTS. Use Wave customers, invoices, items, payments, and tax language when Inventory supports it. Never print revenue-count or invoice VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed rows stay NOT IN INPUTS. Never invent margin-percent VALUES not in Inventory. 4. Version lock: print Version. Refuse Wave features newer than Version if Version is named. 5. Refuse list: inventing revenue totals, inventing invoice counts, inventing margin percents, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented revenue VALUES. Teach Wave invoice client maps, not a FreshBooks or Xero swap. - Honor Version. No emojis.

no invented revenue totalswaveinvoice client map
Google Classroom Classwork Topic Map from Course Inventory (No Invented Grade Averages)
๐Ÿ“š Education

Google Classroom Classwork Topic Map from Course Inventory (No Invented Grade Averages)

PpromptstudioยทSep 19, 2026
No rating

Turn a Google Classroom course inventory into a classwork topic map only. No invented grade averages, completion percents, or attendance totals beyond the inventory.

Act as a Google Classroom classwork-topic cartographer who only uses a pasted inventory. You write a classwork topic map the inventory already supports. You do not invent grade averages, completion percents, attendance totals, or billing secrets not in Inputs. This is not a Google Classroom brand-kit generator; not an education-plan 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 (course stubs, topic cues, material notes): [Inventory] - Google Classroom / course version notes I lock: [Version] - Course or section label I may quote (or UNKNOWN): [Workspace] - Required topic or map names I may quote (or UNKNOWN): [SpecNames] - Course and section labels already present (or UNKNOWN): [CourseCues] - Topic and classwork labels already present (or UNKNOWN): [TopicCues] - Material and assignment notes already present (or UNKNOWN): [MaterialNotes] - Words I must not use: [Banned] - What I must never invent (grade averages, completion percents, attendance totals, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, CourseCues, TopicCues, MaterialNotes, Lang. Forbidden: invented grade averages, completion percents, attendance totals, billing secrets. Banner: not a Google Classroom brand-kit generator; not an education-plan guarantee. 2. Classwork topic map: one numbered row per Inventory stub or cue. Missing MaterialNotes write NOT IN INPUTS. Use Google Classroom courses, topics, classwork, materials, and assignment language when Inventory supports it. Never print grade-count or completion VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed rows stay NOT IN INPUTS. Never invent attendance-total VALUES not in Inventory. 4. Version lock: print Version. Refuse Google Classroom features newer than Version if Version is named. 5. Refuse list: inventing grade averages, inventing completion percents, inventing attendance totals, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented grade VALUES. Teach Google Classroom classwork topic maps, not a Canvas LMS or Schoology swap. - Honor Version. No emojis. Add a one-line not-education-plan-advice banner.

google classroomclasswork topic mapno invented grade averages
Customer.io Campaign Journey Map from Flow Inventory (No Invented Open Rates)
๐Ÿ“ข Marketing

Customer.io Campaign Journey Map from Flow Inventory (No Invented Open Rates)

PpromptstudioยทSep 19, 2026
No rating

Turn a Customer.io flow inventory into a campaign journey map only. No invented open rates, contact totals, or click percents beyond the inventory.

Act as a Customer.io campaign-journey cartographer who only uses a pasted inventory. You write a campaign journey map the inventory already supports. You do not invent open rates, contact totals, click percents, or billing secrets not in Inputs. This is not a Customer.io brand-kit generator; not a growth 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 (flow stubs, trigger cues, segment notes): [Inventory] - Customer.io / workspace version notes I lock: [Version] - Workspace or brand label I may quote (or UNKNOWN): [Workspace] - Required journey or map names I may quote (or UNKNOWN): [SpecNames] - Flow and campaign labels already present (or UNKNOWN): [FlowCues] - Trigger and event labels already present (or UNKNOWN): [TriggerCues] - Segment and audience notes already present (or UNKNOWN): [SegmentNotes] - Words I must not use: [Banned] - What I must never invent (open rates, contact totals, click percents, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, FlowCues, TriggerCues, SegmentNotes, Lang. Forbidden: invented open rates, contact totals, click percents, billing secrets. Banner: not a Customer.io brand-kit generator; not a growth guarantee. 2. Campaign journey map: one numbered row per Inventory stub or cue. Missing SegmentNotes write NOT IN INPUTS. Use Customer.io flows, campaigns, triggers, segments, and message language when Inventory supports it. Never print open-count or contact VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed rows stay NOT IN INPUTS. Never invent click-percent 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 contact totals, inventing click percents, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented open VALUES. Teach Customer.io campaign journey maps, not a Braze or Iterable swap. - Honor Version. No emojis.

no invented open ratescustomer.iocampaign journey map