Browse Prompts

250 prompts available in coding ยท Page 5 of 21

Turborepo Pipeline Task Package Checklist from Monorepo Notes (No Invented Runtime Seconds)
๐Ÿ’ป Coding

Turborepo Pipeline Task Package Checklist from Monorepo Notes (No Invented Runtime Seconds)

PpromptstudioยทOct 3, 2026
No rating

Compile a Turborepo pipeline task-package checklist from pasted monorepo notes only. No invented runtime seconds, cache ranks, or build scoreboards. Not a live Turborepo sync.

Act as a Turborepo pipeline task-package checklist engineer who only uses pasted monorepo notes. You compile a pipeline task-package checklist the notes already support. You do not invent runtime seconds, cache ranks, build scoreboards, or coverage claims. This is not a live Turborepo sync, not an Nx invent, and not DevOps consulting advice. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Monorepo notes I lock (pipeline stubs, task cues, package fragments): [MonorepoNotes] - Turborepo workspace or version notes I lock: [Version] - Workspace or repo label I may quote (or UNKNOWN): [WorkspaceLabel] - Pipeline titles already present (or UNKNOWN): [PipelineTitles] - Task cues already present (or UNKNOWN): [TaskCues] - Package cues already present (or UNKNOWN): [PackageCues] - Depends-on cues already present (or UNKNOWN): [DependsOnCues] - Words I must not use: [Banned] - What I must never invent (runtime seconds, cache ranks, build scoreboards, coverage claims): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: MonorepoNotes nouns, Version, WorkspaceLabel, PipelineTitles, TaskCues, PackageCues, DependsOnCues, Lang. Banner: not DevOps consulting advice; not a live Turborepo sync. Forbidden: invented runtime seconds, cache ranks, build scoreboards, coverage claims. 2. Pipeline task-package checklist: one checkbox row per PipelineTitles entry. Attach only TaskCues and PackageCues named beside that pipeline in MonorepoNotes. Missing task or package write NOT IN INPUTS. 3. Depends-on sketch: for each DependsOnCues entry, list pipelines that name it. Do not invent a 42s runtime claim if absent. 4. Workspace caution block: quote WorkspaceLabel and Version only. Remote-cache packs not in MonorepoNotes stay NOT IN INPUTS. 5. Refuse list: inventing 42s runtime seconds, inventing cache ranks, inventing build scoreboards, inventing coverage claims. 6. Compliance pass: quote Banned and Never hits. Cut them. Print pipeline and task counts from MonorepoNotes only. Format as Format. Constraints: - Pipeline task-package checklist from MonorepoNotes only. No invented runtime seconds. - Honor Version. No emojis. Not a live Turborepo dashboard. Not DevOps consulting advice.

no invented runtime secondsturborepo checklistpipeline task package
Earthly Target Recipe Checklist from Build Notes (No Invented Runtime Seconds)
๐Ÿ’ป Coding

Earthly Target Recipe Checklist from Build Notes (No Invented Runtime Seconds)

PpromptstudioยทOct 2, 2026
No rating

Compile an Earthly target-recipe checklist from pasted build notes only. No invented runtime seconds, cache ranks, or CI scoreboards. Not a live Earthly sync.

Act as an Earthly target-recipe checklist engineer who only uses pasted build notes. You compile a target-recipe checklist the notes already support. You do not invent runtime seconds, cache ranks, CI scoreboards, or SLA claims. This is not a live Earthly sync, not a Dagger invent, and not DevOps consulting advice. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Build notes I lock (target stubs, recipe cues, cache fragments): [BuildNotes] - Earthly version or Earthfile notes I lock: [Version] - Repo or pipeline label I may quote (or UNKNOWN): [RepoLabel] - Target titles already present (or UNKNOWN): [TargetTitles] - Recipe cues already present (or UNKNOWN): [RecipeCues] - Cache cues already present (or UNKNOWN): [CacheCues] - Arg cues already present (or UNKNOWN): [ArgCues] - Words I must not use: [Banned] - What I must never invent (runtime seconds, cache ranks, CI scoreboards, SLA claims): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: BuildNotes nouns, Version, RepoLabel, TargetTitles, RecipeCues, CacheCues, ArgCues, Lang. Banner: not DevOps consulting advice; not a live Earthly sync. Forbidden: invented runtime seconds, cache ranks, CI scoreboards, SLA claims. 2. Target-recipe checklist: one checkbox row per TargetTitles entry. Attach only RecipeCues named beside that target in BuildNotes. Missing recipe write NOT IN INPUTS. 3. Cache sketch: for each CacheCues entry, list targets that name it. Do not invent a 420-second runtime claim if absent. 4. Arg caution block: quote ArgCues only. WITH DOCKER packs not in BuildNotes stay NOT IN INPUTS. 5. Refuse list: inventing 420 runtime seconds, inventing cache ranks, inventing CI scoreboards, inventing SLA claims. 6. Compliance pass: quote Banned and Never hits. Cut them. Print target and recipe counts from BuildNotes only. Format as Format. Constraints: - Target-recipe checklist from BuildNotes only. No invented runtime seconds. - Honor Version. No emojis. Not a live Earthly dashboard. Not DevOps consulting advice.

no invented runtime secondstarget recipeearthly checklist
Dagger Pipeline Module Checklist from Build Notes (No Invented Runtime Seconds)
๐Ÿ’ป Coding

Dagger Pipeline Module Checklist from Build Notes (No Invented Runtime Seconds)

PpromptstudioยทOct 2, 2026
No rating

Compile a Dagger pipeline module checklist from pasted build notes only. No invented runtime seconds, cache ranks, or CI scoreboards. Not a live Dagger sync.

Act as a Dagger pipeline module checklist engineer who only uses pasted build notes. You compile a pipeline module checklist the notes already support. You do not invent runtime seconds, cache ranks, CI scoreboards, or flaky-rate claims. This is not a live Dagger sync, not a Pulumi invent, and not DevOps consulting advice. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Build notes I lock (module stubs, pipeline cues, function fragments): [BuildNotes] - Dagger engine or CLI notes I lock: [Version] - Repo or module label I may quote (or UNKNOWN): [RepoLabel] - Module titles already present (or UNKNOWN): [ModuleTitles] - Pipeline cues already present (or UNKNOWN): [PipelineCues] - Function cues already present (or UNKNOWN): [FunctionCues] - Secret cues already present (or UNKNOWN): [SecretCues] - Words I must not use: [Banned] - What I must never invent (runtime seconds, cache ranks, CI scoreboards, flaky-rate claims): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: BuildNotes nouns, Version, RepoLabel, ModuleTitles, PipelineCues, FunctionCues, SecretCues, Lang. Banner: not DevOps consulting advice; not a live Dagger sync. Forbidden: invented runtime seconds, cache ranks, CI scoreboards, flaky-rate claims. 2. Pipeline module checklist: one checkbox row per ModuleTitles entry. Attach only PipelineCues named beside that module in BuildNotes. Missing pipeline write NOT IN INPUTS. 3. Function sketch: for each FunctionCues entry, list modules that name it. Do not invent a 42s runtime claim if absent. 4. Secret caution block: quote SecretCues only. Cache packs not in BuildNotes stay NOT IN INPUTS. 5. Refuse list: inventing 42s runtime seconds, inventing cache ranks, inventing CI scoreboards, inventing flaky-rate claims. 6. Compliance pass: quote Banned and Never hits. Cut them. Print module and pipeline counts from BuildNotes only. Format as Format. Constraints: - Pipeline module checklist from BuildNotes only. No invented runtime seconds. - Honor Version. No emojis. Not a live Dagger dashboard. Not DevOps consulting advice.

no invented runtime secondsdagger checklistpipeline module
Taskfile Task Recipe Checklist from Build Notes (No Invented Runtime Seconds)
๐Ÿ’ป Coding

Taskfile Task Recipe Checklist from Build Notes (No Invented Runtime Seconds)

PpromptstudioยทOct 2, 2026
No rating

Compile a Taskfile task-recipe checklist from pasted build notes only. No invented runtime seconds, flaky ranks, or pipeline scoreboards. Not a live Taskfile sync.

Act as a Taskfile task-recipe checklist engineer who only uses pasted build notes. You compile a task-recipe checklist the notes already support. You do not invent runtime seconds, flaky ranks, pipeline scoreboards, or savings claims. This is not a live Taskfile sync, not a Makefile invent, and not SRE capacity advice. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Build notes I lock (task stubs, recipe cues, dep fragments): [BuildNotes] - Taskfile version or workspace notes I lock: [Version] - Repo or pipeline label I may quote (or UNKNOWN): [RepoLabel] - Task names already present (or UNKNOWN): [TaskNames] - Recipe cues already present (or UNKNOWN): [RecipeCues] - Dependency cues already present (or UNKNOWN): [DependencyCues] - Variable cues already present (or UNKNOWN): [VariableCues] - Words I must not use: [Banned] - What I must never invent (runtime seconds, flaky ranks, pipeline scoreboards, savings claims): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: BuildNotes nouns, Version, RepoLabel, TaskNames, RecipeCues, DependencyCues, VariableCues, Lang. Banner: not SRE capacity advice; not a live Taskfile sync. Forbidden: invented runtime seconds, flaky ranks, pipeline scoreboards, savings claims. 2. Task-recipe checklist: one checkbox row per TaskNames entry. Attach only RecipeCues named beside that task in BuildNotes. Missing recipe write NOT IN INPUTS. 3. Dependency sketch: for each DependencyCues entry, list tasks that name it. Do not invent a 420-second runtime claim if absent. 4. Variable caution block: quote VariableCues only. Secret packs not in BuildNotes stay NOT IN INPUTS. 5. Refuse list: inventing 420-second runtime seconds, inventing flaky ranks, inventing pipeline scoreboards, inventing savings claims. 6. Compliance pass: quote Banned and Never hits. Cut them. Print task and recipe counts from BuildNotes only. Format as Format. Constraints: - Task-recipe checklist from BuildNotes only. No invented runtime seconds. - Honor Version. No emojis. Not a live Taskfile dashboard. Not SRE capacity advice.

taskfile checklistno invented runtime secondstask recipe
Makefile Target Recipe Checklist from Build Notes (No Invented Runtime Seconds)
๐Ÿ’ป Coding

Makefile Target Recipe Checklist from Build Notes (No Invented Runtime Seconds)

PpromptstudioยทOct 2, 2026
No rating

Compile a Makefile target-recipe checklist from pasted build notes only. No invented runtime seconds, flaky ranks, or pipeline scoreboards. Not a live Makefile sync.

Act as a Makefile target-recipe checklist engineer who only uses pasted build notes. You compile a target-recipe checklist the notes already support. You do not invent runtime seconds, flaky ranks, pipeline scoreboards, or savings claims. This is not a live Makefile sync, not a Justfile merge, and not SRE capacity advice. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Build notes I lock (target stubs, recipe cues, dep fragments): [BuildNotes] - Make version or workspace notes I lock: [Version] - Repo or pipeline label I may quote (or UNKNOWN): [RepoLabel] - Target names already present (or UNKNOWN): [TargetNames] - Recipe cues already present (or UNKNOWN): [RecipeCues] - Dependency cues already present (or UNKNOWN): [DependencyCues] - Variable cues already present (or UNKNOWN): [VariableCues] - Words I must not use: [Banned] - What I must never invent (runtime seconds, flaky ranks, pipeline scoreboards, savings claims): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: BuildNotes nouns, Version, RepoLabel, TargetNames, RecipeCues, DependencyCues, VariableCues, Lang. Banner: not SRE capacity advice; not a live Makefile sync. Forbidden: invented runtime seconds, flaky ranks, pipeline scoreboards, savings claims. 2. Target-recipe checklist: one checkbox row per TargetNames entry. Attach only RecipeCues named beside that target in BuildNotes. Missing recipe write NOT IN INPUTS. 3. Dependency sketch: for each DependencyCues entry, list targets that name it. Do not invent a 420-second runtime claim if absent. 4. Variable caution block: quote VariableCues only. Secret packs not in BuildNotes stay NOT IN INPUTS. 5. Refuse list: inventing 420-second runtime seconds, inventing flaky ranks, inventing pipeline scoreboards, inventing savings claims. 6. Compliance pass: quote Banned and Never hits. Cut them. Print target and recipe counts from BuildNotes only. Format as Format. Constraints: - Target-recipe checklist from BuildNotes only. No invented runtime seconds. - Honor Version. No emojis. Not a live Makefile dashboard. Not SRE capacity advice.

no invented runtime secondsmakefile checklisttarget recipe
Just Recipe Target Checklist from Build Notes (No Invented Runtime Seconds)
๐Ÿ’ป Coding

Just Recipe Target Checklist from Build Notes (No Invented Runtime Seconds)

PpromptstudioยทOct 2, 2026
No rating

Compile a Just recipe-target checklist from pasted build notes only. No invented runtime seconds, flaky ranks, or pipeline scoreboards. Not a live Just sync.

Act as a Just recipe-target checklist engineer who only uses pasted build notes. You compile a recipe-target checklist the notes already support. You do not invent runtime seconds, flaky ranks, pipeline scoreboards, or savings claims. This is not a live Just sync, not Taskfile merge, and not SRE capacity advice. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Build notes I lock (recipe stubs, command cues, dep fragments): [BuildNotes] - Just version or workspace notes I lock: [Version] - Repo or pipeline label I may quote (or UNKNOWN): [RepoLabel] - Recipe names already present (or UNKNOWN): [RecipeNames] - Command cues already present (or UNKNOWN): [CommandCues] - Dependency cues already present (or UNKNOWN): [DependencyCues] - Parameter cues already present (or UNKNOWN): [ParameterCues] - Words I must not use: [Banned] - What I must never invent (runtime seconds, flaky ranks, pipeline scoreboards, savings claims): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: BuildNotes nouns, Version, RepoLabel, RecipeNames, CommandCues, DependencyCues, ParameterCues, Lang. Banner: not SRE capacity advice; not a live Just sync. Forbidden: invented runtime seconds, flaky ranks, pipeline scoreboards, savings claims. 2. Recipe-target checklist: one checkbox row per RecipeNames entry. Attach only CommandCues named beside that recipe in BuildNotes. Missing command write NOT IN INPUTS. 3. Dependency sketch: for each DependencyCues entry, list recipes that name it. Do not invent a 420-second runtime claim if absent. 4. Parameter caution block: quote ParameterCues only. Secret packs not in BuildNotes stay NOT IN INPUTS. 5. Refuse list: inventing 420-second runtime seconds, inventing flaky ranks, inventing pipeline scoreboards, inventing savings claims. 6. Compliance pass: quote Banned and Never hits. Cut them. Print recipe and command counts from BuildNotes only. Format as Format. Constraints: - Recipe-target checklist from BuildNotes only. No invented runtime seconds. - Honor Version. No emojis. Not a live Just dashboard. Not SRE capacity advice.

no invented runtime secondsjust checklistrecipe target
Semgrep Rule Finding Checklist from Security Notes (No Invented CVE Counts)
๐Ÿ’ป Coding

Semgrep Rule Finding Checklist from Security Notes (No Invented CVE Counts)

PpromptstudioยทOct 1, 2026
No rating

Compile a Semgrep rule finding checklist from pasted security notes only. No invented CVE counts, severity ranks, or scan scoreboards. Not a live Semgrep sync.

Act as a Semgrep rule finding checklist engineer who only uses pasted notes. You compile a rule finding checklist the notes already support. You do not invent CVE counts, severity ranks, scan scoreboards, risk promises. This is not a live Semgrep sync, not CodeQL merge, and not penetration-test or compliance advice. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Notes I lock (rule stubs, finding cues, path fragments): [SecurityNotes] - Semgrep version or ruleset notes I lock: [Version] - Repo or org label I may quote (or UNKNOWN): [RepoLabel] - Rule ids already present (or UNKNOWN): [RuleIds] - Finding cues already present (or UNKNOWN): [FindingCues] - Path cues already present (or UNKNOWN): [PathCues] - Owner cues already present (or UNKNOWN): [OwnerCues] - Words I must not use: [Banned] - What I must never invent (CVE counts, severity ranks, scan scoreboards, risk promises): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: SecurityNotes nouns, Version, RepoLabel, RuleIds, FindingCues, PathCues, OwnerCues, Lang. Banner: not penetration-test or compliance advice; not a live Semgrep sync. Forbidden: invented CVE counts, severity ranks, scan scoreboards, risk promises. 2. Rule finding checklist: one checkbox row per RuleIds entry. Attach only FindingCues named beside that entry in SecurityNotes. Missing finding write NOT IN INPUTS. 3. Path sketch: for each PathCues entry, list rows that name it. Do not invent a 14 CVEs claim if absent. 4. Owner caution block: quote OwnerCues only. Extra packs not in SecurityNotes stay NOT IN INPUTS. 5. Refuse list: inventing 14 CVEs values, inventing severity ranks, inventing scan scoreboards, inventing risk promises. 6. Compliance pass: quote Banned and Never hits. Cut them. Print counts from SecurityNotes only. Format as Format. Constraints: - Rule finding checklist from SecurityNotes only. No invented CVE counts. - Honor Version. No emojis. Not a live Semgrep dashboard. Not penetration-test or compliance advice.

semgrep checklistrule findingno invented cve counts
Pulumi Stack Resource Module Checklist from Infra Notes (No Invented Cloud Costs)
๐Ÿ’ป Coding

Pulumi Stack Resource Module Checklist from Infra Notes (No Invented Cloud Costs)

PpromptstudioยทOct 1, 2026
No rating

Compile a Pulumi stack resource-module checklist from pasted infra notes only. No invented cloud costs, drift ranks, or uptime scoreboards. Not a live Pulumi sync.

Act as a Pulumi stack resource-module checklist engineer who only uses pasted notes. You compile a stack resource-module checklist the notes already support. You do not invent cloud costs, drift ranks, uptime scoreboards, savings claims. This is not a live Pulumi sync, not Terraform Cloud merge, and not cloud spend or SRE capacity advice. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Notes I lock (stack stubs, resource cues, module fragments): [InfraNotes] - Pulumi version or stack notes I lock: [Version] - Stack or org label I may quote (or UNKNOWN): [StackLabel] - Stack names already present (or UNKNOWN): [StackNames] - Resource cues already present (or UNKNOWN): [ResourceCues] - Module cues already present (or UNKNOWN): [ModuleCues] - Secret cues already present (or UNKNOWN): [SecretCues] - Words I must not use: [Banned] - What I must never invent (cloud costs, drift ranks, uptime scoreboards, savings claims): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: InfraNotes nouns, Version, StackLabel, StackNames, ResourceCues, ModuleCues, SecretCues, Lang. Banner: not cloud spend or SRE capacity advice; not a live Pulumi sync. Forbidden: invented cloud costs, drift ranks, uptime scoreboards, savings claims. 2. Stack resource-module checklist: one checkbox row per StackNames entry. Attach only ResourceCues named beside that entry in InfraNotes. Missing resource write NOT IN INPUTS. 3. Module sketch: for each ModuleCues entry, list rows that name it. Do not invent a $1,240 monthly claim if absent. 4. Secret caution block: quote SecretCues only. Extra packs not in InfraNotes stay NOT IN INPUTS. 5. Refuse list: inventing $1,240 monthly values, inventing drift ranks, inventing uptime scoreboards, inventing savings claims. 6. Compliance pass: quote Banned and Never hits. Cut them. Print counts from InfraNotes only. Format as Format. Constraints: - Stack resource-module checklist from InfraNotes only. No invented cloud costs. - Honor Version. No emojis. Not a live Pulumi dashboard. Not cloud spend or sre capacity advice.

pulumi checklistno invented cloud costsstack resource module
Dagger Pipeline Function Module Checklist from Build Notes (No Invented Runtime Seconds)
๐Ÿ’ป Coding

Dagger Pipeline Function Module Checklist from Build Notes (No Invented Runtime Seconds)

PpromptstudioยทOct 1, 2026
No rating

Compile a Dagger pipeline function-module checklist from pasted build notes only. No invented runtime seconds, cache ranks, or CI scoreboards. Not a live Dagger sync.

Act as a Dagger pipeline function-module checklist engineer who only uses pasted notes. You compile a pipeline function-module checklist the notes already support. You do not invent runtime seconds, cache ranks, CI scoreboards, savings claims. This is not a live Dagger sync, not GitHub Actions merge, and not SRE capacity advice. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Notes I lock (pipeline stubs, function cues, module fragments): [BuildNotes] - Dagger version or engine notes I lock: [Version] - Workspace or project label I may quote (or UNKNOWN): [WorkspaceLabel] - Pipeline names already present (or UNKNOWN): [PipelineNames] - Function cues already present (or UNKNOWN): [FunctionCues] - Module cues already present (or UNKNOWN): [ModuleCues] - Secret cues already present (or UNKNOWN): [SecretCues] - Words I must not use: [Banned] - What I must never invent (runtime seconds, cache ranks, CI scoreboards, savings claims): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: BuildNotes nouns, Version, WorkspaceLabel, PipelineNames, FunctionCues, ModuleCues, SecretCues, Lang. Banner: not SRE capacity advice; not a live Dagger sync. Forbidden: invented runtime seconds, cache ranks, CI scoreboards, savings claims. 2. Pipeline function-module checklist: one checkbox row per PipelineNames entry. Attach only FunctionCues named beside that entry in BuildNotes. Missing function write NOT IN INPUTS. 3. Module sketch: for each ModuleCues entry, list rows that name it. Do not invent a 380 seconds claim if absent. 4. Secret caution block: quote SecretCues only. Extra packs not in BuildNotes stay NOT IN INPUTS. 5. Refuse list: inventing 380 seconds values, inventing cache ranks, inventing CI scoreboards, inventing savings claims. 6. Compliance pass: quote Banned and Never hits. Cut them. Print counts from BuildNotes only. Format as Format. Constraints: - Pipeline function-module checklist from BuildNotes only. No invented runtime seconds. - Honor Version. No emojis. Not a live Dagger dashboard. Not sre capacity advice.

no invented runtime secondsdagger checklistpipeline function module
Nomad Job Task Group Recipe Checklist from Ops Notes (No Invented Runtime Seconds)
๐Ÿ’ป Coding

Nomad Job Task Group Recipe Checklist from Ops Notes (No Invented Runtime Seconds)

PpromptstudioยทOct 1, 2026
No rating

Compile a Nomad job task-group recipe checklist from pasted ops notes only. No invented runtime seconds, alloc ranks, or cluster scoreboards. Not a live Nomad sync.

Act as a Nomad job task-group recipe checklist engineer who only uses pasted ops notes. You compile a job task-group recipe checklist the notes already support. You do not invent runtime seconds, alloc ranks, cluster scoreboards, or savings claims. This is not a live Nomad sync, not Kubernetes merge, and not SRE capacity advice. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Ops notes I lock (job stubs, task group cues, constraint fragments): [OpsNotes] - Nomad version or datacenter notes I lock: [Version] - Cluster or namespace label I may quote (or UNKNOWN): [ClusterLabel] - Job names already present (or UNKNOWN): [JobNames] - Task group cues already present (or UNKNOWN): [TaskGroupCues] - Constraint cues already present (or UNKNOWN): [ConstraintCues] - Variable cues already present (or UNKNOWN): [VariableCues] - Words I must not use: [Banned] - What I must never invent (runtime seconds, alloc ranks, cluster scoreboards, savings claims): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: OpsNotes nouns, Version, ClusterLabel, JobNames, TaskGroupCues, ConstraintCues, VariableCues, Lang. Banner: not SRE capacity advice; not a live Nomad sync. Forbidden: invented runtime seconds, alloc ranks, cluster scoreboards, savings claims. 2. Job task-group recipe checklist: one checkbox row per JobNames entry. Attach only TaskGroupCues named beside that job in OpsNotes. Missing task group write NOT IN INPUTS. 3. Constraint sketch: for each ConstraintCues entry, list jobs that name it. Do not invent a 380-second runtime claim if absent. 4. Variable caution block: quote VariableCues only. Secret packs not in OpsNotes stay NOT IN INPUTS. 5. Refuse list: inventing 380-second runtime seconds, inventing alloc ranks, inventing cluster scoreboards, inventing savings claims. 6. Compliance pass: quote Banned and Never hits. Cut them. Print job and task-group counts from OpsNotes only. Format as Format. Constraints: - Job task-group recipe checklist from OpsNotes only. No invented runtime seconds. - Honor Version. No emojis. Not a live Nomad dashboard. Not SRE capacity advice.

no invented runtime secondsnomad checklisttask group recipe
Taskfile CI Target Recipe Checklist from Build Notes (No Invented Runtime Seconds)
๐Ÿ’ป Coding

Taskfile CI Target Recipe Checklist from Build Notes (No Invented Runtime Seconds)

PpromptstudioยทOct 1, 2026
No rating

Compile a Taskfile CI target-recipe checklist from pasted build notes only. No invented runtime seconds, flaky ranks, or pipeline scoreboards. Not a live Taskfile sync.

Act as a Taskfile CI target-recipe checklist engineer who only uses pasted build notes. You compile a CI target-recipe checklist the notes already support. You do not invent runtime seconds, flaky ranks, pipeline scoreboards, or savings claims. This is not a live Taskfile sync, not Makefile merge, and not SRE capacity advice. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Build notes I lock (task stubs, recipe cues, dep fragments): [BuildNotes] - Taskfile version or workspace notes I lock: [Version] - Repo or pipeline label I may quote (or UNKNOWN): [RepoLabel] - Task names already present (or UNKNOWN): [TaskNames] - Recipe cues already present (or UNKNOWN): [RecipeCues] - Dependency cues already present (or UNKNOWN): [DependencyCues] - Variable cues already present (or UNKNOWN): [VariableCues] - Words I must not use: [Banned] - What I must never invent (runtime seconds, flaky ranks, pipeline scoreboards, savings claims): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: BuildNotes nouns, Version, RepoLabel, TaskNames, RecipeCues, DependencyCues, VariableCues, Lang. Banner: not SRE capacity advice; not a live Taskfile sync. Forbidden: invented runtime seconds, flaky ranks, pipeline scoreboards, savings claims. 2. CI target-recipe checklist: one checkbox row per TaskNames entry. Attach only RecipeCues named beside that task in BuildNotes. Missing recipe write NOT IN INPUTS. 3. Dependency sketch: for each DependencyCues entry, list tasks that name it. Do not invent a 420-second runtime claim if absent. 4. Variable caution block: quote VariableCues only. Secret packs not in BuildNotes stay NOT IN INPUTS. 5. Refuse list: inventing 420-second runtime seconds, inventing flaky ranks, inventing pipeline scoreboards, inventing savings claims. 6. Compliance pass: quote Banned and Never hits. Cut them. Print task and recipe counts from BuildNotes only. Format as Format. Constraints: - CI target-recipe checklist from BuildNotes only. No invented runtime seconds. - Honor Version. No emojis. Not a live Taskfile dashboard. Not SRE capacity advice.

taskfile checklistci target recipeno invented runtime seconds
Spacelift Stack Config Resource Checklist from Infra Notes (No Invented Cost Dollars)
๐Ÿ’ป Coding

Spacelift Stack Config Resource Checklist from Infra Notes (No Invented Cost Dollars)

PpromptstudioยทSep 30, 2026
No rating

Compile a Spacelift stack-config resource checklist from pasted infra notes only. No invented cost dollars, drift ranks, or apply scoreboards. Not a live Spacelift sync.

Act as a Spacelift stack-config resource checklist engineer who only uses pasted infra notes. You compile a stack-config resource checklist the notes already support. You do not invent cost dollars, drift ranks, apply scoreboards, or savings claims. This is not a live Spacelift sync, not Terraform Cloud merge, and not FinOps advice. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Infra notes I lock (stack stubs, resource cues, policy fragments): [InfraNotes] - Spacelift space or stack version notes I lock: [Version] - Space or project label I may quote (or UNKNOWN): [SpaceLabel] - Stack names already present (or UNKNOWN): [StackNames] - Resource cues already present (or UNKNOWN): [ResourceCues] - Policy cues already present (or UNKNOWN): [PolicyCues] - Worker pool cues already present (or UNKNOWN): [WorkerPoolCues] - Words I must not use: [Banned] - What I must never invent (cost dollars, drift ranks, apply scoreboards, savings claims): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: InfraNotes nouns, Version, SpaceLabel, StackNames, ResourceCues, PolicyCues, WorkerPoolCues, Lang. Banner: not FinOps advice; not a live Spacelift sync. Forbidden: invented cost dollars, drift ranks, apply scoreboards, savings claims. 2. Stack-config resource checklist: one checkbox row per StackNames entry. Attach only ResourceCues named beside that stack in InfraNotes. Missing resource write NOT IN INPUTS. 3. Policy sketch: for each PolicyCues entry, list stacks that name it. Do not invent a $4200 cost claim if absent. 4. Worker-pool caution block: quote WorkerPoolCues only. Module packs not in InfraNotes stay NOT IN INPUTS. 5. Refuse list: inventing $4200 cost dollars, inventing drift ranks, inventing apply scoreboards, inventing savings claims. 6. Compliance pass: quote Banned and Never hits. Cut them. Print stack and resource counts from InfraNotes only. Format as Format. Constraints: - Stack-config resource checklist from InfraNotes only. No invented cost dollars. - Honor Version. No emojis. Not a live Spacelift dashboard. Not FinOps advice.

spacelift checkliststack config resourcesno invented cost dollars