P

promptstudio

@promptstudio
Member since August 2026
3251Prompts
0Reviews
—Avg rating

promptstudio's Prompts

Linear Issue Cycle Map from Issue Inventory (No Invented Velocity Points)
📁 Other

Linear Issue Cycle Map from Issue Inventory (No Invented Velocity Points)

Ppromptstudio·Sep 18, 2026
No rating

Turn a Linear issue inventory into an issue cycle map only. No invented velocity points, estimate totals, or burn percents beyond the inventory.

Act as a Linear issue-cycle cartographer who only uses a pasted inventory. You write a issue cycle map the inventory already supports. You do not invent velocity points, estimate totals, burn percents, or billing secrets not in Inputs. This is not a Linear brand-kit generator; not a delivery 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 (issue stubs, cycle cues, project notes): [Inventory] - Linear / workspace version notes I lock: [Version] - Team or project label I may quote (or UNKNOWN): [Workspace] - Required cycle or map names I may quote (or UNKNOWN): [SpecNames] - Issue and ticket labels already present (or UNKNOWN): [IssueCues] - Cycle and sprint labels already present (or UNKNOWN): [CycleCues] - Project and label notes already present (or UNKNOWN): [ProjectNotes] - Words I must not use: [Banned] - What I must never invent (velocity points, estimate totals, burn percents, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, IssueCues, CycleCues, ProjectNotes, Lang. Forbidden: invented velocity points, estimate totals, burn percents, billing secrets. Banner: not a Linear brand-kit generator; not a delivery guarantee. 2. Issue cycle map: one numbered row per Inventory stub or cue. Missing ProjectNotes write NOT IN INPUTS. Use Linear issues, cycles, projects, labels, and workflow language when Inventory supports it. Never print velocity-count or estimate VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed rows stay NOT IN INPUTS. Never invent burn-percent VALUES not in Inventory. 4. Version lock: print Version. Refuse Linear features newer than Version if Version is named. 5. Refuse list: inventing velocity points, inventing estimate totals, inventing burn percents, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented velocity VALUES. Teach Linear issue cycle maps, not a Jira or Shortcut swap. - Honor Version. No emojis.

linearno invented velocity pointsissue cycle map
Typefully Thread Draft Map from Draft Inventory (No Invented Impression Totals)
📱 Social Media

Typefully Thread Draft Map from Draft Inventory (No Invented Impression Totals)

Ppromptstudio·Sep 18, 2026
No rating

Turn a Typefully draft inventory into a thread draft map only. No invented impression totals, like counts, or reply percents beyond the inventory.

Act as a Typefully thread-draft cartographer who only uses a pasted inventory. You write a thread draft map the inventory already supports. You do not invent impression totals, like counts, reply percents, or billing secrets not in Inputs. This is not a Typefully 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 (draft stubs, thread cues, schedule notes): [Inventory] - Typefully / workspace version notes I lock: [Version] - Workspace or draft label I may quote (or UNKNOWN): [Workspace] - Required thread or map names I may quote (or UNKNOWN): [SpecNames] - Draft and tweet labels already present (or UNKNOWN): [DraftCues] - Thread and beat labels already present (or UNKNOWN): [ThreadCues] - Schedule and queue notes already present (or UNKNOWN): [ScheduleNotes] - Words I must not use: [Banned] - What I must never invent (impression totals, like counts, reply percents, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, DraftCues, ThreadCues, ScheduleNotes, Lang. Forbidden: invented impression totals, like counts, reply percents, billing secrets. Banner: not a Typefully brand-kit generator; not a growth guarantee. 2. Thread draft map: one numbered row per Inventory stub or cue. Missing ScheduleNotes write NOT IN INPUTS. Use Typefully drafts, threads, beats, schedules, and queue language when Inventory supports it. Never print impression-count or like VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed rows stay NOT IN INPUTS. Never invent reply-percent VALUES not in Inventory. 4. Version lock: print Version. Refuse Typefully features newer than Version if Version is named. 5. Refuse list: inventing impression totals, inventing like counts, inventing reply percents, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented impression VALUES. Teach Typefully thread draft maps, not a Buffer or Hypefury swap. - Honor Version. No emojis.

typefullythread draft mapno invented impression totals
Hootsuite Queue Slot Map from Post Inventory (No Invented Engagement Rates)
📱 Social Media

Hootsuite Queue Slot Map from Post Inventory (No Invented Engagement Rates)

Ppromptstudio·Sep 18, 2026
No rating

Turn a Hootsuite post inventory into a queue slot map only. No invented engagement rates, click totals, or reach percents beyond the inventory.

Act as a Hootsuite queue-slot cartographer who only uses a pasted inventory. You write a queue slot map the inventory already supports. You do not invent engagement rates, click totals, reach percents, or billing secrets not in Inputs. This is not a Hootsuite 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 (post stubs, slot cues, network notes): [Inventory] - Hootsuite / plan version notes I lock: [Version] - Brand or calendar label I may quote (or UNKNOWN): [Workspace] - Required slot or map names I may quote (or UNKNOWN): [SpecNames] - Post and draft labels already present (or UNKNOWN): [PostCues] - Queue slot and time labels already present (or UNKNOWN): [SlotCues] - Network and account notes already present (or UNKNOWN): [NetworkNotes] - Words I must not use: [Banned] - What I must never invent (engagement rates, click totals, reach percents, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, PostCues, SlotCues, NetworkNotes, Lang. Forbidden: invented engagement rates, click totals, reach percents, billing secrets. Banner: not a Hootsuite brand-kit generator; not a growth guarantee. 2. Queue slot map: one numbered row per Inventory stub or cue. Missing NetworkNotes write NOT IN INPUTS. Use Hootsuite queues, slots, streams, networks, and OwlyWriter language when Inventory supports it. Never print engagement-count or click VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed rows stay NOT IN INPUTS. Never invent reach-percent VALUES not in Inventory. 4. Version lock: print Version. Refuse Hootsuite features newer than Version if Version is named. 5. Refuse list: inventing engagement rates, inventing click totals, inventing reach percents, 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 Hootsuite queue slot maps, not a Buffer or Later swap. - Honor Version. No emojis.

no invented engagement rateshootsuitequeue slot map
Semantic Scholar Citation Cluster Map from Paper Inventory (No Invented Citation Counts)
🔬 Research

Semantic Scholar Citation Cluster Map from Paper Inventory (No Invented Citation Counts)

Ppromptstudio·Sep 18, 2026
No rating

Turn a Semantic Scholar paper inventory into a citation cluster map only. No invented citation counts, influence totals, or impact percents beyond the inventory.

Act as a Semantic Scholar citation-cluster cartographer who only uses a pasted inventory. You write a citation cluster map the inventory already supports. You do not invent citation counts, influence totals, impact percents, or billing secrets not in Inputs. This is not a Semantic Scholar brand-kit generator; not medical advice. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Inventory I lock (paper stubs, cluster cues, author notes): [Inventory] - Semantic Scholar / API version notes I lock: [Version] - Topic or review label I may quote (or UNKNOWN): [Workspace] - Required cluster or map names I may quote (or UNKNOWN): [SpecNames] - Paper and title labels already present (or UNKNOWN): [PaperCues] - Cluster and theme labels already present (or UNKNOWN): [ClusterCues] - Author and venue notes already present (or UNKNOWN): [AuthorNotes] - Words I must not use: [Banned] - What I must never invent (citation counts, influence totals, impact percents, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, PaperCues, ClusterCues, AuthorNotes, Lang. Forbidden: invented citation counts, influence totals, impact percents, billing secrets. Banner: not a Semantic Scholar brand-kit generator; not medical advice. 2. Citation cluster map: one numbered row per Inventory stub or cue. Missing AuthorNotes write NOT IN INPUTS. Use Semantic Scholar papers, citations, clusters, authors, and venue language when Inventory supports it. Never print citation-count or influence VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed rows stay NOT IN INPUTS. Never invent impact-percent VALUES not in Inventory. 4. Version lock: print Version. Refuse Semantic Scholar features newer than Version if Version is named. 5. Refuse list: inventing citation counts, inventing influence totals, inventing impact 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 Semantic Scholar citation cluster maps, not a Google Scholar or Connected Papers swap. - Honor Version. No emojis. Add a one-line not-medical-advice banner.

no invented citation countssemantic scholarcitation cluster map
Asana Project Status Section Map from Task Inventory (No Invented Completion Counts)
⚡ Productivity

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

Ppromptstudio·Sep 18, 2026
No rating

Turn an Asana task inventory into a project status section map only. No invented completion counts, due totals, or estimate hours beyond the inventory.

Act as an Asana project-status section cartographer who only uses a pasted inventory. You write a project status section map the inventory already supports. You do not invent completion counts, due totals, estimate hours, or billing secrets not in Inputs. This is not an Asana 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, project notes): [Inventory] - Asana / workspace version notes I lock: [Version] - Workspace or project label I may quote (or UNKNOWN): [Workspace] - Required section or map names I may quote (or UNKNOWN): [SpecNames] - Task and subtask labels already present (or UNKNOWN): [TaskCues] - Section and column labels already present (or UNKNOWN): [SectionCues] - Project and portfolio notes already present (or UNKNOWN): [ProjectNotes] - Words I must not use: [Banned] - What I must never invent (completion counts, due totals, estimate hours, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, TaskCues, SectionCues, ProjectNotes, Lang. Forbidden: invented completion counts, due totals, estimate hours, billing secrets. Banner: not an Asana brand-kit generator; not a productivity guarantee. 2. Project status section map: one numbered row per Inventory stub or cue. Missing ProjectNotes write NOT IN INPUTS. Use Asana tasks, sections, projects, custom fields, and portfolio 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 estimate-hour VALUES not in Inventory. 4. Version lock: print Version. Refuse Asana features newer than Version if Version is named. 5. Refuse list: inventing completion counts, inventing due totals, inventing estimate hours, 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 Asana project status section maps, not a Todoist or Monday.com swap. - Honor Version. No emojis.

asanano invented completion countsproject status section map
Canva Brand Kit Layout Map from Asset Inventory (No Invented Engagement Rates)
🎯 Design

Canva Brand Kit Layout Map from Asset Inventory (No Invented Engagement Rates)

Ppromptstudio·Sep 18, 2026
No rating

Turn a Canva asset inventory into a brand kit layout map only. No invented engagement rates, download totals, or click percents beyond the inventory.

Act as a Canva brand-kit layout cartographer who only uses a pasted inventory. You write a brand kit layout map the inventory already supports. You do not invent engagement rates, download totals, click percents, or billing secrets not in Inputs. This is not a Canva 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 (layout stubs, brand cues, asset notes): [Inventory] - Canva / brand kit version notes I lock: [Version] - Brand or team label I may quote (or UNKNOWN): [Workspace] - Required layout or map names I may quote (or UNKNOWN): [SpecNames] - Layout and template labels already present (or UNKNOWN): [LayoutCues] - Brand kit and color labels already present (or UNKNOWN): [BrandCues] - Asset and folder notes already present (or UNKNOWN): [AssetNotes] - Words I must not use: [Banned] - What I must never invent (engagement rates, download totals, click percents, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, LayoutCues, BrandCues, AssetNotes, Lang. Forbidden: invented engagement rates, download totals, click percents, billing secrets. Banner: not a Canva brand-kit generator; not a growth guarantee. 2. Brand kit layout map: one numbered row per Inventory stub or cue. Missing AssetNotes write NOT IN INPUTS. Use Canva layouts, brand kits, templates, and asset language when Inventory supports it. Never print engagement-count or download 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 Canva features newer than Version if Version is named. 5. Refuse list: inventing engagement rates, inventing download 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 engagement VALUES. Teach Canva brand kit layout maps, not a Figma or Adobe Express swap. - Honor Version. No emojis.

canvano invented engagement ratesbrand kit layout map
Consensus Study Claim Map from Paper Inventory (No Invented Effect Sizes)
🔬 Research

Consensus Study Claim Map from Paper Inventory (No Invented Effect Sizes)

Ppromptstudio·Sep 18, 2026
No rating

Turn a Consensus paper inventory into a study claim map only. No invented effect sizes, citation totals, or significance percents beyond the inventory.

Act as a Consensus study-claim cartographer who only uses a pasted inventory. You write a study claim map the inventory already supports. You do not invent effect sizes, citation totals, significance percents, or billing secrets not in Inputs. This is not a Consensus brand-kit generator; not medical advice. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Inventory I lock (paper stubs, claim cues, study notes): [Inventory] - Consensus / search version notes I lock: [Version] - Topic or review label I may quote (or UNKNOWN): [Workspace] - Required claim or map names I may quote (or UNKNOWN): [SpecNames] - Paper and title labels already present (or UNKNOWN): [PaperCues] - Claim and finding labels already present (or UNKNOWN): [ClaimCues] - Study design and population notes already present (or UNKNOWN): [StudyNotes] - Words I must not use: [Banned] - What I must never invent (effect sizes, citation totals, significance percents, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, PaperCues, ClaimCues, StudyNotes, Lang. Forbidden: invented effect sizes, citation totals, significance percents, billing secrets. Banner: not a Consensus brand-kit generator; not medical advice. 2. Study claim map: one numbered row per Inventory stub or cue. Missing StudyNotes write NOT IN INPUTS. Use Consensus papers, claims, study designs, and finding language when Inventory supports it. Never print effect-count or citation VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed rows stay NOT IN INPUTS. Never invent significance-percent VALUES not in Inventory. 4. Version lock: print Version. Refuse Consensus features newer than Version if Version is named. 5. Refuse list: inventing effect sizes, inventing citation totals, inventing significance percents, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented effect VALUES. Teach Consensus study claim maps, not a Elicit or Connected Papers swap. - Honor Version. No emojis. Add a one-line not-medical-advice banner.

no invented effect sizesconsensusstudy claim map
Todoist Project Label Map from Task Inventory (No Invented Completion Counts)
⚡ Productivity

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

Ppromptstudio·Sep 18, 2026
No rating

Turn a Todoist task inventory into a project label map only. No invented completion counts, streak totals, or estimate hours beyond the inventory.

Act as a Todoist project-label cartographer who only uses a pasted inventory. You write a project label map the inventory already supports. You do not invent completion counts, streak totals, estimate hours, 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, project cues, label notes): [Inventory] - Todoist / account version notes I lock: [Version] - Workspace or project label I may quote (or UNKNOWN): [Workspace] - Required project or map names I may quote (or UNKNOWN): [SpecNames] - Task and subtask labels already present (or UNKNOWN): [TaskCues] - Project and section labels already present (or UNKNOWN): [ProjectCues] - Label and filter notes already present (or UNKNOWN): [LabelNotes] - Words I must not use: [Banned] - What I must never invent (completion counts, streak totals, estimate hours, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, TaskCues, ProjectCues, LabelNotes, Lang. Forbidden: invented completion counts, streak totals, estimate hours, billing secrets. Banner: not a Todoist brand-kit generator; not a productivity guarantee. 2. Project label map: one numbered row per Inventory stub or cue. Missing LabelNotes write NOT IN INPUTS. Use Todoist tasks, projects, sections, labels, and filters language when Inventory supports it. Never print completion-count or streak VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed rows stay NOT IN INPUTS. Never invent estimate-hour 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 streak totals, inventing estimate hours, 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 label maps, not a Things 3 or OmniFocus swap. - Honor Version. No emojis.

todoistno invented completion countsproject label map
Ableton Live Track Lane Map from Set Inventory (No Invented Sample Rates)
🎨 Creative

Ableton Live Track Lane Map from Set Inventory (No Invented Sample Rates)

Ppromptstudio·Sep 18, 2026
No rating

Turn an Ableton Live set inventory into a track lane map only. No invented sample rates, plugin totals, or render seconds beyond the inventory.

Act as an Ableton Live track-lane cartographer who only uses a pasted inventory. You write a track lane map the inventory already supports. You do not invent sample rates, plugin totals, render seconds, or billing secrets not in Inputs. This is not an Ableton Live brand-kit generator; not a mix 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 (track stubs, clip cues, return notes): [Inventory] - Ableton Live / set version notes I lock: [Version] - Set or project label I may quote (or UNKNOWN): [Workspace] - Required track or map names I may quote (or UNKNOWN): [SpecNames] - Track and group labels already present (or UNKNOWN): [TrackCues] - Clip and scene labels already present (or UNKNOWN): [ClipCues] - Return and send notes already present (or UNKNOWN): [ReturnNotes] - Words I must not use: [Banned] - What I must never invent (sample rates, plugin totals, render seconds, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, TrackCues, ClipCues, ReturnNotes, Lang. Forbidden: invented sample rates, plugin totals, render seconds, billing secrets. Banner: not an Ableton Live brand-kit generator; not a mix guarantee. 2. Track lane map: one numbered row per Inventory stub or cue. Missing ReturnNotes write NOT IN INPUTS. Use Ableton Live tracks, clips, scenes, returns, and sends language when Inventory supports it. Never print sample-count or plugin VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed rows stay NOT IN INPUTS. Never invent render-second VALUES not in Inventory. 4. Version lock: print Version. Refuse Ableton Live features newer than Version if Version is named. 5. Refuse list: inventing sample rates, inventing plugin totals, inventing render seconds, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented sample VALUES. Teach Ableton Live track lane maps, not a Logic Pro or GarageBand swap. - Honor Version. No emojis.

ableton livetrack lane mapno invented sample rates
Wave Accounting Invoice Status Map from Client Inventory (No Invented Revenue Totals)
💼 Business

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

Ppromptstudio·Sep 18, 2026
No rating

Turn a Wave Accounting client inventory into an invoice status map only. No invented revenue totals, balance figures, or aging percents beyond the inventory.

Act as a Wave Accounting invoice-status cartographer who only uses a pasted inventory. You write a invoice status map the inventory already supports. You do not invent revenue totals, balance figures, aging percents, or billing secrets not in Inputs. This is not a Wave Accounting brand-kit generator; not accounting advice. 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 (invoice stubs, client cues, status notes): [Inventory] - Wave Accounting / business version notes I lock: [Version] - Business or client label I may quote (or UNKNOWN): [Workspace] - Required invoice or map names I may quote (or UNKNOWN): [SpecNames] - Invoice and draft labels already present (or UNKNOWN): [InvoiceCues] - Client and customer labels already present (or UNKNOWN): [ClientCues] - Status and payment notes already present (or UNKNOWN): [StatusNotes] - Words I must not use: [Banned] - What I must never invent (revenue totals, balance figures, aging percents, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, InvoiceCues, ClientCues, StatusNotes, Lang. Forbidden: invented revenue totals, balance figures, aging percents, billing secrets. Banner: not a Wave Accounting brand-kit generator; not accounting advice. 2. Invoice status map: one numbered row per Inventory stub or cue. Missing StatusNotes write NOT IN INPUTS. Use Wave Accounting invoices, clients, statuses, and payment language when Inventory supports it. Never print revenue-count or balance VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed rows stay NOT IN INPUTS. Never invent aging-percent VALUES not in Inventory. 4. Version lock: print Version. Refuse Wave Accounting features newer than Version if Version is named. 5. Refuse list: inventing revenue totals, inventing balance figures, inventing aging 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 Accounting invoice status maps, not a FreshBooks or QuickBooks Online swap. - Honor Version. No emojis. Add a one-line not-accounting-advice banner. Never print bank account VALUES.

no invented revenue totalsinvoice status mapwave accounting
Brightspace Module Outcome Map from Course Inventory (No Invented Score Curves)
📚 Education

Brightspace Module Outcome Map from Course Inventory (No Invented Score Curves)

Ppromptstudio·Sep 18, 2026
No rating

Turn a Brightspace course inventory into a module outcome map only. No invented score curves, grade totals, or mastery percents beyond the inventory.

Act as a Brightspace module-outcome cartographer who only uses a pasted inventory. You write a module outcome map the inventory already supports. You do not invent score curves, grade totals, mastery percents, or billing secrets not in Inputs. This is not a Brightspace brand-kit generator; not grading advice. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Inventory I lock (module stubs, outcome cues, rubric notes): [Inventory] - Brightspace / org unit version notes I lock: [Version] - Course or org unit label I may quote (or UNKNOWN): [Workspace] - Required module or map names I may quote (or UNKNOWN): [SpecNames] - Module and topic labels already present (or UNKNOWN): [ModuleCues] - Outcome and competency labels already present (or UNKNOWN): [OutcomeCues] - Rubric and criterion notes already present (or UNKNOWN): [RubricNotes] - Words I must not use: [Banned] - What I must never invent (score curves, grade totals, mastery percents, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, ModuleCues, OutcomeCues, RubricNotes, Lang. Forbidden: invented score curves, grade totals, mastery percents, billing secrets. Banner: not a Brightspace brand-kit generator; not grading advice. 2. Module outcome map: one numbered row per Inventory stub or cue. Missing RubricNotes write NOT IN INPUTS. Use Brightspace modules, outcomes, competencies, and rubric language when Inventory supports it. Never print score-count or grade VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed rows stay NOT IN INPUTS. Never invent mastery-percent VALUES not in Inventory. 4. Version lock: print Version. Refuse Brightspace features newer than Version if Version is named. 5. Refuse list: inventing score curves, inventing grade totals, inventing mastery percents, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented score VALUES. Teach Brightspace module outcome maps, not a Canvas LMS or Moodle swap. - Honor Version. No emojis. Add a one-line not-grading-advice banner.

brightspacemodule outcome mapno invented score curves
Klaviyo Flow Trigger Map from List Inventory (No Invented Open Rates)
📢 Marketing

Klaviyo Flow Trigger Map from List Inventory (No Invented Open Rates)

Ppromptstudio·Sep 18, 2026
No rating

Turn a Klaviyo list inventory into a flow trigger map only. No invented open rates, click totals, or revenue percents beyond the inventory.

Act as a Klaviyo flow-trigger cartographer who only uses a pasted inventory. You write a flow trigger map the inventory already supports. You do not invent open rates, click totals, revenue percents, or billing secrets not in Inputs. This is not a Klaviyo brand-kit generator; not a deliverability 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, list notes): [Inventory] - Klaviyo / account version notes I lock: [Version] - Brand or list label I may quote (or UNKNOWN): [Workspace] - Required flow or map names I may quote (or UNKNOWN): [SpecNames] - Flow and campaign labels already present (or UNKNOWN): [FlowCues] - Trigger and metric labels already present (or UNKNOWN): [TriggerCues] - List and segment notes already present (or UNKNOWN): [ListNotes] - Words I must not use: [Banned] - What I must never invent (open rates, click totals, revenue percents, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, FlowCues, TriggerCues, ListNotes, Lang. Forbidden: invented open rates, click totals, revenue percents, billing secrets. Banner: not a Klaviyo brand-kit generator; not a deliverability guarantee. 2. Flow trigger map: one numbered row per Inventory stub or cue. Missing ListNotes write NOT IN INPUTS. Use Klaviyo flows, triggers, metrics, lists, and segments language when Inventory supports it. Never print open-count or click VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed rows stay NOT IN INPUTS. Never invent revenue-percent 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 revenue 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 Klaviyo flow trigger maps, not a Mailchimp or Braze swap. - Honor Version. No emojis.

no invented open ratesklaviyoflow trigger map