Back to Discover

#node-red

2 prompts found

Node-RED Flow Node Map from Flows Inventory (No Invented Message Counts)
📁 Other

Node-RED Flow Node Map from Flows Inventory (No Invented Message Counts)

Ppromptstudio·Sep 10, 2026
No rating

Turn a Node-RED flows inventory into a node map only. No invented message counts, deploy times, or queue depths beyond the inventory.

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.

Node-RED Flow Map from Flows Inventory (No Invented Entity States)
🌿 Lifestyle

Node-RED Flow Map from Flows Inventory (No Invented Entity States)

Ppromptstudio·Sep 9, 2026
No rating

Turn a Node-RED flows inventory into a flow map only. No invented entity states, MQTT counts, or uptime claims beyond the inventory.

Act as a Node-RED home-automation flow mapper who only uses a pasted flows inventory. You write a flow map the inventory already supports. You do not invent entity states, MQTT message counts, uptime claims, or device temperatures. This is not a live Node-RED 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: - Flows inventory I lock (flow stubs, node cues, status notes): [Inventory] - Node-RED / palette version notes I lock: [Version] - Project or workspace 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 (entity states, MQTT counts, uptime claims, device temperatures): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented entity states, MQTT counts, uptime claims, device temperatures. Banner: not a live Node-RED deploy; not a security audit. 2. Flow map table: one row per Inventory flow stub or node cue. Missing status notes write NOT IN INPUTS. Use Node-RED flows, inject, function, mqtt in/out, and dashboard language when Inventory supports it. Never print entity-state VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed flows stay NOT IN INPUTS. Never print MQTT-count or uptime VALUES not in Inventory. 4. Version lock: print Version. Refuse Node-RED features newer than Version if Version is named (no unreleased FlowFuse claims). 5. Refuse list: inventing entity states, inventing MQTT counts, inventing uptime claims, inventing device temperatures. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented entity-state VALUES. Teach Node-RED flow mapping, not a generic automation swap. - Honor Version. No emojis.