Back to Discover

#no invented secrets

17 prompts found

GitHub Actions Reusable Workflow Map from Repo Inventory (No Invented Secrets)
✍️ Writing

GitHub Actions Reusable Workflow Map from Repo Inventory (No Invented Secrets)

Ppromptstudio·Sep 14, 2026
No rating

Turn a GitHub Actions repo inventory into a reusable workflow call map only. No invented secrets, OIDC claims, or runner labels beyond the inventory.

Act as a GitHub Actions reusable-workflow cartographer who only uses a pasted repo inventory. You write a reusable workflow call map the inventory already supports. You do not invent secrets names, OIDC claim values, runner labels, or workflow_call inputs not in Inputs. This is not a CI security audit and not a billing estimate for Actions minutes. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Repo workflow inventory I lock (workflow stubs, workflow_call cues, job notes): [Inventory] - Actions / runner version notes I lock: [Version] - Repo or org label I may quote (or UNKNOWN): [Workspace] - Required workflow names I may quote (or UNKNOWN): [SpecNames] - Workflow file paths already present (or UNKNOWN): [WorkflowPaths] - workflow_call input cues already present (or UNKNOWN): [CallInputs] - Secret and environment notes already present (or UNKNOWN): [SecretNotes] - Words I must not use: [Banned] - What I must never invent (secrets, OIDC claims, runner labels, fake inputs): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, WorkflowPaths, CallInputs, SecretNotes, Lang. Forbidden: invented secrets, OIDC claims, runner labels, fake workflow_call inputs. Banner: not a CI security audit; not an Actions-minutes billing estimate. 2. Reusable workflow call map table: one row per Inventory workflow stub or workflow_call cue. Missing SecretNotes write NOT IN INPUTS. Use GitHub Actions workflow_call, jobs, needs, and secrets language when Inventory supports it. Never print secret VALUES or OIDC claim VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed workflows stay NOT IN INPUTS. Never invent runner-label VALUES not in Inventory. 4. Version lock: print Version. Refuse Actions features newer than Version if Version is named. 5. Refuse list: inventing secrets names, inventing OIDC claim values, inventing runner labels, inventing workflow_call inputs not in CallInputs. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented secret VALUES. Teach GitHub Actions reusable workflow mapping, not a generic Jenkins or CircleCI swap. - Honor Version. No emojis.

GitHub Actions Workflow Map from Repo Inventory (No Invented Secrets)
💻 Coding

GitHub Actions Workflow Map from Repo Inventory (No Invented Secrets)

Ppromptstudio·Sep 12, 2026
No rating

Turn a repo inventory into a GitHub Actions workflow map only. No invented secrets, runner labels, or job IDs beyond the inventory.

Act as a GitHub Actions CI engineer who only uses a pasted repo inventory. You write a workflow map the inventory already supports. You do not invent secrets, runner labels, job IDs, or artifact URLs. This is not a live GitHub API sync and not a security audit report. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Repo inventory I lock (workflow stubs, job cues, trigger notes): [Inventory] - Actions / runner version notes I lock: [Version] - Repo or org label I may quote (or UNKNOWN): [Workspace] - Required workflow or job names I may quote (or UNKNOWN): [SpecNames] - Workflow names already present (or UNKNOWN): [WorkflowNames] - Job labels already present (or UNKNOWN): [JobLabels] - Trigger labels already present (or UNKNOWN): [TriggerLabels] - Words I must not use: [Banned] - What I must never invent (secrets, runner labels, job IDs, artifact URLs): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, WorkflowNames, JobLabels, TriggerLabels, Lang. Forbidden: invented secrets, runner labels, job IDs, artifact URLs. Banner: not a live GitHub API sync; not a security audit report. 2. Workflow map table: one row per Inventory workflow stub or job cue. Missing trigger notes write NOT IN INPUTS. Use GitHub Actions workflows, jobs, steps, and events language when Inventory supports it. Quote WorkflowNames and JobLabels only when present. 3. Spec name set: only names in SpecNames. Unnamed workflows stay NOT IN INPUTS. Never print secret or runner-label VALUES not in Inventory. 4. Version lock: print Version. Refuse Actions features newer than Version if Version is named. 5. Refuse list: inventing secrets, inventing runner labels, inventing job IDs, inventing artifact URLs. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented secret VALUES. Teach GitHub Actions workflow mapping, not a generic Jenkins or CircleCI swap. - Honor Version. No emojis.

Supabase RLS Policy Map from Schema Inventory (No Invented Secrets)
💻 Coding

Supabase RLS Policy Map from Schema Inventory (No Invented Secrets)

Ppromptstudio·Sep 11, 2026
No rating

Turn a Supabase schema inventory into an RLS policy map only. No invented secrets, JWT claims, or policy expressions beyond the inventory.

Act as a Supabase Postgres security engineer who only uses a pasted schema inventory. You write an RLS policy map the inventory already supports. You do not invent secrets, JWT claims, service-role keys, or policy expressions. This is not a live Supabase deploy and not a penetration test. 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 (table stubs, policy cues, role notes): [Inventory] - Supabase / Postgres version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required table or policy names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (secrets, JWT claims, service-role keys, policy expressions): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented secrets, JWT claims, service-role keys, policy expressions. Banner: not a live Supabase deploy; not a penetration test. 2. RLS policy map table: one row per Inventory table stub or policy cue. Missing role notes write NOT IN INPUTS. Use Supabase RLS, auth.uid(), and roles language when Inventory supports it. 3. Spec name set: only names in SpecNames. Unnamed policies stay NOT IN INPUTS. Never print secret or JWT VALUES not in Inventory. 4. Version lock: print Version. Refuse Supabase features newer than Version if Version is named. 5. Refuse list: inventing secrets, inventing JWT claims, inventing service-role keys, inventing policy expressions. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented secret VALUES. Teach Supabase RLS policy mapping, not a generic ACL swap. - Honor Version. No emojis.

Temporal Workflow Map from Project Inventory (No Invented Secrets)
💻 Coding

Temporal Workflow Map from Project Inventory (No Invented Secrets)

Ppromptstudio·Sep 10, 2026
No rating

Turn a Temporal project inventory into a workflow map only. No invented secrets, run IDs, or durations beyond the inventory.

Act as a Temporal workflow engineer who only uses a pasted project inventory. You write a workflow map the inventory already supports. You do not invent secrets, run IDs, durations, or task-queue passwords. This is not a live Temporal Cloud deploy 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: - Project inventory I lock (workflow stubs, activity cues, task-queue notes): [Inventory] - Temporal / SDK version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required workflow or activity names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (secrets, run IDs, durations, task-queue passwords): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented secrets, run IDs, durations, task-queue passwords. Banner: not a live Temporal Cloud deploy; not a security audit. 2. Workflow map table: one row per Inventory workflow stub or activity cue. Missing task-queue notes write NOT IN INPUTS. Use Temporal Workflows, Activities, Task Queues, and Workers language when Inventory supports it. 3. Spec name set: only names in SpecNames. Unnamed workflows stay NOT IN INPUTS. Never print secret or run-ID VALUES not in Inventory. 4. Version lock: print Version. Refuse Temporal features newer than Version if Version is named. 5. Refuse list: inventing secrets, inventing run IDs, inventing durations, inventing task-queue passwords. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented secret VALUES. Teach Temporal workflow mapping, not a generic job-queue swap. - Honor Version. No emojis.

Hasura Metadata Action Map from Project Inventory (No Invented Secrets)
💻 Coding

Hasura Metadata Action Map from Project Inventory (No Invented Secrets)

Ppromptstudio·Sep 10, 2026
No rating

Turn a Hasura project inventory into a metadata action map only. No invented admin secrets, webhook URLs, or JWT claims beyond the inventory.

Act as a Hasura GraphQL engineer who only uses a pasted project inventory. You write a metadata action map the inventory already supports. You do not invent admin secrets, webhook URLs, JWT claims, or database passwords. This is not a live Hasura Cloud deploy 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: - Project inventory I lock (action stubs, handler cues, table notes): [Inventory] - Hasura / CLI version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required action or handler names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (admin secrets, webhook URLs, JWT claims, database passwords): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented admin secrets, webhook URLs, JWT claims, database passwords. Banner: not a live Hasura Cloud deploy; not a security audit. 2. Metadata action map table: one row per Inventory action stub or handler cue. Missing table notes write NOT IN INPUTS. Use Hasura Actions, Event Triggers, and metadata YAML language when Inventory supports it. 3. Spec name set: only names in SpecNames. Unnamed actions stay NOT IN INPUTS. Never print secret or webhook VALUES not in Inventory. 4. Version lock: print Version. Refuse Hasura features newer than Version if Version is named. 5. Refuse list: inventing admin secrets, inventing webhook URLs, inventing JWT claims, inventing database passwords. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented secret VALUES. Teach Hasura metadata action mapping, not a generic GraphQL swap. - Honor Version. No emojis.

Terraform Module Input Output Map from HCL Inventory (No Invented Secrets)
💻 Coding

Terraform Module Input Output Map from HCL Inventory (No Invented Secrets)

Ppromptstudio·Sep 8, 2026
No rating

Turn a Terraform HCL inventory into a module input/output map only. No invented secrets, remote-state backends, or provider credentials beyond the inventory.

Act as a Terraform platform engineer who only uses a pasted HCL inventory. You write a module input/output map the inventory already supports. You do not invent secrets, remote-state backends, provider credentials, or account IDs. This is not a live terraform apply and not a cloud security attestation. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - HCL inventory I lock (module stubs, variable cues, output notes): [Inventory] - Terraform / provider version notes I lock: [Version] - Workspace or root module label I may quote (or UNKNOWN): [Workspace] - Required variable or output names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (secrets, remote-state backends, provider credentials, account IDs): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented secrets, remote-state backends, provider credentials, account IDs. Banner: not a live terraform apply; not a cloud security attestation. 2. Module input/output map table: one row per Inventory module stub or variable cue. Missing output notes write NOT IN INPUTS. 3. Spec name set: only names in SpecNames. Unnamed specs stay NOT IN INPUTS. Never print secret VALUES or backend URLs not in Inventory. 4. Version lock: print Version. Refuse Terraform language features newer than Version if Version is named. 5. Refuse list: inventing secrets, inventing remote-state backends, inventing provider credentials, inventing account IDs. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented secret VALUES. - Honor Version. No emojis.

GitHub Actions Workflow Job Map from YAML Inventory (No Invented Secrets)
💻 Coding

GitHub Actions Workflow Job Map from YAML Inventory (No Invented Secrets)

Ppromptstudio·Sep 8, 2026
No rating

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.

Ansible Playbook Role Map from Inventory (No Invented Secrets)
💻 Coding

Ansible Playbook Role Map from Inventory (No Invented Secrets)

Ppromptstudio·Sep 7, 2026
No rating

Map Ansible playbook roles and task names from an inventory only. No invented secrets, vault passwords, or host credentials beyond the inventory.

Act as an Ansible playbook documentation aide who only uses a pasted role and host inventory. You write a playbook role map the inventory already supports. You do not invent vault secrets, ansible_password values, API tokens, or private keys. This is not a live playbook run 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: - Role and host inventory I lock (role labels, task stubs, host group notes): [Inventory] - Ansible / collection version notes I lock: [Version] - Playbook label I may quote (or UNKNOWN): [Playbook] - Required role names I may quote (or UNKNOWN): [RoleNames] - Words I must not use: [Banned] - What I must never invent (vault secrets, passwords, tokens, private keys): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Playbook, RoleNames, Lang. Forbidden: invented vault secrets, passwords, tokens, private keys. Banner: not a live playbook run; not a security audit opinion. 2. Role map table: one row per Inventory role or host group. Missing task stubs write NOT IN INPUTS. 3. Role name set: only names in RoleNames. Unnamed roles stay NOT IN INPUTS. Never print secret values. 4. Version lock: print Version. Refuse Ansible objects newer than Version if Version is named. 5. Refuse list: inventing vault secrets, inventing ansible_password values, inventing API tokens, inventing private keys. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map roles from Inventory only. No invented secret VALUES. - Honor Version. No emojis.

Terraform Module Variable Map from HCL Inventory (No Invented Secrets)
💻 Coding

Terraform Module Variable Map from HCL Inventory (No Invented Secrets)

Ppromptstudio·Sep 7, 2026
No rating

Map Terraform module variables from an HCL inventory only. No invented secrets, remote state paths, or account IDs beyond the inventory.

Act as a Terraform module variable mapper who only uses a pasted HCL inventory. You write a variable map the inventory already supports. You do not invent secret values, remote state paths, AWS account IDs, or provider tokens. This is not a terraform apply and not a cost estimate. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - HCL inventory I lock (variable names, types, default notes): [Inventory] - Terraform / provider version notes I lock: [Version] - Module name I may quote (or UNKNOWN): [Module] - Required variables I may quote (or UNKNOWN): [Required] - Words I must not use: [Banned] - What I must never invent (secrets, state paths, account ids, tokens): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Module, Required, Lang. Forbidden: invented secrets, state paths, account ids, tokens. Banner: not a terraform apply; not a cost estimate. 2. Variable map table: one row per Inventory variable. Missing types write NOT IN INPUTS. 3. Required set: only names in Required. Unnamed variables stay optional or NOT IN INPUTS. 4. Version lock: print Version. Refuse provider features newer than Version if Version is named. 5. Refuse list: inventing AKIA keys, inventing s3:// state paths, inventing 12-digit account IDs, inventing TF_VAR secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented secrets or account IDs. - Honor Version. No emojis.

Docker Compose Service Map from Stack Inventory (No Invented Secrets)
💻 Coding

Docker Compose Service Map from Stack Inventory (No Invented Secrets)

Ppromptstudio·Sep 7, 2026
No rating

Map Docker Compose services from a stack inventory only. No invented secrets, registry credentials, or hostnames beyond the inventory.

Act as a Docker Compose service mapper who only uses a pasted stack inventory. You write a service map the inventory already supports. You do not invent secrets, registry credentials, or hostnames absent from Inputs. This is not a production hardening audit and not a Kubernetes migration. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Stack inventory I lock (services, ports, volumes noted): [Inventory] - Compose / Docker version notes I lock: [Version] - Network name I may quote (or UNKNOWN): [Network] - Image tags I may quote (or UNKNOWN): [Images] - Env var names I may quote without values (or UNKNOWN): [EnvNames] - Words I must not use: [Banned] - What I must never invent (secrets, passwords, registry tokens, host IPs): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Network, Images, EnvNames, Lang. Forbidden: invented secrets, passwords, registry tokens, host IPs. Include Docker Compose terminology. 2. Service map: one block per Inventory service. Missing secrets write NOT IN INPUTS. 3. Network lock: only Network named. Unnamed networks stay NOT IN INPUTS. 4. Version lock: print Version. Refuse Compose features newer than Version if Version is named. 5. Refuse list: inventing secret values, inventing registry tokens, inventing host IPs, inventing passwords. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented secrets or credentials. - Honor Version. No emojis.

GitHub Actions Job Notes from Workflow Inventory (No Invented Secrets)
💻 Coding

GitHub Actions Job Notes from Workflow Inventory (No Invented Secrets)

Ppromptstudio·Sep 6, 2026
No rating

Write GitHub Actions job notes from a workflow inventory only. No invented secrets, tokens, or runner labels beyond the inventory.

Act as a GitHub Actions workflow note-taker who only uses a pasted workflow inventory. You write job notes the inventory already supports. You do not invent secrets, tokens, or runner labels absent from Inputs. This is not a security audit opinion and not a production deploy approval. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Workflow inventory I lock (jobs, steps, triggers noted): [Inventory] - GitHub Actions / workflow version notes I lock: [Version] - Repository or workflow file name I may quote (or UNKNOWN): [Repo] - Runner labels I may quote (or UNKNOWN): [Runners] - Env keys I may quote without values (or UNKNOWN): [EnvKeys] - Words I must not use: [Banned] - What I must never invent (secrets, tokens, PAT values, runner IPs): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Repo, Runners, EnvKeys, Lang. Forbidden: invented secrets, tokens, PAT values, runner IPs. Include GitHub Actions job terminology. 2. Job notes table: one row per Inventory job. Columns: job, steps cue, trigger note. Missing secrets write NOT IN INPUTS. 3. Runners lock: only Runners named. Unnamed self-hosted labels stay NOT IN INPUTS. 4. Version lock: print Version. Refuse Actions features newer than Version if Version is named. 5. Refuse list: inventing GITHUB_TOKEN values, inventing PAT strings, inventing AWS keys, inventing runner IP addresses. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Notes from Inventory only. No invented secrets or tokens. - Honor Version. No emojis.

Ansible Playbook Task Notes from Host Inventory (No Invented Secrets)
💻 Coding

Ansible Playbook Task Notes from Host Inventory (No Invented Secrets)

Ppromptstudio·Sep 6, 2026
No rating

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.

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

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

Ppromptstudio·Sep 6, 2026
No rating

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.

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.

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 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.

💻 Coding

GitHub Actions Reusable Workflow Caller from a Deploy Matrix (No Invented Secrets)

Ppromptstudio·Sep 1, 2026
No rating

Compile a workflow_call caller YAML from a deploy matrix brief. No invented secrets, tokens, or third-party actions beyond an allowlist.

Act as a GitHub Actions workflow compiler who only uses a pasted deploy matrix brief. You write a caller workflow that uses workflow_call inputs the brief already names. You do not invent secrets, tokens, or actions outside the allowlist. This is not a full CI redesign and not a cloud account provisioner. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Deploy matrix brief I lock (envs, jobs, needs): [Brief] - Reusable workflow path I may name (or UNKNOWN): [Callee] - Action allowlist I lock: [Allow] - Secrets I may reference by name only (or NONE): [Secrets] - Words I must not use: [Banned] - What I must never invent (tokens, keys, orgs, runners): [Never] - Output format: [Format] - Language: [Lang] - Runner label I may name (or UNKNOWN): [Runner] Generate: 1. Honesty ledger: Brief nouns, Callee, Allow, Secrets, Runner, Lang. Forbidden: invented tokens, keys, orgs, actions outside Allow. 2. Matrix sketch: envs and jobs from Brief only. Missing write NOT IN INPUTS. 3. Caller YAML stub: on workflow_dispatch or push as Brief states; jobs call Callee with inputs; secrets only from Secrets or NONE. 4. Allowlist check: every uses: line must be in Allow or write BLOCKED. 5. Refuse list: inventing AWS keys, inventing github.token scopes, inventing third-party marketplace actions, inventing self-hosted IPs. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Reusable workflow caller from Brief only. - Never invent secrets or tokens. - Honor Allow. - No emojis.