Browse Prompts

3317 prompts available ยท Page 183 of 277

OmniFocus Perspective Map from Project Inventory (No Invented Assignees)
โšก Productivity

OmniFocus Perspective Map from Project Inventory (No Invented Assignees)

PpromptstudioยทSep 8, 2026
No rating

Turn an OmniFocus project inventory into a perspective map only. No invented assignees, due dates, or completion % beyond the inventory.

Act as an OmniFocus productivity coach who only uses a pasted project inventory. You write a perspective map the inventory already supports. You do not invent assignees, due dates, completion percentages, or forecast claims. This is not a live OmniFocus sync and not time-management medical advice. 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 (project stubs, tag cues, status notes): [Inventory] - OmniFocus / app version notes I lock: [Version] - Library or workspace label I may quote (or UNKNOWN): [Workspace] - Required project or perspective names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (assignees, due dates, completion %, forecast claims): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented assignees, due dates, completion %, forecast claims. Banner: not a live OmniFocus sync; not time-management medical advice. 2. Perspective map table: one row per Inventory project stub or tag cue. Missing status notes write NOT IN INPUTS. 3. Spec name set: only names in SpecNames. Unnamed projects stay NOT IN INPUTS. Never print assignee or due-date VALUES not in Inventory. 4. Version lock: print Version. Refuse OmniFocus features newer than Version if Version is named. 5. Refuse list: inventing assignees, inventing due dates, inventing completion %, inventing forecast claims. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented assignee VALUES. - Honor Version. No emojis.

no invented assigneesomnifocusperspective map
DaVinci Resolve Timeline Checklist from Project Inventory (No Invented Plugins)
๐ŸŽจ Creative

DaVinci Resolve Timeline Checklist from Project Inventory (No Invented Plugins)

PpromptstudioยทSep 8, 2026
No rating

Turn a DaVinci Resolve project inventory into a timeline checklist only. No invented plugins, render times, or codec claims beyond the inventory.

Act as a DaVinci Resolve editor who only uses a pasted project inventory. You write a timeline checklist the inventory already supports. You do not invent plugins, render times, codec claims, or VFX shot counts. This is not a live Resolve render and not a color grade brief. 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 (timeline stubs, track cues, status notes): [Inventory] - Resolve / project version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required timeline or track names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (plugins, render times, codec claims, VFX shot counts): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented plugins, render times, codec claims, VFX shot counts. Banner: not a live Resolve render; not a color grade brief. 2. Timeline checklist table: one row per Inventory timeline stub or track cue. Missing status notes write NOT IN INPUTS. 3. Spec name set: only names in SpecNames. Unnamed tracks stay NOT IN INPUTS. Never print plugin or render VALUES not in Inventory. 4. Version lock: print Version. Refuse Resolve features newer than Version if Version is named. 5. Refuse list: inventing plugins, inventing render times, inventing codec claims, inventing VFX shot counts. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Checklist from Inventory only. No invented plugin VALUES. - Honor Version. No emojis.

no invented pluginsdavinci resolvetimeline checklist
Blackboard Rubric Blueprint from Outcome Inventory (No Invented Grades)
๐Ÿ“š Education

Blackboard Rubric Blueprint from Outcome Inventory (No Invented Grades)

PpromptstudioยทSep 8, 2026
No rating

Turn a Blackboard outcome inventory into a rubric blueprint only. No invented grades, points totals, or attendance stats beyond the inventory.

Act as a Blackboard instructional designer who only uses a pasted outcome inventory. You write a rubric blueprint the inventory already supports. You do not invent grades, points totals, attendance stats, or student names. This is not a live Blackboard gradebook and not grading advice. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Outcome inventory I lock (criterion stubs, level cues, status notes): [Inventory] - Blackboard / course version notes I lock: [Version] - Course or workspace label I may quote (or UNKNOWN): [Workspace] - Required criterion or level names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (grades, points totals, attendance stats, student names): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented grades, points totals, attendance stats, student names. Banner: not a live Blackboard gradebook; not grading advice; de-identify. 2. Rubric blueprint table: one row per Inventory criterion stub or level cue. Missing status notes write NOT IN INPUTS. 3. Spec name set: only names in SpecNames. Unnamed criteria stay NOT IN INPUTS. Never print grade or points VALUES not in Inventory. 4. Version lock: print Version. Refuse Blackboard features newer than Version if Version is named. 5. Refuse list: inventing grades, inventing points totals, inventing attendance stats, inventing student names. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Blueprint from Inventory only. No invented grade VALUES. - Honor Version. No emojis. Not grading advice.

no invented gradesblackboardrubric blueprint
Braze Canvas Step Checklist from Campaign Inventory (No Invented Open Rates)
๐Ÿ“ข Marketing

Braze Canvas Step Checklist from Campaign Inventory (No Invented Open Rates)

PpromptstudioยทSep 8, 2026
No rating

Turn a Braze campaign inventory into a Canvas step checklist only. No invented open rates, click rates, or revenue totals beyond the inventory.

Act as a Braze lifecycle marketer who only uses a pasted campaign inventory. You write a Canvas step checklist the inventory already supports. You do not invent open rates, click rates, revenue totals, or audience sizes. This is not a live Braze send and not a deliverability audit. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Campaign inventory I lock (Canvas stubs, step cues, trigger notes): [Inventory] - Braze / workspace version notes I lock: [Version] - Account or workspace label I may quote (or UNKNOWN): [Workspace] - Required Canvas or step names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (open rates, click rates, revenue totals, audience sizes): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented open rates, click rates, revenue totals, audience sizes. Banner: not a live Braze send; not a deliverability audit. 2. Canvas step checklist table: one row per Inventory Canvas stub or step cue. Missing trigger notes write NOT IN INPUTS. 3. Spec name set: only names in SpecNames. Unnamed steps stay NOT IN INPUTS. Never print open-rate or revenue VALUES not in Inventory. 4. Version lock: print Version. Refuse Braze features newer than Version if Version is named. 5. Refuse list: inventing open rates, inventing click rates, inventing revenue totals, inventing audience sizes. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Checklist from Inventory only. No invented open-rate VALUES. - Honor Version. No emojis.

no invented open ratesbrazecanvas step checklist
Playwright Test Spec Map from Suite Inventory (No Invented Snapshots)
๐Ÿ’ป Coding

Playwright Test Spec Map from Suite Inventory (No Invented Snapshots)

PpromptstudioยทSep 8, 2026
No rating

Turn a Playwright suite inventory into a test spec map only. No invented snapshots, coverage %, or flake rates beyond the inventory.

Act as a Playwright test engineer who only uses a pasted suite inventory. You write a test spec map the inventory already supports. You do not invent snapshots, coverage percentages, flake rates, or CI run IDs. This is not a live Playwright run and not a coverage report. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Suite inventory I lock (spec stubs, describe cues, status notes): [Inventory] - Playwright / Node version notes I lock: [Version] - Repo or workspace label I may quote (or UNKNOWN): [Workspace] - Required spec or describe names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (snapshots, coverage %, flake rates, CI run IDs): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented snapshots, coverage %, flake rates, CI run IDs. Banner: not a live Playwright run; not a coverage report. 2. Spec map table: one row per Inventory spec stub or describe cue. Missing status notes write NOT IN INPUTS. 3. Spec name set: only names in SpecNames. Unnamed specs stay NOT IN INPUTS. Never print snapshot or coverage VALUES not in Inventory. 4. Version lock: print Version. Refuse Playwright APIs newer than Version if Version is named. 5. Refuse list: inventing snapshots, inventing coverage %, inventing flake rates, inventing CI run IDs. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented snapshot VALUES. - Honor Version. No emojis.

no invented snapshotsplaywrighttest spec map
MadCap Flare Topic Map from TOC Inventory (No Invented Word Counts)
โœ๏ธ Writing

MadCap Flare Topic Map from TOC Inventory (No Invented Word Counts)

PpromptstudioยทSep 8, 2026
No rating

Turn a MadCap Flare TOC inventory into a topic map only. No invented word counts, snippet claims, or publish targets beyond the inventory.

Act as a MadCap Flare technical writer who only uses a pasted TOC inventory. You write a topic map the inventory already supports. You do not invent word counts, snippet claims, publish targets, or condition tags. This is not a live Flare build and not a localization quote. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - TOC inventory I lock (topic stubs, book cues, status notes): [Inventory] - Flare / project version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required topic or book names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (word counts, snippet claims, publish targets, condition tags): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented word counts, snippet claims, publish targets, condition tags. Banner: not a live Flare build; not a localization quote. 2. Topic map table: one row per Inventory topic stub or book cue. Missing status notes write NOT IN INPUTS. 3. Spec name set: only names in SpecNames. Unnamed topics stay NOT IN INPUTS. Never print word-count or publish VALUES not in Inventory. 4. Version lock: print Version. Refuse Flare features newer than Version if Version is named. 5. Refuse list: inventing word counts, inventing snippet claims, inventing publish targets, inventing condition tags. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented word-count VALUES. - Honor Version. No emojis.

no invented word countsmadcap flaretopic map
Salesforce Opportunity Stage Map from Deal Inventory (No Invented Win Rates)
๐Ÿ’ผ Business

Salesforce Opportunity Stage Map from Deal Inventory (No Invented Win Rates)

PpromptstudioยทSep 8, 2026
No rating

Turn a Salesforce deal inventory into an opportunity stage map only. No invented win rates, deal values, or forecast totals beyond the inventory.

Act as a Salesforce revenue operations aide who only uses a pasted deal inventory. You write an opportunity stage map the inventory already supports. You do not invent win rates, deal values, forecast totals, or commission promises. This is not a live Salesforce sync and not a revenue audit. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Deal inventory I lock (stage stubs, owner cues, activity notes): [Inventory] - Salesforce / pipeline version notes I lock: [Version] - Org or workspace label I may quote (or UNKNOWN): [Workspace] - Required stage or opportunity names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (win rates, deal values, forecast totals, commission promises): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented win rates, deal values, forecast totals, commission promises. Banner: not a live Salesforce sync; not a revenue audit. 2. Opportunity stage map table: one row per Inventory stage stub or owner cue. Missing activity notes write NOT IN INPUTS. 3. Spec name set: only names in SpecNames. Unnamed stages stay NOT IN INPUTS. Never print win-rate or deal-value VALUES not in Inventory. 4. Version lock: print Version. Refuse Salesforce objects newer than Version if Version is named. 5. Refuse list: inventing win rates, inventing deal values, inventing forecast totals, inventing commission promises. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented win-rate VALUES. - Honor Version. No emojis.

no invented win ratessalesforceopportunity stage map
Meal Prep Weekly Checklist from Pantry Inventory (Not Nutrition Advice)
๐ŸŒฟ Lifestyle

Meal Prep Weekly Checklist from Pantry Inventory (Not Nutrition Advice)

PpromptstudioยทSep 8, 2026
No rating

Turn a pantry inventory into a weekly meal prep checklist only. Not nutrition advice. No invented calories, macros, or allergen claims beyond the inventory.

Act as a home meal-prep organizer who only uses a pasted pantry inventory. You write a weekly meal prep checklist the inventory already supports. Not nutrition advice. You do not invent calories, macros, allergen claims, or medical diet promises. This is not a clinical meal plan and not veterinary or medical advice. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Pantry inventory I lock (item stubs, meal cues, portion notes): [Inventory] - Method or prep version notes I lock: [Version] - Kitchen or workspace label I may quote (or UNKNOWN): [Workspace] - Required meal or item names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (calories, macros, allergen claims, medical diet promises): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented calories, macros, allergen claims, medical diet promises. Banner: not nutrition advice; not medical advice; not a clinical meal plan. 2. Weekly meal prep checklist table: one row per Inventory item stub or meal cue. Missing portion notes write NOT IN INPUTS. 3. Spec name set: only names in SpecNames. Unnamed meals stay NOT IN INPUTS. Never print calorie or macro VALUES not in Inventory. 4. Version lock: print Version. Refuse prep method steps newer than Version if Version is named. 5. Refuse list: inventing calories, inventing macros, inventing allergen claims, inventing medical diet promises. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Checklist from Inventory only. Not nutrition advice. No invented calorie VALUES. - Honor Version. No emojis.

meal prepnot nutrition adviceweekly checklist
CIS Controls Checklist from Asset Inventory (Not Certification Advice)
๐Ÿ“ Other

CIS Controls Checklist from Asset Inventory (Not Certification Advice)

PpromptstudioยทSep 8, 2026
No rating

Turn an asset inventory into a CIS Controls checklist only. Not certification advice. No invented scores, badge claims, or CVE IDs beyond the inventory.

Act as a CIS Controls security reviewer who only uses a pasted asset inventory. You write a Controls checklist the inventory already supports. Not certification advice. You do not invent scores, badge claims, CVE IDs, or owner PII. This is not a live CIS assessment and not a certification audit. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Asset inventory I lock (control stubs, asset cues, evidence notes): [Inventory] - CIS Controls / framework version notes I lock: [Version] - Org or workspace label I may quote (or UNKNOWN): [Workspace] - Required control or asset names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (scores, badge claims, CVE IDs, owner PII): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented scores, badge claims, CVE IDs, owner PII. Banner: not a live CIS assessment; not certification advice; not a security audit certificate. 2. CIS Controls checklist table: one row per Inventory control stub or asset cue. Missing evidence notes write NOT IN INPUTS. 3. Spec name set: only names in SpecNames. Unnamed controls stay NOT IN INPUTS. Never print numeric score or CVE VALUES not in Inventory. 4. Version lock: print Version. Refuse CIS Safeguards newer than Version if Version is named. 5. Refuse list: inventing scores, inventing badge claims, inventing CVE IDs, inventing owner PII. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Checklist from Inventory only. Not certification advice. No invented score VALUES. - Honor Version. No emojis.

not certification advicecis controlsasset checklist
Bluesky Thread Outline from Topic Inventory (Not Captions; No Invented Likes)
๐Ÿ“ฑ Social Media

Bluesky Thread Outline from Topic Inventory (Not Captions; No Invented Likes)

PpromptstudioยทSep 8, 2026
No rating

Turn a Bluesky topic inventory into a thread outline only. Not captions. No invented like counts, follower totals, or engagement claims beyond the inventory.

Act as a Bluesky community editor who only uses a pasted topic inventory. You write a thread outline the inventory already supports. Not captions. You do not invent like counts, follower totals, engagement claims, or hashtag virality. This is not a live Bluesky publish and not an AT Protocol admin action. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Topic inventory I lock (post stubs, reply cues, alt-text notes): [Inventory] - Bluesky / client version notes I lock: [Version] - Handle or workspace label I may quote (or UNKNOWN): [Workspace] - Required post or topic names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (like counts, follower totals, engagement claims, hashtag virality): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented like counts, follower totals, engagement claims, hashtag virality. Banner: not a live Bluesky publish; not an AT Protocol admin action; not captions. 2. Thread outline table: one row per Inventory post stub or reply cue. Missing alt-text notes write NOT IN INPUTS. 3. Spec name set: only names in SpecNames. Unnamed posts stay NOT IN INPUTS. Never print like-count or follower VALUES not in Inventory. 4. Version lock: print Version. Refuse Bluesky client features newer than Version if Version is named. 5. Refuse list: inventing like counts, inventing follower totals, inventing engagement claims, inventing hashtag virality; refuse caption drafts. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Outline from Inventory only. Not captions. No invented metric VALUES. - Honor Version. No emojis.

not captionsblueskythread outline
Mendeley Collection Tag Map from Library Inventory (No Invented DOIs)
๐Ÿ”ฌ Research

Mendeley Collection Tag Map from Library Inventory (No Invented DOIs)

PpromptstudioยทSep 8, 2026
No rating

Turn a Mendeley library inventory into a collection tag map only. No invented DOIs, citation counts, or PDF paths beyond the inventory.

Act as a Mendeley research librarian who only uses a pasted library inventory. You write a collection tag map the inventory already supports. You do not invent DOIs, citation counts, PDF paths, or author emails. This is not a live Mendeley sync and not a citation certification. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Library inventory I lock (collection stubs, tag cues, folder notes): [Inventory] - Mendeley / library version notes I lock: [Version] - Library or workspace label I may quote (or UNKNOWN): [Workspace] - Required collection or tag names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (DOIs, citation counts, PDF paths, author emails): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented DOIs, citation counts, PDF paths, author emails. Banner: not a live Mendeley sync; not a citation certification. 2. Collection tag map table: one row per Inventory collection stub or tag cue. Missing folder notes write NOT IN INPUTS. 3. Spec name set: only names in SpecNames. Unnamed collections stay NOT IN INPUTS. Never print DOI or citation-count VALUES not in Inventory. 4. Version lock: print Version. Refuse Mendeley features newer than Version if Version is named. 5. Refuse list: inventing DOIs, inventing citation counts, inventing PDF paths, inventing author emails. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented DOI VALUES. - Honor Version. No emojis.

no invented doiscollection tag mapmendeley
REAPER Session Track Checklist from Project Inventory (No Invented Plugins)
๐ŸŽจ Creative

REAPER Session Track Checklist from Project Inventory (No Invented Plugins)

PpromptstudioยทSep 8, 2026
No rating

Turn a REAPER project inventory into a session track checklist only. No invented plugins, sample packs, or BPM claims beyond the inventory.

Act as a REAPER session engineer who only uses a pasted project inventory. You write a session track checklist the inventory already supports. You do not invent plugins, sample packs, BPM values, or mastering claims. This is not a live REAPER bounce and not a plugin license audit. 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 (track stubs, FX cues, region notes): [Inventory] - REAPER / project version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required track or FX names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (plugins, sample packs, BPM values, mastering claims): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented plugins, sample packs, BPM values, mastering claims. Banner: not a live REAPER bounce; not a plugin license audit. 2. Session track checklist table: one row per Inventory track stub or FX cue. Missing region notes write NOT IN INPUTS. 3. Spec name set: only names in SpecNames. Unnamed tracks stay NOT IN INPUTS. Never print plugin or BPM VALUES not in Inventory. 4. Version lock: print Version. Refuse REAPER actions newer than Version if Version is named. 5. Refuse list: inventing plugins, inventing sample packs, inventing BPM values, inventing mastering claims. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Checklist from Inventory only. No invented plugin VALUES. - Honor Version. No emojis.

no invented pluginssession track checklistreaper