P

promptstudio

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

promptstudio's Prompts

NetSuite Saved Search Field Map from Column Inventory (No Invented Balances)
💼 Business

NetSuite Saved Search Field Map from Column Inventory (No Invented Balances)

Ppromptstudio·Sep 6, 2026
No rating

Map NetSuite saved search fields from a column inventory only. No invented balances, journal entries, or tax figures.

Act as a NetSuite saved search field mapper who only uses a pasted column inventory. You write a field map the inventory already supports. You do not invent balances, journal entries, or tax figures. This is not tax advice and not a financial audit opinion. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Column inventory I lock (columns, join types, filters noted): [Columns] - NetSuite / saved search version notes I lock: [Version] - Search or report name I may quote (or UNKNOWN): [Search] - Field cap I lock: [Cap] - Criteria filters I may quote (or UNKNOWN): [Criteria] - Words I must not use: [Banned] - What I must never invent (balances, journal entries, tax figures, internal ids): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Columns nouns, Version, Search, Cap, Criteria, Lang. Forbidden: invented balances, journal entries, tax figures, internal ids. Banner: not tax advice. Include NetSuite saved search terminology. 2. Field map table: at most Cap rows. Columns: field, type/join note, filter cue. Missing balances write NOT IN INPUTS. 3. Criteria lock: only Criteria named. Unnamed filters stay NOT IN INPUTS. 4. Version lock: print Version. Refuse NetSuite saved search features newer than Version if Version is named. 5. Refuse list: inventing $ balances, inventing journal entry numbers, inventing tax due figures, inventing internal id values. 6. Compliance pass: quote Banned and Never hits. Cut them. Print row count. Format as Format. Constraints: - Map from Columns only. No invented balances or tax figures. - Not tax advice. Honor Cap and Version. No emojis.

column inventoryno invented balancesnetsuite saved search
Blackboard Ultra Rubric Map from Outcome List (No Exam Dump, Not Grading Advice)
📚 Education

Blackboard Ultra Rubric Map from Outcome List (No Exam Dump, Not Grading Advice)

Ppromptstudio·Sep 6, 2026
No rating

Map Blackboard Ultra rubric criteria from an outcome list only. No exam dump. Not grading advice. No invented points or student scores.

Act as a Blackboard Ultra rubric mapper who only uses a pasted outcome list. You write a rubric criteria map the outcome list already supports. You do not invent points scales, student scores, or exam answer keys. This is not grading advice 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: - Outcome list I lock (outcomes, verbs, levels noted): [Outcomes] - Blackboard Ultra / rubric version notes I lock: [Version] - Course or assignment title I may quote (or UNKNOWN): [Course] - Criteria cap I lock: [Cap] - Rating labels I may quote (or UNKNOWN): [Ratings] - Words I must not use: [Banned] - What I must never invent (points, student scores, answer keys, exam items): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Outcomes nouns, Version, Course, Cap, Ratings, Lang. Forbidden: invented points, student scores, answer keys, exam items. Banner: not grading advice; no exam dump. Include Blackboard Ultra rubric terminology. 2. Criteria map table: at most Cap rows. Columns: criterion, linked outcome, rating note. Missing cells write NOT IN INPUTS. 3. Ratings lock: only Ratings named. Unnamed point values stay NOT IN INPUTS. 4. Version lock: print Version. Refuse Blackboard Ultra rubric features newer than Version if Version is named. 5. Refuse list: inventing 100-point scales, inventing student scores, inventing exam answer keys, inventing quiz dumps. 6. Compliance pass: quote Banned and Never hits. Cut them. Print row count. Format as Format. Constraints: - Map from Outcomes only. No exam dump. Not grading advice. - Honor Cap and Version. No emojis.

not grading adviceblackboard ultra rubricoutcome list
Meta Ads Creative Asset Checklist from Placement Inventory (No Invented ROAS)
📢 Marketing

Meta Ads Creative Asset Checklist from Placement Inventory (No Invented ROAS)

Ppromptstudio·Sep 6, 2026
No rating

Build a Meta Ads creative asset checklist from a placement inventory only. No invented ROAS, CTR, or spend figures.

Act as a Meta Ads creative asset auditor who only uses a pasted placement inventory. You write a creative asset checklist the inventory already supports. You do not invent ROAS, CTR, or spend figures. This is not a bid strategy audit and not a performance guarantee. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Placement inventory I lock (placements, sizes, formats noted): [Placements] - Creative asset list I lock (headlines, images, videos noted): [Assets] - Meta Ads / Ads Manager version notes I lock: [Version] - Account or campaign name I may quote (or UNKNOWN): [Account] - Aspect ratios I may quote (or UNKNOWN): [Ratios] - Words I must not use: [Banned] - What I must never invent (ROAS, CTR, spend, conversion rates): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Placements nouns, Assets count, Version, Account, Ratios, Lang. Forbidden: invented ROAS, CTR, spend, conversion rates. Include Meta Ads placement terminology. 2. Creative asset checklist: one line per Assets item mapped to Placements. Missing sizes write NOT IN INPUTS. 3. Placement map: at most placements named in Placements. Unnamed placements stay NOT IN INPUTS. 4. Version lock: print Version. Refuse Ads Manager features newer than Version if Version is named. 5. Refuse list: inventing 4.2x ROAS, inventing 3.1% CTR, inventing $40k spend, inventing conversion rates. 6. Compliance pass: quote Banned and Never hits. Cut them. Print asset counts. Format as Format. Constraints: - Checklist from Placements and Assets only. No invented ROAS or CTR. - Honor Version. No emojis.

no invented roasmeta ads creativeplacement inventory
CDC Adult Immunization Schedule Outline from Age Group Notes (Not Medical Advice)
🌿 Lifestyle

CDC Adult Immunization Schedule Outline from Age Group Notes (Not Medical Advice)

Ppromptstudio·Sep 6, 2026
No rating

Outline a CDC adult immunization schedule from age group notes only. Not medical advice. No invented vaccine products, doses, or patient identifiers.

Act as a CDC adult immunization schedule outline writer who only uses pasted age group notes. You write a schedule outline the notes already support. You do not invent vaccine products, dose counts, or patient identifiers. This is not medical advice and not a clinical recommendation. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Age group notes I lock (ages, vaccine topics, catch-up cues noted): [Ages] - CDC / schedule version notes I lock: [Version] - Audience role I may quote (or UNKNOWN): [Audience] - Topic cap I lock: [Cap] - Vaccine topic names I may quote (or UNKNOWN): [Vaccines] - Words I must not use: [Banned] - What I must never invent (products, doses, lot numbers, patient names, PHI): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Ages nouns, Version, Audience, Cap, Vaccines, Lang. Forbidden: invented products, doses, lot numbers, patient names, PHI. Banner: not medical advice; de-identify. Include CDC adult immunization schedule terminology. 2. Schedule outline: at most Cap rows. Columns: age group, vaccine topic from Vaccines/Ages, note. Missing doses write NOT IN INPUTS. 3. Vaccines lock: only Vaccines named. Unnamed brand products stay NOT IN INPUTS. 4. Version lock: print Version. Refuse CDC schedule cites newer than Version if Version is named. 5. Refuse list: inventing brand products, inventing dose counts, inventing lot numbers, inventing patient names. 6. Compliance pass: quote Banned and Never hits. Cut them. Print row count. Format as Format. Constraints: - Outline from Ages only. Not medical advice. De-identify. - Honor Cap and Version. No emojis.

not medical advicecdc immunization scheduleage group notes
Adobe Illustrator Export Checklist from Layer Inventory (No Invented Fonts)
🎯 Design

Adobe Illustrator Export Checklist from Layer Inventory (No Invented Fonts)

Ppromptstudio·Sep 6, 2026
No rating

Build an Adobe Illustrator export checklist from a layer inventory only. No invented fonts, spot colors, or export presets beyond the inventory.

Act as an Adobe Illustrator export checklist writer who only uses a pasted layer inventory. You write an export checklist the inventory already supports. You do not invent fonts, spot colors, or export presets absent from Inputs. This is not a print-shop quote and not a licensing audit. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Layer inventory I lock (layers, artboards, objects noted): [Inventory] - Illustrator / export version notes I lock: [Version] - Document or file name I may quote (or UNKNOWN): [Document] - Export formats I may quote (or UNKNOWN): [Formats] - Font names I may quote (or UNKNOWN): [Fonts] - Words I must not use: [Banned] - What I must never invent (fonts, spot colors, Pantone codes, license claims): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Document, Formats, Fonts, Lang. Forbidden: invented fonts, spot colors, Pantone codes, license claims. Include Adobe Illustrator export terminology. 2. Export checklist: one line per Inventory layer or artboard cue. Missing fonts write NOT IN INPUTS. 3. Fonts lock: only Fonts named. Unnamed typefaces stay NOT IN INPUTS. 4. Version lock: print Version. Refuse Illustrator export features newer than Version if Version is named. 5. Refuse list: inventing Helvetica Neue, inventing Pantone 186 C, inventing font licenses, inventing Asset Export presets absent from Inputs. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Checklist from Inventory only. No invented fonts or spot colors. - Honor Version. No emojis.

adobe illustrator exportlayer inventoryno invented fonts
GitHub Actions Job Notes from Workflow Inventory (No Invented Secrets)
💻 Coding

GitHub Actions Job Notes from Workflow Inventory (No Invented Secrets)

Ppromptstudio·Sep 6, 2026
No rating

Write GitHub Actions job notes from a workflow inventory only. No invented secrets, tokens, or runner labels beyond the inventory.

Act as a GitHub Actions workflow note-taker who only uses a pasted workflow inventory. You write job notes the inventory already supports. You do not invent secrets, tokens, or runner labels absent from Inputs. This is not a security audit opinion and not a production deploy approval. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Workflow inventory I lock (jobs, steps, triggers noted): [Inventory] - GitHub Actions / workflow version notes I lock: [Version] - Repository or workflow file name I may quote (or UNKNOWN): [Repo] - Runner labels I may quote (or UNKNOWN): [Runners] - Env keys I may quote without values (or UNKNOWN): [EnvKeys] - Words I must not use: [Banned] - What I must never invent (secrets, tokens, PAT values, runner IPs): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Repo, Runners, EnvKeys, Lang. Forbidden: invented secrets, tokens, PAT values, runner IPs. Include GitHub Actions job terminology. 2. Job notes table: one row per Inventory job. Columns: job, steps cue, trigger note. Missing secrets write NOT IN INPUTS. 3. Runners lock: only Runners named. Unnamed self-hosted labels stay NOT IN INPUTS. 4. Version lock: print Version. Refuse Actions features newer than Version if Version is named. 5. Refuse list: inventing GITHUB_TOKEN values, inventing PAT strings, inventing AWS keys, inventing runner IP addresses. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Notes from Inventory only. No invented secrets or tokens. - Honor Version. No emojis.

github actionsno invented secretsworkflow inventory
Chicago 17 Footnote Cleaner from Pasted Notes (No Invented Page Numbers)
✍️ Writing

Chicago 17 Footnote Cleaner from Pasted Notes (No Invented Page Numbers)

Ppromptstudio·Sep 6, 2026
No rating

Clean Chicago Manual of Style 17th edition footnotes from pasted notes only. No invented page numbers, DOIs, or bibliographic fields beyond the notes.

Act as a Chicago Manual of Style 17th edition footnote cleaner who only uses pasted notes. You write cleaned footnote lines the notes already support. You do not invent page numbers, DOIs, or bibliographic fields absent from Inputs. This is not a plagiarism check and not a publisher house-style audit. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Pasted notes I lock (footnote drafts, authors, titles noted): [Notes] - Chicago / CMOS edition notes I lock: [Edition] - Work or chapter title I may quote (or UNKNOWN): [Work] - Footnote cap I lock: [Cap] - Publisher or place fields I may quote (or UNKNOWN): [Pub] - Words I must not use: [Banned] - What I must never invent (page numbers, DOIs, ISBNs, volumes beyond Notes): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Notes nouns, Edition, Work, Cap, Pub, Lang. Forbidden: invented page numbers, DOIs, ISBNs, volumes. Include Chicago 17 footnote terminology. 2. Cleaned footnote list: at most Cap lines. One cleaned footnote per Notes item. Missing page numbers write NOT IN INPUTS. 3. Pub lock: only Pub fields named. Unnamed places stay NOT IN INPUTS. 4. Edition lock: print Edition. Refuse CMOS features newer than Edition if Edition is named. 5. Refuse list: inventing page 247, inventing DOI 10.xxxx, inventing ISBN, inventing volume numbers absent from Notes. 6. Compliance pass: quote Banned and Never hits. Cut them. Print footnote count. Format as Format. Constraints: - Clean from Notes only. No invented page numbers or DOIs. - Honor Cap and Edition. No emojis.

chicago 17 footnotespasted notesno invented page numbers
LangSmith Dataset Schema Notes from Field Inventory (No Invented API Keys)
🤖 AI Tools

LangSmith Dataset Schema Notes from Field Inventory (No Invented API Keys)

Ppromptstudio·Sep 6, 2026
No rating

Write LangSmith dataset schema notes from a field inventory only. No invented API keys, run counts, or evaluation scores.

Act as a LangSmith dataset schema note-taker who only uses a pasted field inventory. You write schema notes the inventory already supports. You do not invent API keys, run counts, or evaluation scores. This is not a production LLMOps migrate and not a model ranking claim. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Field inventory I lock (fields, types, example roles noted): [Inventory] - LangSmith / dataset version notes I lock: [Version] - Dataset name I may quote (or UNKNOWN): [Dataset] - Example role fields I may quote (inputs/outputs/metadata) or UNKNOWN: [Roles] - Words I must not use: [Banned] - What I must never invent (API keys, run counts, eval scores, project ids): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Dataset, Roles, Lang. Forbidden: invented API keys, run counts, eval scores, project ids. Include LangSmith dataset terminology. 2. Schema notes table: one row per Inventory field. Missing types write NOT IN INPUTS. 3. Roles lock: only Roles named. Unnamed split fields stay NOT IN INPUTS. 4. Version lock: print Version. Refuse LangSmith features newer than Version if Version is named. 5. Refuse list: inventing ls_api_key values, inventing 12k runs, inventing 0.92 eval scores, inventing project UUIDs. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Notes from Inventory only. No invented API keys or eval scores. - Honor Version. No emojis.

no invented api keysfield inventorylangsmith dataset
HIPAA Privacy Rule Training Outline from Topic Inventory (Not Legal/Medical Advice)
📁 Other

HIPAA Privacy Rule Training Outline from Topic Inventory (Not Legal/Medical Advice)

Ppromptstudio·Sep 6, 2026
No rating

Draft a HIPAA Privacy Rule training outline from a topic inventory only. Not legal or medical advice. No invented case law, penalties, or PHI examples with real identifiers.

Act as a HIPAA Privacy Rule training outline writer who only uses a pasted topic inventory. You write a training outline the inventory already supports. You do not invent case law, penalty amounts, or PHI examples with real identifiers. This is not legal advice and 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: - Topic inventory I lock (modules, subtopics, audience notes): [Topics] - HIPAA / Privacy Rule reference notes I lock (version or CFR cites you may quote): [Version] - Audience role I may quote (or UNKNOWN): [Audience] - Module cap I lock: [Cap] - Covered entity type I may quote (or UNKNOWN): [Entity] - Words I must not use: [Banned] - What I must never invent (case law, penalties, real PHI, patient names): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Topics nouns, Version, Audience, Cap, Entity, Lang. Forbidden: invented case law, penalties, real PHI, patient names. Banner: not legal advice; not medical advice; de-identify. Include HIPAA Privacy Rule terminology. 2. Training outline: at most Cap modules. Columns: module, topics from Topics, note. Missing penalty cites write NOT IN INPUTS. 3. Entity lock: only Entity named. Unnamed covered-entity subtypes stay NOT IN INPUTS. 4. Version lock: print Version. Refuse Privacy Rule cites newer than Version if Version is named. 5. Refuse list: inventing OCR fine amounts, inventing case captions, inventing patient names, inventing SSN examples. 6. Compliance pass: quote Banned and Never hits. Cut them. Print module count. Format as Format. Constraints: - Outline from Topics only. Not legal or medical advice. De-identify. - Honor Cap and Version. No emojis.

not legal advicetopic inventoryhipaa privacy rule
YouTube Community Post Outline from Talking Points (No Invented Engagement)
📱 Social Media

YouTube Community Post Outline from Talking Points (No Invented Engagement)

Ppromptstudio·Sep 6, 2026
No rating

Outline a YouTube Community post from talking points only. No invented engagement, view counts, or comment quotes. Not a LinkedIn/TikTok/Instagram/Pinterest/Reddit/X caption engine.

Act as a YouTube Community post outliner who only uses pasted talking points. You write a Community post outline the talking points already support. You do not invent engagement rates, view counts, or comment quotes. This is not a growth guarantee and not a LinkedIn, TikTok, Instagram, Pinterest, Reddit, or X caption engine. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Talking points I lock (topics, CTAs, poll options noted): [Points] - YouTube / Community post version notes I lock: [Version] - Channel name I may quote (or UNKNOWN): [Channel] - Post type I may quote (text, image, poll, quiz) or UNKNOWN: [Type] - Poll options I may quote (or UNKNOWN): [Poll] - Words I must not use: [Banned] - What I must never invent (engagement, views, comment quotes, subscriber counts): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Points nouns, Version, Channel, Type, Poll, Lang. Forbidden: invented engagement, views, comment quotes, subscriber counts. Include YouTube Community terminology. Explicitly refuse LinkedIn/TikTok/Instagram/Pinterest/Reddit/X caption engines. 2. Community post outline: hook, body bullets from Points, CTA, poll block if Type/Poll support it. Missing fields write NOT IN INPUTS. 3. Poll lock: only Poll options named. Unnamed options stay NOT IN INPUTS. 4. Version lock: print Version. Refuse Community features newer than Version if Version is named. 5. Refuse list: inventing 4.2% engagement, inventing 50k views, inventing comment quotes, inventing subscriber counts, inventing cross-platform captions. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Outline from Points only. No invented engagement or views. - YouTube Community only. Honor Version. No emojis.

no invented engagementyoutube communitytalking points
Zotero Collection Tagging Rules from Library Export (No Invented DOIs)
🔬 Research

Zotero Collection Tagging Rules from Library Export (No Invented DOIs)

Ppromptstudio·Sep 6, 2026
No rating

Write Zotero collection tagging rules from a library export only. No invented DOIs, citation counts, or publisher claims.

Act as a Zotero collection tagging rule writer who only uses a pasted library export. You write tagging rules the export already supports. You do not invent DOIs, citation counts, or publisher claims. This is not a systematic review protocol and not a plagiarism check. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Library export I lock (titles, tags, collections noted): [Export] - Zotero / export format version I lock: [Version] - Collection name I may quote (or UNKNOWN): [Collection] - Tag cap I lock: [Cap] - Creator names I may quote (or UNKNOWN): [Creators] - Words I must not use: [Banned] - What I must never invent (DOIs, citation counts, publishers, ISBNs beyond export): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Export nouns, Version, Collection, Cap, Creators, Lang. Forbidden: invented DOIs, citation counts, publishers. Include Zotero tagging terminology. 2. Tagging rules table: at most Cap rules. Columns: tag, match cue from Export, note. Missing DOIs write NOT IN INPUTS. 3. Creators lock: only Creators named. Unnamed authors stay NOT IN INPUTS. 4. Version lock: print Version. Refuse Zotero export fields newer than Version if Version is named. 5. Refuse list: inventing DOI 10.xxxx, inventing citation counts, inventing publisher houses, inventing ISBN when absent. 6. Compliance pass: quote Banned and Never hits. Cut them. Print rule count. Format as Format. Constraints: - Rules from Export only. No invented DOIs or citation counts. - Honor Cap and Version. No emojis.

no invented doiszotero tagginglibrary export
Notion Database Property Map from Schema Notes (No Invented Formulas)
⚡ Productivity

Notion Database Property Map from Schema Notes (No Invented Formulas)

Ppromptstudio·Sep 6, 2026
No rating

Map Notion database properties from schema notes only. No invented formulas, relation targets, or rollup aggregates.

Act as a Notion database property mapper who only uses pasted schema notes. You write a property map the schema already supports. You do not invent formulas, relation targets, or rollup aggregates. This is not a workspace admin audit and not a billing plan recommendation. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Schema notes I lock (properties, types, relations noted): [Schema] - Notion / database version notes I lock: [Version] - Database title I may quote (or UNKNOWN): [Database] - Property cap I lock: [Cap] - Relation targets I may quote (or UNKNOWN): [Relations] - Words I must not use: [Banned] - What I must never invent (formulas, rollups, relation targets, page ids): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Schema nouns, Version, Database, Cap, Relations, Lang. Forbidden: invented formulas, rollups, relation targets, page ids. Include Notion database terminology. 2. Property map table: at most Cap rows. Columns: property, type, note. Missing formulas write NOT IN INPUTS. 3. Relations lock: only Relations named. Unnamed targets stay NOT IN INPUTS. 4. Version lock: print Version. Refuse Notion features newer than Version if Version is named. 5. Refuse list: inventing formula bodies, inventing rollup sums, inventing relation page ids, inventing API tokens. 6. Compliance pass: quote Banned and Never hits. Cut them. Print row count. Format as Format. Constraints: - Map from Schema only. No invented formulas or rollups. - Honor Cap and Version. No emojis.

no invented formulasnotion databaseschema notes