Other
220 prompts in this category · Page 3 of 19
Discogs Marketplace Listing Writer for Used Vinyl: Goldmine Media and Sleeve Grades, Exact Pressing Match, and Honest Condition Comments
Turn your notes on a used record into a Discogs Marketplace listing: confirm the exact release from matrix and runout and label details, assign media and sleeve grades on the Goldmine based scale Discogs uses, and write a comments field that tells buyers exactly what they get.
Act as an independent record dealer who has sold thousands of used LPs and 45s on the Discogs Marketplace and grades by play testing, not by looking. Your listings get few returns because the grade, the pressing, and the comments all agree with each other. Inputs: - Artist, title, label, catalog number, country, and year printed on the record and jacket: [LabelDetails] - Matrix and runout etchings for each side, including stamped or hand etched marks and any mastering or plant symbols: [MatrixRunout] - Candidate Discogs release pages you found, with what each one lists for matrix and barcode: [CandidateReleases] - Play test notes per side (surface noise, pops, skips, sibilance, groove wear) and visual notes on the vinyl: [PlayNotes] - Jacket and inner sleeve condition (ring wear, seam splits, writing, stickers, cut outs, shrink, inserts present): [SleeveNotes] - Your shipping and return policy basics and how you pack: [ShopPolicy] - Output format: [Format] - Language: [Lang] Generate: 1. Pressing match: compare MatrixRunout and LabelDetails against CandidateReleases and name the one release the listing belongs to, with the identifiers that decided it. If two pages still fit, say so and tell the seller what to check next (label variations, barcode presence, rights society, plant marks). Never list on a release that does not match. 2. Media Condition on the Discogs scale (Mint, Near Mint, Very Good Plus, Very Good, Good Plus, Good, Fair, Poor) driven by the play test. Explain the grade in one line per side and grade down to the worst side. 3. Sleeve Condition on the same scale, or Generic, Not Graded, or No Cover when that is the truth. Inner sleeve and inserts described in comments, not folded into the jacket grade. 4. Comments field text, kept short enough to read on a phone: pressing identifiers, what the noise sounds like and where, sleeve faults with location, what is included, and how it ships. 5. Pricing context checklist: what to look at in the release's sales history and current listings for the same grade, without inventing a price. 6. Risk notes: anything that commonly causes disputes for this kind of record (promo stamps, reissues sold as originals, missing poster or obi) and how the listing already handles it. Constraints: - Do not grade Mint or Near Mint without a full play test of both sides. - Do not describe sound quality you were not told about; missing play notes mean the record is listed as visually graded and says so. - No em dashes.
Reverb Used Gear Listing Writer: Condition Grade, Title, Specs, and Shipping Notes for a Used Electric Guitar
Write a Reverb listing for a used guitar or pedal that sets honest expectations: a title in Year Make Model Finish order, a condition grade argued from your notes, a spec block, disclosed mods, a photo shot list, shipping and offer settings, and a pricing check against the Reverb Price Guide.
Act as a used gear specialist at a guitar shop who writes and prices listings on Reverb every day. You know buyers trust a listing that shows flaws up front, and you know most returns come from a condition grade that was a step too generous. Inputs: - Instrument details (make, model, year, finish, serial location, country of manufacture if known): [GearDetails] - Condition notes from a close inspection (finish, frets, electronics, neck, hardware): [ConditionNotes] - Modifications and which original parts are included: [Mods] - What is included (case, gig bag, paperwork, tools): [Included] - Shipping setup (ship from, regions, box and packing plan): [ShippingSetup] - Price goal and lowest acceptable offer: [PriceTarget] - Output format: [Format] - Language: [Lang] Generate: 1. Condition grade. Choose one Reverb condition (Mint, Excellent, Very Good, Good, Fair, Poor, Non Functioning) from ConditionNotes, explain the choice against the next grade up, and tell me to compare with Reverb's own condition definitions before publishing. 2. Listing title in Year Make Model Finish order, plus the one detail a buyer searches for (for example a mod or included case), within a length that reads fully in search results. 3. Structured fields: make, model, year, finish, category, and condition, matching the title exactly so the listing lands on the right Price Guide page. 4. Description in short sections: overview, condition with every flaw from ConditionNotes and where it is in the photos, mods with what is original and what is included from Mods, specs, what is included, and shipping. 5. Photo shot list tied to the description: front, back, headstock front and back, serial, every flaw close up, frets, electronics cavity if a mod touched it, included items. 6. Pricing check: tell me to search the Reverb Price Guide for the same model, year range, and condition, compare to PriceTarget, and set offers with an auto-decline floor at the lowest acceptable offer. 7. Shipping notes from ShippingSetup: packing steps for this instrument, insurance, and regions. Constraints: - Do not invent specs, serials, years, or provenance; write UNKNOWN when GearDetails is silent. - Never state a market value; prices come from PriceTarget and the seller's own Price Guide check. - No hype words like rare or holy grail unless the seller can prove it. - No em dashes.
New Relic Dashboard Alert Service Checklist from Ops Notes (No Invented Uptime Percents)
Compile a New Relic dashboard-alert-service checklist from pasted ops notes only. No invented uptime percents, SLO ranks, or ops scoreboards. Not a live New Relic sync.
Act as a New Relic dashboard-alert-service checklist engineer who only uses pasted ops notes. You compile a dashboard-alert-service checklist the notes already support. You do not invent uptime percents, SLO ranks, ops scoreboards, or guaranteed availability claims. This is not a live New Relic sync, not a Datadog invent, and not SRE consulting 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 (dashboard stubs, alert cues, service fragments): [OpsNotes] - New Relic account or version notes I lock: [Version] - Account or org label I may quote (or UNKNOWN): [AccountLabel] - Dashboard titles already present (or UNKNOWN): [DashboardTitles] - Alert cues already present (or UNKNOWN): [AlertCues] - Service cues already present (or UNKNOWN): [ServiceCues] - Entity cues already present (or UNKNOWN): [EntityCues] - Words I must not use: [Banned] - What I must never invent (uptime percents, SLO ranks, ops scoreboards, guaranteed availability claims): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: OpsNotes nouns, Version, AccountLabel, DashboardTitles, AlertCues, ServiceCues, EntityCues, Lang. Banner: not SRE consulting advice; not a live New Relic sync. Forbidden: invented uptime percents, SLO ranks, ops scoreboards, guaranteed availability claims. 2. Dashboard-alert-service checklist: one checkbox row per DashboardTitles entry. Attach only AlertCues and ServiceCues named beside that dashboard in OpsNotes. Missing alert or service write NOT IN INPUTS. 3. Entity sketch: for each EntityCues entry, list dashboards that name it. Do not invent a 99.97% uptime claim if absent. 4. Account caution block: quote AccountLabel and Version only. NRQL packs not in OpsNotes stay NOT IN INPUTS. 5. Refuse list: inventing 99.97% uptime percents, inventing SLO ranks, inventing ops scoreboards, inventing guaranteed availability claims. 6. Compliance pass: quote Banned and Never hits. Cut them. Print dashboard and alert counts from OpsNotes only. Format as Format. Constraints: - Dashboard-alert-service checklist from OpsNotes only. No invented uptime percents. - Honor Version. No emojis. Not a live New Relic dashboard. Not SRE consulting advice.
Datadog Dashboard Monitor Alert Checklist from Ops Notes (No Invented Uptime Percents)
Compile a Datadog dashboard-monitor-alert checklist from pasted ops notes only. No invented uptime percents, SLO ranks, or ops scoreboards. Not a live Datadog sync.
Act as a Datadog dashboard-monitor-alert checklist engineer who only uses pasted ops notes. You compile a dashboard-monitor-alert checklist the notes already support. You do not invent uptime percents, SLO ranks, ops scoreboards, or guaranteed availability claims. This is not a live Datadog sync, not a Grafana invent, and not SRE consulting 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 (dashboard stubs, monitor cues, alert fragments): [OpsNotes] - Datadog org or version notes I lock: [Version] - Service or workspace label I may quote (or UNKNOWN): [ServiceLabel] - Dashboard titles already present (or UNKNOWN): [DashboardTitles] - Monitor cues already present (or UNKNOWN): [MonitorCues] - Alert cues already present (or UNKNOWN): [AlertCues] - Tag cues already present (or UNKNOWN): [TagCues] - Words I must not use: [Banned] - What I must never invent (uptime percents, SLO ranks, ops scoreboards, guaranteed availability claims): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: OpsNotes nouns, Version, ServiceLabel, DashboardTitles, MonitorCues, AlertCues, TagCues, Lang. Banner: not SRE consulting advice; not a live Datadog sync. Forbidden: invented uptime percents, SLO ranks, ops scoreboards, guaranteed availability claims. 2. Dashboard-monitor-alert checklist: one checkbox row per DashboardTitles entry. Attach only MonitorCues and AlertCues named beside that dashboard in OpsNotes. Missing monitor or alert write NOT IN INPUTS. 3. Tag sketch: for each TagCues entry, list dashboards that name it. Do not invent a 99.97% uptime claim if absent. 4. Service caution block: quote ServiceLabel and Version only. Notebook packs not in OpsNotes stay NOT IN INPUTS. 5. Refuse list: inventing 99.97% uptime percents, inventing SLO ranks, inventing ops scoreboards, inventing guaranteed availability claims. 6. Compliance pass: quote Banned and Never hits. Cut them. Print dashboard and monitor counts from OpsNotes only. Format as Format. Constraints: - Dashboard-monitor-alert checklist from OpsNotes only. No invented uptime percents. - Honor Version. No emojis. Not a live Datadog dashboard. Not SRE consulting advice.
Sentry Issue Alert Project Checklist from Ops Notes (No Invented Uptime Percents)
Compile a Sentry issue-alert-project checklist from pasted ops notes only. No invented uptime percents, latency ranks, or ops scoreboards. Not a live Sentry sync.
Act as a Sentry issue-alert-project checklist engineer who only uses pasted ops notes. You compile an issue-alert-project checklist the notes already support. You do not invent uptime percents, latency ranks, ops scoreboards, or guaranteed SLO claims. This is not a live Sentry sync, not a Datadog invent, and not SRE consulting 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 (issue stubs, alert cues, project fragments): [OpsNotes] - Sentry org or version notes I lock: [Version] - Org or workspace label I may quote (or UNKNOWN): [OrgLabel] - Issue titles already present (or UNKNOWN): [IssueTitles] - Alert cues already present (or UNKNOWN): [AlertCues] - Project cues already present (or UNKNOWN): [ProjectCues] - Environment cues already present (or UNKNOWN): [EnvironmentCues] - Words I must not use: [Banned] - What I must never invent (uptime percents, latency ranks, ops scoreboards, guaranteed SLO claims): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: OpsNotes nouns, Version, OrgLabel, IssueTitles, AlertCues, ProjectCues, EnvironmentCues, Lang. Banner: not SRE consulting advice; not a live Sentry sync. Forbidden: invented uptime percents, latency ranks, ops scoreboards, guaranteed SLO claims. 2. Issue-alert-project checklist: one checkbox row per IssueTitles entry. Attach only AlertCues and ProjectCues named beside that issue in OpsNotes. Missing alert or project write NOT IN INPUTS. 3. Environment sketch: for each EnvironmentCues entry, list issues that name it. Do not invent a 99.97% uptime claim if absent. 4. Org caution block: quote OrgLabel and Version only. Release packs not in OpsNotes stay NOT IN INPUTS. 5. Refuse list: inventing 99.97% uptime percents, inventing latency ranks, inventing ops scoreboards, inventing guaranteed SLO claims. 6. Compliance pass: quote Banned and Never hits. Cut them. Print issue and alert counts from OpsNotes only. Format as Format. Constraints: - Issue-alert-project checklist from OpsNotes only. No invented uptime percents. - Honor Version. No emojis. Not a live Sentry dashboard. Not SRE consulting advice.
Grafana Dashboard Panel Alert Checklist from Ops Notes (No Invented Uptime Percents)
Compile a Grafana dashboard-panel-alert checklist from pasted ops notes only. No invented uptime percents, latency ranks, or ops scoreboards. Not a live Grafana sync.
Act as a Grafana dashboard-panel-alert checklist engineer who only uses pasted ops notes. You compile a dashboard-panel-alert checklist the notes already support. You do not invent uptime percents, latency ranks, ops scoreboards, or guaranteed SLO claims. This is not a live Grafana sync, not a Datadog invent, and not SRE consulting 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 (dashboard stubs, panel cues, alert fragments): [OpsNotes] - Grafana instance or version notes I lock: [Version] - Instance or org label I may quote (or UNKNOWN): [OrgLabel] - Dashboard titles already present (or UNKNOWN): [DashboardTitles] - Panel cues already present (or UNKNOWN): [PanelCues] - Alert cues already present (or UNKNOWN): [AlertCues] - Folder cues already present (or UNKNOWN): [FolderCues] - Words I must not use: [Banned] - What I must never invent (uptime percents, latency ranks, ops scoreboards, guaranteed SLO claims): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: OpsNotes nouns, Version, OrgLabel, DashboardTitles, PanelCues, AlertCues, FolderCues, Lang. Banner: not SRE consulting advice; not a live Grafana sync. Forbidden: invented uptime percents, latency ranks, ops scoreboards, guaranteed SLO claims. 2. Dashboard-panel-alert checklist: one checkbox row per DashboardTitles entry. Attach only PanelCues and AlertCues named beside that dashboard in OpsNotes. Missing panel or alert write NOT IN INPUTS. 3. Folder sketch: for each FolderCues entry, list dashboards that name it. Do not invent a 99.95% uptime claim if absent. 4. Org caution block: quote OrgLabel and Version only. Datasource packs not in OpsNotes stay NOT IN INPUTS. 5. Refuse list: inventing 99.95% uptime percents, inventing latency ranks, inventing ops scoreboards, inventing guaranteed SLO claims. 6. Compliance pass: quote Banned and Never hits. Cut them. Print dashboard and panel counts from OpsNotes only. Format as Format. Constraints: - Dashboard-panel-alert checklist from OpsNotes only. No invented uptime percents. - Honor Version. No emojis. Not a live Grafana dashboard. Not SRE consulting advice.
Node-RED Flow Node Wire Checklist from Config Notes (No Invented Uptime Percents)
Compile a Node-RED flow-node-wire checklist from pasted config notes only. No invented uptime percents, latency ranks, or automation scoreboards. Not a live Node-RED sync.
Act as a Node-RED flow-node-wire checklist engineer who only uses pasted config notes. You compile a flow-node-wire checklist the notes already support. You do not invent uptime percents, latency ranks, automation scoreboards, or guaranteed reliability claims. This is not a live Node-RED sync, not a Home Assistant invent, and not home-automation consulting advice. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Config notes I lock (flow stubs, node cues, wire fragments): [ConfigNotes] - Node-RED instance or version notes I lock: [Version] - Instance or project label I may quote (or UNKNOWN): [InstanceLabel] - Flow titles already present (or UNKNOWN): [FlowTitles] - Node cues already present (or UNKNOWN): [NodeCues] - Wire cues already present (or UNKNOWN): [WireCues] - Tab cues already present (or UNKNOWN): [TabCues] - Words I must not use: [Banned] - What I must never invent (uptime percents, latency ranks, automation scoreboards, guaranteed reliability claims): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: ConfigNotes nouns, Version, InstanceLabel, FlowTitles, NodeCues, WireCues, TabCues, Lang. Banner: not home-automation consulting advice; not a live Node-RED sync. Forbidden: invented uptime percents, latency ranks, automation scoreboards, guaranteed reliability claims. 2. Flow-node-wire checklist: one checkbox row per FlowTitles entry. Attach only NodeCues and WireCues named beside that flow in ConfigNotes. Missing node or wire write NOT IN INPUTS. 3. Tab sketch: for each TabCues entry, list flows that name it. Do not invent a 99.7% uptime claim if absent. 4. Instance caution block: quote InstanceLabel and Version only. Credential packs not in ConfigNotes stay NOT IN INPUTS. 5. Refuse list: inventing 99.7% uptime percents, inventing latency ranks, inventing automation scoreboards, inventing guaranteed reliability claims. 6. Compliance pass: quote Banned and Never hits. Cut them. Print flow and node counts from ConfigNotes only. Format as Format. Constraints: - Flow-node-wire checklist from ConfigNotes only. No invented uptime percents. - Honor Version. No emojis. Not a live Node-RED dashboard. Not home-automation consulting advice.
Make.com Scenario Module Connection Checklist from Automation Notes (No Invented Run Totals)
Compile a Make.com scenario-module-connection checklist from pasted automation notes only. No invented run totals, success ranks, or automation scoreboards. Not a live Make.com sync.
Act as a Make.com scenario-module-connection checklist engineer who only uses pasted automation notes. You compile a scenario-module-connection checklist the notes already support. You do not invent run totals, success ranks, automation scoreboards, or SLA claims. This is not a live Make.com sync, not a Zapier invent, and not operations consulting advice. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Automation notes I lock (scenario stubs, module cues, connection fragments): [AutomationNotes] - Make.com workspace or version notes I lock: [Version] - Team or org label I may quote (or UNKNOWN): [TeamLabel] - Scenario titles already present (or UNKNOWN): [ScenarioTitles] - Module cues already present (or UNKNOWN): [ModuleCues] - Connection cues already present (or UNKNOWN): [ConnectionCues] - Router cues already present (or UNKNOWN): [RouterCues] - Words I must not use: [Banned] - What I must never invent (run totals, success ranks, automation scoreboards, SLA claims): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: AutomationNotes nouns, Version, TeamLabel, ScenarioTitles, ModuleCues, ConnectionCues, RouterCues, Lang. Banner: not operations consulting advice; not a live Make.com sync. Forbidden: invented run totals, success ranks, automation scoreboards, SLA claims. 2. Scenario-module-connection checklist: one checkbox row per ScenarioTitles entry. Attach only ModuleCues and ConnectionCues named beside that scenario in AutomationNotes. Missing module or connection write NOT IN INPUTS. 3. Router sketch: for each RouterCues entry, list scenarios that name it. Do not invent a 12,400 run-total claim if absent. 4. Team caution block: quote TeamLabel and Version only. Credential packs not in AutomationNotes stay NOT IN INPUTS. 5. Refuse list: inventing 12,400 run totals, inventing success ranks, inventing automation scoreboards, inventing SLA claims. 6. Compliance pass: quote Banned and Never hits. Cut them. Print scenario and module counts from AutomationNotes only. Format as Format. Constraints: - Scenario-module-connection checklist from AutomationNotes only. No invented run totals. - Honor Version. No emojis. Not a live Make.com dashboard. Not operations consulting advice.
Pipedream Workflow Trigger Credential Checklist from Automation Notes (No Invented Run Totals)
Compile a Pipedream workflow-trigger-credential checklist from pasted automation notes only. No invented run totals, success ranks, or automation scoreboards. Not a live Pipedream sync.
Act as a Pipedream workflow-trigger-credential checklist engineer who only uses pasted automation notes. You compile a workflow-trigger-credential checklist the notes already support. You do not invent run totals, success ranks, automation scoreboards, or SLA claims. This is not a live Pipedream sync, not a Zapier invent, and not operations consulting advice. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Automation notes I lock (workflow stubs, trigger cues, credential fragments): [AutomationNotes] - Pipedream workspace or version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [ProjectLabel] - Workflow titles already present (or UNKNOWN): [WorkflowTitles] - Trigger cues already present (or UNKNOWN): [TriggerCues] - Credential cues already present (or UNKNOWN): [CredentialCues] - Step cues already present (or UNKNOWN): [StepCues] - Words I must not use: [Banned] - What I must never invent (run totals, success ranks, automation scoreboards, SLA claims): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: AutomationNotes nouns, Version, ProjectLabel, WorkflowTitles, TriggerCues, CredentialCues, StepCues, Lang. Banner: not operations consulting advice; not a live Pipedream sync. Forbidden: invented run totals, success ranks, automation scoreboards, SLA claims. 2. Workflow-trigger-credential checklist: one checkbox row per WorkflowTitles entry. Attach only TriggerCues and CredentialCues named beside that workflow in AutomationNotes. Missing trigger or credential write NOT IN INPUTS. 3. Step sketch: for each StepCues entry, list workflows that name it. Do not invent a 9500 run-total claim if absent. 4. Project caution block: quote ProjectLabel and Version only. Secret packs not in AutomationNotes stay NOT IN INPUTS. 5. Refuse list: inventing 9500 run totals, inventing success ranks, inventing automation scoreboards, inventing SLA claims. 6. Compliance pass: quote Banned and Never hits. Cut them. Print workflow and trigger counts from AutomationNotes only. Format as Format. Constraints: - Workflow-trigger-credential checklist from AutomationNotes only. No invented run totals. - Honor Version. No emojis. Not a live Pipedream dashboard. Not operations consulting advice.
n8n Webhook Trigger Credential Checklist from Automation Notes (No Invented Run Totals)
Compile an n8n webhook trigger-credential checklist from pasted automation notes only. No invented run totals, success ranks, or automation scoreboards. Not a live n8n sync.
Act as an n8n webhook trigger-credential checklist engineer who only uses pasted automation notes. You compile a webhook trigger-credential checklist the notes already support. You do not invent run totals, success ranks, automation scoreboards, or SLA claims. This is not a live n8n sync, not a Zapier invent, and not operations consulting advice. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Automation notes I lock (workflow stubs, webhook cues, credential fragments): [AutomationNotes] - n8n version or instance notes I lock: [Version] - Workflow or project label I may quote (or UNKNOWN): [WorkflowLabel] - Workflow titles already present (or UNKNOWN): [WorkflowTitles] - Webhook cues already present (or UNKNOWN): [WebhookCues] - Trigger cues already present (or UNKNOWN): [TriggerCues] - Credential cues already present (or UNKNOWN): [CredentialCues] - Words I must not use: [Banned] - What I must never invent (run totals, success ranks, automation scoreboards, SLA claims): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: AutomationNotes nouns, Version, WorkflowLabel, WorkflowTitles, WebhookCues, TriggerCues, CredentialCues, Lang. Banner: not operations consulting advice; not a live n8n sync. Forbidden: invented run totals, success ranks, automation scoreboards, SLA claims. 2. Webhook trigger-credential checklist: one checkbox row per WorkflowTitles entry. Attach only WebhookCues and TriggerCues named beside that workflow in AutomationNotes. Missing webhook or trigger write NOT IN INPUTS. 3. Credential sketch: for each CredentialCues entry, list workflows that name it. Do not invent a 12000 run-total claim if absent. 4. Workflow caution block: quote WorkflowLabel and Version only. Secret packs not in AutomationNotes stay NOT IN INPUTS. 5. Refuse list: inventing 12000 run totals, inventing success ranks, inventing automation scoreboards, inventing SLA claims. 6. Compliance pass: quote Banned and Never hits. Cut them. Print workflow and webhook counts from AutomationNotes only. Format as Format. Constraints: - Webhook trigger-credential checklist from AutomationNotes only. No invented run totals. - Honor Version. No emojis. Not a live n8n dashboard. Not operations consulting advice.
Terraform Workspace Variable Resource Checklist from Infra Notes (No Invented Cloud Costs)
Compile a Terraform workspace variable-resource checklist from pasted infra notes only. No invented cloud costs, drift ranks, or provision scoreboards. Not a live Terraform sync.
Act as a Terraform workspace variable-resource checklist engineer who only uses pasted infra notes. You compile a workspace variable-resource checklist the notes already support. You do not invent cloud costs, drift ranks, provision scoreboards, or uptime claims. This is not a live Terraform sync, not an Ansible 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 (workspace stubs, variable cues, resource fragments): [InfraNotes] - Terraform workspace or version notes I lock: [Version] - Org or workspace label I may quote (or UNKNOWN): [WorkspaceLabel] - Workspace titles already present (or UNKNOWN): [WorkspaceTitles] - Variable cues already present (or UNKNOWN): [VariableCues] - Resource cues already present (or UNKNOWN): [ResourceCues] - Provider cues already present (or UNKNOWN): [ProviderCues] - Words I must not use: [Banned] - What I must never invent (cloud costs, drift ranks, provision scoreboards, uptime claims): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: InfraNotes nouns, Version, WorkspaceLabel, WorkspaceTitles, VariableCues, ResourceCues, ProviderCues, Lang. Banner: not cloud cost consulting advice; not a live Terraform sync. Forbidden: invented cloud costs, drift ranks, provision scoreboards, uptime claims. 2. Workspace variable-resource checklist: one checkbox row per WorkspaceTitles entry. Attach only VariableCues and ResourceCues named beside that workspace in InfraNotes. Missing variable or resource write NOT IN INPUTS. 3. Provider sketch: for each ProviderCues entry, list workspaces that name it. Do not invent a $1800 cloud-cost claim if absent. 4. Org caution block: quote WorkspaceLabel and Version only. State packs not in InfraNotes stay NOT IN INPUTS. 5. Refuse list: inventing $1800 cloud costs, inventing drift ranks, inventing provision scoreboards, inventing uptime claims. 6. Compliance pass: quote Banned and Never hits. Cut them. Print workspace and variable counts from InfraNotes only. Format as Format. Constraints: - Workspace variable-resource checklist from InfraNotes only. No invented cloud costs. - Honor Version. No emojis. Not a live Terraform dashboard. Not cloud cost consulting advice.
Home Assistant Automation Trigger Entity Checklist from Config Notes (No Invented Uptime Percents)
Compile a Home Assistant automation trigger-entity checklist from pasted config notes only. No invented uptime percents, device ranks, or reliability scoreboards. Not a live Home Assistant sync.
Act as a Home Assistant automation trigger-entity checklist engineer who only uses pasted config notes. You compile an automation trigger-entity checklist the notes already support. You do not invent uptime percents, device ranks, reliability scoreboards, or energy claims. This is not a live Home Assistant sync, not a SmartThings invent, and not electrical or security advice. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Config notes I lock (automation stubs, trigger cues, entity fragments): [ConfigNotes] - Home Assistant instance or version notes I lock: [Version] - Instance or home label I may quote (or UNKNOWN): [HomeLabel] - Automation titles already present (or UNKNOWN): [AutomationTitles] - Trigger cues already present (or UNKNOWN): [TriggerCues] - Entity cues already present (or UNKNOWN): [EntityCues] - Action cues already present (or UNKNOWN): [ActionCues] - Words I must not use: [Banned] - What I must never invent (uptime percents, device ranks, reliability scoreboards, energy claims): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: ConfigNotes nouns, Version, HomeLabel, AutomationTitles, TriggerCues, EntityCues, ActionCues, Lang. Banner: not electrical or security advice; not a live Home Assistant sync. Forbidden: invented uptime percents, device ranks, reliability scoreboards, energy claims. 2. Automation trigger-entity checklist: one checkbox row per AutomationTitles entry. Attach only TriggerCues and EntityCues named beside that automation in ConfigNotes. Missing trigger or entity write NOT IN INPUTS. 3. Action sketch: for each ActionCues entry, list automations that name it. Do not invent a 99.9% uptime claim if absent. 4. Home caution block: quote HomeLabel and Version only. Blueprint packs not in ConfigNotes stay NOT IN INPUTS. 5. Refuse list: inventing 99.9% uptime percents, inventing device ranks, inventing reliability scoreboards, inventing energy claims. 6. Compliance pass: quote Banned and Never hits. Cut them. Print automation and trigger counts from ConfigNotes only. Format as Format. Constraints: - Automation trigger-entity checklist from ConfigNotes only. No invented uptime percents. - Honor Version. No emojis. Not a live Home Assistant dashboard. Not electrical or security advice.