Browse Prompts
250 prompts available in coding · Page 4 of 21
SQLFluff Config Builder: Team SQL Style Guide to .sqlfluff Rules, dbt Templater Setup, and a Pre-commit Hook
Translate a written SQL style guide into a working SQLFluff setup for a dbt project: a .sqlfluff file with dialect, templater, capitalisation, comma, aliasing, and line length rules, a .sqlfluffignore, a pre-commit hook pinned to your version, and a rollout plan that will not flood an old repo with thousands of lint errors.
Act as an analytics engineer who maintains SQLFluff for dbt projects and has rolled linting out to teams without stalling their pull requests. You turn style guide sentences into exact SQLFluff rule codes and config keys, and you say so when a guideline has no rule behind it. Inputs: - Warehouse and SQL dialect: [Dialect] - SQLFluff version pinned in the repo: [SqlfluffVersion] - dbt adapter, project_dir, profiles_dir, and target used in CI: [DbtSetup] - The team's style guide text, pasted: [StyleGuide] - Folders and models that should be ignored or linted later: [LegacyPaths] - Current lint count or a sample failing model, if known: [BaselineErrors] - Output format: [Format] Generate: 1. Mapping table: each StyleGuide sentence, the SQLFluff rule code and name (for example CP01 capitalisation.keywords, LT04 layout.commas, AL01 aliasing.table, AM03 ambiguous.column_references), the config key and value, and NO RULE when nothing in SQLFluff enforces it. 2. A complete .sqlfluff file: [sqlfluff] core with dialect, templater = dbt, max_line_length, and exclude_rules only for guidelines the team rejected; [sqlfluff:templater:dbt] with project_dir, profiles_dir, profile, and target from DbtSetup; [sqlfluff:indentation]; [sqlfluff:layout:type:comma] line_position; and one [sqlfluff:rules:<rule>] section per configured rule. 3. A .sqlfluffignore covering target/, dbt_packages/, and LegacyPaths. 4. A .pre-commit-config.yaml block using the sqlfluff repo at the pinned SqlfluffVersion, the sqlfluff-lint hook, and additional_dependencies for the dbt adapter and sqlfluff-templater-dbt. Note that the dbt templater needs a compilable project and profile in CI, and offer the jinja templater as a faster fallback with its tradeoff. 5. Rollout plan for an existing repo: run sqlfluff lint to get a baseline, apply sqlfluff fix to one folder per pull request, and lint only changed files in CI until the backlog is clear. 6. Three before and after SQL snippets from the StyleGuide so reviewers can see what each rule changes. Constraints: - Only use rule codes and config keys that exist in the pinned SqlfluffVersion; flag anything you are unsure of as VERIFY. - Never claim a rule enforces naming conventions it does not check. - No em dashes.
Flake8, isort, and Black to Ruff Migration: pyproject.toml Config with Rule Mapping and a noqa Cleanup Plan
Move a Python repo from Flake8 plus plugins, isort, and Black to Ruff. Get a rule by rule mapping, a ready tool.ruff block for pyproject.toml, a pre-commit swap, and a plan for stale noqa comments so the first CI run is not a wall of new errors.
Act as a Python platform engineer who has migrated several monorepos from Flake8, isort, and Black to Ruff. You keep lint behavior the team already agreed on, you say clearly where Ruff differs, and you never select rules nobody asked for. Inputs: - Current Flake8 config (setup.cfg, tox.ini, or .flake8 section, including select, ignore, extend-ignore, per-file-ignores, max-line-length, max-complexity): [Flake8Config] - Flake8 plugins installed (for example flake8-bugbear, flake8-comprehensions, pep8-naming, flake8-docstrings): [Plugins] - isort settings (profile, known_first_party, force_single_line, src paths): [IsortConfig] - Black settings (line-length, target-version, skip-string-normalization): [BlackConfig] - Lowest Python version the code must support: [PythonVersion] - How lint runs today (pre-commit, CI job, Makefile, editor only): [CI] - Output format: [Format] - Language: [Lang] Generate: 1. Rule mapping table. For every Flake8 code family and plugin, give the Ruff prefix (E, W, F, C90, B, C4, N, D, I, UP and so on), whether Ruff implements it, and the gap if it does not (for example W503 and W504 are not implemented, E203 is preview only). Note that Flake8 selects E, F, W, C90 by default while Ruff defaults to E4, E7, E9, F, so the select list must be explicit. 2. The pyproject.toml block. Write the tool.ruff table with line-length and target-version taken from BlackConfig and PythonVersion, the tool.ruff.lint table with select, ignore, and per-file-ignores translated from Flake8Config, a tool.ruff.lint.mccabe table if max-complexity exists, a tool.ruff.lint.isort table translated from IsortConfig, a tool.ruff.lint.pydocstyle convention if D is selected, and a tool.ruff.format table matching BlackConfig. Write the TOML table headers in normal square bracket syntax in your answer. 3. Formatter conflict check. List any selected rules Ruff recommends disabling when ruff format is used (for example W191, E111, E114, E117, D206, D300, COM812, ISC001) and drop them. 4. Tool swap. Show the removed pre-commit hooks or CI steps and the new ones using the astral-sh/ruff-pre-commit repo with the ruff hook (args set to --fix) placed before ruff-format. Leave rev as a placeholder to pin. 5. noqa cleanup plan. Explain how to find stale suppressions with RUF100, how to rewrite plugin codes that changed, and when to use ruff check --add-noqa for a baseline instead of fixing everything in one PR. 6. Rollout order: one commit for config, one for ruff format churn (add it to .git-blame-ignore-revs), one for autofixes, then remove the old tools. Constraints: - Valid TOML only. Do not add rule prefixes that are not traceable to Flake8Config, Plugins, or IsortConfig. - If a Flake8 plugin has no Ruff equivalent, say so and keep it out of the config rather than guessing a prefix. - Do not invent version numbers for Ruff or hooks. - No em dashes.
Dependabot to Renovate Migration Plan with a Ready renovate.json
Migrate a repo from .github/dependabot.yml to Renovate: map every ecosystem, schedule, group, and ignore rule to packageRules, write a validated renovate.json, and plan the cutover so you never get duplicate PRs.
Act as a platform engineer who has migrated many repositories from GitHub Dependabot version updates to Renovate. You translate config field by field, explain each Renovate option you use, and plan a cutover with no duplicate update PRs. Inputs: - Current .github/dependabot.yml pasted in full: [DependabotYml] - Package managers and lockfiles in the repo (npm, pnpm, pip, poetry, docker, github-actions, terraform): [Ecosystems] - Merge policy (who may automerge what, required checks, branch protection): [MergePolicy] - Team timezone and quiet hours: [Timezone] - How Renovate runs (Mend Renovate GitHub App, self-hosted renovate CLI, or GitLab runner) and its version if known: [RenovateRuntime] - Packages that must never jump a major version: [PinnedMajors] - Output format: [Format] Generate: 1. Field map. A table that takes every key in DependabotYml (package-ecosystem, directory, schedule.interval, open-pull-requests-limit, groups with patterns, ignore with update-types, labels, reviewers, commit-message prefix) and names the Renovate equivalent (manager auto-detection or enabledManagers, schedule plus timezone, prConcurrentLimit, packageRules with groupName and matchPackageNames, matchUpdateTypes with enabled false, labels, reviewers or CODEOWNERS, semanticCommits or commitMessagePrefix). Mark anything with no equivalent. 2. renovate.json. Start with $schema and extends config:recommended. Add timezone and schedule in Renovate's natural-language syntax, prConcurrentLimit, minimumReleaseAge for third-party packages, lockFileMaintenance, and packageRules for groups, automerge per MergePolicy, and PinnedMajors. If RenovateRuntime is version 38 or newer, use glob or regex patterns inside matchPackageNames instead of the deprecated matchPackagePatterns. 3. GitHub Actions handling. If Ecosystems includes github-actions, decide whether to add helpers:pinGitHubActionDigests and explain the trade-off. 4. Security updates. Explain that Dependabot security alerts are separate from version updates, and set vulnerabilityAlerts labels and schedule override so security PRs are not held by the weekly schedule. 5. Cutover runbook. Ordered steps: validate with renovate-config-validator, merge the Renovate onboarding PR, check the Dependency Dashboard issue, delete .github/dependabot.yml in the same week, close stale Dependabot PRs, and the rollback step. 6. Open questions. Only items that DependabotYml or MergePolicy leave ambiguous. Constraints: - Valid JSON only in the config block, no comments inside it. - Do not invent repo paths, package names, or reviewers that Inputs did not give. - Never enable automerge for major updates unless MergePolicy says so. - No em dashes.
Bazel Project Target Dependency Checklist from Workspace Notes (No Invented Build Time Seconds)
Compile a Bazel project-target-dependency checklist from pasted workspace notes only. No invented build-time seconds, cache ranks, or CI scoreboards. Not a live Bazel sync.
Act as a Bazel project-target-dependency checklist engineer who only uses pasted workspace notes. You compile a project-target-dependency checklist the notes already support. You do not invent build-time seconds, cache ranks, CI scoreboards, or flaky-test percents. This is not a live Bazel sync, not a Gradle 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: - Workspace notes I lock (project stubs, target cues, dependency fragments): [WorkspaceNotes] - Bazel workspace or version notes I lock: [Version] - Repo or workspace label I may quote (or UNKNOWN): [RepoLabel] - Project titles already present (or UNKNOWN): [ProjectTitles] - Target cues already present (or UNKNOWN): [TargetCues] - Dependency cues already present (or UNKNOWN): [DependencyCues] - Rule cues already present (or UNKNOWN): [RuleCues] - Words I must not use: [Banned] - What I must never invent (build-time seconds, cache ranks, CI scoreboards, flaky-test percents): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: WorkspaceNotes nouns, Version, RepoLabel, ProjectTitles, TargetCues, DependencyCues, RuleCues, Lang. Banner: not DevOps consulting advice; not a live Bazel sync. Forbidden: invented build-time seconds, cache ranks, CI scoreboards, flaky-test percents. 2. Project-target-dependency checklist: one checkbox row per ProjectTitles entry. Attach only TargetCues and DependencyCues named beside that project in WorkspaceNotes. Missing target or dependency write NOT IN INPUTS. 3. Rule sketch: for each RuleCues entry, list projects that name it. Do not invent a 47s build-time claim if absent. 4. Repo caution block: quote RepoLabel and Version only. Package packs not in WorkspaceNotes stay NOT IN INPUTS. 5. Refuse list: inventing 47s build-time seconds, inventing cache ranks, inventing CI scoreboards, inventing flaky-test percents. 6. Compliance pass: quote Banned and Never hits. Cut them. Print project and target counts from WorkspaceNotes only. Format as Format. Constraints: - Project-target-dependency checklist from WorkspaceNotes only. No invented build-time seconds. - Honor Version. No emojis. Not a live Bazel dashboard. Not DevOps consulting advice.
Gradle Project Target Dependency Checklist from Workspace Notes (No Invented Build Time Seconds)
Compile a Gradle project-target-dependency checklist from pasted workspace notes only. No invented build-time seconds, cache ranks, or CI scoreboards. Not a live Gradle sync.
Act as a Gradle project-target-dependency checklist engineer who only uses pasted workspace notes. You compile a project-target-dependency checklist the notes already support. You do not invent build-time seconds, cache ranks, CI scoreboards, or flaky-test percents. This is not a live Gradle sync, not a Maven 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: - Workspace notes I lock (project stubs, target cues, dependency fragments): [WorkspaceNotes] - Gradle workspace or version notes I lock: [Version] - Repo or workspace label I may quote (or UNKNOWN): [RepoLabel] - Project titles already present (or UNKNOWN): [ProjectTitles] - Target cues already present (or UNKNOWN): [TargetCues] - Dependency cues already present (or UNKNOWN): [DependencyCues] - Task cues already present (or UNKNOWN): [TaskCues] - Words I must not use: [Banned] - What I must never invent (build-time seconds, cache ranks, CI scoreboards, flaky-test percents): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: WorkspaceNotes nouns, Version, RepoLabel, ProjectTitles, TargetCues, DependencyCues, TaskCues, Lang. Banner: not DevOps consulting advice; not a live Gradle sync. Forbidden: invented build-time seconds, cache ranks, CI scoreboards, flaky-test percents. 2. Project-target-dependency checklist: one checkbox row per ProjectTitles entry. Attach only TargetCues and DependencyCues named beside that project in WorkspaceNotes. Missing target or dependency write NOT IN INPUTS. 3. Task sketch: for each TaskCues entry, list projects that name it. Do not invent a 52s build-time claim if absent. 4. Repo caution block: quote RepoLabel and Version only. Module packs not in WorkspaceNotes stay NOT IN INPUTS. 5. Refuse list: inventing 52s build-time seconds, inventing cache ranks, inventing CI scoreboards, inventing flaky-test percents. 6. Compliance pass: quote Banned and Never hits. Cut them. Print project and target counts from WorkspaceNotes only. Format as Format. Constraints: - Project-target-dependency checklist from WorkspaceNotes only. No invented build-time seconds. - Honor Version. No emojis. Not a live Gradle dashboard. Not DevOps consulting advice.
Buck2 Project Target Dependency Checklist from Workspace Notes (No Invented Build Time Seconds)
Compile a Buck2 project-target-dependency checklist from pasted workspace notes only. No invented build-time seconds, cache ranks, or CI scoreboards. Not a live Buck2 sync.
Act as a Buck2 project-target-dependency checklist engineer who only uses pasted workspace notes. You compile a project-target-dependency checklist the notes already support. You do not invent build-time seconds, cache ranks, CI scoreboards, or flaky-test percents. This is not a live Buck2 sync, not a Bazel 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: - Workspace notes I lock (project stubs, target cues, dependency fragments): [WorkspaceNotes] - Buck2 workspace or version notes I lock: [Version] - Repo or workspace label I may quote (or UNKNOWN): [RepoLabel] - Project titles already present (or UNKNOWN): [ProjectTitles] - Target cues already present (or UNKNOWN): [TargetCues] - Dependency cues already present (or UNKNOWN): [DependencyCues] - Action cues already present (or UNKNOWN): [ActionCues] - Words I must not use: [Banned] - What I must never invent (build-time seconds, cache ranks, CI scoreboards, flaky-test percents): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: WorkspaceNotes nouns, Version, RepoLabel, ProjectTitles, TargetCues, DependencyCues, ActionCues, Lang. Banner: not DevOps consulting advice; not a live Buck2 sync. Forbidden: invented build-time seconds, cache ranks, CI scoreboards, flaky-test percents. 2. Project-target-dependency checklist: one checkbox row per ProjectTitles entry. Attach only TargetCues and DependencyCues named beside that project in WorkspaceNotes. Missing target or dependency write NOT IN INPUTS. 3. Action sketch: for each ActionCues entry, list projects that name it. Do not invent a 47s build-time claim if absent. 4. Repo caution block: quote RepoLabel and Version only. Cell packs not in WorkspaceNotes stay NOT IN INPUTS. 5. Refuse list: inventing 47s build-time seconds, inventing cache ranks, inventing CI scoreboards, inventing flaky-test percents. 6. Compliance pass: quote Banned and Never hits. Cut them. Print project and target counts from WorkspaceNotes only. Format as Format. Constraints: - Project-target-dependency checklist from WorkspaceNotes only. No invented build-time seconds. - Honor Version. No emojis. Not a live Buck2 dashboard. Not DevOps consulting advice.
Pants Monorepo Target Dependency Checklist from Workspace Notes (No Invented Build-Time Seconds)
Compile a Pants monorepo target-dependency checklist from pasted workspace notes only. No invented build-time seconds, cache ranks, or CI scoreboards. Not a live Pants sync.
Act as a Pants monorepo target-dependency checklist engineer who only uses pasted workspace notes. You compile a target-dependency checklist the notes already support. You do not invent build-time seconds, cache ranks, CI scoreboards, or flaky-test percents. This is not a live Pants sync, not a Bazel 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: - Workspace notes I lock (target stubs, dependency cues, package fragments): [WorkspaceNotes] - Pants workspace or version notes I lock: [Version] - Repo or workspace label I may quote (or UNKNOWN): [RepoLabel] - Target titles already present (or UNKNOWN): [TargetTitles] - Dependency cues already present (or UNKNOWN): [DependencyCues] - Package cues already present (or UNKNOWN): [PackageCues] - Goal cues already present (or UNKNOWN): [GoalCues] - Words I must not use: [Banned] - What I must never invent (build-time seconds, cache ranks, CI scoreboards, flaky-test percents): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: WorkspaceNotes nouns, Version, RepoLabel, TargetTitles, DependencyCues, PackageCues, GoalCues, Lang. Banner: not DevOps consulting advice; not a live Pants sync. Forbidden: invented build-time seconds, cache ranks, CI scoreboards, flaky-test percents. 2. Target-dependency checklist: one checkbox row per TargetTitles entry. Attach only DependencyCues and PackageCues named beside that target in WorkspaceNotes. Missing dependency or package write NOT IN INPUTS. 3. Goal sketch: for each GoalCues entry, list targets that name it. Do not invent a 52s build-time claim if absent. 4. Repo caution block: quote RepoLabel and Version only. Lockfile packs not in WorkspaceNotes stay NOT IN INPUTS. 5. Refuse list: inventing 52s build-time seconds, inventing cache ranks, inventing CI scoreboards, inventing flaky-test percents. 6. Compliance pass: quote Banned and Never hits. Cut them. Print target and dependency counts from WorkspaceNotes only. Format as Format. Constraints: - Target-dependency checklist from WorkspaceNotes only. No invented build-time seconds. - Honor Version. No emojis. Not a live Pants dashboard. Not DevOps consulting advice.
Nx Monorepo Project Target Dependency Checklist from Workspace Notes (No Invented Build-Time Seconds)
Compile an Nx monorepo project-target-dependency checklist from pasted workspace notes only. No invented build-time seconds, cache ranks, or CI scoreboards. Not a live Nx sync.
Act as an Nx monorepo project-target-dependency checklist engineer who only uses pasted workspace notes. You compile a project-target-dependency checklist the notes already support. You do not invent build-time seconds, cache ranks, CI scoreboards, or flaky-test percents. This is not a live Nx sync, not a Turborepo 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: - Workspace notes I lock (project stubs, target cues, dependency fragments): [WorkspaceNotes] - Nx workspace or version notes I lock: [Version] - Repo or workspace label I may quote (or UNKNOWN): [RepoLabel] - Project titles already present (or UNKNOWN): [ProjectTitles] - Target cues already present (or UNKNOWN): [TargetCues] - Dependency cues already present (or UNKNOWN): [DependencyCues] - Library cues already present (or UNKNOWN): [LibraryCues] - Words I must not use: [Banned] - What I must never invent (build-time seconds, cache ranks, CI scoreboards, flaky-test percents): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: WorkspaceNotes nouns, Version, RepoLabel, ProjectTitles, TargetCues, DependencyCues, LibraryCues, Lang. Banner: not DevOps consulting advice; not a live Nx sync. Forbidden: invented build-time seconds, cache ranks, CI scoreboards, flaky-test percents. 2. Project-target-dependency checklist: one checkbox row per ProjectTitles entry. Attach only TargetCues and DependencyCues named beside that project in WorkspaceNotes. Missing target or dependency write NOT IN INPUTS. 3. Library sketch: for each LibraryCues entry, list projects that name it. Do not invent a 48s build-time claim if absent. 4. Repo caution block: quote RepoLabel and Version only. Cache packs not in WorkspaceNotes stay NOT IN INPUTS. 5. Refuse list: inventing 48s build-time seconds, inventing cache ranks, inventing CI scoreboards, inventing flaky-test percents. 6. Compliance pass: quote Banned and Never hits. Cut them. Print project and target counts from WorkspaceNotes only. Format as Format. Constraints: - Project-target-dependency checklist from WorkspaceNotes only. No invented build-time seconds. - Honor Version. No emojis. Not a live Nx dashboard. Not DevOps consulting advice.
pnpm Workspace Package Task Checklist from Monorepo Notes (No Invented Runtime Seconds)
Compile a pnpm workspace-package-task checklist from pasted monorepo notes only. No invented runtime seconds, install ranks, or build scoreboards. Not a live pnpm sync.
Act as a pnpm workspace-package-task checklist engineer who only uses pasted monorepo notes. You compile a workspace-package-task checklist the notes already support. You do not invent runtime seconds, install ranks, build scoreboards, or cache claims. This is not a live pnpm sync, not a Turborepo 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 (workspace stubs, package cues, task fragments): [MonorepoNotes] - pnpm version or workspace notes I lock: [Version] - Repo or workspace label I may quote (or UNKNOWN): [RepoLabel] - Package titles already present (or UNKNOWN): [PackageTitles] - Task cues already present (or UNKNOWN): [TaskCues] - Filter cues already present (or UNKNOWN): [FilterCues] - Script cues already present (or UNKNOWN): [ScriptCues] - Words I must not use: [Banned] - What I must never invent (runtime seconds, install ranks, build scoreboards, cache claims): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: MonorepoNotes nouns, Version, RepoLabel, PackageTitles, TaskCues, FilterCues, ScriptCues, Lang. Banner: not DevOps consulting advice; not a live pnpm sync. Forbidden: invented runtime seconds, install ranks, build scoreboards, cache claims. 2. Workspace-package-task checklist: one checkbox row per PackageTitles entry. Attach only TaskCues and FilterCues named beside that package in MonorepoNotes. Missing task or filter write NOT IN INPUTS. 3. Script sketch: for each ScriptCues entry, list packages that name it. Do not invent a 42 runtime-seconds claim if absent. 4. Repo caution block: quote RepoLabel and Version only. Lockfile packs not in MonorepoNotes stay NOT IN INPUTS. 5. Refuse list: inventing 42 runtime seconds, inventing install ranks, inventing build scoreboards, inventing cache claims. 6. Compliance pass: quote Banned and Never hits. Cut them. Print package and task counts from MonorepoNotes only. Format as Format. Constraints: - Workspace-package-task checklist from MonorepoNotes only. No invented runtime seconds. - Honor Version. No emojis. Not a live pnpm dashboard. Not DevOps consulting advice.
Pulumi Config Secret Stack Checklist from Infra Notes (No Invented Cloud Costs)
Compile a Pulumi config secret-stack checklist from pasted infra notes only. No invented cloud costs, resource ranks, or deploy scoreboards. Not a live Pulumi sync.
Act as a Pulumi config secret-stack checklist engineer who only uses pasted infra notes. You compile a config secret-stack checklist the notes already support. You do not invent cloud costs, resource ranks, deploy scoreboards, or uptime claims. This is not a live Pulumi sync, not a Terraform invent, and not cloud cost consulting 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, config cues, secret fragments): [InfraNotes] - Pulumi project or version notes I lock: [Version] - Project or org label I may quote (or UNKNOWN): [ProjectLabel] - Stack titles already present (or UNKNOWN): [StackTitles] - Config cues already present (or UNKNOWN): [ConfigCues] - Secret cues already present (or UNKNOWN): [SecretCues] - Provider cues already present (or UNKNOWN): [ProviderCues] - Words I must not use: [Banned] - What I must never invent (cloud costs, resource ranks, deploy scoreboards, uptime claims): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: InfraNotes nouns, Version, ProjectLabel, StackTitles, ConfigCues, SecretCues, ProviderCues, Lang. Banner: not cloud cost consulting advice; not a live Pulumi sync. Forbidden: invented cloud costs, resource ranks, deploy scoreboards, uptime claims. 2. Config secret-stack checklist: one checkbox row per StackTitles entry. Attach only ConfigCues and SecretCues named beside that stack in InfraNotes. Missing config or secret write NOT IN INPUTS. 3. Provider sketch: for each ProviderCues entry, list stacks that name it. Do not invent a $4200 cloud-cost claim if absent. 4. Project caution block: quote ProjectLabel and Version only. Preview packs not in InfraNotes stay NOT IN INPUTS. 5. Refuse list: inventing $4200 cloud costs, inventing resource ranks, inventing deploy scoreboards, inventing uptime claims. 6. Compliance pass: quote Banned and Never hits. Cut them. Print stack and config counts from InfraNotes only. Format as Format. Constraints: - Config secret-stack checklist from InfraNotes only. No invented cloud costs. - Honor Version. No emojis. Not a live Pulumi dashboard. Not cloud cost consulting advice.
Bun Package Task Workspace Checklist from Monorepo Notes (No Invented Runtime Seconds)
Compile a Bun package task-workspace checklist from pasted monorepo notes only. No invented runtime seconds, benchmark ranks, or install scoreboards. Not a live Bun sync.
Act as a Bun package task-workspace checklist engineer who only uses pasted monorepo notes. You compile a package task-workspace checklist the notes already support. You do not invent runtime seconds, benchmark ranks, install scoreboards, or speed claims. This is not a live Bun sync, not an npm invent, and not performance 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 (package stubs, task cues, workspace fragments): [MonorepoNotes] - Bun version notes I lock: [Version] - Workspace or repo label I may quote (or UNKNOWN): [WorkspaceLabel] - Package names already present (or UNKNOWN): [PackageNames] - Task cues already present (or UNKNOWN): [TaskCues] - Workspace cues already present (or UNKNOWN): [WorkspaceCues] - Script cues already present (or UNKNOWN): [ScriptCues] - Words I must not use: [Banned] - What I must never invent (runtime seconds, benchmark ranks, install scoreboards, speed claims): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: MonorepoNotes nouns, Version, WorkspaceLabel, PackageNames, TaskCues, WorkspaceCues, ScriptCues, Lang. Banner: not performance consulting advice; not a live Bun sync. Forbidden: invented runtime seconds, benchmark ranks, install scoreboards, speed claims. 2. Package task-workspace checklist: one checkbox row per PackageNames entry. Attach only TaskCues and WorkspaceCues named beside that package in MonorepoNotes. Missing task or workspace write NOT IN INPUTS. 3. Script sketch: for each ScriptCues entry, list packages that name it. Do not invent a 120ms runtime-seconds claim if absent. 4. Workspace caution block: quote WorkspaceLabel and Version only. Lockfile packs not in MonorepoNotes stay NOT IN INPUTS. 5. Refuse list: inventing 120ms runtime seconds, inventing benchmark ranks, inventing install scoreboards, inventing speed claims. 6. Compliance pass: quote Banned and Never hits. Cut them. Print package and task counts from MonorepoNotes only. Format as Format. Constraints: - Package task-workspace checklist from MonorepoNotes only. No invented runtime seconds. - Honor Version. No emojis. Not a live Bun dashboard. Not performance consulting advice.
Deno Task Deploy Package Checklist from Monorepo Notes (No Invented Runtime Seconds)
Compile a Deno task deploy-package checklist from pasted monorepo notes only. No invented runtime seconds, cache ranks, or deploy scoreboards. Not a live Deno sync.
Act as a Deno task deploy-package checklist engineer who only uses pasted monorepo notes. You compile a task deploy-package checklist the notes already support. You do not invent runtime seconds, cache ranks, deploy scoreboards, or coverage claims. This is not a live Deno sync, not a Node 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 (task stubs, deploy cues, package fragments): [MonorepoNotes] - Deno workspace or version notes I lock: [Version] - Workspace or repo label I may quote (or UNKNOWN): [WorkspaceLabel] - Task titles already present (or UNKNOWN): [TaskTitles] - Deploy cues already present (or UNKNOWN): [DeployCues] - Package cues already present (or UNKNOWN): [PackageCues] - Permission cues already present (or UNKNOWN): [PermissionCues] - Words I must not use: [Banned] - What I must never invent (runtime seconds, cache ranks, deploy scoreboards, coverage claims): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: MonorepoNotes nouns, Version, WorkspaceLabel, TaskTitles, DeployCues, PackageCues, PermissionCues, Lang. Banner: not DevOps consulting advice; not a live Deno sync. Forbidden: invented runtime seconds, cache ranks, deploy scoreboards, coverage claims. 2. Task deploy-package checklist: one checkbox row per TaskTitles entry. Attach only DeployCues and PackageCues named beside that task in MonorepoNotes. Missing deploy or package write NOT IN INPUTS. 3. Permission sketch: for each PermissionCues entry, list tasks that name it. Do not invent a 18s runtime claim if absent. 4. Workspace caution block: quote WorkspaceLabel and Version only. Lockfile packs not in MonorepoNotes stay NOT IN INPUTS. 5. Refuse list: inventing 18s runtime seconds, inventing cache ranks, inventing deploy scoreboards, inventing coverage claims. 6. Compliance pass: quote Banned and Never hits. Cut them. Print task and deploy counts from MonorepoNotes only. Format as Format. Constraints: - Task deploy-package checklist from MonorepoNotes only. No invented runtime seconds. - Honor Version. No emojis. Not a live Deno dashboard. Not DevOps consulting advice.