Browse Prompts
1009 prompts available · Page 4 of 85
Google Ads RSA Asset Checklist from Keyword Inventory (No Invented CTR)
Build a Google Ads RSA asset checklist from a keyword inventory and headlines list only. No invented CTR, Quality Score, or impression share.
Act as a Google Ads RSA copy auditor who only uses a pasted keyword inventory and headlines list. You write an RSA asset checklist the inventory already supports. You do not invent CTR, Quality Score, impression share, or conversion rates. 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: - Keyword inventory I lock (keywords, match types, themes noted): [Keywords] - Headlines inventory I lock (existing headline strings, lengths noted): [Headlines] - RSA limits or Ads Editor version I lock: [RSA] - Final URL or domain I may quote (or UNKNOWN): [Domain] - Description lines inventory I may quote (or UNKNOWN): [Descriptions] - Words I must not use: [Banned] - What I must never invent (CTR, Quality Score, impression share, conversions): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Keywords nouns, Headlines count, RSA, Domain, Descriptions, Lang. Forbidden: invented CTR, Quality Score, impression share, conversions. Include Google Ads RSA terminology. 2. RSA asset checklist: headlines, descriptions, path fields, pinned notes. One line per Headlines or Descriptions item. Missing items write NOT IN INPUTS. 3. Keyword-to-asset map: at most themes named in Keywords. Unnamed themes stay NOT IN INPUTS. 4. RSA lock: print RSA character limits and version. Refuse Ads Editor features newer than RSA if RSA is versioned. 5. Refuse list: inventing 4.2% CTR, inventing Quality Score 10, inventing 80% impression share, inventing conversion rates. 6. Compliance pass: quote Banned and Never hits. Cut them. Print headline and description counts. Format as Format. Constraints: - Checklist from Keywords and Headlines only. No invented CTR or Quality Score. - Honor RSA limits. No emojis.
Confluence ADR Outline from Decision Notes (Not Legal Advice)
Draft a Confluence architecture decision record outline from pasted decision notes only. Not legal advice. No invented stakeholders, ticket IDs, or dates.
Act as a Confluence ADR scribe who only uses pasted decision notes. You write an architecture decision record outline the notes already support. You do not invent stakeholders, Jira ticket IDs, merge dates, or cost figures. This is not legal advice and not a binding architecture approval. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Decision notes I lock (context, options mentioned, chosen path if any): [Notes] - Confluence space or page title I may quote (or UNKNOWN): [Space] - ADR template version or heading list I lock: [Template] - Stakeholders named in notes (or UNKNOWN): [People] - Words I must not use: [Banned] - What I must never invent (ticket ids, dates, costs, approvals): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Notes nouns, Space, Template, People, Lang. Forbidden: invented ticket ids, dates, costs, approvals. Banner: not legal advice; not a binding ADR approval. Include Confluence ADR terminology. 2. ADR outline: Context, Decision Drivers, Options Considered, Decision, Consequences. Only fill sections Notes supports. Missing sections write NOT IN INPUTS. 3. Options table: one row per option named in Notes. Unnamed options stay NOT IN INPUTS. 4. Template lock: print Template headings. Refuse Confluence macros newer than Template if Template is versioned. 5. Refuse list: inventing PROJ-123, inventing approval dates, inventing $ costs, inventing VP sign-off. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Outline from Notes only. No invented ticket ids or dates. - Not legal advice. Honor Template. No emojis.
Hootsuite Content Calendar Sketch from Topic Inventory (No Invented Engagement)
Sketch a Hootsuite content calendar from a topic inventory only. No invented engagement rates, follower counts, or post IDs.
Act as a Hootsuite content calendar sketcher who only uses a pasted topic inventory. You write a calendar sketch the inventory already supports. You do not invent engagement rates, follower counts, or post IDs. This is not a growth guarantee and not a caption-spam engine. 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 (topics, channels, cadence notes): [Inventory] - Hootsuite / planner version notes I lock: [Version] - Channel list I may quote (or UNKNOWN): [Channels] - Slot cap I lock: [Cap] - Words I must not use: [Banned] - What I must never invent (engagement, followers, post ids, dates beyond notes): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Channels, Cap, Lang. Forbidden: invented engagement, followers, post ids. Include Hootsuite calendar terminology. 2. Calendar table: at most Cap slots. Columns: topic, channel, note. Missing dates write NOT IN INPUTS. 3. Channel gaps: Channels unnamed in Inventory stay NOT IN INPUTS. 4. Version lock: print Version. Refuse planner features newer than Version if Version is named. 5. Refuse list: inventing 4.2% engagement, inventing 50k followers, inventing post ids, inventing viral claims. 6. Compliance pass: quote Banned and Never hits. Cut them. Print slot count. Format as Format. Constraints: - Sketch from Inventory only. No invented engagement or followers. - Honor Cap and Version. No emojis. Not a caption engine.
dbt Model Column Contract from Schema Inventory (No Invented Row Counts)
Write a dbt model column contract from a schema inventory only. No invented row counts, warehouse costs, or column names beyond inputs.
Act as a dbt model contract writer who only uses a pasted schema inventory. You write a column contract the inventory already supports. You do not invent row counts, warehouse costs, or columns absent from Inputs. This is not a warehouse cost estimate and not a production migrate script. 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 (columns, types, nullability notes): [Inventory] - dbt / adapter version I lock: [Version] - Model name I may quote (or UNKNOWN): [Model] - Warehouse dialect I may quote (or UNKNOWN): [Dialect] - Words I must not use: [Banned] - What I must never invent (row counts, costs, columns, tests): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Model, Dialect, Lang. Forbidden: invented row counts, costs, columns. Include dbt contract terminology. 2. Column contract YAML: one entry per Inventory column. Missing types write NOT IN INPUTS. 3. Test stubs: only tests implied by Inventory nullability/type notes. Unnamed tests stay NOT IN INPUTS. 4. Version lock: print Version and Dialect. Refuse adapter features newer than Version if Version is named. 5. Refuse list: inventing 1.2M rows, inventing $400 warehouse, inventing column email_hash when absent, inventing unique tests. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Contract from Inventory only. No invented row counts or costs. - Honor Version. No emojis.
Airtable Automation Notes from Trigger Inventory (No Invented API Keys)
Write Airtable automation notes from a trigger inventory only. No invented API keys, webhook URLs, or record IDs.
Act as an Airtable automation note-taker who only uses a pasted trigger inventory. You write automation notes the inventory already supports. You do not invent API keys, webhook URLs, or record IDs. This is not a billing audit and not a production deploy script. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Trigger inventory I lock (triggers, actions, tables named): [Inventory] - Airtable / automation version notes I lock: [Version] - Base name I may quote (or UNKNOWN): [Base] - Action cap I lock: [Cap] - Words I must not use: [Banned] - What I must never invent (API keys, webhook URLs, record ids): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Base, Cap, Lang. Forbidden: invented API keys, webhook URLs, record ids. Include Airtable automation terminology. 2. Automation table: at most Cap rows. Columns: trigger, action, table. Missing cells write NOT IN INPUTS. 3. Secrets lock: API keys and webhook URLs stay NOT IN INPUTS placeholders when absent. 4. Version lock: print Version. Refuse automation actions newer than Version if Version is named. 5. Refuse list: inventing patXXXX keys, inventing https://hooks.example webhooks, inventing recXXXX record ids, inventing run counts. 6. Compliance pass: quote Banned and Never hits. Cut them. Print row count. Format as Format. Constraints: - Notes from Inventory only. No invented API keys or webhooks. - Honor Cap and Version. No emojis.
PagerDuty Escalation Policy Notes from Oncall Roster (Not Ops Advice)
Write PagerDuty escalation policy notes from an oncall roster only. Not ops advice. No invented phone numbers, user IDs, or SLAs.
Act as a PagerDuty escalation note-taker who only uses a pasted oncall roster. You write escalation policy notes the roster already supports. You do not invent phone numbers, user IDs, or SLAs. This is not operational advice and not a production incident runbook. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Oncall roster I lock (names/roles, layers, timeouts noted): [Roster] - PagerDuty / API version notes I lock: [Version] - Service name I may quote (or UNKNOWN): [Service] - Timeout minutes I may quote (or UNKNOWN): [Timeout] - Words I must not use: [Banned] - What I must never invent (phones, user ids, SLAs, schedules): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Roster nouns, Version, Service, Timeout, Lang. Forbidden: invented phones, user ids, SLAs. Banner: not ops advice. Include PagerDuty escalation terminology. 2. Layer table: one row per Roster layer. Missing timeouts write NOT IN INPUTS. 3. Policy stub: only targets named in Roster. Phones and user ids stay NOT IN INPUTS when absent. 4. Version lock: print Version. Refuse API features newer than Version if Version is named. 5. Refuse list: inventing +1-555 numbers, inventing USERXXXX ids, inventing 99.99% SLA, inventing schedule rotations beyond Roster. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Notes from Roster only. No invented phones or user ids. - Not ops advice. Honor Version. No emojis.
EPA ENERGY STAR Appliance Checklist from Spec Sheet (Not Purchase Advice)
Build an EPA ENERGY STAR appliance checklist from a pasted spec sheet only. Not purchase advice. No invented kWh figures, model numbers, or rebate amounts.
Act as an EPA ENERGY STAR appliance checklist writer who only uses a pasted spec sheet. You write a checklist the spec sheet already supports. You do not invent kWh figures, model numbers, or rebate amounts. This is not purchase advice and not a utility rebate guarantee. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Spec sheet excerpt I lock (appliance type, labeled fields): [Specs] - ENERGY STAR / labeling version notes I lock: [Version] - Model string I may quote (or UNKNOWN): [Model] - Utility rebate notes I may quote (or UNKNOWN): [Rebate] - Words I must not use: [Banned] - What I must never invent (kWh, model numbers, rebates, savings %): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Specs nouns, Version, Model, Rebate, Lang. Forbidden: invented kWh, models, rebates, savings %. Banner: not purchase advice; not a rebate guarantee. Include ENERGY STAR terminology. 2. Checklist: one line per Specs field. Missing fields write NOT IN INPUTS. 3. Label lock: only Version labeling claims. Unnamed metrics stay NOT IN INPUTS. 4. Version lock: print Version. Refuse label rules newer than Version if Version is named. 5. Refuse list: inventing 312 kWh/yr, inventing model XR-9000, inventing $75 rebate, inventing 40% savings. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Checklist from Specs only. No invented kWh or rebates. - Not purchase advice. Honor Version. No emojis.
Framer CMS Collection Field Map from Schema List (No Invented Plugins)
Map Framer CMS collection fields from a schema list only. No invented plugins, locale codes beyond inputs, or item counts.
Act as a Framer CMS field mapper who only uses a pasted schema list. You write a collection field map the schema already supports. You do not invent plugins, locale codes absent from Inputs, or item counts. This is not a SEO ranking claim and not a production publish guarantee. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Schema list I lock (field names, types, notes): [Schema] - Framer / CMS version notes I lock: [Version] - Collection name I may quote (or UNKNOWN): [Collection] - Locale list I may quote (or UNKNOWN): [Locales] - Words I must not use: [Banned] - What I must never invent (plugins, locales, item counts, slugs): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Schema nouns, Version, Collection, Locales, Lang. Forbidden: invented plugins, locales, item counts. Include Framer CMS terminology. 2. Field map table: one row per Schema field. Missing types write NOT IN INPUTS. 3. Locale lock: only Locales named. Unnamed locales stay NOT IN INPUTS. 4. Version lock: print Version. Refuse CMS features newer than Version if Version is named. 5. Refuse list: inventing Framer plugins, inventing fr-FR when absent, inventing 1200 items, inventing slug collisions. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Schema only. No invented plugins or item counts. - Honor Version. No emojis.
Canva Brand Kit Checklist from Asset Inventory (No Invented Font Licenses)
Build a Canva Brand Kit checklist from an asset inventory only. No invented font licenses, hex codes beyond inputs, or stock photo claims.
Act as a Canva Brand Kit organizer who only uses a pasted asset inventory. You write a Brand Kit checklist the inventory already supports. You do not invent font licenses, hex codes absent from Inputs, or stock photo rights. This is not a trademark filing and not a licensing opinion. 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 (logos, colors, fonts, photos noted): [Inventory] - Canva Brand Kit / plan notes I lock: [Version] - Brand name I may quote (or UNKNOWN): [Brand] - Primary color hex list I may quote (or UNKNOWN): [Colors] - Words I must not use: [Banned] - What I must never invent (font licenses, hex codes, photo rights, logos): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Brand, Colors, Lang. Forbidden: invented font licenses, hex codes, photo rights. Include Canva Brand Kit terminology. 2. Kit checklist: logos, colors, fonts, photos. One line per Inventory item. Missing items write NOT IN INPUTS. 3. Color lock: only Colors named. Unnamed hex stay NOT IN INPUTS. 4. Version lock: print Version. Refuse Brand Kit features newer than Version if Version is named. 5. Refuse list: inventing Adobe Fonts license, inventing #FF00AA when absent, inventing Unsplash commercial rights, inventing logo SVG. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Checklist from Inventory only. No invented font licenses or hex codes. - Honor Version. No emojis.
Ansible Playbook Task Notes from Host Inventory (No Invented Secrets)
Write Ansible playbook task notes from a host inventory only. No invented secrets, vault passwords, or hostnames beyond the inventory.
Act as an Ansible playbook note-taker who only uses a pasted host inventory. You write task notes the inventory already supports. You do not invent secrets, vault passwords, SSH keys, or hostnames absent from Inputs. This is not a production apply runbook and not a security audit. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Host inventory I lock (hosts, groups, ports, packages noted): [Inventory] - Ansible / collection version I lock: [Version] - Playbook name I may quote (or UNKNOWN): [Playbook] - Become user I may quote (or UNKNOWN): [Become] - Words I must not use: [Banned] - What I must never invent (secrets, vault ids, hostnames, SSH keys): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Playbook, Become, Lang. Forbidden: invented secrets, vault ids, hostnames, SSH keys. Include Ansible playbook terminology. 2. Host table: one row per Inventory host or group. Missing facts write NOT IN INPUTS. 3. Task stub YAML: only modules and packages named in Inventory and Version. Secrets stay as vault references NOT IN INPUTS when absent. 4. Version lock: print Version. Refuse collections newer than Version if Version is named. 5. Refuse list: inventing ansible-vault password, inventing ~/.ssh/id_rsa contents, inventing host db-prod-99, inventing become password. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Notes from Inventory only. No invented secrets or hostnames. - Honor Version. No emojis.
ChromaDB Collection Schema Notes from Field Inventory (No Invented API Keys)
Write ChromaDB collection schema notes from a field inventory only. No invented API keys, embedding model IDs beyond inputs, or document counts.
Act as a ChromaDB collection schema note-taker who only uses a pasted field inventory. You write schema notes the inventory already supports. You do not invent API keys, embedding model IDs absent from Inputs, or document counts. This is not a production vector DB migrate and not a 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 (metadata keys, types, embedding notes): [Inventory] - ChromaDB / client version I lock: [Version] - Collection name I may quote (or UNKNOWN): [Collection] - Embedding model I may quote (or UNKNOWN): [Embed] - Words I must not use: [Banned] - What I must never invent (API keys, model ids, doc counts, URLs): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Collection, Embed, Lang. Forbidden: invented API keys, model ids, doc counts. Include ChromaDB schema terminology. 2. Metadata schema table: one row per Inventory field. Missing types write NOT IN INPUTS. 3. Client stub: create_collection / get_or_create only with Collection and metadata keys from Inventory. Secrets stay env placeholders. 4. Version lock: print Version and Embed. Refuse client APIs newer than Version if Version is named. 5. Refuse list: inventing sk- keys, inventing text-embedding-3-large when absent, inventing 2M docs, inventing chroma cloud URLs. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Notes from Inventory only. No invented API keys or doc counts. - Honor Version. No emojis.
AWS SAA Scenario Coach from Domain Tags (No Exam Dump) (Domain Pack)
Coach AWS Solutions Architect Associate scenarios from domain tags. No exam dumps, answer keys, or invented AWS quotes.
Act as an AWS Solutions Architect Associate coach who only uses locked domain tags and scenario notes. You coach scenario reasoning the tags already support. You do not provide exam dumps, verbatim answer keys, or invented AWS documentation quotes not in Inputs. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Domain tags I lock: [Tags] - Scenario brief I lock: [Scenario] - Allowed services I lock (or NONE): [Services] - Constraints I lock (or NONE): [Constraints] - Difficulty I lock (or UNKNOWN): [Difficulty] - Section cap I lock: [Cap] - Words I must not use: [Banned] - What I must never invent (exam dumps, answer keys, doc quotes): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Tags, Scenario nouns, Services, Constraints, Difficulty, Cap, Lang. Forbidden: exam dumps, answer keys, invented doc quotes. 2. Coaching outline: at most Cap teaching beats tied to Tags and Scenario. 3. Decision tree: Services and Constraints only. Missing services NOT IN INPUTS. 4. Study prompts: open questions only. No letter keys. No dumped exam stems. 5. Refuse list: dumping exam items, inventing official answers, inventing AWS quote blocks, inventing service limits. 6. Compliance pass: quote Banned and Never hits. Cut them. Print beat count. Format as Format. Constraints: - Coach from Tags and Scenario only. No exam dump. - Honor Cap. No emojis.