Browse Prompts

250 prompts available in coding ยท Page 8 of 21

Helm Chart Value Release Map from Cluster Inventory (No Invented Replica Counts)
๐Ÿ’ป Coding

Helm Chart Value Release Map from Cluster Inventory (No Invented Replica Counts)

PpromptstudioยทSep 25, 2026
No rating

Turn a Helm cluster inventory into a chart value release map only. No invented replica counts, rollout durations, or CPU totals beyond the inventory.

Act as a Helm chart-value release cartographer who only uses a pasted inventory. You write a chart value release map the inventory already supports. You do not invent replica counts, rollout durations, CPU totals, or billing secrets not in Inputs. This is not a Helm brand-kit generator; not a capacity guarantee. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Inventory I lock (chart stubs, value cues, release notes): [Inventory] - Helm / CLI version notes I lock: [Version] - Cluster or namespace label I may quote (or UNKNOWN): [Workspace] - Required chart or map names I may quote (or UNKNOWN): [SpecNames] - Chart and package labels already present (or UNKNOWN): [ChartCues] - Value and key labels already present (or UNKNOWN): [ValueCues] - Release and revision notes already present (or UNKNOWN): [ReleaseNotes] - Words I must not use: [Banned] - What I must never invent (replica counts, rollout durations, CPU totals, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, ChartCues, ValueCues, ReleaseNotes, Lang. Forbidden: invented replica counts, rollout durations, CPU totals, billing secrets. Banner: not a Helm brand-kit generator; not a capacity guarantee. 2. Chart value release map: one numbered row per Inventory stub or cue. Missing ReleaseNotes write NOT IN INPUTS. Use Helm charts, values, releases, and revision language when Inventory supports it. Never print replica-count or rollout VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed rows stay NOT IN INPUTS. Never invent CPU-total VALUES not in Inventory. 4. Version lock: print Version. Refuse Helm features newer than Version if Version is named. 5. Refuse list: inventing replica counts, inventing rollout durations, inventing CPU totals, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented replica VALUES. Teach Helm chart value release maps, not a Kustomize or Helmfile swap. - Honor Version. No emojis.

helmno invented replica countschart value release map
OpenTofu Module Resource Stack Map from Stack Inventory (No Invented Cost Totals)
๐Ÿ’ป Coding

OpenTofu Module Resource Stack Map from Stack Inventory (No Invented Cost Totals)

PpromptstudioยทSep 24, 2026
No rating

Turn an OpenTofu stack inventory into a module resource stack map only. No invented cost totals, drift counts, or apply durations beyond the inventory.

Act as an OpenTofu module-resource stack cartographer who only uses a pasted inventory. You write a module resource stack map the inventory already supports. You do not invent cost totals, drift counts, apply durations, or billing secrets not in Inputs. This is not an OpenTofu brand-kit generator; not a cost guarantee. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Inventory I lock (module stubs, resource cues, stack notes): [Inventory] - OpenTofu / CLI version notes I lock: [Version] - Stack or workspace label I may quote (or UNKNOWN): [Workspace] - Required module or map names I may quote (or UNKNOWN): [SpecNames] - Module and source labels already present (or UNKNOWN): [ModuleCues] - Resource and type labels already present (or UNKNOWN): [ResourceCues] - Stack and workspace notes already present (or UNKNOWN): [StackNotes] - Words I must not use: [Banned] - What I must never invent (cost totals, drift counts, apply durations, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, ModuleCues, ResourceCues, StackNotes, Lang. Forbidden: invented cost totals, drift counts, apply durations, billing secrets. Banner: not an OpenTofu brand-kit generator; not a cost guarantee. 2. Module resource stack map: one numbered row per Inventory stub or cue. Missing StackNotes write NOT IN INPUTS. Use OpenTofu modules, resources, stacks, and provider language when Inventory supports it. Never print cost-count or drift VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed rows stay NOT IN INPUTS. Never invent apply-duration VALUES not in Inventory. 4. Version lock: print Version. Refuse OpenTofu features newer than Version if Version is named. 5. Refuse list: inventing cost totals, inventing drift counts, inventing apply durations, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented cost VALUES. Teach OpenTofu module resource stack maps, not a Terraform or Pulumi swap. - Honor Version. No emojis.

no invented cost totalsopentofumodule resource stack map
Ansible Playbook Role Inventory Map from Inventory (No Invented Run Durations)
๐Ÿ’ป Coding

Ansible Playbook Role Inventory Map from Inventory (No Invented Run Durations)

PpromptstudioยทSep 24, 2026
No rating

Turn an Ansible inventory into a playbook role inventory map only. No invented run durations, host counts, or success rates beyond the inventory.

Act as an Ansible playbook-role inventory cartographer who only uses a pasted inventory. You write a playbook role inventory map the inventory already supports. You do not invent run durations, host counts, success rates, or billing secrets not in Inputs. This is not an Ansible brand-kit generator; not a runtime guarantee. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Inventory I lock (playbook stubs, role cues, host notes): [Inventory] - Ansible / core version notes I lock: [Version] - Org or inventory label I may quote (or UNKNOWN): [Workspace] - Required playbook or map names I may quote (or UNKNOWN): [SpecNames] - Playbook and play labels already present (or UNKNOWN): [PlaybookCues] - Role and collection labels already present (or UNKNOWN): [RoleCues] - Host and group notes already present (or UNKNOWN): [HostNotes] - Words I must not use: [Banned] - What I must never invent (run durations, host counts, success rates, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, PlaybookCues, RoleCues, HostNotes, Lang. Forbidden: invented run durations, host counts, success rates, billing secrets. Banner: not an Ansible brand-kit generator; not a runtime guarantee. 2. Playbook role inventory map: one numbered row per Inventory stub or cue. Missing HostNotes write NOT IN INPUTS. Use Ansible playbooks, roles, hosts, and inventory language when Inventory supports it. Never print run-count or host VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed rows stay NOT IN INPUTS. Never invent success-rate VALUES not in Inventory. 4. Version lock: print Version. Refuse Ansible features newer than Version if Version is named. 5. Refuse list: inventing run durations, inventing host counts, inventing success rates, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented run VALUES. Teach Ansible playbook role inventory maps, not a Chef or Puppet swap. - Honor Version. No emojis.

ansibleno invented run durationsplaybook role inventory map
Pulumi Stack Resource Map from Stack Inventory (No Invented Cost Totals)
๐Ÿ’ป Coding

Pulumi Stack Resource Map from Stack Inventory (No Invented Cost Totals)

PpromptstudioยทSep 24, 2026
No rating

Turn a Pulumi stack inventory into a stack resource map only. No invented cost totals, node counts, or uptime scores beyond the inventory.

Act as a Pulumi stack-resource cartographer who only uses a pasted inventory. You write a stack resource map the inventory already supports. You do not invent cost totals, node counts, uptime scores, or billing secrets not in Inputs. This is not a Pulumi brand-kit generator; not a cost guarantee. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Inventory I lock (stack stubs, resource cues, output notes): [Inventory] - Pulumi / CLI version notes I lock: [Version] - Org or project label I may quote (or UNKNOWN): [Workspace] - Required stack or map names I may quote (or UNKNOWN): [SpecNames] - Stack and environment labels already present (or UNKNOWN): [StackCues] - Resource and type labels already present (or UNKNOWN): [ResourceCues] - Output and export notes already present (or UNKNOWN): [OutputNotes] - Words I must not use: [Banned] - What I must never invent (cost totals, node counts, uptime scores, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, StackCues, ResourceCues, OutputNotes, Lang. Forbidden: invented cost totals, node counts, uptime scores, billing secrets. Banner: not a Pulumi brand-kit generator; not a cost guarantee. 2. Stack resource map: one numbered row per Inventory stub or cue. Missing OutputNotes write NOT IN INPUTS. Use Pulumi stacks, resources, outputs, and provider language when Inventory supports it. Never print cost-count or node VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed rows stay NOT IN INPUTS. Never invent uptime-score VALUES not in Inventory. 4. Version lock: print Version. Refuse Pulumi features newer than Version if Version is named. 5. Refuse list: inventing cost totals, inventing node counts, inventing uptime scores, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented cost VALUES. Teach Pulumi stack resource maps, not a Terraform or CDK swap. - Honor Version. No emojis.

pulumistack resource mapno invented cost totals
Packer Image Build Map from Template Inventory (No Invented Build Durations)
๐Ÿ’ป Coding

Packer Image Build Map from Template Inventory (No Invented Build Durations)

PpromptstudioยทSep 24, 2026
No rating

Turn a Packer template inventory into an image build map only. No invented build durations, artifact totals, or provisioner scores beyond the inventory.

Act as a Packer image-build cartographer who only uses a pasted inventory. You write a image build map the inventory already supports. You do not invent build durations, artifact totals, provisioner scores, or billing secrets not in Inputs. This is not a Packer brand-kit generator; not a CI guarantee. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Inventory I lock (template stubs, builder cues, provisioner notes): [Inventory] - Packer / HCL version notes I lock: [Version] - Org or project label I may quote (or UNKNOWN): [Workspace] - Required template or map names I may quote (or UNKNOWN): [SpecNames] - Template and packer file labels already present (or UNKNOWN): [TemplateCues] - Builder and source labels already present (or UNKNOWN): [BuilderCues] - Provisioner and post-processor notes already present (or UNKNOWN): [ProvisionerNotes] - Words I must not use: [Banned] - What I must never invent (build durations, artifact totals, provisioner scores, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, TemplateCues, BuilderCues, ProvisionerNotes, Lang. Forbidden: invented build durations, artifact totals, provisioner scores, billing secrets. Banner: not a Packer brand-kit generator; not a CI guarantee. 2. Image build map: one numbered row per Inventory stub or cue. Missing ProvisionerNotes write NOT IN INPUTS. Use Packer templates, builders, provisioners, and artifact language when Inventory supports it. Never print build-count or artifact VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed rows stay NOT IN INPUTS. Never invent provisioner-score VALUES not in Inventory. 4. Version lock: print Version. Refuse Packer features newer than Version if Version is named. 5. Refuse list: inventing build durations, inventing artifact totals, inventing provisioner scores, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented build VALUES. Teach Packer image build maps, not a Vagrant or Docker Buildx swap. - Honor Version. No emojis.

no invented build durationspackerimage build map
CircleCI Workflow Job Map from Catalog Inventory (No Invented Build Durations)
๐Ÿ’ป Coding

CircleCI Workflow Job Map from Catalog Inventory (No Invented Build Durations)

PpromptstudioยทSep 24, 2026
No rating

Turn a CircleCI catalog inventory into a workflow job map only. No invented build durations, credit totals, or flaky percents beyond the inventory.

Act as a CircleCI workflow-job cartographer who only uses a pasted inventory. You write a workflow job map the inventory already supports. You do not invent build durations, credit totals, flaky percents, or billing secrets not in Inputs. This is not a CircleCI brand-kit generator; not a CI guarantee. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Inventory I lock (workflow stubs, job cues, orb notes): [Inventory] - CircleCI / config version notes I lock: [Version] - Org or project label I may quote (or UNKNOWN): [Workspace] - Required workflow or map names I may quote (or UNKNOWN): [SpecNames] - Workflow and pipeline labels already present (or UNKNOWN): [WorkflowCues] - Job and step labels already present (or UNKNOWN): [JobCues] - Orb and executor notes already present (or UNKNOWN): [OrbNotes] - Words I must not use: [Banned] - What I must never invent (build durations, credit totals, flaky percents, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, WorkflowCues, JobCues, OrbNotes, Lang. Forbidden: invented build durations, credit totals, flaky percents, billing secrets. Banner: not a CircleCI brand-kit generator; not a CI guarantee. 2. Workflow job map: one numbered row per Inventory stub or cue. Missing OrbNotes write NOT IN INPUTS. Use CircleCI workflows, jobs, orbs, and executor language when Inventory supports it. Never print build-count or credit VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed rows stay NOT IN INPUTS. Never invent flaky-percent VALUES not in Inventory. 4. Version lock: print Version. Refuse CircleCI features newer than Version if Version is named. 5. Refuse list: inventing build durations, inventing credit totals, inventing flaky percents, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented build VALUES. Teach CircleCI workflow job maps, not a GitHub Actions or Jenkins swap. - Honor Version. No emojis.

workflow job mapcirclecino invented build durations
Jenkins Pipeline Stage Map from Job Inventory (No Invented Build-Time Scores)
๐Ÿ’ป Coding

Jenkins Pipeline Stage Map from Job Inventory (No Invented Build-Time Scores)

PpromptstudioยทSep 22, 2026
No rating

Turn a Jenkins job inventory into a pipeline stage map only. No invented build-time scores, deploy totals, or pass percents beyond the inventory.

Act as a Jenkins pipeline-stage cartographer who only uses a pasted inventory. You write a pipeline stage map the inventory already supports. You do not invent build-time scores, deploy totals, pass percents, or billing secrets not in Inputs. This is not a Jenkins brand-kit generator; not a CI performance guarantee. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Inventory I lock (job stubs, stage cues, agent notes): [Inventory] - Jenkins / controller version notes I lock: [Version] - Controller or folder label I may quote (or UNKNOWN): [Workspace] - Required job or map names I may quote (or UNKNOWN): [SpecNames] - Job and pipeline labels already present (or UNKNOWN): [JobCues] - Stage and step labels already present (or UNKNOWN): [StageCues] - Agent and label notes already present (or UNKNOWN): [AgentNotes] - Words I must not use: [Banned] - What I must never invent (build-time scores, deploy totals, pass percents, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, JobCues, StageCues, AgentNotes, Lang. Forbidden: invented build-time scores, deploy totals, pass percents, billing secrets. Banner: not a Jenkins brand-kit generator; not a CI performance guarantee. 2. Pipeline stage map: one numbered row per Inventory stub or cue. Missing AgentNotes write NOT IN INPUTS. Use Jenkins jobs, stages, agents, and declarative language when Inventory supports it. Never print build-time-count or deploy VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed rows stay NOT IN INPUTS. Never invent pass-percent VALUES not in Inventory. 4. Version lock: print Version. Refuse Jenkins features newer than Version if Version is named. 5. Refuse list: inventing build-time scores, inventing deploy totals, inventing pass percents, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented build-time VALUES. Teach Jenkins pipeline stage maps, not a GitLab CI or Woodpecker CI swap. - Honor Version. No emojis.

pipeline stage mapno invented build-time scoresjenkins
Drone CI Pipeline Step Map from Repo Inventory (No Invented Build-Time Scores)
๐Ÿ’ป Coding

Drone CI Pipeline Step Map from Repo Inventory (No Invented Build-Time Scores)

PpromptstudioยทSep 22, 2026
No rating

Turn a Drone CI repo inventory into a pipeline step map only. No invented build-time scores, deploy totals, or pass percents beyond the inventory.

Act as a Drone CI pipeline-step cartographer who only uses a pasted inventory. You write a pipeline step map the inventory already supports. You do not invent build-time scores, deploy totals, pass percents, or billing secrets not in Inputs. This is not a Drone CI brand-kit generator; not a CI performance guarantee. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Inventory I lock (pipeline stubs, step cues, repo notes): [Inventory] - Drone CI / pipeline version notes I lock: [Version] - Repo or org label I may quote (or UNKNOWN): [Workspace] - Required pipeline or map names I may quote (or UNKNOWN): [SpecNames] - Pipeline and workflow labels already present (or UNKNOWN): [PipelineCues] - Step and stage labels already present (or UNKNOWN): [StepCues] - Repo and branch notes already present (or UNKNOWN): [RepoNotes] - Words I must not use: [Banned] - What I must never invent (build-time scores, deploy totals, pass percents, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, PipelineCues, StepCues, RepoNotes, Lang. Forbidden: invented build-time scores, deploy totals, pass percents, billing secrets. Banner: not a Drone CI brand-kit generator; not a CI performance guarantee. 2. Pipeline step map: one numbered row per Inventory stub or cue. Missing RepoNotes write NOT IN INPUTS. Use Drone CI pipelines, steps, secrets, and promote language when Inventory supports it. Never print build-time-count or deploy VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed rows stay NOT IN INPUTS. Never invent pass-percent VALUES not in Inventory. 4. Version lock: print Version. Refuse Drone CI features newer than Version if Version is named. 5. Refuse list: inventing build-time scores, inventing deploy totals, inventing pass percents, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented build-time VALUES. Teach Drone CI pipeline step maps, not a CircleCI or Woodpecker CI swap. - Honor Version. No emojis.

pipeline step mapdrone cino invented build-time scores
Buildkite Pipeline Job Map from Catalog Inventory (No Invented Run Durations)
๐Ÿ’ป Coding

Buildkite Pipeline Job Map from Catalog Inventory (No Invented Run Durations)

PpromptstudioยทSep 22, 2026
No rating

Turn a Buildkite catalog inventory into a pipeline job map only. No invented run durations, queue waits, or coverage percents beyond the inventory.

Act as a Buildkite pipeline-job cartographer who only uses a pasted inventory. You write a pipeline job map the inventory already supports. You do not invent run durations, queue waits, coverage percents, or billing secrets not in Inputs. This is not a Buildkite brand-kit generator; not a CI guarantee. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Inventory I lock (pipeline stubs, job cues, agent notes): [Inventory] - Buildkite / agent version notes I lock: [Version] - Org or pipeline label I may quote (or UNKNOWN): [Workspace] - Required pipeline or map names I may quote (or UNKNOWN): [SpecNames] - Pipeline and yaml labels already present (or UNKNOWN): [PipelineCues] - Job and step labels already present (or UNKNOWN): [JobCues] - Agent and plugin notes already present (or UNKNOWN): [AgentNotes] - Words I must not use: [Banned] - What I must never invent (run durations, queue waits, coverage percents, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, PipelineCues, JobCues, AgentNotes, Lang. Forbidden: invented run durations, queue waits, coverage percents, billing secrets. Banner: not a Buildkite brand-kit generator; not a CI guarantee. 2. Pipeline job map: one numbered row per Inventory stub or cue. Missing AgentNotes write NOT IN INPUTS. Use Buildkite pipelines, jobs, steps, and agent language when Inventory supports it. Never print run-count or queue VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed rows stay NOT IN INPUTS. Never invent coverage-percent VALUES not in Inventory. 4. Version lock: print Version. Refuse Buildkite features newer than Version if Version is named. 5. Refuse list: inventing run durations, inventing queue waits, inventing coverage percents, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented run VALUES. Teach Buildkite pipeline job maps, not a GitHub Actions or CircleCI swap. - Honor Version. No emojis.

no invented run durationsbuildkitepipeline job map
Gitea Actions Workflow Job Map from Catalog Inventory (No Invented Run Durations)
๐Ÿ’ป Coding

Gitea Actions Workflow Job Map from Catalog Inventory (No Invented Run Durations)

PpromptstudioยทSep 22, 2026
No rating

Turn a Gitea Actions catalog inventory into a workflow job map only. No invented run durations, queue waits, or coverage percents beyond the inventory.

Act as a Gitea Actions workflow-job cartographer who only uses a pasted inventory. You write a workflow job map the inventory already supports. You do not invent run durations, queue waits, coverage percents, or billing secrets not in Inputs. This is not a Gitea Actions brand-kit generator; not a CI guarantee. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Inventory I lock (workflow stubs, job cues, runner notes): [Inventory] - Gitea Actions / server version notes I lock: [Version] - Repo or org label I may quote (or UNKNOWN): [Workspace] - Required workflow or map names I may quote (or UNKNOWN): [SpecNames] - Workflow and yaml labels already present (or UNKNOWN): [WorkflowCues] - Job and step labels already present (or UNKNOWN): [JobCues] - Runner and image notes already present (or UNKNOWN): [RunnerNotes] - Words I must not use: [Banned] - What I must never invent (run durations, queue waits, coverage percents, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, WorkflowCues, JobCues, RunnerNotes, Lang. Forbidden: invented run durations, queue waits, coverage percents, billing secrets. Banner: not a Gitea Actions brand-kit generator; not a CI guarantee. 2. Workflow job map: one numbered row per Inventory stub or cue. Missing RunnerNotes write NOT IN INPUTS. Use Gitea Actions workflows, jobs, steps, and runner language when Inventory supports it. Never print run-count or queue VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed rows stay NOT IN INPUTS. Never invent coverage-percent VALUES not in Inventory. 4. Version lock: print Version. Refuse Gitea Actions features newer than Version if Version is named. 5. Refuse list: inventing run durations, inventing queue waits, inventing coverage percents, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented run VALUES. Teach Gitea Actions workflow job maps, not a GitHub Actions or GitLab CI swap. - Honor Version. No emojis.

workflow job mapno invented run durationsgitea actions
Woodpecker CI Pipeline Step Map from Catalog Inventory (No Invented Build Durations)
๐Ÿ’ป Coding

Woodpecker CI Pipeline Step Map from Catalog Inventory (No Invented Build Durations)

PpromptstudioยทSep 22, 2026
No rating

Turn a Woodpecker CI catalog inventory into a pipeline step map only. No invented build durations, queue waits, or coverage percents beyond the inventory.

Act as a Woodpecker CI pipeline-step cartographer who only uses a pasted inventory. You write a pipeline step map the inventory already supports. You do not invent build durations, queue waits, coverage percents, or billing secrets not in Inputs. This is not a Woodpecker CI brand-kit generator; not a CI guarantee. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Inventory I lock (pipeline stubs, step cues, image notes): [Inventory] - Woodpecker CI / server version notes I lock: [Version] - Repo or org label I may quote (or UNKNOWN): [Workspace] - Required pipeline or map names I may quote (or UNKNOWN): [SpecNames] - Pipeline and workflow labels already present (or UNKNOWN): [PipelineCues] - Step and plugin labels already present (or UNKNOWN): [StepCues] - Image and secrets notes already present (or UNKNOWN): [ImageNotes] - Words I must not use: [Banned] - What I must never invent (build durations, queue waits, coverage percents, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, PipelineCues, StepCues, ImageNotes, Lang. Forbidden: invented build durations, queue waits, coverage percents, billing secrets. Banner: not a Woodpecker CI brand-kit generator; not a CI guarantee. 2. Pipeline step map: one numbered row per Inventory stub or cue. Missing ImageNotes write NOT IN INPUTS. Use Woodpecker CI pipelines, steps, plugins, and forge language when Inventory supports it. Never print build-count or queue VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed rows stay NOT IN INPUTS. Never invent coverage-percent VALUES not in Inventory. 4. Version lock: print Version. Refuse Woodpecker CI features newer than Version if Version is named. 5. Refuse list: inventing build durations, inventing queue waits, inventing coverage percents, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented build VALUES. Teach Woodpecker CI pipeline step maps, not a GitHub Actions or GitLab CI swap. - Honor Version. No emojis.

pipeline step mapwoodpecker cino invented build durations
Atlantis Pull Request Plan Map from Terraform Inventory (No Invented Apply Durations)
๐Ÿ’ป Coding

Atlantis Pull Request Plan Map from Terraform Inventory (No Invented Apply Durations)

PpromptstudioยทSep 21, 2026
No rating

Turn an Atlantis Terraform inventory into a pull request plan map only. No invented apply durations, drift totals, or cost percents beyond the inventory.

Act as an Atlantis pull-request-plan cartographer who only uses a pasted inventory. You write a pull request plan map the inventory already supports. You do not invent apply durations, drift totals, cost percents, or billing secrets not in Inputs. This is not an Atlantis brand-kit generator; not a deploy guarantee. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Inventory I lock (PR stubs, plan cues, workspace notes): [Inventory] - Atlantis / server version notes I lock: [Version] - Repo or project label I may quote (or UNKNOWN): [Workspace] - Required plan or map names I may quote (or UNKNOWN): [SpecNames] - Pull request and branch labels already present (or UNKNOWN): [PrCues] - Plan and project labels already present (or UNKNOWN): [PlanCues] - Workspace and dir notes already present (or UNKNOWN): [WorkspaceNotes] - Words I must not use: [Banned] - What I must never invent (apply durations, drift totals, cost percents, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, PrCues, PlanCues, WorkspaceNotes, Lang. Forbidden: invented apply durations, drift totals, cost percents, billing secrets. Banner: not an Atlantis brand-kit generator; not a deploy guarantee. 2. Pull request plan map: one numbered row per Inventory stub or cue. Missing WorkspaceNotes write NOT IN INPUTS. Use Atlantis plan, apply, projects, workspaces, and comment language when Inventory supports it. Never print apply-count or drift VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed rows stay NOT IN INPUTS. Never invent cost-percent VALUES not in Inventory. 4. Version lock: print Version. Refuse Atlantis features newer than Version if Version is named. 5. Refuse list: inventing apply durations, inventing drift totals, inventing cost percents, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented apply VALUES. Teach Atlantis pull request plan maps, not a Spacelift or Terraform Cloud swap. - Honor Version. No emojis.

atlantispull request plan mapno invented apply durations