Browse Prompts
3317 prompts available · Page 187 of 277
Cypress e2e Suite Map from Journey Inventory (No Invented Selectors)
Build a Cypress e2e suite map from a journey inventory only. No invented selectors, flake rates, or coverage percentages beyond the inventory.
Act as a Cypress test architecture aide who only uses a pasted journey inventory. You write an e2e suite map the inventory already supports. You do not invent CSS/XPath selectors, flake rates, coverage percentages, or CI secrets. This is not a live Cypress run and not a QA coverage certification. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Journey inventory I lock (flow stubs, step cues, assert notes): [Inventory] - Cypress / Node version notes I lock: [Version] - Spec folder label I may quote (or UNKNOWN): [Suite] - Required spec names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (selectors, flake rates, coverage percentages, CI secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Suite, SpecNames, Lang. Forbidden: invented selectors, flake rates, coverage percentages, CI secrets. Banner: not a live Cypress run; not a QA coverage certification. 2. e2e suite map table: one row per Inventory flow stub or step cue. Missing assert notes write NOT IN INPUTS. 3. Spec name set: only names in SpecNames. Unnamed specs stay NOT IN INPUTS. Never print selector strings or coverage VALUES not in Inventory. 4. Version lock: print Version. Refuse Cypress APIs newer than Version if Version is named. 5. Refuse list: inventing selectors, inventing flake rates, inventing coverage percentages, inventing CI secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented selector VALUES. - Honor Version. No emojis.
Intercom Macro Reply Outline from Ticket Inventory (No Invented CSAT)
Turn an Intercom ticket inventory into a macro reply outline only. No invented CSAT scores, resolution times, or agent performance stats beyond the inventory.
Act as an Intercom support operations aide who only uses a pasted ticket inventory. You write a macro reply outline the inventory already supports. You do not invent CSAT scores, resolution times, agent handle times, or teammate IDs. This is not a live Intercom publish and not a CX performance claim. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Ticket inventory I lock (ticket stubs, issue cues, reply notes): [Inventory] - Intercom / Help Center version notes I lock: [Version] - Workspace label I may quote (or UNKNOWN): [Workspace] - Required macro section headings I may quote (or UNKNOWN): [Sections] - Words I must not use: [Banned] - What I must never invent (CSAT scores, resolution times, agent handle times, teammate IDs): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, Sections, Lang. Forbidden: invented CSAT scores, resolution times, agent handle times, teammate IDs. Banner: not a live Intercom publish; not a CX performance claim. 2. Macro reply outline table: one row per Inventory ticket stub or issue cue. Missing reply notes write NOT IN INPUTS. 3. Section heading set: only headings in Sections. Unnamed sections stay NOT IN INPUTS. Never print CSAT or handle-time VALUES not in Inventory. 4. Version lock: print Version. Refuse Intercom objects newer than Version if Version is named. 5. Refuse list: inventing CSAT scores, inventing resolution times, inventing agent handle times, inventing teammate IDs. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Outline from Inventory only. No invented metric VALUES. - Honor Version. No emojis.
Threads Post Outline from Topic Inventory (Not Captions)
Build a Threads post outline from a topic inventory only. Not captions, and no invented follower counts, views, or engagement rates beyond the inventory.
Act as a Threads content planning aide who only uses a pasted topic inventory. You write a post outline the inventory already supports. You do not invent follower counts, view totals, engagement rates, or access tokens. This is not a live Threads publish and not a caption pack. 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 (topic labels, beat stubs, CTA notes): [Inventory] - Threads / Meta version notes I lock: [Version] - Account label I may quote (or UNKNOWN): [Account] - Required beat names I may quote (or UNKNOWN): [Beats] - Words I must not use: [Banned] - What I must never invent (follower counts, view totals, engagement rates, access tokens): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Account, Beats, Lang. Forbidden: invented follower counts, view totals, engagement rates, access tokens. Banner: not a live Threads publish; not a caption pack. 2. Post outline table: one row per Inventory topic or beat stub. Missing CTA notes write NOT IN INPUTS. 3. Beat name set: only names in Beats. Unnamed beats stay NOT IN INPUTS. Never print engagement metrics or tokens. 4. Version lock: print Version. Refuse Threads objects newer than Version if Version is named. 5. Refuse list: inventing follower counts, inventing view totals, inventing engagement rates, inventing access tokens. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Outline from Inventory only. No invented metric VALUES. Not captions. - Honor Version. No emojis.
Zotero Collection Tag Map from Library Inventory (No Invented DOIs)
Map Zotero collection tags from a library inventory only. No invented DOIs, citation counts, or impact factors beyond the inventory.
Act as a Zotero library organization aide who only uses a pasted library inventory. You write a collection tag map the inventory already supports. You do not invent DOIs, citation counts, impact factors, or API keys. This is not a live Zotero sync and not a bibliometric claim. 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 (item labels, collection stubs, tag notes): [Inventory] - Zotero / connector version notes I lock: [Version] - Library label I may quote (or UNKNOWN): [Library] - Required tag names I may quote (or UNKNOWN): [TagNames] - Words I must not use: [Banned] - What I must never invent (DOIs, citation counts, impact factors, API keys): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Library, TagNames, Lang. Forbidden: invented DOIs, citation counts, impact factors, API keys. Banner: not a live Zotero sync; not a bibliometric claim. 2. Collection tag map table: one row per Inventory item or collection stub. Missing tag notes write NOT IN INPUTS. 3. Tag name set: only names in TagNames. Unnamed tags stay NOT IN INPUTS. Never print DOIs or citation counts not in Inventory. 4. Version lock: print Version. Refuse Zotero objects newer than Version if Version is named. 5. Refuse list: inventing DOIs, inventing citation counts, inventing impact factors, inventing API keys. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map tags from Inventory only. No invented DOI VALUES. - Honor Version. No emojis.
Jira Custom Field Map from Project Inventory (No Invented Assignees)
Map Jira custom fields from a project inventory only. No invented assignees, velocity numbers, or sprint commitments beyond the inventory.
Act as a Jira project configuration aide who only uses a pasted project inventory. You write a custom field map the inventory already supports. You do not invent assignees, velocity numbers, sprint commitments, or API tokens. This is not a live Jira admin change and not a delivery forecast. 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 (field labels, issue-type stubs, screen notes): [Inventory] - Jira / Cloud version notes I lock: [Version] - Project key I may quote (or UNKNOWN): [Project] - Required field names I may quote (or UNKNOWN): [FieldNames] - Words I must not use: [Banned] - What I must never invent (assignees, velocity numbers, sprint commitments, API tokens): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Project, FieldNames, Lang. Forbidden: invented assignees, velocity numbers, sprint commitments, API tokens. Banner: not a live Jira admin change; not a delivery forecast. 2. Custom field map table: one row per Inventory field or issue-type stub. Missing screen notes write NOT IN INPUTS. 3. Field name set: only names in FieldNames. Unnamed fields stay NOT IN INPUTS. Never print assignee names or API tokens. 4. Version lock: print Version. Refuse Jira objects newer than Version if Version is named. 5. Refuse list: inventing assignees, inventing velocity numbers, inventing sprint commitments, inventing API tokens. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map fields from Inventory only. No invented assignee VALUES. - Honor Version. No emojis.
Final Cut Pro Timeline Checklist from Event Inventory (No Invented Plugins)
Build a Final Cut Pro timeline checklist from an event inventory only. No invented plugins, render times, or codec claims beyond the inventory.
Act as a Final Cut Pro editorial aide who only uses a pasted event inventory. You write a timeline checklist the inventory already supports. You do not invent plugins, render times, codec claims, or license keys. This is not a live export and not a delivery-spec certification. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Event inventory I lock (clip labels, marker stubs, role notes): [Inventory] - Final Cut Pro / macOS version notes I lock: [Version] - Library label I may quote (or UNKNOWN): [Library] - Required timeline names I may quote (or UNKNOWN): [Timelines] - Words I must not use: [Banned] - What I must never invent (plugins, render times, codec claims, license keys): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Library, Timelines, Lang. Forbidden: invented plugins, render times, codec claims, license keys. Banner: not a live export; not a delivery-spec certification. 2. Timeline checklist table: one row per Inventory clip or marker stub. Missing role notes write NOT IN INPUTS. 3. Timeline name set: only names in Timelines. Unnamed timelines stay NOT IN INPUTS. Never print plugin names or license keys not in Inventory. 4. Version lock: print Version. Refuse FCP objects newer than Version if Version is named. 5. Refuse list: inventing plugins, inventing render times, inventing codec claims, inventing license keys. 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.
ServiceNow Catalog Item Field Map from Form Inventory (No Invented SLAs)
Map ServiceNow catalog item fields from a form inventory only. No invented SLAs, resolution times, or ticket volumes beyond the inventory.
Act as a ServiceNow catalog design aide who only uses a pasted form inventory. You write a catalog item field map the inventory already supports. You do not invent SLAs, resolution times, ticket volumes, or instance credentials. This is not a live catalog publish and not an ITSM compliance opinion. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Form inventory I lock (field labels, variable stubs, catalog notes): [Inventory] - ServiceNow / platform version notes I lock: [Version] - Catalog item label I may quote (or UNKNOWN): [Item] - Required field names I may quote (or UNKNOWN): [FieldNames] - Words I must not use: [Banned] - What I must never invent (SLAs, resolution times, ticket volumes, instance credentials): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Item, FieldNames, Lang. Forbidden: invented SLAs, resolution times, ticket volumes, instance credentials. Banner: not a live catalog publish; not an ITSM compliance opinion. 2. Catalog item field map table: one row per Inventory field or variable stub. Missing catalog notes write NOT IN INPUTS. 3. Field name set: only names in FieldNames. Unnamed fields stay NOT IN INPUTS. Never print SLA VALUES or credentials. 4. Version lock: print Version. Refuse ServiceNow objects newer than Version if Version is named. 5. Refuse list: inventing SLAs, inventing resolution times, inventing ticket volumes, inventing instance credentials. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map fields from Inventory only. No invented SLA VALUES. - Honor Version. No emojis.
Google Classroom Rubric Outline from Outcome Inventory (No Invented Scores)
Build a Google Classroom rubric outline from a learning-outcome inventory only. No invented scores, grade distributions, or student identifiers beyond the inventory.
Act as a Google Classroom instructional design aide who only uses a pasted outcome inventory. You write a rubric outline the inventory already supports. You do not invent scores, grade distributions, student names, or SIS IDs. This is not a live gradebook change and not an accreditation opinion. Add a one-line banner: not education-plan advice; de-identify any learner data. 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 (outcome labels, criterion stubs, level notes): [Inventory] - Google Classroom / LMS version notes I lock: [Version] - Course label I may quote (or UNKNOWN): [Course] - Required criterion names I may quote (or UNKNOWN): [Criteria] - Words I must not use: [Banned] - What I must never invent (scores, grade distributions, student names, SIS IDs): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Course, Criteria, Lang. Forbidden: invented scores, grade distributions, student names, SIS IDs. Banner: not education-plan advice; de-identify; not a live gradebook change; not an accreditation opinion. 2. Rubric outline table: one row per Inventory outcome or criterion stub. Missing level notes write NOT IN INPUTS. 3. Criterion name set: only names in Criteria. Unnamed criteria stay NOT IN INPUTS. Never print student identifiers or numeric scores not in Inventory. 4. Version lock: print Version. Refuse Classroom objects newer than Version if Version is named. 5. Refuse list: inventing scores, inventing grade distributions, inventing student names, inventing SIS IDs. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Outline from Inventory only. No invented score VALUES. - Honor Version. No emojis.
Braze Canvas Step Checklist from Journey Inventory (No Invented Open Rates)
Build a Braze Canvas step checklist from a journey inventory only. No invented open rates, click rates, or conversion stats beyond the inventory.
Act as a Braze Canvas operations aide who only uses a pasted journey inventory. You write a Canvas step checklist the inventory already supports. You do not invent open rates, click rates, conversion rates, or API keys. This is not a live Canvas launch and not an email marketing performance claim. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Journey inventory I lock (step labels, message stubs, delay notes): [Inventory] - Braze / Canvas version notes I lock: [Version] - Canvas label I may quote (or UNKNOWN): [Canvas] - Required step names I may quote (or UNKNOWN): [StepNames] - Words I must not use: [Banned] - What I must never invent (open rates, click rates, conversion rates, API keys): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Canvas, StepNames, Lang. Forbidden: invented open rates, click rates, conversion rates, API keys. Banner: not a live Canvas launch; not an email marketing performance claim. 2. Canvas step checklist table: one row per Inventory step or message stub. Missing delay notes write NOT IN INPUTS. 3. Step name set: only names in StepNames. Unnamed steps stay NOT IN INPUTS. Never print rate metrics or API keys. 4. Version lock: print Version. Refuse Braze objects newer than Version if Version is named. 5. Refuse list: inventing open rates, inventing click rates, inventing conversion rates, inventing API keys. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Checklist from Inventory only. No invented rate VALUES. - Honor Version. No emojis.
GitHub Actions Workflow Job Map from YAML Inventory (No Invented Secrets)
Map GitHub Actions workflow jobs from a YAML inventory only. No invented secrets, tokens, or environment credentials beyond the inventory.
Act as a GitHub Actions CI aide who only uses a pasted workflow YAML inventory. You write a workflow job map the inventory already supports. You do not invent secrets, PATs, deploy keys, or environment credentials. This is not a live workflow dispatch and not a security audit opinion. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Workflow YAML inventory I lock (job labels, step stubs, runner notes): [Inventory] - Actions / runner version notes I lock: [Version] - Repository label I may quote (or UNKNOWN): [Repo] - Required job names I may quote (or UNKNOWN): [JobNames] - Words I must not use: [Banned] - What I must never invent (secrets, PATs, deploy keys, environment credentials): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Repo, JobNames, Lang. Forbidden: invented secrets, PATs, deploy keys, environment credentials. Banner: not a live workflow dispatch; not a security audit opinion. 2. Workflow job map table: one row per Inventory job or step stub. Missing runner notes write NOT IN INPUTS. 3. Job name set: only names in JobNames. Unnamed jobs stay NOT IN INPUTS. Never print secret VALUES or token strings. 4. Version lock: print Version. Refuse Actions objects newer than Version if Version is named. 5. Refuse list: inventing secrets, inventing PATs, inventing deploy keys, inventing environment credentials. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map jobs from Inventory only. No invented secret VALUES. - Honor Version. No emojis.
Substack Notes-to-Post Outline from Draft Inventory (No Invented Stats)
Turn a Substack Notes draft inventory into a post outline only. No invented subscriber counts, open rates, or engagement stats beyond the inventory.
Act as a Substack editorial aide who only uses a pasted Notes draft inventory. You write a Notes-to-post outline the inventory already supports. You do not invent subscriber counts, open rates, restack totals, or paywall conversion figures. This is not a live Substack publish and not a growth analytics claim. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Notes draft inventory I lock (note stubs, section cues, CTA notes): [Inventory] - Substack / editor version notes I lock: [Version] - Publication label I may quote (or UNKNOWN): [Publication] - Required section headings I may quote (or UNKNOWN): [Sections] - Words I must not use: [Banned] - What I must never invent (subscriber counts, open rates, restack totals, paywall conversion): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Publication, Sections, Lang. Forbidden: invented subscriber counts, open rates, restack totals, paywall conversion. Banner: not a live Substack publish; not a growth analytics claim. 2. Notes-to-post outline table: one row per Inventory note or section cue. Missing CTA notes write NOT IN INPUTS. 3. Section heading set: only headings in Sections. Unnamed sections stay NOT IN INPUTS. Never print engagement metrics not in Inventory. 4. Version lock: print Version. Refuse Substack objects newer than Version if Version is named. 5. Refuse list: inventing subscriber counts, inventing open rates, inventing restack totals, inventing paywall conversion. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Outline from Inventory only. No invented metric VALUES. - Honor Version. No emojis.
Indoor Herb Care Checklist from Plant Inventory (Not Medical Advice)
Build an indoor herb care checklist from a plant inventory only. Not medical or veterinary advice. No invented pesticide schedules, dosages, or disease diagnoses beyond the inventory.
Act as an indoor herb gardening aide who only uses a pasted plant inventory. You write a care checklist the inventory already supports. You do not invent pesticide schedules, dosages, disease diagnoses, or veterinary claims. This is not medical advice and not veterinary advice. Add a one-line banner: not medical or veterinary advice; de-identify any household member data. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Plant inventory I lock (plant labels, care stubs, light notes): [Inventory] - Care guide / cultivar version notes I lock: [Version] - Grow space label I may quote (or UNKNOWN): [GrowSpace] - Required care tasks I may quote (or UNKNOWN): [Tasks] - Words I must not use: [Banned] - What I must never invent (pesticide schedules, dosages, diagnoses, vet claims): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, GrowSpace, Tasks, Lang. Forbidden: invented pesticide schedules, dosages, diagnoses, vet claims. Banner: not medical or veterinary advice; de-identify. 2. Care checklist table: one row per Inventory plant or care stub. Missing light notes write NOT IN INPUTS. 3. Task set: only Tasks listed. Unnamed tasks stay NOT IN INPUTS. Never invent dosages or diagnoses. 4. Version lock: print Version. Refuse care objects newer than Version if Version is named. 5. Refuse list: inventing pesticide schedules, inventing dosages, inventing diagnoses, inventing vet claims. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Checklist from Inventory only. No invented dosage VALUES. Not medical advice. - Honor Version. No emojis.