📁 Other
Node-RED Flow Node Map from Flows Inventory (No Invented Message Counts)
Turn a Node-RED flows inventory into a node map only. No invented message counts, deploy times, or queue depths beyond the inventory.
0Reviews
Prompt
Act as a Node-RED flows specialist who only uses a pasted flows inventory. You write a flow node map the inventory already supports. You do not invent message counts, deploy times, queue depths, or CPU usage. This is not a live Node-RED runtime call 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: - Flows inventory I lock (flow stubs, node cues, wire notes): [Inventory] - Node-RED / runtime version notes I lock: [Version] - Instance or project label I may quote (or UNKNOWN): [Workspace] - Required flow or tab names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (message counts, deploy times, queue depths, CPU usage): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented message counts, deploy times, queue depths, CPU usage. Banner: not a live Node-RED runtime call; not a security audit. 2. Flow node map table: one row per Inventory flow stub or node cue. Missing wire notes write NOT IN INPUTS. Use Node-RED inject, function, switch, and debug node language when Inventory supports it. 3. Spec name set: only names in SpecNames. Unnamed flows stay NOT IN INPUTS. Never print message-count or deploy-time VALUES not in Inventory. 4. Version lock: print Version. Refuse Node-RED features newer than Version if Version is named. 5. Refuse list: inventing message counts, inventing deploy times, inventing queue depths, inventing CPU usage. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented message-count VALUES. Teach Node-RED flow mapping, not a generic automation swap. - Honor Version. No emojis.
Instructions
Replace every [bracket] with your details before running. Works on ChatGPT, Claude, and Gemini.
Generated Output
This image was generated using the prompt above.
Examples
Example Input
Inventory: flow Harbor Quay Berth MQTT Bridge as pasted node cue mqtt in berth/# as pasted wire note to function Normalize as pasted; flow River Ops Gate Alert as pasted node cue inject every 5m as pasted. Message count NOT IN INPUTS. Deploy time NONE. Version: Node-RED 3.1 as pasted (do not invent unreleased AI assist APIs) Workspace: Harbor Quay Node-RED Instance as pasted SpecNames: Berth MQTT Bridge as pasted; Gate Alert as pasted. Tide Dashboard UNKNOWN. Banned: guaranteed message count, deploy invent, queue invent, CPU invent Never: invent message counts, invent deploy times, invent queue depths, invent CPU usage Format: ledger + table + specs + version + refuse + compliance Lang: English
Example Output
1. Ledger. Inventory: flow Harbor Quay Berth MQTT Bridge node cue mqtt in berth/# wire note to function Normalize; flow River Ops Gate Alert node cue inject every 5m. Message count NOT IN INPUTS. Deploy time NONE. Version Node-RED 3.1. Workspace Harbor Quay Node-RED Instance. SpecNames Berth MQTT Bridge; Gate Alert; Tide Dashboard UNKNOWN. Lang English. Banner: not a live Node-RED runtime call; not a security audit. Forbidden: invented message counts, deploy times, queue depths, CPU usage, guaranteed message count, deploy invent, queue invent, CPU invent. 2. Flow node map. 1. Harbor Quay Berth MQTT Bridge | node mqtt in berth/# as pasted | wire to function Normalize as pasted | message count NOT IN INPUTS | deploy time NONE | Node-RED flow map only. 2. River Ops Gate Alert | node inject every 5m as pasted | wire NOT IN INPUTS | message count NOT IN INPUTS | deploy time NONE. Queue depths not printed. CPU usage not invented. 3. Spec name set. Berth MQTT Bridge; Gate Alert as SpecNames. Tide Dashboard UNKNOWN so write Tide Dashboard NOT IN INPUTS. No message-count VALUES printed. No third flow invented. 4. Version lock. Node-RED 3.1 as pasted. Unreleased AI assist APIs not used. Dashboard 2 schema NOT IN INPUTS. 5. Refuse. Message invent: refused. Deploy invent: refused. Queue invent: refused. CPU invent: refused. Guaranteed message count: refused. 6. Compliance. Banned hits none. Format ledger+table+specs+version+refuse+compliance. Gaps: wire for River Ops Gate Alert, Tide Dashboard decision, credential names, context keys, catch nodes if any. Missing-data policy: if a field was blank, write NOT IN INPUTS rather than guessing. Lock any tool version named in Inputs; if unnamed, write unknown. No invented testimonials, star ratings, or press logos. If legal, clinical, insurance, HR, education-plan, or veterinary content appears, add a one-line not-advice and de-identify banner. Quote banned-word hits and cut them. End with a gaps list of five bullets the user still owes you. Character and byte caps in the job are hard; print counts when relevant. Refuse to backfill DOIs, exam dumps, PHI, PII, or compensation promises not in Inputs.