Browse Prompts
1009 prompts available · Page 6 of 85
Terraform Module README from Variable Inventory (No Invented Providers) (Domain Pack)
Write a Terraform module README from a variable inventory. No invented providers, resources, or versions.
Act as a Terraform README author who only uses a locked variable 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): [VarInventory] - 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: 0. Terraform module README from variable inventory must document variables before providers from Inputs. 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.
Terraform Module README from Resource Inventory (No Invented Providers) (Domain Pack)
Draft a Terraform module README from a resource inventory. No invented providers, versions, or resources.
Act as a Terraform docs engineer 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: 0. Terraform module README from resource inventory must lock providers and resources from Inputs. 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.
Google Ads RSA Pack from Offer Facts (No Invented CTR) (Domain Pack)
Build Google Ads Responsive Search Ad headlines and descriptions from offer facts. No invented CTR or reviews.
Act as a Google Ads RSA copywriter who only uses locked offer facts. You build a RSA pack 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: [OfferFacts] - Our product name I lock: [Headlines] - Competitor name I lock: [Descriptions] - Objection list I lock (or NONE): [Keywords] - Proof points I lock (or NONE): [Landing] - 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: 0. Google Ads RSA pack must draft headlines and descriptions from offer facts without CTR claims outside Inputs. 1. Honesty ledger: Matrix nouns, Ours, Competitor, Objections, Proof, Cap, Lang. Forbidden: invented claims, win rates, quotes, prices Include Google Ads, RSA, headlines, CTR terminology. 2. Battlecard sections: at most Cap. Landmines and differentiators from Matrix only (tool focus: Google Ads, RSA, headlines, CTR). 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.
GitHub Actions Reusable Workflow from Job Inventory (No Invented Secrets) (Domain Pack)
Draft a GitHub Actions reusable workflow from a job inventory. No invented secrets, tokens, or runner labels.
Act as a GitHub Actions reusable workflow author who only uses a locked job inventory. You emit reusable 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: [WorkflowInputs] - Secrets allowlist I lock (or NONE): [Secrets] - Runner I lock (or UNKNOWN): [Runner] - Action pins I lock (or NONE): [WorkflowOutputs] - 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: 0. GitHub Actions reusable workflow must declare workflow_call inputs and secrets only from Inputs. 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.
dbt Model Docs from Column Inventory (No Invented Sources) (Domain Pack)
Write dbt model documentation from a column inventory. No invented sources, tests, or lineage edges.
Act as a dbt documentation specialist who only uses a locked column inventory. You write dbt model docs 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): [Columns] - Variables map I lock (or NONE): [Model] - Outputs map I lock (or NONE): [Sources] - Providers I lock (or UNKNOWN): [Tests] - Example usage notes I lock (or NONE): [Meta] - 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: 0. dbt model docs must document columns and sources only from the column inventory Inputs. 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.
Continue.dev Config Notes from Repo Conventions (No Invented Paths) (Domain Pack)
Draft Continue.dev config notes from repo conventions. No invented paths, secrets, or model versions beyond Inputs.
Act as a Continue.dev config notes author who only uses locked repo conventions. You write Continue.dev config notes the conventions already support. 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: 0. Continue.dev config notes must cite repo conventions and paths from Inputs. 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.
Continue.dev Config from Stack Brief (No Invented Models) (Domain Pack)
Draft a Continue.dev config from a stack brief. No invented models, providers, or secrets.
Act as a Continue.dev config author who only uses a locked stack brief. 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: 0. Continue.dev config from stack brief must name models and providers only from Inputs. 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.
Claude Projects System Prompt from Role Pack (No Invented Tools) (Domain Pack)
Build a Claude Projects system prompt from a role pack. No invented tools or capabilities.
Act as a Claude Projects system prompt engineer who only uses a locked role pack. You write agent instructions the brief already supports. You do not invent shell commands, git hooks, MCP tools, or repo paths 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 brief I lock: [RepoBrief] - Stack I lock: [Stack] - Paths I may name: [Paths] - Commands I may quote: [Commands] - Agent duties I lock (or NONE): [Duties] - Section cap I lock: [Cap] - Words I must not use: [Banned] - What I must never invent (commands, hooks, MCP tools, paths): [Never] - Output format: [Format] - Language: [Lang] Generate: 0. Claude Projects system prompt must list tools and knowledge only from the role pack Inputs. 1. Honesty ledger: RepoBrief nouns, Stack, Paths, Commands, Duties, Cap, Lang. Forbidden: invented commands, hooks, MCP tools, paths. 2. AGENTS.md outline: at most Cap sections. 3. AGENTS.md body: purpose, stack, paths, commands, duties from Inputs only. 4. Guardrails: refuse inventing hooks or MCP servers; mark unknowns NOT IN INPUTS. 5. Refuse list: inventing husky hooks, inventing mcp.json, inventing make release, inventing apps/admin. 6. Compliance pass: quote Banned and Never hits. Cut them. Print section count. Format as Format. Constraints: - AGENTS.md from RepoBrief only. No invented commands. - Honor Cap. No emojis.
Asana Project Template from Workflow Brief (No Invented Assignees) (Domain Pack)
Turn a workflow brief into an Asana project template with sections and task stubs. No invented assignees, due dates, or custom fields.
Act as an Asana workflow template designer who only uses a locked workflow brief. 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: 0. Asana project template must use workflow brief sections and tasks without assignees outside Inputs. 1. Honesty ledger: Matrix nouns, Partner, Ours, Offer, Cta, Cap, Lang. Forbidden: invented logos, quotes, win rates, certs Include Asana, template, workflow, assignees terminology. 2. One-pager outline: at most Cap sections from Matrix and Offer (tool focus: Asana, template, workflow, assignees). 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.
Asana Project Charter from Scope Notes (No Invented Dates) (Domain Pack)
Build an Asana project charter from locked scope notes. No invented dates, owners, or budgets.
Act as an Asana project charter writer who only uses locked scope notes. 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: 0. Asana project charter must use scope notes, goals, and dates only from Inputs. 1. Honesty ledger: Matrix nouns, Category, Audience, Named, Cap, Lang. Forbidden: invented reviews, stars, quotes, logos Include Asana, charter, scope, dates terminology. 2. Page outline: at most Cap H2 sections from Matrix only (tool focus: Asana, charter, scope, dates). 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.
Aider Convention Notes from Repo Patterns (No Invented Paths) (Domain Pack)
Draft Aider convention notes from repo patterns. No invented paths, secrets, or tool versions beyond Inputs.
Act as an Aider convention notes librarian who only uses locked repo patterns. You draft convention notes Aider can load for pair sessions from repo patterns. You do not add shell commands, paths, package managers, or CI jobs 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 (layout, naming, modules): [RepoPatterns] - Stack I lock (languages, frameworks, versions if any): [Stack] - Paths I may name (or NONE): [Paths] - Hook notes I lock (or NONE): [Hooks] - Test and lint notes I lock (or NONE): [Tests] - Section cap I lock: [Cap] - Words I must not use: [Banned] - What I must never invent (paths, versions, commands, hooks): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: RepoPatterns nouns, Stack, Paths, Hooks, Tests, Cap, Lang. Forbidden: paths, versions, commands, hooks outside Inputs. 2. Convention notes outline: at most Cap H2 sections from RepoPatterns only. 3. Notes body: quote Stack, Paths, Hooks, Tests. Missing items write NOT IN INPUTS. 4. Aider load notes: how to attach these convention notes; do not add slash-commands outside Inputs. 5. Refuse list: npm run build invent, src/lib invent, pre-commit invent, Python 3.13 invent. 6. Compliance pass: quote Banned and Never hits. Cut them. Print section count. Format as Format. Constraints: - Convention notes from RepoPatterns only. No paths outside Inputs. - Honor Cap. No emojis.
Cursor Rules File from Repo Conventions (No Invented Paths) (Domain Pack)
Draft a Cursor rules file from repo conventions. No invented paths or tool claims.
Act as a Cursor rules librarian who only uses locked repo conventions. You draft a Cursor rules file the conventions already support. You do not invent filesystem paths, tool claims, or commands 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 conventions I lock (dirs, style, review rules): [Conventions] - Paths allowlist I lock: [Paths] - Commands allowlist I lock (or NONE): [Commands] - Stack I lock: [Stack] - Cursor rules filename I may quote (or UNKNOWN): [RulesFile] - Section cap I lock: [Cap] - Words I must not use: [Banned] - What I must never invent (paths, commands, tools, secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Conventions nouns, Paths, Commands, Stack, RulesFile, Cap, Lang. Forbidden: invented paths, commands, tools, secrets. 2. Rules outline: at most Cap sections grounded in Conventions. 3. Path and command tables: only Paths and Commands rows. Missing write NOT IN INPUTS. 4. Cursor rules body: paste-ready rules scoped to Paths; RulesFile UNKNOWN stays unknown. 5. Refuse list: inventing rule file paths not listed, inventing scripts not in Commands, inventing undeclared dirs. 6. Compliance pass: quote Banned and Never hits. Cut them. Print counts. Format as Format. Constraints: - Rules from Conventions only. No invented paths. - Honor Cap. No emojis.