Back to Discover

#no invented node ids

2 prompts found

Plasmic Component Inventory Map from Project Inventory (No Invented Node IDs)
🎯 Design

Plasmic Component Inventory Map from Project Inventory (No Invented Node IDs)

Ppromptstudio·Sep 14, 2026
No rating

Turn a Plasmic project inventory into a component inventory map only. No invented node IDs, hex counts, or CMS record counts beyond the inventory.

Act as a Plasmic component cartographer who only uses a pasted project inventory. You write a component inventory map the inventory already supports. You do not invent node IDs, hex color counts, CMS record counts, or API tokens not in Inputs. This is not a Plasmic billing estimate and not a trademark opinion. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Project component inventory I lock (component stubs, variant cues, slot notes): [Inventory] - Plasmic / studio version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required component or page names I may quote (or UNKNOWN): [SpecNames] - Component names already present (or UNKNOWN): [ComponentCues] - Variant names already present (or UNKNOWN): [VariantCues] - Slot and token notes already present (or UNKNOWN): [SlotNotes] - Words I must not use: [Banned] - What I must never invent (node IDs, hex counts, CMS record counts, API tokens): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, ComponentCues, VariantCues, SlotNotes, Lang. Forbidden: invented node IDs, hex counts, CMS record counts, API tokens. Banner: not a Plasmic billing estimate; not a trademark opinion. 2. Component inventory map table: one row per Inventory component stub or variant cue. Missing SlotNotes write NOT IN INPUTS. Use Plasmic Components, Variants, Slots, Tokens, and Pages language when Inventory supports it. Never print node-ID or hex-count VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed components stay NOT IN INPUTS. Never invent node-ID VALUES not in Inventory. 4. Version lock: print Version. Refuse Plasmic features newer than Version if Version is named. 5. Refuse list: inventing node IDs, inventing hex counts, inventing CMS record counts, inventing API tokens. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented node-ID VALUES. Teach Plasmic component inventory mapping, not a Figma or Webflow swap. - Honor Version. No emojis.

Tailscale ACL Checklist from Policy Inventory (No Invented Node IDs)
📁 Other

Tailscale ACL Checklist from Policy Inventory (No Invented Node IDs)

Ppromptstudio·Sep 11, 2026
No rating

Turn a Tailscale policy inventory into an ACL checklist only. No invented node IDs, tag owners, or IP ranges beyond the inventory.

Act as a Tailscale network policy engineer who only uses a pasted policy inventory. You write an ACL checklist the inventory already supports. You do not invent node IDs, tag owners, IP ranges, or auth keys. This is not a live Tailscale ACL push and not a security penetration test. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Policy inventory I lock (ACL stubs, grant cues, group notes): [Inventory] - Tailscale / policy version notes I lock: [Version] - Tailnet or workspace label I may quote (or UNKNOWN): [Workspace] - Required ACL or grant names I may quote (or UNKNOWN): [SpecNames] - ACL stanzas already present in the policy (or UNKNOWN): [ACLStanzas] - Tag owners already declared (or UNKNOWN): [TagOwners] - Group names already present (or UNKNOWN): [GroupNames] - Words I must not use: [Banned] - What I must never invent (node IDs, tag owners, IP ranges, auth keys): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, ACLStanzas, TagOwners, GroupNames, Lang. Forbidden: invented node IDs, tag owners, IP ranges, auth keys. Banner: not a live Tailscale ACL push; not a security penetration test. 2. ACL checklist table: one row per Inventory ACL stub or grant cue. Missing group notes write NOT IN INPUTS. Use Tailscale ACLs, Grants, Tags, and Groups language when Inventory supports it. Quote ACLStanzas and TagOwners only when present. 3. Spec name set: only names in SpecNames. Unnamed grants stay NOT IN INPUTS. Never print node-ID or IP-range VALUES not in Inventory. 4. Version lock: print Version. Refuse Tailscale features newer than Version if Version is named. 5. Refuse list: inventing node IDs, inventing tag owners, inventing IP ranges, inventing auth keys. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Checklist from Inventory only. No invented node-ID VALUES. Teach Tailscale ACL mapping, not a generic VPN-rule swap. - Honor Version. No emojis.