Browse Prompts

1018 prompts available ยท Page 10 of 85

Cloudflare Workers wrangler.toml Binding Notes from Binding Inventory (No Invented Secrets)
๐Ÿ’ป Coding

Cloudflare Workers wrangler.toml Binding Notes from Binding Inventory (No Invented Secrets)

PpromptstudioยทSep 6, 2026
No rating

Write Cloudflare Workers wrangler.toml binding notes from a binding inventory only. No invented secrets, account IDs, or KV namespaces.

Act as a Cloudflare Workers config note-taker who only uses a pasted binding inventory. You write wrangler.toml binding notes the inventory already supports. You do not invent secrets, account IDs, KV namespace IDs, or R2 bucket names. This is not a production deploy script and not an account audit. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Binding inventory I lock (binding names, types, notes): [Inventory] - Wrangler / Workers compatibility date or version I lock: [Version] - Worker name I may quote (or UNKNOWN): [Worker] - Words I must not use: [Banned] - What I must never invent (secrets, account ids, namespace ids, bucket names): [Never] - Output format: [Format] - Language: [Lang] - Environment name I may quote (or UNKNOWN): [Env] Generate: 1. Honesty ledger: Inventory nouns, Version, Worker, Env, Lang. Forbidden: invented secrets, account ids, namespace ids, bucket names. 2. Binding table: one row per Inventory binding. Missing ids write NOT IN INPUTS. 3. wrangler.toml stub: only sections supported by Inventory and Version. Placeholders for secrets stay NOT IN INPUTS comments, never fake values. 4. Version lock: print Version. Refuse APIs newer than Version if Version is named. 5. Refuse list: inventing ACCOUNT_ID, inventing a KV id, inventing API tokens, inventing .dev domain secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Notes from Inventory only. No invented secrets or account ids. - Honor Version. No emojis.

no invented secretswrangler.tomlworkers bindings
ISO 9001 Nonconformance Report (NCR) Draft from Deviation Notes (Not Audit Opinion)
๐Ÿ’ผ Business

ISO 9001 Nonconformance Report (NCR) Draft from Deviation Notes (Not Audit Opinion)

PpromptstudioยทSep 6, 2026
No rating

Draft an ISO 9001 NCR from deviation notes only. Not an audit opinion. No invented clause cites, CAPA owners, or dates.

Act as a quality-system NCR clerk who only uses pasted deviation notes. You draft a nonconformance report the notes already support. You do not invent ISO clause numbers, CAPA owners, root causes, or due dates. This is not an audit opinion, not a certification decision, and not legal advice. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Deviation notes I lock: [Notes] - ISO 9001 edition I lock (or UNKNOWN): [Edition] - NCR ID I may quote (or UNKNOWN): [NcrId] - Words I must not use: [Banned] - What I must never invent (clause cites, owners, root causes, due dates): [Never] - Output format: [Format] - Language: [Lang] - Product or process name I may quote (or UNKNOWN): [Process] Generate: 1. Honesty ledger: Notes nouns, Edition, NcrId, Process, Lang. Forbidden: invented clauses, owners, root causes, due dates. Banner: not an audit opinion; not a certification decision. 2. NCR draft sections: description of nonconformity from Notes only; immediate containment if present; else NOT IN INPUTS. 3. Clause map: only if Edition and a clause appear in Notes; otherwise write clause NOT IN INPUTS. 4. CAPA stub: owner, root cause, due date stay NOT IN INPUTS unless present in Notes. 5. Refuse list: inventing 8.7, inventing a MRB chair, inventing a 30-day due date, inventing a certificate number. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - NCR from Notes only. Not an audit opinion. - Honor Edition. No emojis.

deviation notesiso 9001 ncrnot audit opinion
Terraform Module README from Resource Inventory (No Invented Defaults) (Domain Pack)
๐Ÿ’ป Coding

Terraform Module README from Resource Inventory (No Invented Defaults) (Domain Pack)

PpromptstudioยทSep 6, 2026
No rating

Write a Terraform module README from a resource inventory. No invented defaults, providers, or secret values.

Act as a Terraform docs writer who only uses a locked resource inventory. You write module README sections the inventory already supports. You do not invent default values, provider versions, secret literals, or resources 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: - Resource inventory I lock (resource types, names, notes): [Resources] - Variables map I lock (or NONE): [Vars] - Outputs map I lock (or NONE): [Outputs] - Providers I lock (or UNKNOWN): [Providers] - Example usage notes I lock (or NONE): [Example] - Section cap I lock: [Cap] - Words I must not use: [Banned] - What I must never invent (defaults, providers, secrets, resources): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Resources nouns, Vars, Outputs, Providers, Example, Cap, Lang. Forbidden: invented defaults, providers, secrets, resources. 2. README outline: at most Cap H2 sections. 3. Resources / Variables / Outputs tables: only inventory rows. Missing defaults write NOT IN INPUTS. 4. Providers and example: Providers and Example only; omit fake terraform block versions. 5. Refuse list: inventing default numbers, inventing provider versions if unnamed, inventing access key literals, inventing extra resources. 6. Compliance pass: quote Banned and Never hits. Cut them. Print section count. Format as Format. Constraints: - README from Resources only. No invented defaults. - Honor Cap. No emojis.

resource inventoryterraform readmeno invented defaults
Partner One-Pager from Capability Matrix (No Invented Logos) (Domain Pack)
๐Ÿ“ข Marketing

Partner One-Pager from Capability Matrix (No Invented Logos) (Domain Pack)

PpromptstudioยทSep 6, 2026
No rating

Draft a partner one-pager from a capability matrix. No invented logos, customer quotes, or win rates.

Act as a partner marketing writer who only uses a locked capability matrix. You draft a one-pager the matrix already supports. You do not invent partner logos, customer quotes, win rates, or certifications 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: - Capability matrix I lock: [Matrix] - Partner name I lock: [Partner] - Our name I lock: [Ours] - Offer bullets I lock (or NONE): [Offer] - CTA I lock (or UNKNOWN): [Cta] - Section cap I lock: [Cap] - Words I must not use: [Banned] - What I must never invent (logos, quotes, win rates, certs): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Matrix nouns, Partner, Ours, Offer, Cta, Cap, Lang. Forbidden: invented logos, quotes, win rates, certs. 2. One-pager outline: at most Cap sections from Matrix and Offer. 3. Capability bullets: matrix cells only. Empty cells NOT IN INPUTS. 4. Logo and quote slots: write NOT IN INPUTS rather than inventing assets. 5. Refuse list: inventing a partner logo file, inventing attach rates, inventing a customer quote, inventing certification seals. 6. Compliance pass: quote Banned and Never hits. Cut them. Print section count. Format as Format. Constraints: - One-pager from Matrix only. No invented logos. - Honor Cap. No emojis.

partner one-pagercapability matrixno invented logos
OpenAI Codex CLI Conventions from Repo Patterns (No Invented Paths) (Domain Pack)
๐Ÿค– AI Tools

OpenAI Codex CLI Conventions from Repo Patterns (No Invented Paths) (Domain Pack)

PpromptstudioยทSep 6, 2026
No rating

Draft OpenAI Codex CLI convention notes from repo patterns only. No invented paths or model tags.

Act as an OpenAI Codex CLI conventions librarian who only uses locked repo patterns. You write convention notes Codex CLI can follow from the patterns already present. You do not invent filesystem paths, model tags, or tool permissions 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: - Repo patterns I lock (dirs, file types, style notes): [Patterns] - Stack I lock: [Stack] - Paths allowlist I lock: [Paths] - Commands allowlist I lock (or NONE): [Commands] - Model tag I may quote (or UNKNOWN): [Model] - Section cap I lock: [Cap] - Words I must not use: [Banned] - What I must never invent (paths, models, secrets, permissions): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Patterns nouns, Stack, Paths, Commands, Model, Cap, Lang. Forbidden: invented paths, models, secrets, permissions. 2. Conventions outline: at most Cap sections grounded in Patterns. 3. Path and command tables: only Paths and Commands rows. Missing write NOT IN INPUTS. 4. Codex CLI notes: how to scope edits; Model UNKNOWN stays unknown. 5. Refuse list: inventing config keys, inventing model tags if unnamed, inventing secrets paths, inventing src/internal. 6. Compliance pass: quote Banned and Never hits. Cut them. Print counts. Format as Format. Constraints: - Notes from Patterns only. No invented paths. - Honor Cap. No emojis.

repo patternscodex cli conventionsno invented paths
GitHub Actions Workflow from Job Inventory (No Invented Secrets) (Domain Pack)
๐Ÿ’ป Coding

GitHub Actions Workflow from Job Inventory (No Invented Secrets) (Domain Pack)

PpromptstudioยทSep 6, 2026
No rating

Generate a GitHub Actions workflow from a job inventory. No invented secrets, runners, or orgs.

Act as a GitHub Actions workflow author who only uses a locked job inventory. You emit workflow YAML the inventory already supports. You do not invent secret names, runner labels, environments, or organization slugs 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: - Job inventory I lock (job ids, steps, needs): [Jobs] - Trigger I lock: [Trigger] - Secrets allowlist I lock (or NONE): [Secrets] - Runner I lock (or UNKNOWN): [Runner] - Action pins I lock (or NONE): [Actions] - Job cap I lock: [Cap] - Words I must not use: [Banned] - What I must never invent (secrets, runners, orgs, environments): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Jobs nouns, Trigger, Secrets, Runner, Actions, Cap, Lang. Forbidden: invented secrets, runners, orgs, environments. 2. Workflow YAML: at most Cap jobs from Jobs. Missing steps write # NOT IN INPUTS. 3. Secrets and env: only Secrets names. NONE means omit secrets blocks. 4. Needs graph: only needs edges listed in Jobs. 5. Refuse list: inventing cloud key secrets, inventing larger runners, inventing environment production, inventing org names. 6. Compliance pass: quote Banned and Never hits. Cut them. Print job count. Format as Format. Constraints: - YAML from Jobs only. No invented secrets. - Honor Cap and Trigger. No emojis.

github actions workflowno invented secretsjob inventory
GitHub Actions Workflow Comments from Pipeline Inventory (No Invented Secrets) (Domain Pack)
๐Ÿ’ป Coding

GitHub Actions Workflow Comments from Pipeline Inventory (No Invented Secrets) (Domain Pack)

PpromptstudioยทSep 6, 2026
No rating

Annotate a GitHub Actions workflow from a pipeline inventory. No invented secrets, runners, or action versions.

Act as a GitHub Actions reviewer who only uses a locked pipeline inventory. You write YAML comments and review notes the inventory already supports. You do not invent secret names, runner labels, action SHAs, or environments 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: - Pipeline inventory I lock (jobs, steps, triggers): [Inventory] - Secrets allowlist I lock (or NONE): [Secrets] - Runner labels I lock (or UNKNOWN): [Runners] - Action pins I lock (or NONE): [Actions] - Comment cap I lock: [Cap] - Words I must not use: [Banned] - What I must never invent (secrets, runners, action versions, orgs): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Secrets, Runners, Actions, Cap, Lang. Forbidden: invented secrets, runners, action versions, orgs. 2. Workflow skeleton with comments: only jobs and steps in Inventory. Missing write NOT IN INPUTS comments. 3. Secrets and runners notes: quote Secrets and Runners only. 4. Action pin table: Actions only. Unpinned stay NOT IN INPUTS. 5. Refuse list: inventing secret names, inventing runner labels if unnamed, inventing action tags if unpinned, inventing org names. 6. Compliance pass: quote Banned and Never hits. Cut them. Print comment count vs Cap. Format as Format. Constraints: - Comments from Inventory only. No invented secrets. - Honor Cap. No emojis.

no invented secretspipeline inventorygithub actions comments
G2 Category Page Outline from Feature Matrix (No Invented Reviews) (Domain Pack)
๐Ÿ“ข Marketing

G2 Category Page Outline from Feature Matrix (No Invented Reviews) (Domain Pack)

PpromptstudioยทSep 6, 2026
No rating

Outline a G2-style category page from a feature matrix. No invented reviews, star ratings, or competitor quotes.

Act as a G2-style category page outliner who only uses a locked feature matrix. You write page outlines the matrix already supports. You do not invent star ratings, review quotes, competitor claims, or logos 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: - Feature matrix I lock (products x features): [Matrix] - Category name I lock (or UNKNOWN): [Category] - Audience I lock (or UNKNOWN): [Audience] - Section cap I lock: [Cap] - Words I must not use: [Banned] - What I must never invent (reviews, stars, quotes, logos): [Never] - Output format: [Format] - Language: [Lang] - Competitors named in matrix only: [Named] Generate: 1. Honesty ledger: Matrix nouns, Category, Audience, Named, Cap, Lang. Forbidden: invented reviews, stars, quotes, logos. 2. Page outline: at most Cap H2 sections from Matrix only. 3. Comparison bullets: only cells present in Matrix. Empty cells NOT IN INPUTS. 4. Review placeholders: write NOT IN INPUTS rather than inventing quotes or stars. 5. Refuse list: inventing star ratings, inventing a badge, inventing a customer quote, inventing a logo URL. 6. Compliance pass: quote Banned and Never hits. Cut them. Print section count. Format as Format. Constraints: - Outline from Matrix only. No invented reviews. - Honor Cap. No emojis.

no invented reviewsfeature matrixg2 category outline
Flux Product Packshot Prompt from a SKU Brief (No Logos or Fake Labels) (Domain Pack)
๐ŸŽฏ Design

Flux Product Packshot Prompt from a SKU Brief (No Logos or Fake Labels) (Domain Pack)

PpromptstudioยทSep 6, 2026
No rating

Compile a Flux product packshot prompt from a SKU brief. No logos, fake labels, or celebrities.

Act as a Flux product packshot prompt engineer who only uses a locked SKU brief. You compile a paste-ready packshot prompt the brief already supports. You do not invent logos, fake nutrition or warning labels, celebrity likenesses, or SKUs 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: - SKU brief I lock: [Sku] - Label policy I lock (what text may appear): [LabelPolicy] - Surface I lock: [Surface] - Light I lock: [Light] - Lens look I lock (or UNKNOWN): [Lens] - Negative tokens I lock: [Neg] - Aspect ratio I lock: [Aspect] - Brand ban list I lock: [BrandBan] - Word cap for the Flux prompt block: [Cap] - Words I must not use: [Banned] - What I must never invent (logos, fake labels, celebs, SKUs): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Sku nouns, LabelPolicy, Surface, Light, Lens, Aspect, BrandBan, Cap, Lang. Forbidden: logos, fake labels, celebs, invented SKUs. 2. SKU lock and label policy: quote Sku; apply LabelPolicy. Any banned label text write REFUSED. 3. Studio plan: Surface, Light, Lens only. 4. Flux prompt block: paste-ready under Cap with Aspect. No fake labels. 5. Negatives and refuse: Neg, BrandBan, and LabelPolicy violations. 6. Compliance pass: quote Banned and Never hits. Cut them. Print counts. Format as Format. Constraints: - Packshot from Sku only. No logos or fake labels. - Honor Aspect, Cap, LabelPolicy. No emojis.

sku briefflux packshotno fake labels
Flux Product Hero Prompt from SKU Notes (No Logos or Celebs) (Domain Pack)
๐ŸŽฏ Design

Flux Product Hero Prompt from SKU Notes (No Logos or Celebs) (Domain Pack)

PpromptstudioยทSep 6, 2026
No rating

Compile a paste-ready Flux product hero prompt from locked SKU notes. No logos, celebrities, or invented brand marks.

Act as a Flux packshot and hero prompt engineer who only uses locked SKU notes. You compile a paste-ready Flux hero image prompt the notes already support. You do not invent logos, celebrity likenesses, fake brand marks, or labels 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: - SKU notes I lock (product, color, finish, props): [Sku] - Surface and backdrop I lock: [Surface] - Light recipe I lock: [Light] - Camera and lens I lock (or UNKNOWN): [Lens] - Negative tokens I lock: [Neg] - Aspect ratio I lock: [Aspect] - Brand and logo ban list I lock: [BrandBan] - Word cap for the Flux prompt block: [Cap] - Words I must not use: [Banned] - What I must never invent (logos, celebs, fake labels, hex codes): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Sku nouns, Surface, Light, Lens, Aspect, BrandBan, Cap, Lang. Forbidden: logos, celebs, fake labels, invented hex. 2. Locked facts block: quote Sku, Surface, Light only. Missing fields write NOT IN INPUTS. 3. Camera and light plan: Lens and Light only. Unknown focal length stays NOT IN INPUTS. 4. Flux prompt block: paste-ready single paragraph under Cap words. Include Aspect. No readable logos. 5. Negatives: merge Neg with BrandBan. Refuse logos and celebrity likenesses. 6. Compliance pass: quote Banned and Never hits. Cut them. Print word count vs Cap. Format as Format. Constraints: - Hero prompt from Sku only. No logos or celebs. - Honor Aspect and Cap. No emojis.

sku notesflux hero promptno logos celebs
Flux Packshot Prompt from Product Attributes (No Logos or Celebs) (Domain Pack)
๐ŸŽฏ Design

Flux Packshot Prompt from Product Attributes (No Logos or Celebs) (Domain Pack)

PpromptstudioยทSep 6, 2026
No rating

Compile a Flux packshot prompt from locked product attributes. No logos, celebrities, or invented brand marks.

Act as a Flux packshot prompt engineer who only uses locked product attributes. You compile a paste-ready catalog packshot prompt the attributes already support. You do not invent logos, celebrity likenesses, fake barcodes, or materials 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: - Product attributes I lock (shape, material, color, size cue): [Attrs] - Packshot surface I lock: [Surface] - Light setup I lock: [Light] - Camera height and angle I lock (or UNKNOWN): [Angle] - Negative tokens I lock: [Neg] - Aspect ratio I lock: [Aspect] - Brand ban list I lock: [BrandBan] - Word cap for the Flux prompt block: [Cap] - Words I must not use: [Banned] - What I must never invent (logos, celebs, barcodes, materials): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Attrs nouns, Surface, Light, Angle, Aspect, BrandBan, Cap, Lang. Forbidden: logos, celebs, barcodes, invented materials. 2. Attribute lock: quote Attrs only. Missing size or finish write NOT IN INPUTS. 3. Studio plan: Surface, Light, Angle only. Unknown stand height stays NOT IN INPUTS. 4. Flux prompt block: paste-ready packshot under Cap words with Aspect. 5. Negatives: Neg plus BrandBan. Refuse logos and celebs. 6. Compliance pass: quote Banned and Never hits. Cut them. Print counts. Format as Format. Constraints: - Packshot from Attrs only. No logos or celebs. - Honor Aspect and Cap. No emojis.

no logosproduct attributesflux packshot
Competitor Battlecard from Feature Matrix (No Invented Claims) (Domain Pack)
๐Ÿ“ข Marketing

Competitor Battlecard from Feature Matrix (No Invented Claims) (Domain Pack)

PpromptstudioยทSep 6, 2026
No rating

Build a competitor battlecard from a feature matrix. No invented claims or win rates.

Act as a competitive enablement writer who only uses a locked feature matrix. You build a battlecard the matrix already supports. You do not invent win rates, pricing claims, customer quotes, or features 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: - Feature matrix I lock: [Matrix] - Our product name I lock: [Ours] - Competitor name I lock: [Competitor] - Objection list I lock (or NONE): [Objections] - Proof points I lock (or NONE): [Proof] - Section cap I lock: [Cap] - Words I must not use: [Banned] - What I must never invent (claims, win rates, quotes, prices): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Matrix nouns, Ours, Competitor, Objections, Proof, Cap, Lang. Forbidden: invented claims, win rates, quotes, prices. 2. Battlecard sections: at most Cap. Landmines and differentiators from Matrix only. 3. Talk tracks: only for Objections present; else NOT IN INPUTS. 4. Proof table: Proof only. Missing metrics stay NOT IN INPUTS. 5. Refuse list: inventing win rates, inventing analyst quotes, inventing prices, inventing feature cells. 6. Compliance pass: quote Banned and Never hits. Cut them. Print section count. Format as Format. Constraints: - Battlecard from Matrix only. No invented claims. - Honor Cap. No emojis.

feature matrixcompetitor battlecardno invented claims