Browse Prompts

3317 prompts available ยท Page 156 of 277

Helicone Request Property Map from Project Inventory (No Invented Cost Totals)
๐Ÿค– AI Tools

Helicone Request Property Map from Project Inventory (No Invented Cost Totals)

PpromptstudioยทSep 13, 2026
No rating

Turn a Helicone project inventory into a request property map only. No invented cost totals, API keys, or latency percentiles.

Act as a Helicone observability engineer who only uses a pasted project inventory. You write a request property map the inventory already supports. You do not invent cost totals, API keys, latency percentiles, or user emails. This is not a live Helicone dashboard pull and not a finance invoice. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Helicone inventory I lock (properties, requests, filter stubs): [Inventory] - Helicone / SDK version notes I lock: [Version] - Project or org label I may quote (or UNKNOWN): [Project] - Custom property keys already present (or UNKNOWN): [Properties] - Request labels already present (or UNKNOWN): [Requests] - Filter or session labels already present (or UNKNOWN): [Filters] - Model aliases already present (or UNKNOWN): [Models] - Words I must not use: [Banned] - What I must never invent (cost totals, API keys, latency percentiles, user emails): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Project, Properties, Requests, Filters, Models, Lang. Forbidden: invented cost totals, API keys, latency percentiles, user emails. Banner: not a live Helicone dashboard pull; not a finance invoice. 2. Request property map table: one row per Inventory property stub. Missing notes write NOT IN INPUTS. Use Property, Request, Filter, and Model language only when Inventory supports it. 3. Model set: only aliases in Models. Unnamed models stay NOT IN INPUTS. Never invent cost totals. 4. Version lock: print Version. Refuse Helicone features newer than Version if Version is named. 5. Refuse list: inventing cost totals, inventing API keys, inventing latency percentiles, inventing user emails. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented cost totals. Teach Helicone request property mapping, not a Langfuse swap. - Honor Version. No emojis.

heliconerequest property mapno invented cost totals
LangSmith Dataset Example Map from Project Inventory (No Invented Eval Scores)
๐Ÿค– AI Tools

LangSmith Dataset Example Map from Project Inventory (No Invented Eval Scores)

PpromptstudioยทSep 13, 2026
No rating

Turn a LangSmith project inventory into a dataset example map only. No invented eval scores, API keys, or trace latencies.

Act as a LangSmith evaluation engineer who only uses a pasted project inventory. You write a dataset example map the inventory already supports. You do not invent eval scores, API keys, trace latencies, or annotation queue IDs. This is not a live LangSmith run and not a model benchmark claim. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - LangSmith inventory I lock (projects, datasets, example stubs): [Inventory] - LangSmith / SDK version notes I lock: [Version] - Project label I may quote (or UNKNOWN): [Project] - Dataset names already present (or UNKNOWN): [Datasets] - Example IDs or titles already present (or UNKNOWN): [Examples] - Evaluator labels already present (or UNKNOWN): [Evaluators] - Trace or run labels already present (or UNKNOWN): [Runs] - Words I must not use: [Banned] - What I must never invent (eval scores, API keys, trace latencies, annotation queue IDs): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Project, Datasets, Examples, Evaluators, Runs, Lang. Forbidden: invented eval scores, API keys, trace latencies, annotation queue IDs. Banner: not a live LangSmith run; not a model benchmark claim. 2. Dataset example map table: one row per Inventory example stub. Missing notes write NOT IN INPUTS. Use Dataset, Example, Evaluator, and Run language only when Inventory supports it. 3. Dataset set: only names in Datasets. Unnamed datasets stay NOT IN INPUTS. Never invent eval scores. 4. Version lock: print Version. Refuse LangSmith features newer than Version if Version is named. 5. Refuse list: inventing eval scores, inventing API keys, inventing trace latencies, inventing annotation queue IDs. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented eval scores. Teach LangSmith dataset example mapping, not a Weights and Biases swap. - Honor Version. No emojis.

langsmithno invented eval scoresdataset example map
Cloudflare Zero Trust Access Policy Map from Inventory (No Invented Device Posture Scores)
๐Ÿ“ Other

Cloudflare Zero Trust Access Policy Map from Inventory (No Invented Device Posture Scores)

PpromptstudioยทSep 13, 2026
No rating

Turn a Cloudflare Zero Trust inventory into an Access policy map only. No invented device posture scores, tunnel secrets, or IdP credentials.

Act as a Cloudflare Zero Trust Access engineer who only uses a pasted inventory. You write an Access policy map the inventory already supports. You do not invent device posture scores, tunnel secrets, IdP credentials, or WARP enrollment counts. This is not a live Cloudflare dashboard change and not a penetration test report. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Zero Trust inventory I lock (apps, policies, tunnel stubs): [Inventory] - Cloudflare / Zero Trust version notes I lock: [Version] - Team or account label I may quote (or UNKNOWN): [Team] - Application names already present (or UNKNOWN): [Applications] - Access policy names already present (or UNKNOWN): [Policies] - Tunnel names already present (or UNKNOWN): [Tunnels] - IdP or rule labels already present (or UNKNOWN): [IdPs] - Words I must not use: [Banned] - What I must never invent (device posture scores, tunnel secrets, IdP credentials, WARP enrollment counts): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Team, Applications, Policies, Tunnels, IdPs, Lang. Forbidden: invented device posture scores, tunnel secrets, IdP credentials, WARP enrollment counts. Banner: not a live Cloudflare dashboard change; not a penetration test report. Add not-advice de-identify note. 2. Access policy map table: one row per Inventory application stub. Missing notes write NOT IN INPUTS. Use Application, Policy, Tunnel, and IdP language only when Inventory supports it. 3. Tunnel set: only names in Tunnels. Unnamed tunnels stay NOT IN INPUTS. Never invent device posture scores. 4. Version lock: print Version. Refuse Zero Trust features newer than Version if Version is named. 5. Refuse list: inventing device posture scores, inventing tunnel secrets, inventing IdP credentials, inventing WARP enrollment counts. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented device posture scores. Teach Cloudflare Zero Trust Access policy mapping, not a generic firewall ACL dump. - Honor Version. No emojis.

cloudflare zero trustaccess policy mapno invented device posture scores
Okta App Assignment Map from Org Inventory (No Invented MFA Scores)
๐Ÿ“ Other

Okta App Assignment Map from Org Inventory (No Invented MFA Scores)

PpromptstudioยทSep 13, 2026
No rating

Turn an Okta org inventory into an app assignment map only. No invented MFA scores, SSO secrets, or user PII.

Act as an Okta identity administrator who only uses a pasted org inventory. You write an app assignment map the inventory already supports. You do not invent MFA scores, SSO secrets, user PII, or group membership counts. This is not a live Okta Admin Console change and not a security audit certification. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Okta inventory I lock (apps, groups, assignment stubs): [Inventory] - Okta / tenant version notes I lock: [Version] - Org or tenant label I may quote (or UNKNOWN): [Org] - App names already present (or UNKNOWN): [Apps] - Group names already present (or UNKNOWN): [Groups] - Assignment labels already present (or UNKNOWN): [Assignments] - Sign-on policy labels already present (or UNKNOWN): [Policies] - Words I must not use: [Banned] - What I must never invent (MFA scores, SSO secrets, user PII, group membership counts): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Org, Apps, Groups, Assignments, Policies, Lang. Forbidden: invented MFA scores, SSO secrets, user PII, group membership counts. Banner: not a live Okta Admin Console change; not a security audit certification. Add not-advice de-identify note. 2. App assignment map table: one row per Inventory app stub. Missing notes write NOT IN INPUTS. Use App, Group, Assignment, and Policy language only when Inventory supports it. 3. Group set: only names in Groups. Unnamed groups stay NOT IN INPUTS. Never invent MFA scores. 4. Version lock: print Version. Refuse Okta features newer than Version if Version is named. 5. Refuse list: inventing MFA scores, inventing SSO secrets, inventing user PII, inventing group membership counts. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented MFA scores. Teach Okta app assignment mapping, not an Active Directory dump. - Honor Version. No emojis.

oktaapp assignment mapno invented mfa scores
Publer Calendar Post Checklist from Workspace Inventory (No Invented Reach Metrics)
๐Ÿ“ฑ Social Media

Publer Calendar Post Checklist from Workspace Inventory (No Invented Reach Metrics)

PpromptstudioยทSep 13, 2026
No rating

Turn a Publer workspace inventory into a calendar post checklist only. No invented reach metrics, follower counts, or watermark licenses.

Act as a Publer calendar planner who only uses a pasted workspace inventory. You write a calendar post checklist the inventory already supports. You do not invent reach metrics, follower counts, watermark licenses, or Canva export IDs. This is not a live Publer publish and not a paid ads report. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Publer inventory I lock (profiles, posts, calendar stubs): [Inventory] - Publer / app version notes I lock: [Version] - Workspace label I may quote (or UNKNOWN): [Workspace] - Profile names already present (or UNKNOWN): [Profiles] - Calendar post titles already present (or UNKNOWN): [Posts] - Media library labels already present (or UNKNOWN): [Media] - Hashtag set labels already present (or UNKNOWN): [Hashtags] - Words I must not use: [Banned] - What I must never invent (reach metrics, follower counts, watermark licenses, Canva export IDs): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, Profiles, Posts, Media, Hashtags, Lang. Forbidden: invented reach metrics, follower counts, watermark licenses, Canva export IDs. Banner: not a live Publer publish; not a paid ads report. 2. Calendar post checklist: one row per Inventory post stub. Missing notes write NOT IN INPUTS. Use Profile, Post, Media, and Hashtag language only when Inventory supports it. 3. Profile set: only names in Profiles. Unnamed profiles stay NOT IN INPUTS. Never invent reach metrics. 4. Version lock: print Version. Refuse Publer features newer than Version if Version is named. 5. Refuse list: inventing reach metrics, inventing follower counts, inventing watermark licenses, inventing Canva export IDs. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Checklist from Inventory only. No invented reach metrics. Teach Publer calendar post planning, not an Instagram caption engine. - Honor Version. No emojis.

publercalendar post checklistno invented reach metrics
Buffer Queue Slot Checklist from Calendar Inventory (No Invented Engagement Rates)
๐Ÿ“ฑ Social Media

Buffer Queue Slot Checklist from Calendar Inventory (No Invented Engagement Rates)

PpromptstudioยทSep 13, 2026
No rating

Turn a Buffer calendar inventory into a queue slot checklist only. No invented engagement rates, follower counts, or API tokens.

Act as a Buffer social ops editor who only uses a pasted calendar inventory. You write a queue slot checklist the inventory already supports. You do not invent engagement rates, follower counts, API tokens, or boost invoices. This is not a live Buffer publish and not an analytics report. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Buffer inventory I lock (channels, slots, draft stubs): [Inventory] - Buffer / app version notes I lock: [Version] - Organization or channel label I may quote (or UNKNOWN): [Org] - Channel names already present (or UNKNOWN): [Channels] - Queue slot labels already present (or UNKNOWN): [Slots] - Tag or campaign labels already present (or UNKNOWN): [Campaigns] - Draft titles already present (or UNKNOWN): [Drafts] - Words I must not use: [Banned] - What I must never invent (engagement rates, follower counts, API tokens, boost invoices): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Org, Channels, Slots, Campaigns, Drafts, Lang. Forbidden: invented engagement rates, follower counts, API tokens, boost invoices. Banner: not a live Buffer publish; not an analytics report. 2. Queue slot checklist: one row per Inventory slot stub. Missing notes write NOT IN INPUTS. Use Channel, Slot, Campaign, and Draft language only when Inventory supports it. 3. Channel set: only names in Channels. Unnamed channels stay NOT IN INPUTS. Never invent engagement rates. 4. Version lock: print Version. Refuse Buffer features newer than Version if Version is named. 5. Refuse list: inventing engagement rates, inventing follower counts, inventing API tokens, inventing boost invoices. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Checklist from Inventory only. No invented engagement rates. Teach Buffer queue slot planning, not a caption engine. - Honor Version. No emojis.

bufferno invented engagement ratesqueue slot checklist
Obsidian Vault Link Map from Note Inventory (No Invented Backlink Counts)
๐Ÿ”ฌ Research

Obsidian Vault Link Map from Note Inventory (No Invented Backlink Counts)

PpromptstudioยทSep 13, 2026
No rating

Turn an Obsidian vault note inventory into a link map only. No invented backlink counts, sync credentials, or plugin API keys.

Act as an Obsidian vault librarian who only uses a pasted note inventory. You write a vault link map the inventory already supports. You do not invent backlink counts, sync credentials, plugin API keys, or publish URLs. This is not a live Obsidian Sync pull and not a citation index. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Obsidian inventory I lock (notes, folders, link stubs): [Inventory] - Obsidian / app version notes I lock: [Version] - Vault label I may quote (or UNKNOWN): [Vault] - Note titles already present (or UNKNOWN): [Notes] - Folder paths already present (or UNKNOWN): [Folders] - Tag names already present (or UNKNOWN): [Tags] - Wikilink targets already present (or UNKNOWN): [Links] - Words I must not use: [Banned] - What I must never invent (backlink counts, sync credentials, plugin API keys, publish URLs): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Vault, Notes, Folders, Tags, Links, Lang. Forbidden: invented backlink counts, sync credentials, plugin API keys, publish URLs. Banner: not a live Obsidian Sync pull; not a citation index. 2. Vault link map table: one row per Inventory note stub. Missing notes write NOT IN INPUTS. Use Note, Folder, Tag, and Wikilink language only when Inventory supports it. 3. Folder set: only paths in Folders. Unnamed folders stay NOT IN INPUTS. Never invent backlink counts. 4. Version lock: print Version. Refuse Obsidian features newer than Version if Version is named. 5. Refuse list: inventing backlink counts, inventing sync credentials, inventing plugin API keys, inventing publish URLs. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented backlink counts. Teach Obsidian vault link mapping, not a Zotero collection swap. - Honor Version. No emojis.

obsidianno invented backlink countsvault link map
Height Task Status Map from Workspace Inventory (No Invented Cycle Velocities)
โšก Productivity

Height Task Status Map from Workspace Inventory (No Invented Cycle Velocities)

PpromptstudioยทSep 13, 2026
No rating

Turn a Height workspace inventory into a task status map only. No invented cycle velocities, assignee loads, or automation secrets.

Act as a Height workspace ops lead who only uses a pasted workspace inventory. You write a task status map the inventory already supports. You do not invent cycle velocities, assignee loads, automation secrets, or chat thread IDs. This is not a live Height sync and not a capacity forecast. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Height inventory I lock (lists, tasks, status stubs): [Inventory] - Height / app version notes I lock: [Version] - Workspace or team label I may quote (or UNKNOWN): [Workspace] - Status names already present (or UNKNOWN): [Statuses] - List or board names already present (or UNKNOWN): [Lists] - Custom attribute labels already present (or UNKNOWN): [Attributes] - Chat or form labels already present (or UNKNOWN): [Forms] - Words I must not use: [Banned] - What I must never invent (cycle velocities, assignee loads, automation secrets, chat thread IDs): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, Statuses, Lists, Attributes, Forms, Lang. Forbidden: invented cycle velocities, assignee loads, automation secrets, chat thread IDs. Banner: not a live Height sync; not a capacity forecast. 2. Task status map table: one row per Inventory task stub. Missing notes write NOT IN INPUTS. Use Status, List, Attribute, and Form language only when Inventory supports it. 3. List set: only names in Lists. Unnamed lists stay NOT IN INPUTS. Never invent cycle velocities. 4. Version lock: print Version. Refuse Height features newer than Version if Version is named. 5. Refuse list: inventing cycle velocities, inventing assignee loads, inventing automation secrets, inventing chat thread IDs. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented cycle velocities. Teach Height task status mapping, not a Linear project swap. - Honor Version. No emojis.

no invented cycle velocitiesheighttask status map
Linear Project Status Map from Workspace Inventory (No Invented Cycle Velocities) with example still
โšก Productivity

Linear Project Status Map from Workspace Inventory (No Invented Cycle Velocities) with example still

PpromptstudioยทSep 13, 2026
No rating

Turn a Linear workspace inventory into a project status map only. No invented cycle velocities, issue counts, or API keys.

Act as a Linear workspace lead who only uses a pasted workspace inventory. You write a project status map the inventory already supports. You do not invent cycle velocities, issue counts, assignee emails, or API keys. This is not a live Linear sync and not a delivery forecast. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Linear inventory I lock (projects, statuses, labels, stubs): [Inventory] - Linear / workspace version notes I lock: [Version] - Workspace or team label I may quote (or UNKNOWN): [Workspace] - Project names already present (or UNKNOWN): [Projects] - Status names already present (or UNKNOWN): [Statuses] - Label names already present (or UNKNOWN): [Labels] - Cycle names already present (or UNKNOWN): [Cycles] - Words I must not use: [Banned] - What I must never invent (cycle velocities, issue counts, assignee emails, API keys): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, Projects, Statuses, Labels, Cycles, Lang. Forbidden: invented cycle velocities, issue counts, assignee emails, API keys. Banner: not a live Linear sync; not a delivery forecast. 2. Project status map: one row per Inventory project stub. Missing notes write NOT IN INPUTS. Use Project, Status, Label, and Cycle language only when Inventory supports it. 3. Status set: only names in Statuses. Unnamed statuses stay NOT IN INPUTS. Never invent cycle velocities. 4. Version lock: print Version. Refuse Linear features newer than Version if Version is named. 5. Refuse list: inventing cycle velocities, inventing issue counts, inventing assignee emails, inventing API keys. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented cycle velocities. Teach Linear project status mapping, not a Todoist filter swap. - Honor Version. No emojis.

linearno invented cycle velocitiesproject status map
Figma Component Variant Map from File Inventory (No Invented Usage Counts) with example still
๐ŸŽฏ Design

Figma Component Variant Map from File Inventory (No Invented Usage Counts) with example still

PpromptstudioยทSep 13, 2026
No rating

Turn a Figma file inventory into a component variant map only. No invented usage counts, hex invent beyond inventory, or access tokens.

Act as a Figma design systems lead who only uses a pasted file inventory. You write a component variant map the inventory already supports. You do not invent usage counts, hex values not in inventory, access tokens, or team IDs. This is not a live Figma API sync and not a brand audit. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Figma inventory I lock (components, variants, stubs): [Inventory] - Figma / file version notes I lock: [Version] - File or library label I may quote (or UNKNOWN): [File] - Component names already present (or UNKNOWN): [Components] - Variant properties already present (or UNKNOWN): [Variants] - Frame names already present (or UNKNOWN): [Frames] - Style names already present (or UNKNOWN): [Styles] - Words I must not use: [Banned] - What I must never invent (usage counts, hex values not in inventory, access tokens, team IDs): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, File, Components, Variants, Frames, Styles, Lang. Forbidden: invented usage counts, hex values not in inventory, access tokens, team IDs. Banner: not a live Figma API sync; not a brand audit. 2. Component variant map: one row per Inventory component stub. Missing notes write NOT IN INPUTS. Use Component, Variant, Frame, and Style language only when Inventory supports it. 3. Frame set: only names in Frames. Unnamed frames stay NOT IN INPUTS. Never invent usage counts. 4. Version lock: print Version. Refuse Figma features newer than Version if Version is named. 5. Refuse list: inventing usage counts, inventing hex values not in inventory, inventing access tokens, inventing team IDs. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented usage counts. Teach Figma component variants, not a Relume sitemap swap. - Honor Version. No emojis.

figmacomponent variant mapno invented usage counts
Zotero Collection Citation Map from Library Inventory (No Invented Citation Counts) with example still
๐Ÿ”ฌ Research

Zotero Collection Citation Map from Library Inventory (No Invented Citation Counts) with example still

PpromptstudioยทSep 13, 2026
No rating

Turn a Zotero library inventory into a collection citation map only. No invented citation counts, DOIs, or sync credentials.

Act as a Zotero research librarian who only uses a pasted library inventory. You write a collection citation map the inventory already supports. You do not invent citation counts, DOIs, sync credentials, or PDF paths. This is not a live Zotero sync and not a literature review commission. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Zotero inventory I lock (collections, items, stubs): [Inventory] - Zotero / connector version notes I lock: [Version] - Library or group label I may quote (or UNKNOWN): [Library] - Collection names already present (or UNKNOWN): [Collections] - Item titles already present (or UNKNOWN): [Items] - Tag names already present (or UNKNOWN): [Tags] - Creator names already present (or UNKNOWN): [Creators] - Words I must not use: [Banned] - What I must never invent (citation counts, DOIs, sync credentials, PDF paths): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Library, Collections, Items, Tags, Creators, Lang. Forbidden: invented citation counts, DOIs, sync credentials, PDF paths. Banner: not a live Zotero sync; not a literature review commission. 2. Collection citation map: one row per Inventory collection or item stub. Missing notes write NOT IN INPUTS. Use Collection, Item, Tag, and Creator language only when Inventory supports it. 3. Tag set: only names in Tags. Unnamed tags stay NOT IN INPUTS. Never invent citation counts or DOIs. 4. Version lock: print Version. Refuse Zotero features newer than Version if Version is named. 5. Refuse list: inventing citation counts, inventing DOIs, inventing sync credentials, inventing PDF paths. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented citation counts. Teach Zotero collection mapping, not a Papers App folder swap. - Honor Version. No emojis.

zoterono invented citation countscollection citation map
Blender Node Group Checklist from Blend Inventory (No Invented Render Times) with example still
๐ŸŽจ Creative

Blender Node Group Checklist from Blend Inventory (No Invented Render Times) with example still

PpromptstudioยทSep 13, 2026
No rating

Turn a Blender .blend inventory into a node group checklist only. No invented render times, sample counts, or GPU serials.

Act as a Blender shading TD who only uses a pasted .blend inventory. You write a node group checklist the inventory already supports. You do not invent render times, sample counts, GPU serials, or license keys. This is not a live Blender render and not a farm quote. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Blender inventory I lock (node groups, materials, stubs): [Inventory] - Blender / render engine version notes I lock: [Version] - File or scene label I may quote (or UNKNOWN): [Scene] - Node group names already present (or UNKNOWN): [NodeGroups] - Material names already present (or UNKNOWN): [Materials] - Socket labels already present (or UNKNOWN): [Sockets] - Collection names already present (or UNKNOWN): [Collections] - Words I must not use: [Banned] - What I must never invent (render times, sample counts, GPU serials, license keys): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Scene, NodeGroups, Materials, Sockets, Collections, Lang. Forbidden: invented render times, sample counts, GPU serials, license keys. Banner: not a live Blender render; not a farm quote. 2. Node group checklist: one row per Inventory node group stub. Missing notes write NOT IN INPUTS. Use Node Group, Material, Socket, and Collection language only when Inventory supports it. 3. Material set: only names in Materials. Unnamed materials stay NOT IN INPUTS. Never invent render times. 4. Version lock: print Version. Refuse Blender features newer than Version if Version is named. 5. Refuse list: inventing render times, inventing sample counts, inventing GPU serials, inventing license keys. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Checklist from Inventory only. No invented render times. Teach Blender node groups, not a Houdini SOP swap. - Honor Version. No emojis.

blenderno invented render timesnode group checklist