💻

Coding

82 prompts in this category · Page 4 of 7

💻 Coding

GitLab CODEOWNERS File from a Repo Map (No Invented Usernames)

Ppromptstudio·Aug 29, 2026
No rating

Write a GitLab CODEOWNERS file from a repo map. No invented usernames, groups, or paths.

Act as a GitLab CODEOWNERS author who only uses a pasted repo map. You write path rules and optional sections. You do not invent usernames, groups, or paths. This is not a GitHub CODEOWNERS plus branch-protection kit, not an OWNERS file for Gerrit, and not a CODEOWNERS v2 essay. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Repo map (paths and owners I allow): [Map] - Default owners I allow (or NONE): [Default] - Sections I allow (or NONE): [Sections] - Words I must not use: [Banned] - What I must never invent (usernames, groups, paths): [Never] - Output format: [Format] - Language for comments: [Lang] - Max rules: [Max] - GitLab version note I lock (or UNKNOWN): [Version] Generate: 1. Honesty ledger: Map paths, Default, Sections, Version, Lang, Max. Forbidden: invented @users, invented groups, extra paths. 2. Version note: quote Version or write VERSION UNKNOWN. GitLab section syntax only if Sections is not NONE. 3. CODEOWNERS body: at most Max rules. Paths and owners only from Map and Default. 4. Default: if Default is NONE, do not add a * rule. 5. Refuse list: GitHub branch protection YAML, Gerrit OWNERS, invented @backend-team. 6. Groups: only groups written in Map. Do not expand a team name into people. 7. Never: do not add @root or @admin unless listed. 8. Compliance pass: quote Banned and Never hits. Cut them. Count rules vs Max. Format as Format. Constraints: - GitLab CODEOWNERS from Map. Not GitHub branch protection and not Gerrit. - Never invent usernames, groups, or paths. - Stay at or under Max rules. - No emojis.

gitlab codeowners fileno invented usernamesrepo map owners
💻 Coding

Earthly Earthfile Multi-Stage from a Service Brief (Version-Locked Images, No Invented Bases)

Ppromptstudio·Aug 29, 2026
No rating

Write a multi-stage Earthfile from a service brief. Lock base images and versions in Inputs. Do not invent tags or registries.

Act as an Earthly Earthfile author who only uses a pasted service brief. You write a multi-stage Earthfile with VERSION, deps, build, and a runtime image. You do not invent base image names, tags, or registries. This is not a Dockerfile-only dump, not a Buildah script, and not a docker-compose file. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Service brief (language, entrypoint, ports I allow): [Brief] - Base images I lock with exact tags: [Images] - Earthly VERSION I lock (or UNKNOWN): [Earthly] - Build targets I allow: [Targets] - Words I must not use: [Banned] - What I must never invent (tags, registries, ports): [Never] - Output format: [Format] - Language for comments: [Lang] - Package versions I lock (or NONE): [Packages] Generate: 1. Honesty ledger: Brief nouns, Images, Earthly, Targets, Packages, Lang. Forbidden: invented tags, invented registries, extra ports. 2. Image lock table: each Images line quoted. If a stage needs an image not listed, write NOT IN INPUTS rather than picking alpine:latest. 3. Earthfile body: VERSION from Earthly or VERSION UNKNOWN. Targets only. Copy only paths named in Brief. 4. Runtime: EXPOSE only ports in Brief. USER only if Brief names a user. HEALTHCHECK only if Brief names one. 5. Refuse list: Dockerfile FROM without Earthly targets, docker-compose services, Buildah bud, invented SHA256 digests. 6. Packages: quote Packages or write NONE. Do not add a pinned apk add line that is not locked. 7. Never: do not write :latest. Do not invent ghcr.io or ecr URLs. 8. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Earthfile from Brief and Images only. Not a Dockerfile-only dump and not compose. - Never invent base image names, tags, or registries. - Only Targets named in Inputs. - No emojis.

earthly earthfile multi-stageversion-locked base imagesno invented docker tags
💻 Coding

GitHub Actions Workflow YAML from a Job List (No Invented Actions beyond Allowlist)

Ppromptstudio·Aug 28, 2026
No rating

Draft a GitHub Actions workflow YAML from a pasted job list. Never invent actions beyond the allowlist or unlisted secrets.

Act as a GitHub Actions workflow YAML writer who only uses a pasted job list and an action allowlist. You emit on/jobs/steps YAML. You do not invent actions beyond the allowlist, runners, or secrets. This is not a reusable workflow publisher, not a Dependabot config writer, and not a matrix generator from a test plan. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Pasted job list (name, steps in plain language): [Jobs] - Action allowlist (owner/name@ref or NONE): [Allow] - Runner I lock (or NONE): [Runner] - Triggers I lock: [On] - Secrets I may name (exact list or NONE): [Secrets] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language: [Lang] - Max jobs: [Max] Generate: 1. Honesty ledger: job count, Allow status, Runner status, On, Secrets status, Lang, Max. Forbidden: invented actions, invented secrets. 2. Job map: each job name with steps from Jobs; mark steps that need an action vs run:. 3. Workflow YAML: name, on from On, jobs up to Max. uses: only if the action is on Allow. If Allow NONE, use run: only. 4. Allowlist check: every uses: line quoted against Allow or marked REFUSED. 5. Refuse list: invented docker/login-action, invented github.token scopes, invented environments. 6. Diff notes: Banned/Never cuts. 7. Runner note: if Runner NONE write runs-on: NOT IN INPUTS as a comment and skip a fake ubuntu pin. 8. Compliance pass: Banned/Never hits. Job count vs Max. Gaps list of five. Format as Format. Constraints: - Workflow YAML from Jobs + Allow only. Not Dependabot and not a matrix-from-test-plan card. - Never invent actions beyond Allow or secrets beyond Secrets. - Stay at or under Max jobs. - No emojis.

github actions workflowno invented actionsactions yaml from job list
💻 Coding

sqlc Query Annotations from a SQL Dump (No Invented Tables)

Ppromptstudio·Aug 28, 2026
No rating

Annotate sqlc queries from a pasted SQL dump. Never invent tables, columns, or query names beyond the dump.

Act as a sqlc query annotator who only uses a pasted SQL dump. You add -- name: and :one/:many/:exec comments. You do not invent tables, columns, or joins. This is not a Prisma schema writer, not a raw ORM model generator, and not a Flyway migration author. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Pasted SQL statements: [SQL] - sqlc version I lock (or UNKNOWN): [Version] - Package name I lock (or UNKNOWN): [Package] - Naming style for query names: [Style] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language: [Lang] - Max queries: [Max] Generate: 1. Honesty ledger: statement count, Version, Package, Style, Lang, Max. Forbidden: invented tables, invented columns, invented joins. 2. Statement map: kind (SELECT/INSERT/UPDATE/DELETE), tables touched from SQL only. 3. Annotated SQL: up to Max queries with -- name: Name :one|:many|:exec. Only tables/columns in SQL. 4. Name list: Style applied; never invent resources not in SQL. 5. Refuse list: invented tables, invented WHERE columns, invented RETURNING lists. 6. Diff notes: Banned/Never cuts. 7. Version/package note: UNKNOWN spelled when blank. 8. Compliance pass: Banned/Never hits. Query count vs Max. Gaps list of five. Format as Format. Constraints: - sqlc annotations from SQL only. Not Prisma and not migrations. - Never invent tables or columns. - Stay at or under Max queries. - No emojis.

sqlc query annotationsno invented tablessqlc from sql dump
💻 Coding

Terraform Module Variables Doc from variables.tf (No Invented Resources)

Ppromptstudio·Aug 28, 2026
No rating

Document Terraform module variables from a pasted variables.tf. Never invent resources, providers, or unlisted variables.

Act as a Terraform module variables documenter who only uses a pasted variables.tf. You produce a markdown variables table and usage notes. You do not invent resources, providers, or variables. This is not a full module generator, not an OpenTofu rewrite, and not a terragrunt stack. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Pasted variables.tf (or variable blocks): [TF] - Module name I lock (or UNKNOWN): [Module] - Provider I may mention (or NONE): [Provider] - Required Terraform version I lock (or UNKNOWN): [Version] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language: [Lang] - Max variables to document: [Max] Generate: 1. Honesty ledger: variable count in TF, Module, Provider, Version, Lang, Max. Forbidden: invented resources, invented variables, invented defaults. 2. Variable map: name, type, default present/absent, description present/absent from TF only. 3. Markdown table: up to Max rows. Columns name | type | default | required | description. Defaults only if in TF. 4. Example module block: only variables that appear; omit values NOT IN INPUTS. 5. Refuse list: invented aws_instance blocks, invented outputs, invented backends. 6. Diff notes: Banned/Never cuts. 7. Provider/version note: Provider NONE or Version UNKNOWN spelled explicitly. 8. Compliance pass: Banned/Never hits. Row count vs Max. Gaps list of five. Format as Format. Constraints: - Variables doc from TF only. Not a full module scaffold and not terragrunt. - Never invent resources, providers, or variables. - Stay at or under Max rows. - No emojis.

terraform variables docno invented resourcesvariables.tf documentation
💻 Coding

Protocol Buffers .proto from an RPC List (No Invented RPCs)

Ppromptstudio·Aug 28, 2026
No rating

Write proto3 syntax service and messages from a pasted RPC list. Version-lock proto3 vs unknown. No invented RPCs, fields, or google.api options unless listed.

Act as a Protocol Buffers proto3 sketcher who only uses a pasted RPC list. You write syntax, package, service, and message stubs. You do not invent RPCs, fields, or google.api options unless listed. This is not OpenAPI, not GraphQL, and not Avro. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - RPC list (rpc name, request, response nouns): [RPCs] - Syntax lock (proto3 or UNKNOWN): [Syntax] - Package name I allow (or UNKNOWN): [Package] - Field lists per message I allow (or NONE): [Fields] - google.api options I allow (or NONE): [Options] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language for comments: [Lang] - Service name I allow: [Service] Generate: 1. Honesty ledger: RPCs, Syntax, Package, Fields, Options, Service, Lang. Forbidden: inventing RPCs or fields. 2. syntax and package lines: if Syntax UNKNOWN write SYNTAX UNKNOWN; if Package UNKNOWN write PACKAGE UNKNOWN. 3. service block: only RPCs listed. rpc signatures use request/response names from Inputs. 4. message stubs: fields only from Fields; if NONE, empty messages with NOT IN INPUTS comment. 5. options: only Options; if NONE, no google.api.http invent. 6. Refuse: OpenAPI paths, GraphQL types, Avro schemas, inventing streaming unless RPCs say stream. 7. Version note: lock proto3 only when Syntax says so. 8. Compliance pass: quote Banned and Never. Gaps list of five. Format as Format. Constraints: - proto3 service from RPCs only. Not OpenAPI, GraphQL, or Avro. - Never invent RPCs, fields, or google.api options when NONE/UNKNOWN. - Only RPCs named in Inputs. - No emojis.

protobuf proto from rpc listproto3 service sketchno invented rpcs
💻 Coding

Nix flake.nix from a Package List (No Invented Overlays)

Ppromptstudio·Aug 28, 2026
No rating

Scaffold flake.nix (inputs, devShell, packages) from a package list. Do not invent overlays, nixpkgs pins, or unlisted packages.

Act as a Nix flake.nix sketcher who only uses a pasted package list. You write inputs, devShell, and packages stubs. You do not invent overlays, nixpkgs commit pins, or packages not listed. This is not a Dockerfile, not Terraform, and not a full NixOS module. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Package list for devShell and/or packages: [Packages] - nixpkgs input I lock (URL or UNKNOWN): [Nixpkgs] - System I allow (or UNKNOWN): [System] - Overlay names I allow (or NONE): [Overlays] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language for comments: [Lang] - Flake description string I allow: [Desc] - Extra inputs I may name (or NONE): [ExtraInputs] Generate: 1. Honesty ledger: Packages, Nixpkgs, System, Overlays, ExtraInputs, Desc, Lang. Forbidden: inventing overlays, inventing pins. 2. inputs block: nixpkgs only if Nixpkgs locked; else write NIXPKGS UNKNOWN placeholder comment. 3. outputs stub: forEachSystem or single System. If System UNKNOWN, write SYSTEM UNKNOWN. 4. devShell: buildInputs/packages only from Packages. 5. packages: only if Packages marks a package output; else write NO PACKAGE OUTPUT IN INPUTS. 6. overlays: only Overlays; if NONE, do not add overlay =. 7. Refuse: Dockerfile COPY, Terraform resources, NixOS module invent, unlisted packages. 8. Compliance pass: quote Banned and Never. Gaps list of five. Format as Format. Constraints: - flake.nix from Packages only. Not Dockerfile and not NixOS module. - Never invent overlays or nixpkgs pins when UNKNOWN/NONE. - Only packages named in Inputs. - No emojis.

nix flake from packagesflake.nix scaffoldno invented nix overlays
💻 Coding

PostgreSQL Migration from a Schema Delta Brief

Ppromptstudio·Aug 27, 2026
No rating

Write a PostgreSQL migration from a schema delta brief. Never invent tables, columns, or extensions not listed.

Act as a PostgreSQL migration clerk who only uses a schema delta brief. You write up/down SQL for listed changes. You do not invent tables, columns, or extensions. This is not an ORM generator and not a data backfill inventer. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Schema delta brief: [Delta] - Postgres version I lock: [PGVer] - Migration tool I allow (or raw SQL): [Tool] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Delta nouns, PGVer, Tool, Lang. 2. Version lock: PGVer. 3. Change list numbered from Delta only. 4. Up migration SQL. Only objects in Delta. If type missing, write TYPE UNKNOWN and stop that statement. 5. Down migration SQL reversing only stated ups. 6. Refuse: inventing extensions (uuid-ossp) if not in Delta, inventing backfill UPDATE data, inventing indexes not requested. 7. Lock/timeout notes: only if Delta states; else LOCK NOTES NOT IN INPUTS. 8. Compliance pass: Banned and Never. Format as Format. Constraints: - Migration from Delta+PGVer only. Not an ORM scaffold. - Never invent tables/columns/extensions. - Provide up and down. - No emojis.

postgresql migration schema deltapostgres ddl from briefschema delta migration sql
💻 Coding

Zig build.zig from a Module List (No Invented Packages)

Ppromptstudio·Aug 27, 2026
No rating

Draft a Zig build.zig from a locked module list and Zig version. Never invent packages, targets, or versions.

Act as a Zig build.zig clerk who only uses a module list and a locked Zig version. You draft build.zig steps for the listed modules. You do not invent packages, targets, or Zig versions. This is not a full application generator and not a Cargo.toml translator. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Zig version I lock: [ZigVer] - Module list (name + path): [Modules] - Executable name I allow (or UNKNOWN): [Exe] - Target I allow (or UNKNOWN): [Target] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: ZigVer, Modules, Exe, Target, Lang. Forbidden: invented packages, invented Zig releases. 2. Version lock line: ZigVer only. 3. Module table: name, path quoted from Modules. 4. build.zig sketch: addModule / addExecutable only for listed items. If Exe UNKNOWN, write EXE UNKNOWN and skip binary. 5. Target: quote Target or TARGET UNKNOWN. Do not invent aarch64-macos. 6. Refuse: inventing zig fetch URLs, inventing dependency hashes, inventing C library links not in Modules. 7. Test note: if no test module listed, write TESTS NOT IN INPUTS. 8. Compliance pass: Banned and Never. Format as Format. Constraints: - build.zig from Modules + ZigVer only. Not a full app scaffold. - Never invent packages or Zig versions. - Keep Exe/Target UNKNOWN when blank. - No emojis.

zig build.zig from module listno invented packages zigzig build script scaffold
💻 Coding

Go cobra CLI from a Command Brief (No Invented Modules)

Ppromptstudio·Aug 27, 2026
No rating

Scaffold a Go CLI with cobra from a command brief. Do not invent modules, flags, or versions not locked in Inputs.

Act as a Go cobra CLI sketcher who only uses a pasted command brief. You write a cobra-based CLI skeleton (go.mod stub + root/subcommand files). You do not invent modules, flags, or module versions not locked in Inputs. This is not a full production app, not a cobra-cli generator dump, and not a Rust clap port. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Command brief (bin name, subcommands, flags): [Brief] - Go version I lock (or UNKNOWN): [Go] - cobra version I lock (or UNKNOWN): [Cobra] - Extra modules I may name: [Mods or NONE] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language for comments: [Lang] - Module path I allow (or UNKNOWN): [Module] Generate: 1. Honesty ledger: Brief, Go, Cobra, Mods, Module, Lang. Forbidden: extra modules, inventing cobra v2 if UNKNOWN. 2. go.mod stub: module path from Module or MODULE UNKNOWN. cobra require only if Cobra locked; else write COBRA VERSION UNKNOWN. 3. Root command sketch: Use cobra.Command. Subcommands and flags only from Brief. 4. Subcommand stubs: match Brief. No network calls unless Brief says so. 5. Mods: attach only Mods. If Brief needs viper and Mods is NONE, write NOT IN INPUTS. 6. Go version: quote Go or GO VERSION UNKNOWN. Do not default to 1.22 if UNKNOWN. 7. Refuse: inventing gin, inventing gorm, inventing cobra-cli generate output beyond the sketch. 8. Compliance pass: quote Banned and Never. Format as Format. Constraints: - Go cobra CLI from Brief only. Not a full app and not a Rust clap port. - Never invent modules or versions when UNKNOWN. - Only subcommands named in Brief. - No emojis.

go cobra cli scaffoldcobra command briefno invented go modules
💻 Coding

Pulumi Python Component from a Resource List (No Invented Providers)

Ppromptstudio·Aug 27, 2026
No rating

Scaffold a Pulumi Python component from a pasted resource list. Do not invent providers, package versions, or cloud resources not listed.

Act as a Pulumi Python component sketcher who only uses a pasted resource list. You write a ComponentResource stub and resource registrations. You do not invent providers, package versions, or resources not listed. This is not Terraform HCL, not AWS CDK, and not a full deploy. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Resource list (logical names and types I allow): [Resources] - Pulumi language lock: Python - Provider packages I lock (or UNKNOWN): [Providers] - Component class name I allow: [Class] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language for comments: [Lang] - Stack outputs I may export: [Outputs or NONE] Generate: 1. Honesty ledger: Resources, Providers, Class, Outputs, Lang. Forbidden: extra providers, inventing awsx if not locked. 2. Provider lock: if Providers UNKNOWN, write PROVIDERS UNKNOWN and do not import pulumi_aws by default. 3. Component stub: class Class(ComponentResource). Register only Resources. 4. Resource blocks: one per Resources entry. Properties only if present in Inputs; else NOT IN INPUTS. 5. Outputs: export only Outputs. If NONE, write no exports. 6. Refuse: Terraform resources, CDK constructs, invented IAM policies. 7. requirements note: list only Providers locked; else UNKNOWN. 8. Compliance pass: quote Banned and Never. Format as Format. Constraints: - Pulumi Python component from Resources only. Not Terraform and not CDK. - Never invent providers or versions when UNKNOWN. - Only resources named in Inputs. - No emojis.

pulumi python componentpulumi resource list scaffoldno invented pulumi providers
💻 Coding

Rust clap CLI from a Command Brief (No Invented Crates)

Ppromptstudio·Aug 27, 2026
No rating

Scaffold a Rust CLI with clap from a command brief. Do not invent crates, features, or versions not locked in Inputs.

Act as a Rust clap CLI sketcher who only uses a pasted command brief. You write a clap-based CLI skeleton (Cargo.toml stub + main/args). You do not invent crates, features, or crate versions not locked in Inputs. This is not a full production app, not a Tokio service, and not a Python argparse port. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Command brief (bin name, subcommands, flags): [Brief] - Rust edition I lock (2021/2024/UNKNOWN): [Edition] - clap version I lock (or UNKNOWN): [Clap] - Extra crates I may name: [Crates or NONE] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language for comments: [Lang] - Error style I allow (thiserror/anyhow/UNKNOWN): [Errors] Generate: 1. Honesty ledger: Brief, Edition, Clap, Crates, Errors, Lang. Forbidden: extra crates, inventing clap 5 if UNKNOWN. 2. Cargo.toml stub: package name from Brief. clap dependency only if Clap locked; else write CLAP VERSION UNKNOWN and leave a placeholder comment. 3. Args sketch: derive Parser. Subcommands and flags only from Brief. 4. main sketch: match subcommands. No network calls unless Brief says so. 5. Crates: attach only Crates. If Brief needs serde and Crates is NONE, write NOT IN INPUTS. 6. Errors: only Errors style. If UNKNOWN, print UNKNOWN and do not pick anyhow by default. 7. Refuse: inventing tokio, inventing reqwest, inventing clap macros not needed. 8. Compliance pass: quote Banned and Never. Format as Format. Constraints: - Rust clap CLI from Brief only. Not a full app and not a Python port. - Never invent crates or versions when UNKNOWN. - Only subcommands named in Brief. - No emojis.

rust clap cli scaffoldclap command briefno invented rust crates