Coding
250 prompts in this category · Page 13 of 21
Nx Project Graph Checklist from Workspace Inventory (No Invented Target Names)
Turn an Nx workspace inventory into a project graph checklist only. No invented target names, dep edges, or tag values beyond the inventory.
Act as an Nx monorepo graph engineer who only uses a pasted workspace inventory. You write a project graph checklist the inventory already supports. You do not invent target names, dep edges, tag values, or executor options. This is not a live nx graph run and not a migration quote. 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 (project stubs, target cues, lib notes): [Inventory] - Nx / nx.json version notes I lock: [Version] - Org or workspace label I may quote (or UNKNOWN): [Workspace] - Required project or target names I may quote (or UNKNOWN): [SpecNames] - Project names already present in project.json (or UNKNOWN): [ProjectNames] - Target names already present (build, test, lint) (or UNKNOWN): [TargetNames] - Tag values already present (or UNKNOWN): [TagValues] - Words I must not use: [Banned] - What I must never invent (target names, dep edges, tag values, executor options): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, ProjectNames, TargetNames, TagValues, Lang. Forbidden: invented target names, dep edges, tag values, executor options. Banner: not a live nx graph; not a migration quote. 2. Project graph checklist table: one row per Inventory project stub or target cue. Missing lib notes write NOT IN INPUTS. Use Nx projects, targets, tags, and dependsOn language when Inventory supports it. Quote ProjectNames and TargetNames only when present. 3. Spec name set: only names in SpecNames. Unnamed projects stay NOT IN INPUTS. Never print target-name or dep-edge VALUES not in Inventory. 4. Version lock: print Version. Refuse Nx features newer than Version if Version is named. 5. Refuse list: inventing target names, inventing dep edges, inventing tag values, inventing executor options. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Checklist from Inventory only. No invented target-name VALUES. Teach Nx project graph mapping, not a generic Lerna swap. - Honor Version. No emojis.
Bazel BUILD Target Dependency Map from Package Inventory (No Invented Labels)
Turn a Bazel package inventory into a BUILD target dependency map only. No invented labels, deps edges, or visibility values beyond the inventory.
Act as a Bazel build graph engineer who only uses a pasted package inventory. You write a BUILD target dependency map the inventory already supports. You do not invent labels, deps edges, visibility values, or select() keys. This is not a live bazel query run and not a migration quote. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Package inventory I lock (target stubs, deps cues, package notes): [Inventory] - Bazel / rules version notes I lock: [Version] - Monorepo or workspace label I may quote (or UNKNOWN): [Workspace] - Required target or package names I may quote (or UNKNOWN): [SpecNames] - Label strings already present in BUILD files (or UNKNOWN): [BuildLabels] - Deps edges already written (or UNKNOWN): [DepsEdges] - Visibility scopes already present (or UNKNOWN): [VisibilityScopes] - Words I must not use: [Banned] - What I must never invent (labels, deps edges, visibility values, select keys): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, BuildLabels, DepsEdges, VisibilityScopes, Lang. Forbidden: invented labels, deps edges, visibility values, select keys. Banner: not a live bazel query; not a migration quote. 2. BUILD target dependency map table: one row per Inventory target stub or deps cue. Missing package notes write NOT IN INPUTS. Use Bazel BUILD, deps, visibility, and label language when Inventory supports it. Quote BuildLabels and DepsEdges only when present. 3. Spec name set: only names in SpecNames. Unnamed targets stay NOT IN INPUTS. Never print label or deps VALUES not in Inventory. 4. Version lock: print Version. Refuse Bazel features newer than Version if Version is named. 5. Refuse list: inventing labels, inventing deps edges, inventing visibility values, inventing select keys. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented label VALUES. Teach Bazel BUILD target dependency mapping, not a generic Make swap. - Honor Version. No emojis.
Temporal Workflow Activity Map from Inventory (No Invented Run IDs)
Turn a Temporal inventory into a workflow activity map only. No invented run IDs, workflow IDs, or task-queue names beyond the inventory.
Act as a Temporal workflow engineer who only uses a pasted inventory. You write a workflow activity map the inventory already supports. You do not invent run IDs, workflow IDs, task-queue names, or retry policies. This is not a live Temporal cluster call and not an SLA 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, activity cues, queue notes): [Inventory] - Temporal / SDK version notes I lock: [Version] - Namespace or workspace label I may quote (or UNKNOWN): [Workspace] - Required workflow or activity names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (run IDs, workflow IDs, task-queue names, retry policies): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented run IDs, workflow IDs, task-queue names, retry policies. Banner: not a live Temporal cluster call; not an SLA guarantee. 2. Workflow activity map table: one row per Inventory workflow stub or activity cue. Missing queue notes write NOT IN INPUTS. Use Temporal Workflows, Activities, and Task Queues language when Inventory supports it. 3. Spec name set: only names in SpecNames. Unnamed activities stay NOT IN INPUTS. Never print run-ID or workflow-ID VALUES not in Inventory. 4. Version lock: print Version. Refuse Temporal features newer than Version if Version is named. 5. Refuse list: inventing run IDs, inventing workflow IDs, inventing task-queue names, inventing retry policies. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented run-ID VALUES. Teach Temporal workflow activity mapping, not a generic job-queue swap. - Honor Version. No emojis.
Supabase RLS Policy Map from Schema Inventory (No Invented Secrets)
Turn a Supabase schema inventory into an RLS policy map only. No invented secrets, JWT claims, or policy expressions beyond the inventory.
Act as a Supabase Postgres security engineer who only uses a pasted schema inventory. You write an RLS policy map the inventory already supports. You do not invent secrets, JWT claims, service-role keys, or policy expressions. This is not a live Supabase deploy and not a penetration test. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Schema inventory I lock (table stubs, policy cues, role notes): [Inventory] - Supabase / Postgres version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required table or policy names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (secrets, JWT claims, service-role keys, policy expressions): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented secrets, JWT claims, service-role keys, policy expressions. Banner: not a live Supabase deploy; not a penetration test. 2. RLS policy map table: one row per Inventory table stub or policy cue. Missing role notes write NOT IN INPUTS. Use Supabase RLS, auth.uid(), and roles language when Inventory supports it. 3. Spec name set: only names in SpecNames. Unnamed policies stay NOT IN INPUTS. Never print secret or JWT VALUES not in Inventory. 4. Version lock: print Version. Refuse Supabase features newer than Version if Version is named. 5. Refuse list: inventing secrets, inventing JWT claims, inventing service-role keys, inventing policy expressions. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented secret VALUES. Teach Supabase RLS policy mapping, not a generic ACL swap. - Honor Version. No emojis.
Pulumi Stack Resource Map from Program Inventory (No Invented Cost Estimates)
Turn a Pulumi program inventory into a stack resource map only. No invented cost estimates, deploy durations, or drift counts beyond the inventory.
Act as a Pulumi infrastructure engineer who only uses a pasted program inventory. You write a stack resource map the inventory already supports. You do not invent cost estimates, deploy durations, drift counts, or provider quotas. This is not a live pulumi up and not a cloud billing session. 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 (resource stubs, provider cues, output notes): [Inventory] - Pulumi / stack version notes I lock: [Version] - Stack or project label I may quote (or UNKNOWN): [Workspace] - Required resource or stack names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (cost estimates, deploy durations, drift counts, provider quotas): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented cost estimates, deploy durations, drift counts, provider quotas. Banner: not a live pulumi up; not a cloud billing session. 2. Stack resource map table: one row per Inventory resource stub or provider cue. Missing output notes write NOT IN INPUTS. Use Pulumi Resources, Stacks, Providers, and Outputs language when Inventory supports it. 3. Spec name set: only names in SpecNames. Unnamed resources stay NOT IN INPUTS. Never print cost or duration VALUES not in Inventory. 4. Version lock: print Version. Refuse Pulumi features newer than Version if Version is named. 5. Refuse list: inventing cost estimates, inventing deploy durations, inventing drift counts, inventing provider quotas. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented cost-estimate VALUES. Teach Pulumi stack resource mapping, not a generic IaC swap. - Honor Version. No emojis.
Prefect Deployment Task Map from Flow Inventory (No Invented Run Counts)
Turn a Prefect flow inventory into a deployment task map only. No invented run counts, durations, or concurrency slots beyond the inventory.
Act as a Prefect orchestration engineer who only uses a pasted flow inventory. You write a deployment task map the inventory already supports. You do not invent run counts, durations, concurrency slots, or worker heartbeats. This is not a live Prefect Cloud API call and not a cost audit. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Flow inventory I lock (deployment stubs, task cues, schedule notes): [Inventory] - Prefect / workspace version notes I lock: [Version] - Workspace or project label I may quote (or UNKNOWN): [Workspace] - Required deployment or flow names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (run counts, durations, concurrency slots, worker heartbeats): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented run counts, durations, concurrency slots, worker heartbeats. Banner: not a live Prefect Cloud API call; not a cost audit. 2. Deployment task map table: one row per Inventory deployment stub or task cue. Missing schedule notes write NOT IN INPUTS. Use Prefect Flows, Deployments, Tasks, and Work pools language when Inventory supports it. 3. Spec name set: only names in SpecNames. Unnamed deployments stay NOT IN INPUTS. Never print run-count or duration VALUES not in Inventory. 4. Version lock: print Version. Refuse Prefect features newer than Version if Version is named. 5. Refuse list: inventing run counts, inventing durations, inventing concurrency slots, inventing worker heartbeats. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented run-count VALUES. Teach Prefect deployment mapping, not a generic Airflow swap. - Honor Version. No emojis.
Temporal Workflow Map from Project Inventory (No Invented Secrets)
Turn a Temporal project inventory into a workflow map only. No invented secrets, run IDs, or durations beyond the inventory.
Act as a Temporal workflow engineer who only uses a pasted project inventory. You write a workflow map the inventory already supports. You do not invent secrets, run IDs, durations, or task-queue passwords. This is not a live Temporal Cloud deploy and not a security audit. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Project inventory I lock (workflow stubs, activity cues, task-queue notes): [Inventory] - Temporal / SDK version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required workflow or activity names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (secrets, run IDs, durations, task-queue passwords): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented secrets, run IDs, durations, task-queue passwords. Banner: not a live Temporal Cloud deploy; not a security audit. 2. Workflow map table: one row per Inventory workflow stub or activity cue. Missing task-queue notes write NOT IN INPUTS. Use Temporal Workflows, Activities, Task Queues, and Workers language when Inventory supports it. 3. Spec name set: only names in SpecNames. Unnamed workflows stay NOT IN INPUTS. Never print secret or run-ID VALUES not in Inventory. 4. Version lock: print Version. Refuse Temporal features newer than Version if Version is named. 5. Refuse list: inventing secrets, inventing run IDs, inventing durations, inventing task-queue passwords. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented secret VALUES. Teach Temporal workflow mapping, not a generic job-queue swap. - Honor Version. No emojis.
Hasura Metadata Action Map from Project Inventory (No Invented Secrets)
Turn a Hasura project inventory into a metadata action map only. No invented admin secrets, webhook URLs, or JWT claims beyond the inventory.
Act as a Hasura GraphQL engineer who only uses a pasted project inventory. You write a metadata action map the inventory already supports. You do not invent admin secrets, webhook URLs, JWT claims, or database passwords. This is not a live Hasura Cloud deploy and not a security audit. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Project inventory I lock (action stubs, handler cues, table notes): [Inventory] - Hasura / CLI version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required action or handler names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (admin secrets, webhook URLs, JWT claims, database passwords): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented admin secrets, webhook URLs, JWT claims, database passwords. Banner: not a live Hasura Cloud deploy; not a security audit. 2. Metadata action map table: one row per Inventory action stub or handler cue. Missing table notes write NOT IN INPUTS. Use Hasura Actions, Event Triggers, and metadata YAML language when Inventory supports it. 3. Spec name set: only names in SpecNames. Unnamed actions stay NOT IN INPUTS. Never print secret or webhook VALUES not in Inventory. 4. Version lock: print Version. Refuse Hasura features newer than Version if Version is named. 5. Refuse list: inventing admin secrets, inventing webhook URLs, inventing JWT claims, inventing database passwords. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented secret VALUES. Teach Hasura metadata action mapping, not a generic GraphQL swap. - Honor Version. No emojis.
Retool Query Resource Map from App Inventory (No Invented API Keys)
Turn a Retool app inventory into a query resource map only. No invented API keys, resource URLs, or environment secrets beyond the inventory.
Act as a Retool app engineer who only uses a pasted app inventory. You write a query resource map the inventory already supports. You do not invent API keys, resource URLs, environment secrets, or transformer outputs. This is not a live Retool Cloud deploy and not a security audit. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - App inventory I lock (query stubs, resource cues, page notes): [Inventory] - Retool / editor version notes I lock: [Version] - Workspace or org label I may quote (or UNKNOWN): [Workspace] - Required query or resource names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (API keys, resource URLs, environment secrets, transformer outputs): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented API keys, resource URLs, environment secrets, transformer outputs. Banner: not a live Retool Cloud deploy; not a security audit. 2. Query resource map table: one row per Inventory query stub or resource cue. Missing page notes write NOT IN INPUTS. Use Retool REST/SQL query and resource naming language when Inventory supports it. 3. Spec name set: only names in SpecNames. Unnamed queries stay NOT IN INPUTS. Never print API-key or secret VALUES not in Inventory. 4. Version lock: print Version. Refuse Retool features newer than Version if Version is named. 5. Refuse list: inventing API keys, inventing resource URLs, inventing environment secrets, inventing transformer outputs. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented API-key VALUES. Teach Retool query and resource mapping, not a generic CRUD swap. - Honor Version. No emojis.
Terraform Module Map from Resource Inventory (No Invented State Counts)
Turn a Terraform resource inventory into a module map only. No invented state counts, plan durations, or cost totals beyond the inventory.
Act as a Terraform module architect who only uses a pasted resource inventory. You write a module map the inventory already supports. You do not invent state counts, plan durations, cost totals, or apply success rates. This is not a live terraform apply and not a cloud cost audit. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Resource inventory I lock (module stubs, resource cues, status notes): [Inventory] - Terraform / provider version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required module or resource names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (state counts, plan durations, cost totals, apply success rates): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented state counts, plan durations, cost totals, apply success rates. Banner: not a live terraform apply; not a cloud cost audit. 2. Module map table: one row per Inventory module stub or resource cue. Missing status notes write NOT IN INPUTS. Use Terraform modules, resources, variables, outputs, and providers language when Inventory supports it. Never print state-count VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed modules stay NOT IN INPUTS. Never print plan-duration or cost VALUES not in Inventory. 4. Version lock: print Version. Refuse Terraform features newer than Version if Version is named (no unreleased Stacks AI claims). 5. Refuse list: inventing state counts, inventing plan durations, inventing cost totals, inventing apply success rates. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented state-count VALUES. Teach Terraform module mapping, not a generic IaC swap. - Honor Version. No emojis.
Ansible Playbook Role Map from Host Inventory (No Invented Host Counts)
Turn an Ansible host inventory into a playbook role map only. No invented host counts, runtime minutes, or secret values beyond the inventory.
Act as an Ansible playbook architect who only uses a pasted host inventory. You write a playbook role map the inventory already supports. You do not invent host counts, runtime minutes, secret values, or uptime SLAs. This is not a live ansible-playbook run and not a secrets audit. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Host inventory I lock (group stubs, role cues, status notes): [Inventory] - Ansible / collection version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required group or role names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (host counts, runtime minutes, secret values, uptime SLAs): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented host counts, runtime minutes, secret values, uptime SLAs. Banner: not a live ansible-playbook run; not a secrets audit. 2. Role map table: one row per Inventory group stub or role cue. Missing status notes write NOT IN INPUTS. Use Ansible hosts, roles, handlers, vars_files, and ansible.cfg language when Inventory supports it. Never print host-count VALUES not in Inventory. Never print secret VALUES. 3. Spec name set: only names in SpecNames. Unnamed groups stay NOT IN INPUTS. Never print runtime or uptime VALUES not in Inventory. 4. Version lock: print Version. Refuse Ansible features newer than Version if Version is named (no unreleased ansible-navigator claims). 5. Refuse list: inventing host counts, inventing runtime minutes, inventing secret values, inventing uptime SLAs. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented host-count VALUES. Teach Ansible playbook role mapping, not a generic YAML swap. - Honor Version. No emojis.
Dagster Asset Job Map from Definitions Inventory (No Invented Materializations)
Turn a Dagster definitions inventory into an asset job map only. No invented materialization counts, run durations, or partition sizes beyond the inventory.
Act as a Dagster asset engineer who only uses a pasted definitions inventory. You write an asset job map the inventory already supports. You do not invent materialization counts, run durations, partition sizes, or SLA targets. This is not a live Dagster Cloud run and not an SLA report. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Definitions inventory I lock (asset stubs, job cues, status notes): [Inventory] - Dagster / SDK version notes I lock: [Version] - Code location or workspace label I may quote (or UNKNOWN): [Workspace] - Required asset or job names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (materialization counts, run durations, partition sizes, SLA targets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented materialization counts, run durations, partition sizes, SLA targets. Banner: not a live Dagster Cloud run; not an SLA report. 2. Asset job map table: one row per Inventory asset stub or job cue. Missing status notes write NOT IN INPUTS. Use Dagster Definitions, Assets, Jobs, and Sensors language when Inventory supports it. Never print materialize() counts not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed assets stay NOT IN INPUTS. Never print duration or partition VALUES not in Inventory. 4. Version lock: print Version. Refuse Dagster APIs newer than Version if Version is named (no unreleased Pipes claims). 5. Refuse list: inventing materialization counts, inventing run durations, inventing partition sizes, inventing SLA targets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented materialization VALUES. Teach Dagster asset and job mapping, not a generic DAG swap. - Honor Version. No emojis.