💻

Coding

82 prompts in this category · Page 1 of 7

Kubernetes NetworkPolicy Notes from CIDR/Port Inventory (No Invented Cluster IPs/Secrets)
💻 Coding

Kubernetes NetworkPolicy Notes from CIDR/Port Inventory (No Invented Cluster IPs/Secrets)

Ppromptstudio·Sep 6, 2026
No rating

Write Kubernetes NetworkPolicy notes from a CIDR and port inventory only. No invented cluster IPs, secrets, or namespace UIDs beyond the inventory.

Act as a Kubernetes NetworkPolicy note-taker who only uses a pasted CIDR and port inventory. You write NetworkPolicy notes the inventory already supports. You do not invent cluster IPs, secrets, or namespace UIDs absent from Inputs. This is not a security audit opinion and not a production change approval. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - CIDR and port inventory I lock (CIDRs, ports, pods noted): [Inventory] - Kubernetes / NetworkPolicy version notes I lock: [Version] - Namespace name I may quote (or UNKNOWN): [Namespace] - Pod selector labels I may quote (or UNKNOWN): [Selectors] - Policy types I may quote (or UNKNOWN): [PolicyTypes] - Words I must not use: [Banned] - What I must never invent (cluster IPs, secrets, kubeconfig tokens, namespace UIDs): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Namespace, Selectors, PolicyTypes, Lang. Forbidden: invented cluster IPs, secrets, kubeconfig tokens, namespace UIDs. Include Kubernetes NetworkPolicy terminology. 2. NetworkPolicy notes table: one row per Inventory CIDR or port cue. Columns: rule, cidr/port, direction. Missing cluster IPs write NOT IN INPUTS. 3. Selectors lock: only Selectors named. Unnamed labels stay NOT IN INPUTS. 4. Version lock: print Version. Refuse NetworkPolicy features newer than Version if Version is named. 5. Refuse list: inventing clusterIP values, inventing Secret data, inventing kubeconfig tokens, inventing namespace UIDs. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Notes from Inventory only. No invented cluster IPs or secrets. - Honor Version. No emojis.

kubernetes networkpolicycidr port inventoryno invented cluster ips
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.

github actionsno invented secretsworkflow inventory
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.

no invented secretsansible playbookhost inventory
Terraform Module README from Variable Map (No Invented Providers) (Domain Pack)
💻 Coding

Terraform Module README from Variable Map (No Invented Providers) (Domain Pack)

Ppromptstudio·Sep 6, 2026
No rating

Write a Terraform module README from a locked variable map. No invented providers, versions, or example credentials.

Act as a Terraform module README writer who only uses a locked variable map. 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): [VarsMap] - 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 map must list variables and providers only 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 readmevariable mapno invented providers
Terraform Module README from Variable Inventory (No Invented Providers) (Domain Pack)
💻 Coding

Terraform Module README from Variable Inventory (No Invented Providers) (Domain Pack)

Ppromptstudio·Sep 6, 2026
No rating

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 readmevariable inventoryno invented providers
Terraform Module README from Resource Inventory (No Invented Providers) (Domain Pack)
💻 Coding

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

Ppromptstudio·Sep 6, 2026
No rating

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.

terraform module readmeresource inventoryno invented providers
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.

no invented secretsjob inventorygithub actions reusable workflow
dbt Model Docs from Column Inventory (No Invented Sources) (Domain Pack)
💻 Coding

dbt Model Docs from Column Inventory (No Invented Sources) (Domain Pack)

Ppromptstudio·Sep 6, 2026
No rating

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.

column inventorydbt model docsno invented sources
Terraform AWS Security Group Notes from CIDR Inventory (No Invented Account IDs)
💻 Coding

Terraform AWS Security Group Notes from CIDR Inventory (No Invented Account IDs)

Ppromptstudio·Sep 6, 2026
No rating

Write Terraform AWS security group notes from a CIDR inventory only. No invented account IDs, VPC IDs, or rule descriptions beyond the inventory.

Act as a Terraform AWS security-group note-taker who only uses a pasted CIDR inventory. You write aws_security_group notes the inventory already supports. You do not invent AWS account IDs, VPC IDs, or rule descriptions that are not in Inputs. This is not a production apply script and not a cloud audit. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - CIDR inventory I lock (CIDRs, ports, protocols, direction notes): [Inventory] - Terraform / AWS provider version I lock: [Version] - Security group name I may quote (or UNKNOWN): [SgName] - VPC id I may quote (or UNKNOWN): [VpcId] - Words I must not use: [Banned] - What I must never invent (account ids, vpc ids, open 0.0.0.0/0 when absent): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, SgName, VpcId, Lang. Forbidden: invented account ids, vpc ids, open CIDRs not in Inventory. 2. Rule table: one row per Inventory line. Missing ports write NOT IN INPUTS. 3. HCL stub: only rules supported by Inventory and Version. Placeholders for unknown ids stay NOT IN INPUTS comments. 4. Version lock: print Version. Refuse provider features newer than Version if Version is named. 5. Refuse list: inventing 123456789012, inventing vpc-0abc, inventing 0.0.0.0/0 when absent, inventing ssh from the world. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Notes from Inventory only. No invented account or VPC ids. - Honor Version. No emojis.

terraform sgcidr inventoryno invented account ids
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
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
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