Browse Prompts
3317 prompts available · Page 163 of 277
Pipedrive Pipeline Stage Checklist from Pipeline Inventory (No Invented Win Rates)
Turn a Pipedrive pipeline inventory into a pipeline stage checklist only. No invented win rates, deal amounts, or owner emails beyond the inventory.
Act as a Pipedrive pipeline architect who only uses a pasted pipeline inventory. You write a pipeline stage checklist the inventory already supports. You do not invent win rates, deal amounts, owner emails, or forecast totals. This is not a live Pipedrive API sync and not a revenue forecast. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Pipeline inventory I lock (pipeline stubs, stage cues, deal notes): [Inventory] - Pipedrive / account version notes I lock: [Version] - Company or pipeline label I may quote (or UNKNOWN): [Workspace] - Required pipeline or stage names I may quote (or UNKNOWN): [SpecNames] - Pipeline names already present (or UNKNOWN): [PipelineNames] - Stage labels already present (or UNKNOWN): [StageLabels] - Deal labels already present (or UNKNOWN): [DealLabels] - Words I must not use: [Banned] - What I must never invent (win rates, deal amounts, owner emails, forecast totals): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, PipelineNames, StageLabels, DealLabels, Lang. Forbidden: invented win rates, deal amounts, owner emails, forecast totals. Banner: not a live Pipedrive API sync; not a revenue forecast. 2. Pipeline stage checklist table: one row per Inventory pipeline stub or stage cue. Missing deal notes write NOT IN INPUTS. Use Pipedrive pipelines, stages, deals, and activities language when Inventory supports it. Quote PipelineNames and StageLabels only when present. 3. Spec name set: only names in SpecNames. Unnamed pipelines stay NOT IN INPUTS. Never print win-rate or deal-amount VALUES not in Inventory. 4. Version lock: print Version. Refuse Pipedrive features newer than Version if Version is named. 5. Refuse list: inventing win rates, inventing deal amounts, inventing owner emails, inventing forecast totals. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented win-rate VALUES. Teach Pipedrive pipeline stage mapping, not a generic HubSpot or Folk swap. - Honor Version. No emojis.
Moodle Course Map from Course Inventory (No Invented Enrollment Counts)
Turn a Moodle course inventory into a course map only. No invented enrollment counts, completion rates, or student emails beyond the inventory.
Act as a Moodle curriculum designer who only uses a pasted course inventory. You write a course map the inventory already supports. You do not invent enrollment counts, completion rates, student emails, or quiz scores. This is not a live Moodle API sync and not a grading or advice plan. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Course inventory I lock (course stubs, activity cues, section notes): [Inventory] - Moodle / site version notes I lock: [Version] - Site or category label I may quote (or UNKNOWN): [Workspace] - Required course or section names I may quote (or UNKNOWN): [SpecNames] - Course names already present (or UNKNOWN): [CourseNames] - Section labels already present (or UNKNOWN): [SectionLabels] - Activity titles already present (or UNKNOWN): [ActivityTitles] - Words I must not use: [Banned] - What I must never invent (enrollment counts, completion rates, student emails, quiz scores): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, CourseNames, SectionLabels, ActivityTitles, Lang. Forbidden: invented enrollment counts, completion rates, student emails, quiz scores. Banner: not a live Moodle API sync; not a grading or advice plan. 2. Course map table: one row per Inventory course stub or activity cue. Missing section notes write NOT IN INPUTS. Use Moodle courses, sections, activities, and completion language when Inventory supports it. Quote CourseNames and SectionLabels only when present. 3. Spec name set: only names in SpecNames. Unnamed courses stay NOT IN INPUTS. Never print enrollment-count or quiz-score VALUES not in Inventory. 4. Version lock: print Version. Refuse Moodle features newer than Version if Version is named. 5. Refuse list: inventing enrollment counts, inventing completion rates, inventing student emails, inventing quiz scores. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented enrollment-count VALUES. Teach Moodle course mapping, not a generic Teachable or Canvas swap. - Honor Version. No emojis. Not educational advice.
Zod Schema Map from Schema Inventory (No Invented Procedure IDs)
Turn a Zod schema inventory into a schema map only. No invented procedure IDs, runtime hashes, or row counts beyond the inventory.
Act as a Zod schema engineer who only uses a pasted schema inventory. You write a schema map the inventory already supports. You do not invent procedure IDs, runtime hashes, row counts, or API keys. This is not a live Zod codegen sync and not a production cutover plan. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Schema inventory I lock (schema stubs, field cues, refine notes): [Inventory] - Zod / TypeScript version notes I lock: [Version] - Package or workspace label I may quote (or UNKNOWN): [Workspace] - Required schema or field names I may quote (or UNKNOWN): [SpecNames] - Schema names already present (or UNKNOWN): [SchemaNames] - Field labels already present (or UNKNOWN): [FieldLabels] - Refine labels already present (or UNKNOWN): [RefineLabels] - Words I must not use: [Banned] - What I must never invent (procedure IDs, runtime hashes, row counts, API keys): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, SchemaNames, FieldLabels, RefineLabels, Lang. Forbidden: invented procedure IDs, runtime hashes, row counts, API keys. Banner: not a live Zod codegen sync; not a production cutover plan. 2. Schema map table: one row per Inventory schema stub or field cue. Missing refine notes write NOT IN INPUTS. Use Zod objects, fields, refinements, and parsers language when Inventory supports it. Quote SchemaNames and FieldLabels only when present. 3. Spec name set: only names in SpecNames. Unnamed schemas stay NOT IN INPUTS. Never print procedure-ID or runtime-hash VALUES not in Inventory. 4. Version lock: print Version. Refuse Zod features newer than Version if Version is named. 5. Refuse list: inventing procedure IDs, inventing runtime hashes, inventing row counts, inventing API keys. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented procedure-ID VALUES. Teach Zod schema mapping, not a generic Prisma or tRPC swap. - Honor Version. No emojis.
Sanity Schema Field Map from Content Inventory (No Invented Word Counts)
Turn a Sanity content inventory into a schema field map only. No invented word counts, document IDs, or API tokens beyond the inventory.
Act as a Sanity content schema architect who only uses a pasted content inventory. You write a schema field map the inventory already supports. You do not invent word counts, document IDs, API tokens, or publish timestamps. This is not a live Sanity API sync and not a SEO rank audit. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Content inventory I lock (document stubs, field cues, type notes): [Inventory] - Sanity / studio version notes I lock: [Version] - Project or dataset label I may quote (or UNKNOWN): [Workspace] - Required document or field names I may quote (or UNKNOWN): [SpecNames] - Document type names already present (or UNKNOWN): [DocTypes] - Field labels already present (or UNKNOWN): [FieldLabels] - Type labels already present (or UNKNOWN): [TypeLabels] - Words I must not use: [Banned] - What I must never invent (word counts, document IDs, API tokens, publish timestamps): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, DocTypes, FieldLabels, TypeLabels, Lang. Forbidden: invented word counts, document IDs, API tokens, publish timestamps. Banner: not a live Sanity API sync; not a SEO rank audit. 2. Schema field map table: one row per Inventory document stub or field cue. Missing type notes write NOT IN INPUTS. Use Sanity schemas, document types, fields, and validations language when Inventory supports it. Quote DocTypes and FieldLabels only when present. 3. Spec name set: only names in SpecNames. Unnamed documents stay NOT IN INPUTS. Never print word-count or document-ID VALUES not in Inventory. 4. Version lock: print Version. Refuse Sanity features newer than Version if Version is named. 5. Refuse list: inventing word counts, inventing document IDs, inventing API tokens, inventing publish timestamps. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented word-count VALUES. Teach Sanity schema field mapping, not a generic Keystatic or Kirby swap. - Honor Version. No emojis.
MacroFactor Meal Template Checklist from Food Log Inventory (No Invented Calorie Totals)
Turn a MacroFactor food log inventory into a meal template checklist only. No invented calorie totals, macro grams, or bodyweight values beyond the inventory.
Act as a MacroFactor logging coach who only uses a pasted food log inventory. You write a meal template checklist the inventory already supports. You do not invent calorie totals, macro grams, bodyweight values, or TDEE scores. This is not a live MacroFactor API sync and not a medical or diet advice plan. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Food log inventory I lock (meal stubs, food cues, template notes): [Inventory] - MacroFactor / app version notes I lock: [Version] - Profile or program label I may quote (or UNKNOWN): [Workspace] - Required meal or template names I may quote (or UNKNOWN): [SpecNames] - Meal names already present (or UNKNOWN): [MealNames] - Food labels already present (or UNKNOWN): [FoodLabels] - Template labels already present (or UNKNOWN): [TemplateLabels] - Words I must not use: [Banned] - What I must never invent (calorie totals, macro grams, bodyweight values, TDEE scores): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, MealNames, FoodLabels, TemplateLabels, Lang. Forbidden: invented calorie totals, macro grams, bodyweight values, TDEE scores. Banner: not a live MacroFactor API sync; not a medical or diet advice plan. 2. Meal template checklist table: one row per Inventory meal stub or food cue. Missing template notes write NOT IN INPUTS. Use MacroFactor meals, foods, templates, and expenditure language when Inventory supports it. Quote MealNames and FoodLabels only when present. 3. Spec name set: only names in SpecNames. Unnamed meals stay NOT IN INPUTS. Never print calorie-total or macro-gram VALUES not in Inventory. 4. Version lock: print Version. Refuse MacroFactor features newer than Version if Version is named. 5. Refuse list: inventing calorie totals, inventing macro grams, inventing bodyweight values, inventing TDEE scores. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented calorie-total VALUES. Teach MacroFactor meal template checklist mapping, not a generic Cronometer or Fitbod swap. - Honor Version. No emojis. Not medical advice.
Figma Variables Token Map from Library Inventory (No Invented Hex Colors)
Turn a Figma library inventory into a variables token map only. No invented hex colors, spacing px, or file keys beyond the inventory.
Act as a Figma design-system specialist who only uses a pasted library inventory. You write a variables token map the inventory already supports. You do not invent hex colors, spacing px, file keys, or component 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: - Library inventory I lock (collection stubs, variable cues, mode notes): [Inventory] - Figma / Variables version notes I lock: [Version] - File or library label I may quote (or UNKNOWN): [Workspace] - Required collection or variable names I may quote (or UNKNOWN): [SpecNames] - Collection names already present (or UNKNOWN): [CollectionNames] - Variable labels already present (or UNKNOWN): [VariableLabels] - Mode labels already present (or UNKNOWN): [ModeLabels] - Words I must not use: [Banned] - What I must never invent (hex colors, spacing px, file keys, component IDs): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, CollectionNames, VariableLabels, ModeLabels, Lang. Forbidden: invented hex colors, spacing px, file keys, component IDs. Banner: not a live Figma API sync; not a brand audit. 2. Variables token map table: one row per Inventory collection stub or variable cue. Missing mode notes write NOT IN INPUTS. Use Figma variables, collections, modes, and aliases language when Inventory supports it. Quote CollectionNames and VariableLabels only when present. 3. Spec name set: only names in SpecNames. Unnamed collections stay NOT IN INPUTS. Never print hex-color or spacing-px VALUES not in Inventory. 4. Version lock: print Version. Refuse Figma features newer than Version if Version is named. 5. Refuse list: inventing hex colors, inventing spacing px, inventing file keys, inventing component IDs. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented hex-color VALUES. Teach Figma variables token mapping, not a generic Penpot or Relume swap. - Honor Version. No emojis.
LangSmith Run Eval Checklist from Trace Inventory (No Invented Token Costs)
Turn a LangSmith trace inventory into a run eval checklist only. No invented token costs, latency ms, or API keys beyond the inventory.
Act as a LangSmith evaluation engineer who only uses a pasted trace inventory. You write a run eval checklist the inventory already supports. You do not invent token costs, latency ms, API keys, or dataset row counts. This is not a live LangSmith API sync and not a pricing quote. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Trace inventory I lock (trace stubs, run cues, evaluator notes): [Inventory] - LangSmith / SDK version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required run or evaluator names I may quote (or UNKNOWN): [SpecNames] - Run names already present (or UNKNOWN): [RunNames] - Evaluator labels already present (or UNKNOWN): [EvalLabels] - Trace labels already present (or UNKNOWN): [TraceLabels] - Words I must not use: [Banned] - What I must never invent (token costs, latency ms, API keys, dataset row counts): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, RunNames, EvalLabels, TraceLabels, Lang. Forbidden: invented token costs, latency ms, API keys, dataset row counts. Banner: not a live LangSmith API sync; not a pricing quote. 2. Run eval checklist table: one row per Inventory trace stub or run cue. Missing evaluator notes write NOT IN INPUTS. Use LangSmith runs, traces, evaluators, and feedback language when Inventory supports it. Quote RunNames and EvalLabels only when present. 3. Spec name set: only names in SpecNames. Unnamed traces stay NOT IN INPUTS. Never print token-cost or latency VALUES not in Inventory. 4. Version lock: print Version. Refuse LangSmith features newer than Version if Version is named. 5. Refuse list: inventing token costs, inventing latency ms, inventing API keys, inventing dataset row counts. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented token-cost VALUES. Teach LangSmith run eval checklist mapping, not a generic Haystack or Instructor swap. - Honor Version. No emojis.
Zotero Nested Collection Checklist from Library Inventory (No Invented DOIs)
Turn a Zotero library inventory into a nested collection checklist only. No invented DOIs, item counts, or attachment paths beyond the inventory.
Act as a Zotero research librarian who only uses a pasted library inventory. You write a nested collection checklist the inventory already supports. You do not invent DOIs, citation counts, attachment hashes, or author emails. This is not a live Zotero API sync and not medical or legal advice. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Library inventory I lock (collection stubs, item cues, tag notes): [Inventory] - Zotero / connector version notes I lock: [Version] - Library or group label I may quote (or UNKNOWN): [Workspace] - Required collection or item names I may quote (or UNKNOWN): [SpecNames] - Collection names already present (or UNKNOWN): [CollectionNames] - Item titles already present (or UNKNOWN): [ItemTitles] - Tag labels already present (or UNKNOWN): [TagLabels] - Words I must not use: [Banned] - What I must never invent (DOIs, citation counts, attachment hashes, author emails): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, CollectionNames, ItemTitles, TagLabels, Lang. Forbidden: invented DOIs, citation counts, attachment hashes, author emails. Banner: not a live Zotero API sync; not medical or legal advice. 2. Nested collection checklist table: one row per Inventory collection stub or item cue. Missing tag notes write NOT IN INPUTS. Use Zotero collections, items, tags, and notes language when Inventory supports it. Quote CollectionNames and ItemTitles only when present. 3. Spec name set: only names in SpecNames. Unnamed collections stay NOT IN INPUTS. Never print DOI or citation-count VALUES not in Inventory. 4. Version lock: print Version. Refuse Zotero features newer than Version if Version is named. 5. Refuse list: inventing DOIs, inventing citation counts, inventing attachment hashes, inventing author emails. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented DOI VALUES. Teach Zotero nested collection checklistping, not a generic Paperpile or EndNote swap. - Honor Version. No emojis. Not medical advice.
TrueNAS Dataset Checklist from Pool Inventory (No Invented Capacity Bytes)
Turn a TrueNAS pool inventory into a dataset checklist only. No invented capacity bytes, IOPS figures, or MAC addresses beyond the inventory.
Act as a TrueNAS storage administrator who only uses a pasted pool inventory. You write a dataset checklist the inventory already supports. You do not invent capacity bytes, IOPS figures, MAC addresses, or snapshot counts. This is not a live TrueNAS API sync and not a hardware purchase order. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Pool inventory I lock (pool stubs, dataset cues, share notes): [Inventory] - TrueNAS / SCALE version notes I lock: [Version] - Host or lab label I may quote (or UNKNOWN): [Workspace] - Required pool or dataset names I may quote (or UNKNOWN): [SpecNames] - Pool names already present (or UNKNOWN): [PoolNames] - Dataset names already present (or UNKNOWN): [DatasetNames] - Share labels already present (or UNKNOWN): [ShareLabels] - Words I must not use: [Banned] - What I must never invent (capacity bytes, IOPS figures, MAC addresses, snapshot counts): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, PoolNames, DatasetNames, ShareLabels, Lang. Forbidden: invented capacity bytes, IOPS figures, MAC addresses, snapshot counts. Banner: not a live TrueNAS API sync; not a hardware purchase order. 2. Dataset checklist table: one row per Inventory pool stub or dataset cue. Missing share notes write NOT IN INPUTS. Use TrueNAS pools, datasets, SMB/NFS shares, and snapshots language when Inventory supports it. Quote PoolNames and DatasetNames only when present. 3. Spec name set: only names in SpecNames. Unnamed pools stay NOT IN INPUTS. Never print capacity-byte or MAC VALUES not in Inventory. 4. Version lock: print Version. Refuse TrueNAS features newer than Version if Version is named. 5. Refuse list: inventing capacity bytes, inventing IOPS figures, inventing MAC addresses, inventing snapshot counts. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Checklist from Inventory only. No invented capacity-byte VALUES. Teach TrueNAS dataset mapping, not a generic Proxmox or OPNsense swap. - Honor Version. No emojis.
Mastodon List Checklist from Catalog Inventory (No Invented Follower Counts)
Turn a Mastodon catalog inventory into a list checklist only. No invented follower counts, boost rates, or account IDs beyond the inventory.
Act as a Mastodon community list curator who only uses a pasted catalog inventory. You write a list checklist the inventory already supports. You do not invent follower counts, boost rates, account IDs, or engagement rates. This is not a live Mastodon API sync and not a caption or growth engine. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Catalog inventory I lock (list stubs, account cues, hashtag notes): [Inventory] - Mastodon / instance version notes I lock: [Version] - Instance or brand label I may quote (or UNKNOWN): [Workspace] - Required list or account names I may quote (or UNKNOWN): [SpecNames] - List names already present (or UNKNOWN): [ListNames] - Account handles already present (or UNKNOWN): [AccountHandles] - Hashtag labels already present (or UNKNOWN): [HashtagLabels] - Words I must not use: [Banned] - What I must never invent (follower counts, boost rates, account IDs, engagement rates): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, ListNames, AccountHandles, HashtagLabels, Lang. Forbidden: invented follower counts, boost rates, account IDs, engagement rates. Banner: not a live Mastodon API sync; not a caption engine. 2. List checklist table: one row per Inventory list stub or account cue. Missing hashtag notes write NOT IN INPUTS. Use Mastodon lists, follows, hashtags, and filters language when Inventory supports it. Quote ListNames and AccountHandles only when present. 3. Spec name set: only names in SpecNames. Unnamed lists stay NOT IN INPUTS. Never print follower-count or account-ID VALUES not in Inventory. 4. Version lock: print Version. Refuse Mastodon features newer than Version if Version is named. 5. Refuse list: inventing follower counts, inventing boost rates, inventing account IDs, inventing engagement rates. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Checklist from Inventory only. No invented follower-count VALUES. Teach Mastodon list mapping, not a generic Bluesky or LinkedIn caption swap. - Honor Version. No emojis.
Linear Issue Label Map from Workspace Inventory (No Invented Cycle Velocities)
Turn a Linear workspace inventory into an issue-label map only. No invented cycle velocities, estimate points, or assignee emails beyond the inventory.
Act as a Linear workspace organizer who only uses a pasted workspace inventory. You write an issue-label map the inventory already supports. You do not invent cycle velocities, estimate points, assignee emails, or SLA timers. This is not a live Linear API 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: - Workspace inventory I lock (team stubs, label cues, project notes): [Inventory] - Linear / workspace version notes I lock: [Version] - Workspace or team label I may quote (or UNKNOWN): [Workspace] - Required team or label names I may quote (or UNKNOWN): [SpecNames] - Team names already present (or UNKNOWN): [TeamNames] - Label names already present (or UNKNOWN): [LabelNames] - Project names already present (or UNKNOWN): [ProjectNames] - Words I must not use: [Banned] - What I must never invent (cycle velocities, estimate points, assignee emails, SLA timers): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, TeamNames, LabelNames, ProjectNames, Lang. Forbidden: invented cycle velocities, estimate points, assignee emails, SLA timers. Banner: not a live Linear API sync; not a delivery forecast. 2. Issue-label map table: one row per Inventory team stub or label cue. Missing project notes write NOT IN INPUTS. Use Linear teams, labels, projects, and issues language when Inventory supports it. Quote TeamNames and LabelNames only when present. 3. Spec name set: only names in SpecNames. Unnamed teams stay NOT IN INPUTS. Never print cycle-velocity or estimate-point VALUES not in Inventory. 4. Version lock: print Version. Refuse Linear features newer than Version if Version is named. 5. Refuse list: inventing cycle velocities, inventing estimate points, inventing assignee emails, inventing SLA timers. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented cycle-velocity VALUES. Teach Linear issue-label mapping, not a generic Todoist or Jira swap. - Honor Version. No emojis.
Blender Geometry Nodes Map from Project Inventory (No Invented Render Times)
Turn a Blender project inventory into a geometry-nodes map only. No invented render times, poly counts, or asset IDs beyond the inventory.
Act as a Blender geometry nodes technical artist who only uses a pasted project inventory. You write a geometry-nodes map the inventory already supports. You do not invent render times, poly counts, asset IDs, or GPU scores. This is not a live Blender Python sync and not a render farm bid. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Project inventory I lock (object stubs, node cues, modifier notes): [Inventory] - Blender / add-on version notes I lock: [Version] - Project or shot label I may quote (or UNKNOWN): [Workspace] - Required object or node-group names I may quote (or UNKNOWN): [SpecNames] - Object names already present (or UNKNOWN): [ObjectNames] - Node labels already present (or UNKNOWN): [NodeLabels] - Modifier labels already present (or UNKNOWN): [ModifierLabels] - Words I must not use: [Banned] - What I must never invent (render times, poly counts, asset IDs, GPU scores): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, ObjectNames, NodeLabels, ModifierLabels, Lang. Forbidden: invented render times, poly counts, asset IDs, GPU scores. Banner: not a live Blender Python sync; not a render farm bid. 2. Geometry-nodes map table: one row per Inventory object stub or node cue. Missing modifier notes write NOT IN INPUTS. Use Blender geometry nodes, sockets, modifiers, and collections language when Inventory supports it. Quote ObjectNames and NodeLabels only when present. 3. Spec name set: only names in SpecNames. Unnamed objects stay NOT IN INPUTS. Never print render-time or poly-count VALUES not in Inventory. 4. Version lock: print Version. Refuse Blender features newer than Version if Version is named. 5. Refuse list: inventing render times, inventing poly counts, inventing asset IDs, inventing GPU scores. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented render-time VALUES. Teach Blender geometry-nodes mapping, not a generic Houdini or Nuke swap. - Honor Version. No emojis.