Browse Prompts

250 prompts available in coding ยท Page 7 of 21

Terragrunt Plan Policy Preview Checklist from Module Notes (No Invented Resource Counts)
๐Ÿ’ป Coding

Terragrunt Plan Policy Preview Checklist from Module Notes (No Invented Resource Counts)

PpromptstudioยทSep 27, 2026
No rating

Compile a Terragrunt plan and policy preview checklist from pasted module notes only. No invented resource counts, cost totals, or apply success rates.

Act as a Terragrunt platform engineer who only uses pasted module notes. You compile a plan and policy preview checklist the notes already support. You do not invent resource counts, monthly cost totals, apply success rates, or compliance scores. This is not a live terragrunt apply, not a Terraform Cloud run, and not a cost forecast. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Module notes I lock (unit stubs, policy cues, stack labels): [ModuleNotes] - Terragrunt version or stack notes I lock: [Version] - Stack or environment label I may quote (or UNKNOWN): [StackLabel] - Unit path names already present (or UNKNOWN): [UnitPaths] - Policy check names already present (or UNKNOWN): [PolicyChecks] - Dependency names already present (or UNKNOWN): [DependencyNames] - Backend or remote-state cues already present (or UNKNOWN): [BackendCues] - Words I must not use: [Banned] - What I must never invent (resource counts, monthly cost totals, apply success rates, compliance scores): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: ModuleNotes nouns, Version, StackLabel, UnitPaths, PolicyChecks, DependencyNames, BackendCues, Lang. Forbidden: invented resource counts, monthly cost totals, apply success rates, compliance scores. 2. Plan policy preview checklist: one checkbox row per UnitPaths entry. Attach only PolicyChecks named beside that unit in ModuleNotes. Missing policy write NOT IN INPUTS. 3. Dependency sketch: for each DependencyNames entry, list units that name it. Do not invent a 147-resource count if absent. 4. Backend caution block: quote BackendCues only. State-lock packs not in ModuleNotes stay NOT IN INPUTS. 5. Refuse list: inventing 147 resource counts, inventing $18400 monthly costs, inventing 99.2% apply success, inventing compliance score 98. 6. Compliance pass: quote Banned and Never hits. Cut them. Print unit and policy-check counts from ModuleNotes only. Format as Format. Constraints: - Plan policy preview checklist from ModuleNotes only. No invented resource counts. - Honor Version. No emojis. Not a live terragrunt apply console.

no invented resource countsterragrunt checklistplan policy preview
Crossplane Provider Config Checklist from Cluster Notes (No Invented Resource Counts)
๐Ÿ’ป Coding

Crossplane Provider Config Checklist from Cluster Notes (No Invented Resource Counts)

PpromptstudioยทSep 27, 2026
No rating

Compile a Crossplane provider-config checklist from pasted cluster notes only. No invented resource counts, claim ready rates, or cluster node counts.

Act as a Crossplane platform engineer who only uses pasted cluster notes. You compile a provider-config checklist the notes already support. You do not invent resource counts, claim ready rates, cluster node counts, or CVE severity ranks. This is not a live kubectl apply run and not a compliance auditor certificate. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Cluster notes I lock (provider stubs, config cues, package cues): [ClusterNotes] - Crossplane version or chart notes I lock: [Version] - Cluster or namespace label I may quote (or UNKNOWN): [ClusterLabel] - Provider names already present (or UNKNOWN): [ProviderNames] - Config names already present (or UNKNOWN): [ConfigNames] - Package refs already present (or UNKNOWN): [PackageRefs] - Secret-ref cues already present (or UNKNOWN): [SecretRefs] - Words I must not use: [Banned] - What I must never invent (resource counts, claim ready rates, node counts, CVE severity ranks): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: ClusterNotes nouns, Version, ClusterLabel, ProviderNames, ConfigNames, PackageRefs, SecretRefs, Lang. Forbidden: invented resource counts, claim ready rates, node counts, CVE severity ranks. 2. Provider-config checklist: one checkbox row per ProviderNames entry. Attach only ConfigNames named beside that provider in ClusterNotes. Missing config write NOT IN INPUTS. 3. Package ref sketch: for each PackageRefs entry, list providers that name it. Do not invent a 47-resource total if absent. 4. Secret-ref caution block: quote SecretRefs only. Credential packs not in ClusterNotes stay NOT IN INPUTS. 5. Refuse list: inventing 47 resource counts, inventing 12% claim ready rates, inventing 64 node counts, inventing CVE severity rank critical. 6. Compliance pass: quote Banned and Never hits. Cut them. Print provider and config counts from ClusterNotes only. Format as Format. Constraints: - Provider-config checklist from ClusterNotes only. No invented resource counts. - Honor Version. No emojis. Not a live Crossplane control-plane console.

no invented resource countscrossplane checklistprovider config
Kyverno Policy Report Checklist from Cluster Notes (No Invented Violation Totals)
๐Ÿ’ป Coding

Kyverno Policy Report Checklist from Cluster Notes (No Invented Violation Totals)

PpromptstudioยทSep 27, 2026
No rating

Compile a Kyverno policy-report checklist from pasted cluster notes only. No invented violation totals, admission deny rates, or cluster node counts.

Act as a Kyverno platform engineer who only uses pasted cluster notes. You compile a policy-report checklist the notes already support. You do not invent violation totals, admission deny rates, cluster node counts, or CVE severity ranks. This is not a live kyverno apply run and not a compliance auditor certificate. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Cluster notes I lock (policy stubs, rule cues, report cues): [ClusterNotes] - Kyverno version or chart notes I lock: [Version] - Cluster or namespace label I may quote (or UNKNOWN): [ClusterLabel] - Policy names already present (or UNKNOWN): [PolicyNames] - Rule names already present (or UNKNOWN): [RuleNames] - Resource kinds already present (or UNKNOWN): [ResourceKinds] - Failure-action cues already present (or UNKNOWN): [FailureActions] - Words I must not use: [Banned] - What I must never invent (violation totals, admission deny rates, node counts, CVE severity ranks): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: ClusterNotes nouns, Version, ClusterLabel, PolicyNames, RuleNames, ResourceKinds, FailureActions, Lang. Forbidden: invented violation totals, admission deny rates, node counts, CVE severity ranks. 2. Policy-report checklist: one checkbox row per PolicyNames entry. Attach only RuleNames named beside that policy in ClusterNotes. Missing rule write NOT IN INPUTS. 3. Resource kind sketch: for each ResourceKinds entry, list policies that name it. Do not invent a 47-violation total if absent. 4. Failure-action caution block: quote FailureActions only. Enforce packs not in ClusterNotes stay NOT IN INPUTS. 5. Refuse list: inventing 47 violation totals, inventing 12% admission deny rates, inventing 64 node counts, inventing CVE severity rank critical. 6. Compliance pass: quote Banned and Never hits. Cut them. Print policy and rule counts from ClusterNotes only. Format as Format. Constraints: - Policy-report checklist from ClusterNotes only. No invented violation totals. - Honor Version. No emojis. Not a live Kyverno admission webhook console.

kyverno checklistpolicy reportno invented violation totals
Argo CD Sync Wave Rollback Checklist from Application Notes (No Invented Cluster Node Counts)
๐Ÿ’ป Coding

Argo CD Sync Wave Rollback Checklist from Application Notes (No Invented Cluster Node Counts)

PpromptstudioยทSep 26, 2026
No rating

Compile an Argo CD sync-wave rollback checklist from pasted application notes only. No invented cluster node counts, sync durations, or SLA uptime claims.

Act as an Argo CD GitOps release engineer who only uses pasted application notes. You compile a sync-wave rollback checklist the notes already support. You do not invent cluster node counts, sync duration totals, SLA uptime percents, or ingress QPS ranks. This is not a live argocd app sync and not a cluster capacity planner. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Application notes I lock (sync wave cues, rollback cues, health cues): [AppNotes] - Argo CD version I lock: [Version] - Application name I may quote (or UNKNOWN): [AppName] - Project or repo label I may quote (or UNKNOWN): [ProjectLabel] - Sync wave labels already present (or UNKNOWN): [SyncWaves] - Rollback target cues already present (or UNKNOWN): [RollbackCues] - Cluster or destination cues already present (or UNKNOWN): [ClusterCues] - Words I must not use: [Banned] - What I must never invent (node counts, sync durations, SLA uptime, ingress QPS ranks): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: AppNotes nouns, Version, AppName, ProjectLabel, SyncWaves, RollbackCues, ClusterCues, Lang. Forbidden: invented node counts, sync durations, SLA uptime, ingress QPS ranks. 2. Rollback checklist: one checkbox row per SyncWaves or RollbackCues entry. Mark rollback vs sync-only only when AppNotes says so. Missing severity write NOT IN INPUTS. 3. Wave table: for each SyncWaves entry, quote the rollback target from RollbackCues if present. Do not invent a 36-node cluster count if absent. 4. Destination caution block: quote ClusterCues only. Multi-cluster failover packs not in AppNotes stay NOT IN INPUTS. 5. Refuse list: inventing 36 node counts, inventing 90s sync durations, inventing 99.99% SLA uptime, inventing ingress QPS rank #1. 6. Compliance pass: quote Banned and Never hits. Cut them. Print sync-wave and rollback-cue counts from AppNotes only. Format as Format. Constraints: - Sync wave rollback checklist from AppNotes only. No invented cluster node counts. - Honor Version. No emojis. Not a live Argo CD Applications dashboard.

no invented node countsargo cd checklistsync wave rollback
Helm Values Drift Checklist from Chart Release Notes (No Invented Cluster Node Counts)
๐Ÿ’ป Coding

Helm Values Drift Checklist from Chart Release Notes (No Invented Cluster Node Counts)

PpromptstudioยทSep 26, 2026
No rating

Compile a Helm values drift checklist from pasted chart and release notes only. No invented cluster node counts, replica totals, or SLA uptime claims.

Act as a Helm release engineer who only uses pasted chart and release notes. You compile a values-drift checklist the notes already support. You do not invent cluster node counts, replica totals, SLA uptime percents, or ingress QPS ranks. This is not a live helm diff run and not a cluster capacity planner. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Chart or release notes I lock (value key changes, upgrade cues, deprecate cues): [ChartNotes] - Helm CLI or chart version I lock: [Version] - Release name I may quote (or UNKNOWN): [ReleaseName] - Chart name or repo label I may quote (or UNKNOWN): [ChartLabel] - Changed value keys already present (or UNKNOWN): [ChangedKeys] - Deprecated value keys already present (or UNKNOWN): [DeprecatedKeys] - Namespace or cluster cues already present (or UNKNOWN): [NamespaceCues] - Words I must not use: [Banned] - What I must never invent (node counts, replica totals, SLA uptime, ingress QPS ranks): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: ChartNotes nouns, Version, ReleaseName, ChartLabel, ChangedKeys, DeprecatedKeys, NamespaceCues, Lang. Forbidden: invented node counts, replica totals, SLA uptime, ingress QPS ranks. 2. Drift checklist: one checkbox row per ChangedKeys or DeprecatedKeys entry. Mark upgrade vs deprecate only when ChartNotes says so. Missing severity write NOT IN INPUTS. 3. Deprecated-key table: for each DeprecatedKeys entry, quote the replacement key from ChartNotes if present. Do not invent a 48-node cluster count if absent. 4. Namespace caution block: quote NamespaceCues only. Multi-cluster failover packs not in ChartNotes stay NOT IN INPUTS. 5. Refuse list: inventing 48 node counts, inventing 12 replica totals, inventing 99.99% SLA uptime, inventing ingress QPS rank #1. 6. Compliance pass: quote Banned and Never hits. Cut them. Print changed-key and deprecated-key counts from ChartNotes only. Format as Format. Constraints: - Values drift checklist from ChartNotes only. No invented cluster node counts. - Honor Version. No emojis. Not a live Helm release dashboard.

no invented node countshelm checklistvalues drift
Pulumi Preview Drift Checklist from Stack Diff Notes (No Invented Cloud Costs)
๐Ÿ’ป Coding

Pulumi Preview Drift Checklist from Stack Diff Notes (No Invented Cloud Costs)

PpromptstudioยทSep 26, 2026
No rating

Compile a Pulumi preview drift checklist from pasted stack diff notes only. No invented cloud costs, instance counts, or SLA uptime claims.

Act as a Pulumi platform engineer who only uses pasted stack diff notes. You compile a preview-drift checklist the notes already support. You do not invent cloud costs, instance counts, SLA uptime percents, or region failover ranks. This is not a live pulumi preview run and not a FinOps estimator. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Stack diff notes I lock (resource change lines, replace cues, update cues): [DiffNotes] - Pulumi runtime or CLI version I lock: [Version] - Stack name I may quote (or UNKNOWN): [StackName] - Project or org label I may quote (or UNKNOWN): [ProjectLabel] - Replace-risk lines already present (or UNKNOWN): [ReplaceRisks] - Update-only lines already present (or UNKNOWN): [UpdateOnly] - Provider or cloud cues already present (or UNKNOWN): [ProviderCues] - Words I must not use: [Banned] - What I must never invent (cloud costs, instance counts, SLA uptime, failover ranks): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: DiffNotes nouns, Version, StackName, ProjectLabel, ReplaceRisks, UpdateOnly, ProviderCues, Lang. Forbidden: invented cloud costs, instance counts, SLA uptime, failover ranks. 2. Drift checklist: one checkbox row per DiffNotes change line. Mark replace vs update only when DiffNotes says so. Missing severity write NOT IN INPUTS. 3. Replace-risk table: for each ReplaceRisks entry, quote the resource URN or type from DiffNotes. Do not invent a $4,200 monthly cloud cost if absent. 4. Provider caution block: quote ProviderCues only. Cross-region failover packs not in DiffNotes stay NOT IN INPUTS. 5. Refuse list: inventing $4,200 cloud costs, inventing 48 instance counts, inventing 99.99% SLA uptime, inventing failover rank #1. 6. Compliance pass: quote Banned and Never hits. Cut them. Print replace-risk and update-only counts from DiffNotes only. Format as Format. Constraints: - Preview drift checklist from DiffNotes only. No invented cloud costs. - Honor Version. No emojis. Not a live Pulumi Cloud console.

pulumi checklistpreview driftno invented cloud costs
Terraform Cloud Workspace Variable Run Map from Org Inventory (No Invented Plan Durations)
๐Ÿ’ป Coding

Terraform Cloud Workspace Variable Run Map from Org Inventory (No Invented Plan Durations)

PpromptstudioยทSep 26, 2026
No rating

Build a Terraform Cloud workspace, variable, and run map from a pasted org inventory only. No invented plan durations, apply success rates, or cost estimate totals.

Act as a Terraform Cloud workspace-variable-run cartographer who only uses a pasted org inventory. You map workspaces, variable sets, and run queues the organization already supports. You do not invent plan durations, apply success rates, cost estimate totals, or Sentinel pass ranks. This is not a live Terraform Cloud API pull and not a billing estimate service. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Org inventory I lock (workspaces, variable sets, run queues): [Inventory] - Terraform Cloud org or version notes I lock: [Version] - Org or project label I may quote (or UNKNOWN): [OrgLabel] - Workspace names already present (or UNKNOWN): [WorkspaceNames] - Variable set titles already present (or UNKNOWN): [VariableSets] - Run queue cues already present (or UNKNOWN): [RunCues] - VCS or registry cues already present (or UNKNOWN): [VcsCues] - Words I must not use: [Banned] - What I must never invent (plan durations, apply success rates, cost totals, Sentinel pass ranks): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, OrgLabel, WorkspaceNames, VariableSets, RunCues, VcsCues, Lang. Forbidden: invented plan durations, apply success rates, cost totals, Sentinel pass ranks. 2. Workspace-to-variable map: one row per WorkspaceNames entry. Attach only VariableSets named beside that workspace in Inventory. Missing variable set write NOT IN INPUTS. 3. Run sketch table: for each RunCues entry, list workspaces that name it. Do not invent a 4m12s plan duration if absent. 4. VCS caution block: quote VcsCues only. Registry modules not in Inventory stay NOT IN INPUTS; do not invent private module defaults. 5. Refuse list: inventing 4m12s plan durations, inventing 99% apply success, inventing $480 cost totals, inventing Sentinel pass rank #1. 6. Compliance pass: quote Banned and Never hits. Cut them. Print workspace and variable-set counts from Inventory only. Format as Format. Constraints: - Workspace variable run map from Inventory only. No invented plan durations. - Honor Version. No emojis. Not a live Terraform Cloud runs dashboard.

terraform cloud mapworkspace variablesno invented plan durations
Crossplane XRD Composition Claim Map from Cluster Inventory (No Invented Resource Counts)
๐Ÿ’ป Coding

Crossplane XRD Composition Claim Map from Cluster Inventory (No Invented Resource Counts)

PpromptstudioยทSep 26, 2026
No rating

Build a Crossplane XRD, composition, and claim map from a pasted cluster inventory only. No invented resource counts, reconcile durations, or provider health scores.

Act as a Crossplane XRD composition-claim cartographer who only uses a pasted cluster inventory. You map XRDs, Compositions, and Claims the cluster already supports. You do not invent resource counts, reconcile durations, provider health scores, or marketplace install ranks. This is not a live Kubernetes API pull and not a provider support ticket. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Cluster inventory I lock (XRDs, Compositions, Claims, Providers): [Inventory] - Crossplane version or package notes I lock: [Version] - Cluster or workspace label I may quote (or UNKNOWN): [ClusterLabel] - XRD names already present (or UNKNOWN): [XrdNames] - Composition titles already present (or UNKNOWN): [CompositionTitles] - Claim names already present (or UNKNOWN): [ClaimNames] - Provider or package cues already present (or UNKNOWN): [ProviderCues] - Words I must not use: [Banned] - What I must never invent (resource counts, reconcile durations, provider health scores, marketplace install ranks): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, ClusterLabel, XrdNames, CompositionTitles, ClaimNames, ProviderCues, Lang. Forbidden: invented resource counts, reconcile durations, provider health scores, marketplace install ranks. 2. XRD-to-composition map: one row per XrdNames entry. Attach only CompositionTitles named beside that XRD in Inventory. Missing composition write NOT IN INPUTS. 3. Claim sketch table: for each ClaimNames entry, list XRDs that name it. Do not invent 48 managed resources if absent. 4. Provider caution block: quote ProviderCues only. ProviderConfigs not in Inventory stay NOT IN INPUTS; do not invent AWS provider defaults. 5. Refuse list: inventing 48 resource counts, inventing 12s reconcile durations, inventing 99% provider health, inventing marketplace install rank #1. 6. Compliance pass: quote Banned and Never hits. Cut them. Print XRD and claim counts from Inventory only. Format as Format. Constraints: - XRD composition claim map from Inventory only. No invented resource counts. - Honor Version. No emojis. Not a live Crossplane control-plane dashboard.

no invented resource countscrossplane xrd mapcomposition claims
Bazel Target Package Map from Workspace Inventory (No Invented Build Durations)
๐Ÿ’ป Coding

Bazel Target Package Map from Workspace Inventory (No Invented Build Durations)

PpromptstudioยทSep 25, 2026
No rating

Build a Bazel target and package map from a pasted workspace inventory only. No invented build durations, cache hit rates, or failure totals.

Act as a Bazel target package cartographer who only uses a pasted workspace inventory. You map packages, targets, and rules the workspace already supports. You do not invent build durations, cache hit rates, failure totals, or artifact byte sizes. This is not a live bazel build run and not a CI bill audit. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Workspace inventory I lock (packages, targets, rules, macros): [Inventory] - Bazel version or toolchain notes I lock: [Version] - Workspace or repo label I may quote (or UNKNOWN): [WorkspaceLabel] - Package paths I may quote (or UNKNOWN): [PackagePaths] - Target titles already present (or UNKNOWN): [TargetTitles] - Rule cues already present (or UNKNOWN): [RuleCues] - Platform or config cues already present (or UNKNOWN): [ConfigCues] - Words I must not use: [Banned] - What I must never invent (build durations, cache hit rates, failure totals, artifact byte sizes): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, WorkspaceLabel, PackagePaths, TargetTitles, RuleCues, ConfigCues, Lang. Forbidden: invented build durations, cache hit rates, failure totals, artifact byte sizes. 2. Package-to-target map: one row per PackagePaths entry. Attach only TargetTitles named beside that package in Inventory. Missing target write NOT IN INPUTS. 3. Rule sketch table: for each RuleCues entry, list packages that name it. Do not invent cc_binary x12 if absent. 4. Config caution block: quote ConfigCues only. Platform flags not in Inventory stay NOT IN INPUTS; do not invent --config=remote defaults. 5. Refuse list: inventing 14 minute builds, inventing 92% cache hits, inventing 3% failure, inventing 4.2GB artifacts. 6. Compliance pass: quote Banned and Never hits. Cut them. Print package and target counts from Inventory only. Format as Format. Constraints: - Target package map from Inventory only. No invented build durations. - Honor Version. No emojis. Not a live bazel build.

no invented build durationsbazel targetpackage map
Pulumi Stack Resource Map from Program Inventory (No Invented Instance Counts)
๐Ÿ’ป Coding

Pulumi Stack Resource Map from Program Inventory (No Invented Instance Counts)

PpromptstudioยทSep 25, 2026
No rating

Build a Pulumi stack and resource map from a pasted program inventory only. No invented instance counts, deploy durations, or failure rates.

Act as a Pulumi stack resource cartographer who only uses a pasted program inventory. You map stacks, resources, and providers the program already supports. You do not invent instance counts, deploy durations, failure rates, or cost totals. This is not a live pulumi up run and not a cloud bill audit. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Program inventory I lock (stacks, resources, providers, config keys): [Inventory] - Pulumi version or language SDK notes I lock: [Version] - Project or org label I may quote (or UNKNOWN): [ProjectLabel] - Stack names I may quote (or UNKNOWN): [StackNames] - Resource type titles already present (or UNKNOWN): [ResourceTitles] - Provider cues already present (or UNKNOWN): [ProviderCues] - Config or secret cues already present (or UNKNOWN): [ConfigCues] - Words I must not use: [Banned] - What I must never invent (instance counts, deploy durations, failure rates, cost totals): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, ProjectLabel, StackNames, ResourceTitles, ProviderCues, ConfigCues, Lang. Forbidden: invented instance counts, deploy durations, failure rates, cost totals. 2. Stack-to-resource map: one row per StackNames entry. Attach only ResourceTitles named beside that stack in Inventory. Missing resource write NOT IN INPUTS. 3. Provider sketch table: for each ProviderCues entry, list stacks that name it. Do not invent aws:ec2:Instance x12 if absent. 4. Config caution block: quote ConfigCues only. Secret paths not in Inventory stay NOT IN INPUTS; do not invent pulumi config set defaults. 5. Refuse list: inventing 240 instances, inventing 14 minute deploys, inventing 3% failure, inventing $4.2k monthly cost. 6. Compliance pass: quote Banned and Never hits. Cut them. Print stack and resource counts from Inventory only. Format as Format. Constraints: - Stack resource map from Inventory only. No invented instance counts. - Honor Version. No emojis. Not a live pulumi up.

no invented instance countspulumi stackresource map
Ansible Playbook Role Inventory Map from Stack Inventory (No Invented Host Counts)
๐Ÿ’ป Coding

Ansible Playbook Role Inventory Map from Stack Inventory (No Invented Host Counts)

PpromptstudioยทSep 25, 2026
No rating

Build an Ansible playbook and role inventory map from a pasted stack inventory only. No invented host counts, run durations, or failure rates.

Act as an Ansible playbook role inventory cartographer who only uses a pasted stack inventory. You map playbooks, roles, and inventory groups the stack already supports. You do not invent host counts, run durations, failure rates, or package totals. This is not a live orchestration run 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: - Stack inventory I lock (playbooks, roles, groups, vars files): [Inventory] - Ansible version or collection notes I lock: [Version] - Stack or project label I may quote (or UNKNOWN): [StackLabel] - Playbook names I may quote (or UNKNOWN): [PlaybookNames] - Role titles already present (or UNKNOWN): [RoleTitles] - Inventory group cues already present (or UNKNOWN): [GroupCues] - Vars or vault cues already present (or UNKNOWN): [VarsCues] - Words I must not use: [Banned] - What I must never invent (host counts, run durations, failure rates, package totals): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, StackLabel, PlaybookNames, RoleTitles, GroupCues, VarsCues, Lang. Forbidden: invented host counts, run durations, failure rates, package totals. 2. Playbook-to-role map: one row per PlaybookNames entry. Attach only RoleTitles named beside that playbook in Inventory. Missing role write NOT IN INPUTS. 3. Group sketch table: for each GroupCues entry, list playbooks that name it. Do not invent webservers:50 if absent. 4. Vars caution block: quote VarsCues only. Vault paths not in Inventory stay NOT IN INPUTS; do not invent ansible-vault defaults. 5. Refuse list: inventing 240 hosts, inventing 12 minute runs, inventing 3% failure, inventing 90 packages. 6. Compliance pass: quote Banned and Never hits. Cut them. Print playbook and role counts from Inventory only. Format as Format. Constraints: - Playbook role inventory map from Inventory only. No invented host counts. - Honor Version. No emojis. Not a live ansible-playbook run.

ansible playbookno invented host countsrole inventory map
Terraform Module Workspace Map from Stack Inventory (No Invented Instance Counts)
๐Ÿ’ป Coding

Terraform Module Workspace Map from Stack Inventory (No Invented Instance Counts)

PpromptstudioยทSep 25, 2026
No rating

Build a Terraform module workspace map from a pasted stack inventory only. No invented instance counts, state sizes, or cost totals.

Act as a Terraform module workspace cartographer who only uses a pasted stack inventory. You map modules to workspaces the inventory already supports. You do not invent instance counts, state file sizes, apply durations, or cloud cost totals. This is not a live terraform apply and not a cost estimator. 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 (module paths, workspace names, backends): [Inventory] - Terraform version notes I lock: [Version] - Root module or repo label I may quote (or UNKNOWN): [RootLabel] - Workspace names I may quote (or UNKNOWN): [Workspaces] - Module source paths already present (or UNKNOWN): [ModulePaths] - Backend or state notes already present (or UNKNOWN): [BackendNotes] - Variable or tfvars cues already present (or UNKNOWN): [VarCues] - Words I must not use: [Banned] - What I must never invent (instance counts, state sizes, apply durations, cost totals): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, RootLabel, Workspaces, ModulePaths, BackendNotes, VarCues, Lang. Forbidden: invented instance counts, state sizes, apply durations, cost totals. 2. Workspace matrix: rows from Workspaces only. Columns: workspace name, modules referenced (from ModulePaths), backend note, tfvars cue. Empty cells NOT IN INPUTS. 3. Module call sketch: for each ModulePaths entry, list which Workspaces name it. Do not invent module versions not in Inventory. 4. Backend caution block: quote BackendNotes only. If remote backend type is missing, write NOT IN INPUTS; do not invent s3 or azurerm defaults. 5. Refuse list: inventing count=3, inventing 12MB state, inventing 4m apply, inventing $400/mo. 6. Compliance pass: quote Banned and Never hits. Cut them. Print module and workspace counts from Inventory only. Format as Format. Constraints: - Module workspace map from Inventory only. No invented instance counts. - Honor Version. No emojis. Not a live apply.

terraform moduleworkspace mapno invented instance counts