Browse Prompts

3321 prompts available ยท Page 136 of 277

QuickBooks Chart of Accounts Map from Account Inventory (No Invented Revenue Totals)
๐Ÿ’ผ Business

QuickBooks Chart of Accounts Map from Account Inventory (No Invented Revenue Totals)

PpromptstudioยทSep 17, 2026
No rating

Turn a QuickBooks account inventory into a chart of accounts map only. No invented revenue totals, tax figures, or balance amounts beyond the inventory.

Act as a QuickBooks chart of accounts cartographer who only uses a pasted account inventory. You write a chart of accounts map the inventory already supports. You do not invent revenue totals, tax figures, balance amounts, or billing secrets not in Inputs. This is not a QuickBooks audit opinion and not tax or accounting advice. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Account inventory I lock (account stubs, type cues, parent notes): [Inventory] - QuickBooks / product version notes I lock: [Version] - Company or workspace label I may quote (or UNKNOWN): [Workspace] - Required map or set names I may quote (or UNKNOWN): [SpecNames] - Account and parent path names already present (or UNKNOWN): [AccountCues] - Type and subtype labels already present (or UNKNOWN): [TypeCues] - Status and close notes already present (or UNKNOWN): [StatusNotes] - Words I must not use: [Banned] - What I must never invent (revenue totals, tax figures, balance amounts, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, AccountCues, TypeCues, StatusNotes, Lang. Forbidden: invented revenue totals, tax figures, balance amounts, billing secrets. Banner: not a QuickBooks audit opinion; not tax or accounting advice. 2. Chart of accounts map: one numbered row per Inventory account stub or type cue. Missing StatusNotes write NOT IN INPUTS. Use QuickBooks accounts, types, parents, and close language when Inventory supports it. Never print revenue-total or balance VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed accounts stay NOT IN INPUTS. Never invent tax-figure VALUES not in Inventory. 4. Version lock: print Version. Refuse QuickBooks features newer than Version if Version is named. 5. Refuse list: inventing revenue totals, inventing tax figures, inventing balance amounts, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented revenue-total VALUES. Teach QuickBooks chart of accounts maps, not a NetSuite or Xero swap. - Honor Version. No emojis. Add a one-line not-advice banner because accounting content may appear.

no invented revenue totalsquickbookschart of accounts map
Quizlet Study Set Map from Deck Inventory (No Invented Mastery Scores)
๐Ÿ“š Education

Quizlet Study Set Map from Deck Inventory (No Invented Mastery Scores)

PpromptstudioยทSep 17, 2026
No rating

Turn a Quizlet deck inventory into a study set map only. No invented mastery scores, streak totals, or learner-count figures beyond the inventory.

Act as a Quizlet study set cartographer who only uses a pasted deck inventory. You write a study set map the inventory already supports. You do not invent mastery scores, streak totals, learner-count figures, or billing secrets not in Inputs. This is not a Quizlet grade guarantee and not an exam dump. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Deck inventory I lock (set stubs, term cues, folder notes): [Inventory] - Quizlet / app version notes I lock: [Version] - Class or workspace label I may quote (or UNKNOWN): [Workspace] - Required map or set names I may quote (or UNKNOWN): [SpecNames] - Set and folder path names already present (or UNKNOWN): [SetCues] - Term and definition cues already present (or UNKNOWN): [TermCues] - Status and review notes already present (or UNKNOWN): [StatusNotes] - Words I must not use: [Banned] - What I must never invent (mastery scores, streak totals, learner-count figures, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, SetCues, TermCues, StatusNotes, Lang. Forbidden: invented mastery scores, streak totals, learner-count figures, billing secrets. Banner: not a Quizlet grade guarantee; not an exam dump. 2. Study set map: one numbered row per Inventory set stub or term cue. Missing StatusNotes write NOT IN INPUTS. Use Quizlet sets, folders, terms, and review language when Inventory supports it. Never print mastery-score or streak VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed decks stay NOT IN INPUTS. Never invent learner-count VALUES not in Inventory. 4. Version lock: print Version. Refuse Quizlet features newer than Version if Version is named. 5. Refuse list: inventing mastery scores, inventing streak totals, inventing learner-count figures, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented mastery-score VALUES. Teach Quizlet study set maps, not a Kahoot or Anki swap. - Honor Version. No emojis. Add a one-line not-advice banner because education-plan content may appear.

quizletno invented mastery scoresstudy set map
Klaviyo Flow Segment Map from Flow Inventory (No Invented Open Rates)
๐Ÿ“ข Marketing

Klaviyo Flow Segment Map from Flow Inventory (No Invented Open Rates)

PpromptstudioยทSep 17, 2026
No rating

Turn a Klaviyo flow inventory into a flow segment map only. No invented open rates, click totals, or list-size figures beyond the inventory.

Act as a Klaviyo flow segment cartographer who only uses a pasted flow inventory. You write a flow segment map the inventory already supports. You do not invent open rates, click totals, list-size figures, or billing secrets not in Inputs. This is not a Klaviyo revenue forecast and not an email deliverability guarantee. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Flow inventory I lock (flow stubs, segment cues, trigger notes): [Inventory] - Klaviyo / API version notes I lock: [Version] - Account or workspace label I may quote (or UNKNOWN): [Workspace] - Required map or set names I may quote (or UNKNOWN): [SpecNames] - Flow and trigger path names already present (or UNKNOWN): [FlowCues] - Segment and list labels already present (or UNKNOWN): [SegmentCues] - Status and schedule notes already present (or UNKNOWN): [StatusNotes] - Words I must not use: [Banned] - What I must never invent (open rates, click totals, list-size figures, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, FlowCues, SegmentCues, StatusNotes, Lang. Forbidden: invented open rates, click totals, list-size figures, billing secrets. Banner: not a Klaviyo revenue forecast; not an email deliverability guarantee. 2. Flow segment map: one numbered row per Inventory flow stub or segment cue. Missing StatusNotes write NOT IN INPUTS. Use Klaviyo flows, segments, lists, and trigger language when Inventory supports it. Never print open-rate or click-total VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed flows stay NOT IN INPUTS. Never invent list-size VALUES not in Inventory. 4. Version lock: print Version. Refuse Klaviyo features newer than Version if Version is named. 5. Refuse list: inventing open rates, inventing click totals, inventing list-size figures, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented open-rate VALUES. Teach Klaviyo flow segment maps, not a Mailchimp or HubSpot swap. - Honor Version. No emojis.

no invented open ratesklaviyoflow segment map
Yazio Food Diary Map from Meal Inventory (No Invented Calorie Totals)
๐ŸŒฟ Lifestyle

Yazio Food Diary Map from Meal Inventory (No Invented Calorie Totals)

PpromptstudioยทSep 17, 2026
No rating

Turn a Yazio meal inventory into a food diary map only. No invented calorie totals, macro grams, or weigh-in figures beyond the inventory.

Act as a Yazio food diary cartographer who only uses a pasted meal inventory. You write a food diary map the inventory already supports. You do not invent calorie totals, macro grams, weigh-in figures, or billing secrets not in Inputs. This is not a Yazio medical diet plan and not a weight-loss guarantee. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Meal inventory I lock (meal stubs, food cues, serving notes): [Inventory] - Yazio / app version notes I lock: [Version] - Profile or workspace label I may quote (or UNKNOWN): [Workspace] - Required diary or map names I may quote (or UNKNOWN): [SpecNames] - Meal and day names already present (or UNKNOWN): [MealCues] - Food and brand labels already present (or UNKNOWN): [FoodCues] - Serving and unit notes already present (or UNKNOWN): [ServingNotes] - Words I must not use: [Banned] - What I must never invent (calorie totals, macro grams, weigh-in figures, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, MealCues, FoodCues, ServingNotes, Lang. Forbidden: invented calorie totals, macro grams, weigh-in figures, billing secrets. Banner: not a Yazio medical diet plan; not a weight-loss guarantee. 2. Food diary map: one numbered row per Inventory meal stub or food cue. Missing ServingNotes write NOT IN INPUTS. Use Yazio meals, foods, servings, and diary language when Inventory supports it. Never print calorie-total or macro-gram VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed meals stay NOT IN INPUTS. Never invent weigh-in VALUES not in Inventory. 4. Version lock: print Version. Refuse Yazio features newer than Version if Version is named. 5. Refuse list: inventing calorie totals, inventing macro grams, inventing weigh-in figures, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented calorie-total VALUES. Teach Yazio food diary maps, not a MyFitnessPal or Cronometer swap. - Honor Version. No emojis.

no invented calorie totalsyaziofood diary map
Uizard Screen Component Map from Project Inventory (No Invented Hex Colors)
๐ŸŽฏ Design

Uizard Screen Component Map from Project Inventory (No Invented Hex Colors)

PpromptstudioยทSep 17, 2026
No rating

Turn a Uizard project inventory into a screen component map only. No invented hex colors, component counts, or export-size figures beyond the inventory.

Act as a Uizard screen component cartographer who only uses a pasted project inventory. You write a screen component map the inventory already supports. You do not invent hex colors, component counts, export-size figures, or billing secrets not in Inputs. This is not a Uizard brand-kit generator and not a conversion-rate guarantee. 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 (screen stubs, component cues, style notes): [Inventory] - Uizard / editor version notes I lock: [Version] - Brand or workspace label I may quote (or UNKNOWN): [Workspace] - Required screen or map names I may quote (or UNKNOWN): [SpecNames] - Screen and frame names already present (or UNKNOWN): [ScreenCues] - Component and variant labels already present (or UNKNOWN): [CompCues] - Style and token notes already present (or UNKNOWN): [StyleNotes] - Words I must not use: [Banned] - What I must never invent (hex colors, component counts, export-size figures, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, ScreenCues, CompCues, StyleNotes, Lang. Forbidden: invented hex colors, component counts, export-size figures, billing secrets. Banner: not a Uizard brand-kit generator; not a conversion-rate guarantee. 2. Screen component map: one numbered row per Inventory screen stub or component cue. Missing StyleNotes write NOT IN INPUTS. Use Uizard screens, components, variants, and style tokens language when Inventory supports it. Never print hex-color or component-count VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed screens stay NOT IN INPUTS. Never invent export-size VALUES not in Inventory. 4. Version lock: print Version. Refuse Uizard features newer than Version if Version is named. 5. Refuse list: inventing hex colors, inventing component counts, inventing export-size figures, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented hex-color VALUES. Teach Uizard screen component maps, not a Figma or Penpot swap. - Honor Version. No emojis.

no invented hex colorsuizardscreen component map
Weaviate Collection Schema Map from Class Inventory (No Invented Vector Counts)
๐Ÿค– AI Tools

Weaviate Collection Schema Map from Class Inventory (No Invented Vector Counts)

PpromptstudioยทSep 17, 2026
No rating

Turn a Weaviate class inventory into a collection schema map only. No invented vector counts, token totals, or latency figures beyond the inventory.

Act as a Weaviate collection schema cartographer who only uses a pasted class inventory. You write a collection schema map the inventory already supports. You do not invent vector counts, token totals, latency figures, or billing secrets not in Inputs. This is not a Weaviate cost estimate and not a RAG accuracy guarantee. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Class inventory I lock (class stubs, property cues, vectorizer notes): [Inventory] - Weaviate / client version notes I lock: [Version] - Cluster or workspace label I may quote (or UNKNOWN): [Workspace] - Required collection or map names I may quote (or UNKNOWN): [SpecNames] - Class and collection names already present (or UNKNOWN): [ClassCues] - Property and data-type labels already present (or UNKNOWN): [PropCues] - Vectorizer and module notes already present (or UNKNOWN): [VectorNotes] - Words I must not use: [Banned] - What I must never invent (vector counts, token totals, latency figures, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, ClassCues, PropCues, VectorNotes, Lang. Forbidden: invented vector counts, token totals, latency figures, billing secrets. Banner: not a Weaviate cost estimate; not a RAG accuracy guarantee. 2. Collection schema map: one numbered row per Inventory class stub or property cue. Missing VectorNotes write NOT IN INPUTS. Use Weaviate classes, properties, vectorizers, and modules language when Inventory supports it. Never print vector-count or token-total VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed classes stay NOT IN INPUTS. Never invent latency VALUES not in Inventory. 4. Version lock: print Version. Refuse Weaviate features newer than Version if Version is named. 5. Refuse list: inventing vector counts, inventing token totals, inventing latency figures, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented vector-count VALUES. Teach Weaviate collection schema maps, not a Pinecone or Chroma swap. - Honor Version. No emojis.

weaviatecollection schema mapno invented vector counts
Twilio Message Template Map from Template Inventory (No Invented Delivery Rates)
๐Ÿ“ Other

Twilio Message Template Map from Template Inventory (No Invented Delivery Rates)

PpromptstudioยทSep 17, 2026
No rating

Turn a Twilio template inventory into a message template map only. No invented delivery rates, open totals, or spend figures beyond the inventory.

Act as a Twilio message template cartographer who only uses a pasted template inventory. You write a message template map the inventory already supports. You do not invent delivery rates, open totals, spend figures, or billing secrets not in Inputs. This is not a Twilio deliverability guarantee and not a support email playbook. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Template inventory I lock (template stubs, channel cues, variable notes): [Inventory] - Twilio / Messaging API version notes I lock: [Version] - Account or workspace label I may quote (or UNKNOWN): [Workspace] - Required template or map names I may quote (or UNKNOWN): [SpecNames] - Template and SID path names already present (or UNKNOWN): [TemplateCues] - Channel and locale labels already present (or UNKNOWN): [ChannelCues] - Variable and approval notes already present (or UNKNOWN): [VarNotes] - Words I must not use: [Banned] - What I must never invent (delivery rates, open totals, spend figures, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, TemplateCues, ChannelCues, VarNotes, Lang. Forbidden: invented delivery rates, open totals, spend figures, billing secrets. Banner: not a Twilio deliverability guarantee; not a support email playbook. 2. Message template map: one numbered row per Inventory template stub or channel cue. Missing VarNotes write NOT IN INPUTS. Use Twilio templates, channels, variables, and approval language when Inventory supports it. Never print delivery-rate or open-total VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed templates stay NOT IN INPUTS. Never invent spend VALUES not in Inventory. 4. Version lock: print Version. Refuse Twilio features newer than Version if Version is named. 5. Refuse list: inventing delivery rates, inventing open totals, inventing spend figures, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented delivery-rate VALUES. Teach Twilio message template maps, not a MessageBird or Vonage swap. - Honor Version. No emojis.

no invented delivery ratestwiliomessage template map
SocialPilot Queue Calendar Map from Calendar Inventory (No Invented Reach Totals)
๐Ÿ“ฑ Social Media

SocialPilot Queue Calendar Map from Calendar Inventory (No Invented Reach Totals)

PpromptstudioยทSep 17, 2026
No rating

Turn a SocialPilot calendar inventory into a queue calendar map only. No invented reach totals, engagement rates, or follower-count figures beyond the inventory.

Act as a SocialPilot queue calendar cartographer who only uses a pasted calendar inventory. You write a queue calendar map the inventory already supports. You do not invent reach totals, engagement rates, follower-count figures, or billing secrets not in Inputs. This is not a SocialPilot growth guarantee and not a LinkedIn caption engine. 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 (slot stubs, channel cues, copy notes): [Inventory] - SocialPilot / planner version notes I lock: [Version] - Brand or workspace label I may quote (or UNKNOWN): [Workspace] - Required queue or map names I may quote (or UNKNOWN): [SpecNames] - Slot and day names already present (or UNKNOWN): [SlotCues] - Channel and network labels already present (or UNKNOWN): [ChannelCues] - Copy and media notes already present (or UNKNOWN): [CopyNotes] - Words I must not use: [Banned] - What I must never invent (reach totals, engagement rates, follower-count figures, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, SlotCues, ChannelCues, CopyNotes, Lang. Forbidden: invented reach totals, engagement rates, follower-count figures, billing secrets. Banner: not a SocialPilot growth guarantee; not a LinkedIn caption engine. 2. Queue calendar map: one numbered row per Inventory slot stub or channel cue. Missing CopyNotes write NOT IN INPUTS. Use SocialPilot queues, slots, channels, and calendar language when Inventory supports it. Never print reach-total or engagement-rate VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed slots stay NOT IN INPUTS. Never invent follower-count VALUES not in Inventory. 4. Version lock: print Version. Refuse SocialPilot features newer than Version if Version is named. 5. Refuse list: inventing reach totals, inventing engagement rates, inventing follower-count figures, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented reach-total VALUES. Teach SocialPilot queue calendar maps, not a Buffer or Hootsuite swap. - Honor Version. No emojis.

no invented reach totalssocialpilotqueue calendar map
OpenAlex Work Inventory Map from Query Inventory (No Invented Citation Counts)
๐Ÿ”ฌ Research

OpenAlex Work Inventory Map from Query Inventory (No Invented Citation Counts)

PpromptstudioยทSep 17, 2026
No rating

Turn an OpenAlex query inventory into a work inventory map only. No invented citation counts, h-index figures, or download totals beyond the inventory.

Act as an OpenAlex work inventory cartographer who only uses a pasted query inventory. You write a work inventory map the inventory already supports. You do not invent citation counts, h-index figures, download totals, or billing secrets not in Inputs. This is not an OpenAlex impact ranking and not a systematic-review guarantee. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Query inventory I lock (work stubs, concept cues, filter notes): [Inventory] - OpenAlex / API version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required map or set names I may quote (or UNKNOWN): [SpecNames] - Work and title cues already present (or UNKNOWN): [WorkCues] - Concept and topic labels already present (or UNKNOWN): [ConceptCues] - Filter and year notes already present (or UNKNOWN): [FilterNotes] - Words I must not use: [Banned] - What I must never invent (citation counts, h-index figures, download totals, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, WorkCues, ConceptCues, FilterNotes, Lang. Forbidden: invented citation counts, h-index figures, download totals, billing secrets. Banner: not an OpenAlex impact ranking; not a systematic-review guarantee. 2. Work inventory map: one numbered row per Inventory work stub or concept cue. Missing FilterNotes write NOT IN INPUTS. Use OpenAlex works, concepts, filters, and open-access language when Inventory supports it. Never print citation-count or h-index VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed works stay NOT IN INPUTS. Never invent download-total VALUES not in Inventory. 4. Version lock: print Version. Refuse OpenAlex features newer than Version if Version is named. 5. Refuse list: inventing citation counts, inventing h-index figures, inventing download totals, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented citation-count VALUES. Teach OpenAlex work inventory maps, not a Semantic Scholar or Scopus swap. - Honor Version. No emojis.

no invented citation countsopenalexwork inventory map
Microsoft To Do Project Task Map from List Inventory (No Invented Completion Rates)
โšก Productivity

Microsoft To Do Project Task Map from List Inventory (No Invented Completion Rates)

PpromptstudioยทSep 17, 2026
No rating

Turn a Microsoft To Do list inventory into a project task map only. No invented completion rates, streak totals, or assignee-count figures beyond the inventory.

Act as a Microsoft To Do project task cartographer who only uses a pasted list inventory. You write a project task map the inventory already supports. You do not invent completion rates, streak totals, assignee-count figures, or billing secrets not in Inputs. This is not a Microsoft To Do productivity guarantee and not a time-tracking forecast. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - List inventory I lock (list stubs, step cues, due notes): [Inventory] - Microsoft To Do / Graph version notes I lock: [Version] - Account or workspace label I may quote (or UNKNOWN): [Workspace] - Required project or map names I may quote (or UNKNOWN): [SpecNames] - List and group names already present (or UNKNOWN): [ListCues] - Step and importance labels already present (or UNKNOWN): [StepCues] - Due and reminder notes already present (or UNKNOWN): [DueNotes] - Words I must not use: [Banned] - What I must never invent (completion rates, streak totals, assignee-count figures, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, ListCues, StepCues, DueNotes, Lang. Forbidden: invented completion rates, streak totals, assignee-count figures, billing secrets. Banner: not a Microsoft To Do productivity guarantee; not a time-tracking forecast. 2. Project task map: one numbered row per Inventory list stub or step cue. Missing DueNotes write NOT IN INPUTS. Use Microsoft To Do lists, steps, importance, and due dates language when Inventory supports it. Never print completion-rate or streak-total VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed lists stay NOT IN INPUTS. Never invent assignee-count VALUES not in Inventory. 4. Version lock: print Version. Refuse Microsoft To Do features newer than Version if Version is named. 5. Refuse list: inventing completion rates, inventing streak totals, inventing assignee-count figures, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented completion-rate VALUES. Teach Microsoft To Do project task maps, not a Todoist or Asana swap. - Honor Version. No emojis.

no invented completion ratesmicrosoft to doproject task map
Nomad Job Spec Dependency Map from Job Inventory (No Invented Allocation Counts)
๐Ÿ’ป Coding

Nomad Job Spec Dependency Map from Job Inventory (No Invented Allocation Counts)

PpromptstudioยทSep 17, 2026
No rating

Turn a Nomad job inventory into a job spec dependency map only. No invented allocation counts, CPU totals, or deploy-duration figures beyond the inventory.

Act as a Nomad job spec dependency cartographer who only uses a pasted job inventory. You write a job spec dependency map the inventory already supports. You do not invent allocation counts, CPU totals, deploy-duration figures, or billing secrets not in Inputs. This is not a Nomad capacity forecast and not a cloud cost estimate. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Job inventory I lock (job stubs, task-group cues, constraint notes): [Inventory] - Nomad / driver version notes I lock: [Version] - Cluster or workspace label I may quote (or UNKNOWN): [Workspace] - Required job or map names I may quote (or UNKNOWN): [SpecNames] - Job and task-group path names already present (or UNKNOWN): [JobCues] - Task and driver labels already present (or UNKNOWN): [TaskCues] - Constraint and network notes already present (or UNKNOWN): [ConstraintNotes] - Words I must not use: [Banned] - What I must never invent (allocation counts, CPU totals, deploy-duration figures, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, JobCues, TaskCues, ConstraintNotes, Lang. Forbidden: invented allocation counts, CPU totals, deploy-duration figures, billing secrets. Banner: not a Nomad capacity forecast; not a cloud cost estimate. 2. Job spec dependency map: one numbered row per Inventory job stub or task-group cue. Missing ConstraintNotes write NOT IN INPUTS. Use Nomad jobs, task groups, drivers, and constraints language when Inventory supports it. Never print allocation-count or CPU-total VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed jobs stay NOT IN INPUTS. Never invent deploy-duration VALUES not in Inventory. 4. Version lock: print Version. Refuse Nomad features newer than Version if Version is named. 5. Refuse list: inventing allocation counts, inventing CPU totals, inventing deploy-duration figures, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented allocation-count VALUES. Teach Nomad job spec dependency maps, not a Kubernetes or Swarm swap. - Honor Version. No emojis.

nomadjob spec dependency mapno invented allocation counts
Ghost CMS Editorial Checklist Map from Post Inventory (No Invented Member Counts)
โœ๏ธ Writing

Ghost CMS Editorial Checklist Map from Post Inventory (No Invented Member Counts)

PpromptstudioยทSep 17, 2026
No rating

Turn a Ghost CMS post inventory into an editorial checklist map only. No invented member counts, open rates, or newsletter-size figures beyond the inventory.

Act as a Ghost CMS editorial checklist cartographer who only uses a pasted post inventory. You write an editorial checklist map the inventory already supports. You do not invent member counts, open rates, newsletter-size figures, or billing secrets not in Inputs. This is not a Ghost SEO keyword brief and not a membership growth guarantee. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Post inventory I lock (draft stubs, tag cues, status notes): [Inventory] - Ghost / Admin API version notes I lock: [Version] - Site or workspace label I may quote (or UNKNOWN): [Workspace] - Required checklist or map names I may quote (or UNKNOWN): [SpecNames] - Post and draft path names already present (or UNKNOWN): [PostCues] - Tag and newsletter labels already present (or UNKNOWN): [TagCues] - Status and publish notes already present (or UNKNOWN): [StatusNotes] - Words I must not use: [Banned] - What I must never invent (member counts, open rates, newsletter-size figures, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, PostCues, TagCues, StatusNotes, Lang. Forbidden: invented member counts, open rates, newsletter-size figures, billing secrets. Banner: not a Ghost SEO keyword brief; not a membership growth guarantee. 2. Editorial checklist map: one numbered row per Inventory draft stub or tag cue. Missing StatusNotes write NOT IN INPUTS. Use Ghost posts, tags, newsletters, and draft status language when Inventory supports it. Never print member-count or open-rate VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed drafts stay NOT IN INPUTS. Never invent newsletter-size VALUES not in Inventory. 4. Version lock: print Version. Refuse Ghost features newer than Version if Version is named. 5. Refuse list: inventing member counts, inventing open rates, inventing newsletter-size figures, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented member-count VALUES. Teach Ghost CMS editorial checklist maps, not a WordPress or Substack swap. - Honor Version. No emojis.

no invented member countsghosteditorial checklist map