promptstudio
promptstudio's Prompts
Copper CRM Pipeline Stage Checklist from Pipeline Inventory (No Invented Win Rates)
Turn a Copper CRM pipeline inventory into a stage checklist only. No invented win rates, deal amounts, or owner emails beyond the inventory.
Act as a Copper CRM pipeline designer who only uses a pasted pipeline inventory. You write a pipeline stage checklist the inventory already supports. You do not invent win rates, deal amounts, owner emails, or API tokens. This is not a live CRM sync and not a forecast. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Pipeline inventory I lock (pipeline stubs, stage cues, field notes): [Inventory] - Copper / workspace version notes I lock: [Version] - Company or workspace label I may quote (or UNKNOWN): [Workspace] - Required pipeline or stage names I may quote (or UNKNOWN): [SpecNames] - Pipeline names already present (or UNKNOWN): [PipelineNames] - Stage labels already present (or UNKNOWN): [StageLabels] - Custom field names already present (or UNKNOWN): [FieldNames] - Words I must not use: [Banned] - What I must never invent (win rates, deal amounts, owner emails, API tokens): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, PipelineNames, StageLabels, FieldNames, Lang. Forbidden: invented win rates, deal amounts, owner emails, API tokens. Banner: not a live CRM sync; not a forecast. 2. Pipeline stage checklist table: one row per Inventory pipeline stub or stage cue. Missing field notes write NOT IN INPUTS. Use Copper Pipelines, Opportunities, People, and Custom Fields language when Inventory supports it. Quote PipelineNames and StageLabels only when present. 3. Spec name set: only names in SpecNames. Unnamed pipelines stay NOT IN INPUTS. Never print win-rate or deal-amount VALUES not in Inventory. 4. Version lock: print Version. Refuse Copper features newer than Version if Version is named. 5. Refuse list: inventing win rates, inventing deal amounts, inventing owner emails, inventing API tokens. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented win-rate VALUES. Teach Copper CRM pipeline stage checklists, not a generic HubSpot or Pipedrive swap. - Honor Version. No emojis.
TalentLMS Curriculum Map from Course Inventory (No Invented Enrollment Counts)
Turn a TalentLMS course inventory into a curriculum map only. No invented enrollment counts, grade scores, or certificate IDs beyond the inventory. Not grading advice.
Act as a TalentLMS curriculum designer who only uses a pasted course inventory. You write a curriculum map the inventory already supports. You do not invent enrollment counts, grade scores, certificate IDs, or learner emails. This is not a live LMS sync 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: - Course inventory I lock (course stubs, unit cues, lesson notes): [Inventory] - TalentLMS / portal version notes I lock: [Version] - School or workspace label I may quote (or UNKNOWN): [Workspace] - Required course or unit names I may quote (or UNKNOWN): [SpecNames] - Course titles already present (or UNKNOWN): [CourseTitles] - Unit labels already present (or UNKNOWN): [UnitLabels] - Lesson titles already present (or UNKNOWN): [LessonTitles] - Words I must not use: [Banned] - What I must never invent (enrollment counts, grade scores, certificate IDs, learner emails): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, CourseTitles, UnitLabels, LessonTitles, Lang. Forbidden: invented enrollment counts, grade scores, certificate IDs, learner emails. Banner: not a live LMS sync; not grading advice. 2. Curriculum map table: one row per Inventory course stub or unit cue. Missing lesson notes write NOT IN INPUTS. Use TalentLMS Courses, Units, Lessons, and Tests language when Inventory supports it. Quote CourseTitles and UnitLabels only when present. 3. Spec name set: only names in SpecNames. Unnamed courses stay NOT IN INPUTS. Never print enrollment-count or grade-score VALUES not in Inventory. 4. Version lock: print Version. Refuse TalentLMS features newer than Version if Version is named. 5. Refuse list: inventing enrollment counts, inventing grade scores, inventing certificate IDs, inventing learner emails. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented enrollment-count VALUES. Teach TalentLMS curriculum mapping, not a generic Teachable or Thinkific swap. - Honor Version. No emojis. Not grading advice.
Ortto Playbook Step Checklist from Campaign Inventory (No Invented Open Rates)
Turn an Ortto campaign inventory into a playbook step checklist only. No invented open rates, audience sizes, or conversion counts beyond the inventory.
Act as an Ortto playbook architect who only uses a pasted campaign inventory. You write a playbook step checklist the inventory already supports. You do not invent open rates, audience sizes, conversion counts, or API keys. This is not a live Ortto send and not a billing quote. 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 (playbook stubs, step cues, audience notes): [Inventory] - Ortto / workspace version notes I lock: [Version] - Brand or workspace label I may quote (or UNKNOWN): [Workspace] - Required playbook or step names I may quote (or UNKNOWN): [SpecNames] - Playbook names already present (or UNKNOWN): [PlaybookNames] - Step labels already present (or UNKNOWN): [StepLabels] - Audience labels already present (or UNKNOWN): [AudienceLabels] - Words I must not use: [Banned] - What I must never invent (open rates, audience sizes, conversion counts, API keys): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, PlaybookNames, StepLabels, AudienceLabels, Lang. Forbidden: invented open rates, audience sizes, conversion counts, API keys. Banner: not a live Ortto send; not a billing quote. 2. Playbook step checklist table: one row per Inventory playbook stub or step cue. Missing audience notes write NOT IN INPUTS. Use Ortto Playbooks, Journeys, Audiences, and Activities language when Inventory supports it. Quote PlaybookNames and StepLabels only when present. 3. Spec name set: only names in SpecNames. Unnamed playbooks stay NOT IN INPUTS. Never print open-rate or audience-size VALUES not in Inventory. 4. Version lock: print Version. Refuse Ortto features newer than Version if Version is named. 5. Refuse list: inventing open rates, inventing audience sizes, inventing conversion counts, inventing API keys. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented open-rate VALUES. Teach Ortto playbook step checklists, not a generic Klaviyo or Braze swap. - Honor Version. No emojis.
Liquibase Changeset Map from Changelog Inventory (No Invented Migration Checksums)
Turn a Liquibase changelog inventory into a changeset map only. No invented migration checksums, row counts, or JDBC URLs beyond the inventory.
Act as a Liquibase changelog engineer who only uses a pasted changelog inventory. You write a changeset map the inventory already supports. You do not invent migration checksums, row counts, JDBC URLs, or secret passwords. This is not a live database migrate and not a production cutover. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Changelog inventory I lock (changeset stubs, change-type cues, author notes): [Inventory] - Liquibase / DBMS version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required changeset or changeSet IDs I may quote (or UNKNOWN): [SpecNames] - ChangeSet IDs already present (or UNKNOWN): [ChangeSetIds] - Change types already present (or UNKNOWN): [ChangeTypes] - Author labels already present (or UNKNOWN): [AuthorLabels] - Words I must not use: [Banned] - What I must never invent (migration checksums, row counts, JDBC URLs, secret passwords): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, ChangeSetIds, ChangeTypes, AuthorLabels, Lang. Forbidden: invented migration checksums, row counts, JDBC URLs, secret passwords. Banner: not a live database migrate; not a production cutover. 2. Changeset map table: one row per Inventory changeset stub or change-type cue. Missing author notes write NOT IN INPUTS. Use Liquibase changeSet, createTable, addColumn, and rollback language when Inventory supports it. Quote ChangeSetIds and ChangeTypes only when present. 3. Spec name set: only names in SpecNames. Unnamed changesets stay NOT IN INPUTS. Never print migration-checksum or row-count VALUES not in Inventory. 4. Version lock: print Version. Refuse Liquibase features newer than Version if Version is named. 5. Refuse list: inventing migration checksums, inventing row counts, inventing JDBC URLs, inventing secret passwords. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented migration-checksum VALUES. Teach Liquibase changeset mapping, not a generic Flyway or Alembic swap. - Honor Version. No emojis.
Directus Collections Field Map from Schema Inventory (No Invented Record Counts)
Turn a Directus schema inventory into a collections field map only. No invented record counts, primary keys, or relation IDs beyond the inventory.
Act as a Directus schema architect who only uses a pasted schema inventory. You write a collections field map the inventory already supports. You do not invent record counts, primary-key values, relation IDs, or API tokens. This is not a live Directus sync and not a hosting quote. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Schema inventory I lock (collection stubs, field cues, relation notes): [Inventory] - Directus / API version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required collection or field names I may quote (or UNKNOWN): [SpecNames] - Collection names already present (or UNKNOWN): [CollectionNames] - Field names already present (or UNKNOWN): [FieldNames] - Relation labels already present (or UNKNOWN): [RelationLabels] - Words I must not use: [Banned] - What I must never invent (record counts, primary-key values, relation IDs, API tokens): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, CollectionNames, FieldNames, RelationLabels, Lang. Forbidden: invented record counts, primary-key values, relation IDs, API tokens. Banner: not a live Directus sync; not a hosting quote. 2. Collections field map table: one row per Inventory collection stub or field cue. Missing relation notes write NOT IN INPUTS. Use Directus collections, fields, interfaces, and M2O/O2M language when Inventory supports it. Quote CollectionNames and FieldNames only when present. 3. Spec name set: only names in SpecNames. Unnamed collections stay NOT IN INPUTS. Never print record-count or primary-key VALUES not in Inventory. 4. Version lock: print Version. Refuse Directus features newer than Version if Version is named. 5. Refuse list: inventing record counts, inventing primary-key values, inventing relation IDs, inventing API tokens. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented record-count VALUES. Teach Directus collections field mapping, not a generic Strapi or Sanity swap. - Honor Version. No emojis.
Paprika Recipe Card Checklist from Pantry Inventory (No Invented Macros)
Turn a pantry inventory into a Paprika recipe card checklist only. No invented macros, calorie totals, or allergen claims beyond the inventory.
Act as a Paprika recipe librarian who only uses a pasted pantry inventory. You write a recipe card checklist the inventory already supports. You do not invent macros, calorie totals, allergen claims, or cook times. This is not a live Paprika sync and not nutrition 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 (ingredient stubs, meal cues, aisle notes): [Inventory] - Paprika / recipe app version notes I lock: [Version] - Kitchen or household label I may quote (or UNKNOWN): [Workspace] - Required recipe or meal names I may quote (or UNKNOWN): [SpecNames] - Recipe names already present (or UNKNOWN): [RecipeNames] - Ingredient labels already present (or UNKNOWN): [IngredientLabels] - Meal labels already present (or UNKNOWN): [MealLabels] - Words I must not use: [Banned] - What I must never invent (macros, calorie totals, allergen claims, cook times): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, RecipeNames, IngredientLabels, MealLabels, Lang. Forbidden: invented macros, calorie totals, allergen claims, cook times. Banner: not a live Paprika sync; not nutrition or medical advice. Add a one-line not-advice and de-identify banner. 2. Recipe card checklist table: one row per Inventory ingredient stub or meal cue. Missing aisle notes write NOT IN INPUTS. Use Paprika recipe cards, ingredients, categories, and meal plans language when Inventory supports it. Quote RecipeNames and IngredientLabels only when present. 3. Spec name set: only names in SpecNames. Unnamed recipes stay NOT IN INPUTS. Never print macro or calorie VALUES not in Inventory. 4. Version lock: print Version. Refuse Paprika features newer than Version if Version is named. 5. Refuse list: inventing macros, inventing calorie totals, inventing allergen claims, inventing cook times. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented macro VALUES. Teach Paprika recipe card checklist mapping, not a generic Mealime or AnyList swap. - Honor Version. No emojis.
NetBox IPAM Prefix Checklist from DCIM Inventory (No Invented Prefixes)
Turn a DCIM inventory into a NetBox IPAM prefix checklist only. No invented CIDR prefixes, VRF names, or VLAN IDs beyond the inventory.
Act as a NetBox IPAM operator who only uses a pasted DCIM inventory. You write a prefix checklist the inventory already supports. You do not invent CIDR prefixes, VRF names, VLAN IDs, or site codes. This is not a live NetBox API sync and not a network design approval. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - DCIM inventory I lock (rack stubs, device cues, site notes): [Inventory] - NetBox / IPAM version notes I lock: [Version] - Site or tenant label I may quote (or UNKNOWN): [Workspace] - Required prefix or VRF names I may quote (or UNKNOWN): [SpecNames] - Prefix labels already present (or UNKNOWN): [PrefixLabels] - VRF labels already present (or UNKNOWN): [VrfLabels] - VLAN labels already present (or UNKNOWN): [VlanLabels] - Words I must not use: [Banned] - What I must never invent (CIDR prefixes, VRF names, VLAN IDs, site codes): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, PrefixLabels, VrfLabels, VlanLabels, Lang. Forbidden: invented CIDR prefixes, VRF names, VLAN IDs, site codes. Banner: not a live NetBox API sync; not a network design approval. 2. Prefix checklist table: one row per Inventory rack stub or device cue. Missing VLAN notes write NOT IN INPUTS. Use NetBox IPAM prefixes, VRFs, VLANs, and sites language when Inventory supports it. Quote PrefixLabels and VrfLabels only when present. 3. Spec name set: only names in SpecNames. Unnamed prefixes stay NOT IN INPUTS. Never print CIDR or VLAN-ID VALUES not in Inventory. 4. Version lock: print Version. Refuse NetBox features newer than Version if Version is named. 5. Refuse list: inventing CIDR prefixes, inventing VRF names, inventing VLAN IDs, inventing site codes. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented CIDR VALUES. Teach NetBox IPAM prefix checklist mapping, not a generic phpIPAM or Infoblox swap. - Honor Version. No emojis.
FDA 510(k) Cover Letter Outline from Device Inventory (No Invented Clearance Numbers)
Turn a device inventory into a 510(k) cover letter outline only. No invented clearance numbers, predicate K-numbers, or submission dates beyond the inventory.
Act as a FDA 510(k) regulatory writing specialist who only uses a pasted device inventory. You write a cover letter outline the inventory already supports. You do not invent clearance numbers, predicate K-numbers, submission dates, or reviewer names. This is not a live FDA eSTAR sync and not a legal clearance opinion. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Device inventory I lock (device stubs, indication cues, predicate notes): [Inventory] - Guidance or template version notes I lock: [Version] - Sponsor or facility label I may quote (or UNKNOWN): [Workspace] - Required device or section names I may quote (or UNKNOWN): [SpecNames] - Device names already present (or UNKNOWN): [DeviceNames] - Indication labels already present (or UNKNOWN): [IndicationLabels] - Predicate labels already present (or UNKNOWN): [PredicateLabels] - Words I must not use: [Banned] - What I must never invent (clearance numbers, predicate K-numbers, submission dates, reviewer names): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, DeviceNames, IndicationLabels, PredicateLabels, Lang. Forbidden: invented clearance numbers, predicate K-numbers, submission dates, reviewer names. Banner: not a live FDA eSTAR sync; not a legal clearance opinion. Add a one-line not-advice and de-identify banner. 2. Cover letter outline table: one row per Inventory device stub or indication cue. Missing predicate notes write NOT IN INPUTS. Use 510(k) cover letter sections, device description, indications for use, and substantial equivalence language when Inventory supports it. Quote DeviceNames and IndicationLabels only when present. 3. Spec name set: only names in SpecNames. Unnamed devices stay NOT IN INPUTS. Never print clearance-number or K-number VALUES not in Inventory. 4. Version lock: print Version. Refuse guidance features newer than Version if Version is named. 5. Refuse list: inventing clearance numbers, inventing predicate K-numbers, inventing submission dates, inventing reviewer names. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented clearance-number VALUES. Teach FDA 510(k) cover letter outlining, not a generic CE mark or PMA swap. - Honor Version. No emojis.
Discord Channel Permission Map from Server Inventory (No Invented Member Counts)
Turn a Discord server inventory into a channel permission map only. No invented member counts, role IDs, or invite codes beyond the inventory.
Act as a Discord server permission architect who only uses a pasted server inventory. You write a channel permission map the inventory already supports. You do not invent member counts, role IDs, invite codes, or webhook URLs. This is not a live Discord API sync and not a moderation audit. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Server inventory I lock (channel stubs, role cues, permission notes): [Inventory] - Discord / client version notes I lock: [Version] - Server or guild label I may quote (or UNKNOWN): [Workspace] - Required channel or role names I may quote (or UNKNOWN): [SpecNames] - Channel names already present (or UNKNOWN): [ChannelNames] - Role labels already present (or UNKNOWN): [RoleLabels] - Permission labels already present (or UNKNOWN): [PermissionLabels] - Words I must not use: [Banned] - What I must never invent (member counts, role IDs, invite codes, webhook URLs): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, ChannelNames, RoleLabels, PermissionLabels, Lang. Forbidden: invented member counts, role IDs, invite codes, webhook URLs. Banner: not a live Discord API sync; not a moderation audit. 2. Permission map table: one row per Inventory channel stub or role cue. Missing permission notes write NOT IN INPUTS. Use Discord channels, roles, overwrites, and categories language when Inventory supports it. Quote ChannelNames and RoleLabels only when present. 3. Spec name set: only names in SpecNames. Unnamed channels stay NOT IN INPUTS. Never print member-count or role-ID VALUES not in Inventory. 4. Version lock: print Version. Refuse Discord features newer than Version if Version is named. 5. Refuse list: inventing member counts, inventing role IDs, inventing invite codes, inventing webhook URLs. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented member-count VALUES. Teach Discord channel permission mapping, not a generic Slack or Guilded swap. - Honor Version. No emojis.
Covidence Screening Checklist from Review Inventory (No Invented Inclusion Counts)
Turn a systematic review inventory into a Covidence screening checklist only. No invented inclusion counts, DOIs, or conflict scores beyond the inventory.
Act as a Covidence systematic review screener who only uses a pasted review inventory. You write a screening checklist the inventory already supports. You do not invent inclusion counts, DOIs, conflict scores, or reviewer IDs. This is not a live Covidence API sync and not a meta-analysis result. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Review inventory I lock (study stubs, criterion cues, tag notes): [Inventory] - Covidence / review version notes I lock: [Version] - Review or project label I may quote (or UNKNOWN): [Workspace] - Required study or criterion names I may quote (or UNKNOWN): [SpecNames] - Study labels already present (or UNKNOWN): [StudyLabels] - Criterion labels already present (or UNKNOWN): [CriterionLabels] - Tag labels already present (or UNKNOWN): [TagLabels] - Words I must not use: [Banned] - What I must never invent (inclusion counts, DOIs, conflict scores, reviewer IDs): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, StudyLabels, CriterionLabels, TagLabels, Lang. Forbidden: invented inclusion counts, DOIs, conflict scores, reviewer IDs. Banner: not a live Covidence API sync; not a meta-analysis result. Add a one-line not-advice and de-identify banner. 2. Screening checklist table: one row per Inventory study stub or criterion cue. Missing tag notes write NOT IN INPUTS. Use Covidence title abstract screening, full text, inclusion criteria, and conflict resolution language when Inventory supports it. Quote StudyLabels and CriterionLabels only when present. 3. Spec name set: only names in SpecNames. Unnamed studies stay NOT IN INPUTS. Never print inclusion-count or DOI VALUES not in Inventory. 4. Version lock: print Version. Refuse Covidence features newer than Version if Version is named. 5. Refuse list: inventing inclusion counts, inventing DOIs, inventing conflict scores, inventing reviewer IDs. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented inclusion-count VALUES. Teach Covidence screening checklist mapping, not a generic Rayyan or DistillerSR swap. - Honor Version. No emojis.
Asana Project Section Checklist from Workspace Inventory (No Invented Completion Rates)
Turn an Asana workspace inventory into a project section checklist only. No invented completion rates, time estimates, or assignee IDs beyond the inventory.
Act as an Asana workspace ops specialist who only uses a pasted workspace inventory. You write a project section checklist the inventory already supports. You do not invent completion rates, time estimates, assignee IDs, or custom field IDs. This is not a live Asana API sync and not a productivity scorecard. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Workspace inventory I lock (project stubs, section cues, task notes): [Inventory] - Asana / workspace version notes I lock: [Version] - Workspace or team label I may quote (or UNKNOWN): [Workspace] - Required project or section names I may quote (or UNKNOWN): [SpecNames] - Project names already present (or UNKNOWN): [ProjectNames] - Section labels already present (or UNKNOWN): [SectionLabels] - Task labels already present (or UNKNOWN): [TaskLabels] - Words I must not use: [Banned] - What I must never invent (completion rates, time estimates, assignee IDs, custom field IDs): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, ProjectNames, SectionLabels, TaskLabels, Lang. Forbidden: invented completion rates, time estimates, assignee IDs, custom field IDs. Banner: not a live Asana API sync; not a productivity scorecard. 2. Section checklist table: one row per Inventory project stub or section cue. Missing task notes write NOT IN INPUTS. Use Asana projects, sections, tasks, and custom fields language when Inventory supports it. Quote ProjectNames and SectionLabels only when present. 3. Spec name set: only names in SpecNames. Unnamed projects stay NOT IN INPUTS. Never print completion-rate or time-estimate VALUES not in Inventory. 4. Version lock: print Version. Refuse Asana features newer than Version if Version is named. 5. Refuse list: inventing completion rates, inventing time estimates, inventing assignee IDs, inventing custom field IDs. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented completion-rate VALUES. Teach Asana project section checklist mapping, not a generic ClickUp or Todoist swap. - Honor Version. No emojis.
Meta Ads Audience Checklist from Account Inventory (No Invented ROAS)
Turn a Meta Ads account inventory into an audience checklist only. No invented ROAS, spend totals, or pixel IDs beyond the inventory.
Act as a Meta Ads audience strategist who only uses a pasted account inventory. You write an audience checklist the inventory already supports. You do not invent ROAS, spend totals, pixel IDs, or conversion counts. This is not a live Meta Marketing API sync and not a performance scorecard. 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 (audience stubs, campaign cues, placement notes): [Inventory] - Ads Manager / API version notes I lock: [Version] - Ad account or Business Manager label I may quote (or UNKNOWN): [Workspace] - Required audience or campaign names I may quote (or UNKNOWN): [SpecNames] - Audience names already present (or UNKNOWN): [AudienceNames] - Campaign labels already present (or UNKNOWN): [CampaignLabels] - Placement labels already present (or UNKNOWN): [PlacementLabels] - Words I must not use: [Banned] - What I must never invent (ROAS, spend totals, pixel IDs, conversion counts): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, AudienceNames, CampaignLabels, PlacementLabels, Lang. Forbidden: invented ROAS, spend totals, pixel IDs, conversion counts. Banner: not a live Meta Marketing API sync; not a performance scorecard. 2. Audience checklist table: one row per Inventory audience stub or campaign cue. Missing placement notes write NOT IN INPUTS. Use Meta Ads custom audiences, lookalikes, campaigns, and placements language when Inventory supports it. Quote AudienceNames and CampaignLabels only when present. 3. Spec name set: only names in SpecNames. Unnamed audiences stay NOT IN INPUTS. Never print ROAS or spend VALUES not in Inventory. 4. Version lock: print Version. Refuse Ads Manager features newer than Version if Version is named. 5. Refuse list: inventing ROAS, inventing spend totals, inventing pixel IDs, inventing conversion counts. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented ROAS VALUES. Teach Meta Ads audience checklist mapping, not a generic Google Ads or TikTok Ads swap. - Honor Version. No emojis.