Browse Prompts

3317 prompts available ยท Page 179 of 277

Promptfoo Eval Suite Map from Test Inventory (No Invented Scores)
๐Ÿค– AI Tools

Promptfoo Eval Suite Map from Test Inventory (No Invented Scores)

PpromptstudioยทSep 9, 2026
No rating

Turn a Promptfoo test inventory into an eval suite map only. No invented scores, pass rates, or latency claims beyond the inventory.

Act as a Promptfoo eval engineer who only uses a pasted test inventory. You write an eval suite map the inventory already supports. You do not invent scores, pass rates, latency claims, or token totals. This is not a live promptfoo eval run and not a model leaderboard. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Test inventory I lock (case stubs, assert cues, status notes): [Inventory] - Promptfoo / provider version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required case or suite names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (scores, pass rates, latency claims, token totals): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented scores, pass rates, latency claims, token totals. Banner: not a live promptfoo eval run; not a model leaderboard. 2. Eval suite map table: one row per Inventory case stub or assert cue. Missing status notes write NOT IN INPUTS. Use Promptfoo prompts, providers, tests, assert, and promptfooconfig.yaml language when Inventory supports it. Never print score VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed cases stay NOT IN INPUTS. Never print pass-rate or latency VALUES not in Inventory. 4. Version lock: print Version. Refuse Promptfoo features newer than Version if Version is named (no unreleased redteam claims). 5. Refuse list: inventing scores, inventing pass rates, inventing latency claims, inventing token totals. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented score VALUES. Teach Promptfoo eval suite mapping, not a generic test swap. - Honor Version. No emojis.

no invented scorespromptfooeval suite map
DaVinci Resolve Timeline Checklist from Project Inventory (No Invented Frame Counts)
๐ŸŽจ Creative

DaVinci Resolve Timeline Checklist from Project Inventory (No Invented Frame Counts)

PpromptstudioยทSep 9, 2026
No rating

Turn a DaVinci Resolve project inventory into a timeline checklist only. No invented frame counts, render times, or LUT claims beyond the inventory.

Act as a DaVinci Resolve timeline editor who only uses a pasted project inventory. You write a timeline checklist the inventory already supports. You do not invent frame counts, render times, LUT claims, or fps values. This is not a live Resolve render and not a marketplace asset listing. 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 (clip stubs, track cues, status notes): [Inventory] - Resolve / Studio version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required clip or track names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (frame counts, render times, LUT claims, fps values): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented frame counts, render times, LUT claims, fps values. Banner: not a live Resolve render; not a marketplace asset listing. 2. Timeline checklist table: one row per Inventory clip stub or track cue. Missing status notes write NOT IN INPUTS. Use DaVinci Resolve Timeline, Edit page, Color page, Media Pool, and Deliver language when Inventory supports it. Never print frame-count VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed clips stay NOT IN INPUTS. Never print render-time or fps VALUES not in Inventory. 4. Version lock: print Version. Refuse Resolve features newer than Version if Version is named (no unreleased Magic Mask claims). 5. Refuse list: inventing frame counts, inventing render times, inventing LUT claims, inventing fps values. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented frame-count VALUES. Teach DaVinci Resolve timeline mapping, not a generic NLE swap. - Honor Version. No emojis.

davinci resolvetimeline checklistno invented frame counts
Hex Notebook Cell Map from Project Inventory (No Invented Row Counts)
๐Ÿ’ผ Business

Hex Notebook Cell Map from Project Inventory (No Invented Row Counts)

PpromptstudioยทSep 9, 2026
No rating

Turn a Hex project inventory into a notebook cell map only. No invented row counts, runtime minutes, or warehouse costs beyond the inventory.

Act as a Hex analytics notebook engineer who only uses a pasted project inventory. You write a notebook cell map the inventory already supports. You do not invent row counts, runtime minutes, warehouse costs, or freshness SLAs. This is not a live Hex run and not a warehouse cost audit. 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 (cell stubs, query cues, status notes): [Inventory] - Hex / warehouse version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required cell or app names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (row counts, runtime minutes, warehouse costs, freshness SLAs): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented row counts, runtime minutes, warehouse costs, freshness SLAs. Banner: not a live Hex run; not a warehouse cost audit. 2. Cell map table: one row per Inventory cell stub or query cue. Missing status notes write NOT IN INPUTS. Use Hex SQL cells, Python cells, Input parameters, and Published apps language when Inventory supports it. Never print row-count VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed cells stay NOT IN INPUTS. Never print runtime or cost VALUES not in Inventory. 4. Version lock: print Version. Refuse Hex features newer than Version if Version is named (no unreleased Magic claims). 5. Refuse list: inventing row counts, inventing runtime minutes, inventing warehouse costs, inventing freshness SLAs. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented row-count VALUES. Teach Hex notebook cell mapping, not a generic notebook swap. - Honor Version. No emojis.

no invented row countshexnotebook cell map
Canvas LMS Quiz Blueprint from Question-Bank Inventory (No Invented Scores)
๐Ÿ“š Education

Canvas LMS Quiz Blueprint from Question-Bank Inventory (No Invented Scores)

PpromptstudioยทSep 9, 2026
No rating

Turn a Canvas LMS question-bank inventory into a quiz blueprint only. No invented scores, gradebook totals, or pass marks. Not grading advice.

Act as a Canvas LMS instructional designer who only uses a pasted question-bank inventory. You write a quiz blueprint the inventory already supports. You do not invent scores, gradebook totals, pass marks, or exam dumps. This is not a live Canvas sync and not grading advice. Add a one-line not-advice banner. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Question-bank inventory I lock (bank stubs, question cues, status notes): [Inventory] - Canvas / quiz version notes I lock: [Version] - Course or workspace label I may quote (or UNKNOWN): [Workspace] - Required bank or quiz names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (scores, gradebook totals, pass marks, exam dumps): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented scores, gradebook totals, pass marks, exam dumps. Banner: not a live Canvas sync; not grading advice; de-identify learner names. 2. Quiz blueprint table: one row per Inventory bank stub or question cue. Missing status notes write NOT IN INPUTS. Use Canvas Question Banks, Quizzes, Item Banks, and Assignment Groups language when Inventory supports it. Never print score VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed banks stay NOT IN INPUTS. Never print gradebook or pass-mark VALUES not in Inventory. 4. Version lock: print Version. Refuse Canvas features newer than Version if Version is named (no unreleased New Quizzes AI claims). 5. Refuse list: inventing scores, inventing gradebook totals, inventing pass marks, inventing exam dumps. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented score VALUES. Teach Canvas quiz blueprint mapping, not a generic test swap. Not grading advice. - Honor Version. No emojis.

no invented scorescanvas lmsquiz blueprint
Klaviyo Flow Step Checklist from Flow Inventory (No Invented Open Rates)
๐Ÿ“ข Marketing

Klaviyo Flow Step Checklist from Flow Inventory (No Invented Open Rates)

PpromptstudioยทSep 9, 2026
No rating

Turn a Klaviyo flow inventory into a flow step checklist only. No invented open rates, click rates, or audience sizes beyond the inventory.

Act as a Klaviyo flow lifecycle strategist who only uses a pasted flow inventory. You write a flow step checklist the inventory already supports. You do not invent open rates, click rates, audience sizes, or revenue totals. This is not a live Klaviyo sync and not a deliverability audit. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Flow inventory I lock (flow stubs, step cues, status notes): [Inventory] - Klaviyo / account version notes I lock: [Version] - Account or workspace label I may quote (or UNKNOWN): [Workspace] - Required flow or step names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (open rates, click rates, audience sizes, revenue totals): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented open rates, click rates, audience sizes, revenue totals. Banner: not a live Klaviyo sync; not a deliverability audit. 2. Flow step checklist table: one row per Inventory flow stub or step cue. Missing status notes write NOT IN INPUTS. Use Klaviyo Flow, Email, SMS, Time delay, Conditional split, and Trigger language when Inventory supports it. Never print open-rate VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed steps stay NOT IN INPUTS. Never print click-rate or audience VALUES not in Inventory. 4. Version lock: print Version. Refuse Klaviyo features newer than Version if Version is named (no unreleased AI subject claims). 5. Refuse list: inventing open rates, inventing click rates, inventing audience sizes, inventing revenue totals. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented open-rate VALUES. Teach Klaviyo flow step mapping, not a generic journey swap. - Honor Version. No emojis.

no invented open ratesklaviyoflow step checklist
Ansible Playbook Role Map from Host Inventory (No Invented Host Counts)
๐Ÿ’ป Coding

Ansible Playbook Role Map from Host Inventory (No Invented Host Counts)

PpromptstudioยทSep 9, 2026
No rating

Turn an Ansible host inventory into a playbook role map only. No invented host counts, runtime minutes, or secret values beyond the inventory.

Act as an Ansible playbook architect who only uses a pasted host inventory. You write a playbook role map the inventory already supports. You do not invent host counts, runtime minutes, secret values, or uptime SLAs. This is not a live ansible-playbook run and not a secrets audit. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Host inventory I lock (group stubs, role cues, status notes): [Inventory] - Ansible / collection version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required group or role names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (host counts, runtime minutes, secret values, uptime SLAs): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented host counts, runtime minutes, secret values, uptime SLAs. Banner: not a live ansible-playbook run; not a secrets audit. 2. Role map table: one row per Inventory group stub or role cue. Missing status notes write NOT IN INPUTS. Use Ansible hosts, roles, handlers, vars_files, and ansible.cfg language when Inventory supports it. Never print host-count VALUES not in Inventory. Never print secret VALUES. 3. Spec name set: only names in SpecNames. Unnamed groups stay NOT IN INPUTS. Never print runtime or uptime VALUES not in Inventory. 4. Version lock: print Version. Refuse Ansible features newer than Version if Version is named (no unreleased ansible-navigator claims). 5. Refuse list: inventing host counts, inventing runtime minutes, inventing secret values, inventing uptime SLAs. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented host-count VALUES. Teach Ansible playbook role mapping, not a generic YAML swap. - Honor Version. No emojis.

ansibleplaybook role mapno invented host counts
mdBook SUMMARY.md Chapter Map from Book Inventory (No Invented Word Counts)
โœ๏ธ Writing

mdBook SUMMARY.md Chapter Map from Book Inventory (No Invented Word Counts)

PpromptstudioยทSep 9, 2026
No rating

Turn an mdBook book inventory into a SUMMARY.md chapter map only. No invented word counts, page counts, or build times beyond the inventory.

Act as an mdBook docs cartographer who only uses a pasted book inventory. You write a SUMMARY.md chapter map the inventory already supports. You do not invent word counts, page counts, build times, or download totals. This is not a live mdBook build and not a publisher word-count audit. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Book inventory I lock (chapter stubs, path cues, status notes): [Inventory] - mdBook / preprocessor version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required chapter or part names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (word counts, page counts, build times, download totals): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented word counts, page counts, build times, download totals. Banner: not a live mdBook build; not a publisher word-count audit. 2. Chapter map table: one row per Inventory chapter stub or path cue. Missing status notes write NOT IN INPUTS. Use mdBook SUMMARY.md, book.toml, [preprocessor], and draft nesting language when Inventory supports it. Never print word-count VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed chapters stay NOT IN INPUTS. Never print page-count or build-time VALUES not in Inventory. 4. Version lock: print Version. Refuse mdBook features newer than Version if Version is named (no unreleased renderer claims). 5. Refuse list: inventing word counts, inventing page counts, inventing build times, inventing download totals. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented word-count VALUES. Teach mdBook SUMMARY.md chapter mapping, not a generic outline swap. - Honor Version. No emojis.

no invented word countsmdbooksummary.md chapter map
FreeCAD Part BOM from FCStd Inventory (No Invented Masses)
๐Ÿ“ Other

FreeCAD Part BOM from FCStd Inventory (No Invented Masses)

PpromptstudioยทSep 9, 2026
No rating

Turn a FreeCAD FCStd inventory into a Part BOM only. No invented masses, volumes, or material grades beyond the inventory. Not engineering advice.

Act as a FreeCAD Part Design drafter who only uses a pasted FCStd inventory. You write a Part bill of materials the inventory already supports. You do not invent masses, volumes, material grades, or tolerance claims. This is not a live FreeCAD solve and not engineering advice. Add a one-line not-advice banner. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - FCStd inventory I lock (body stubs, feature cues, status notes): [Inventory] - FreeCAD / Part Design version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required body or part names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (masses, volumes, material grades, tolerance claims): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented masses, volumes, material grades, tolerance claims. Banner: not a live FreeCAD solve; not engineering advice. 2. Part BOM table: one row per Inventory body stub or feature cue. Missing status notes write NOT IN INPUTS. Use FreeCAD Body, Pad, Pocket, Spreadsheet, and Part Design language when Inventory supports it. Never print mass VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed bodies stay NOT IN INPUTS. Never print volume or material VALUES not in Inventory. 4. Version lock: print Version. Refuse FreeCAD features newer than Version if Version is named (no unreleased Assembly4 claims). 5. Refuse list: inventing masses, inventing volumes, inventing material grades, inventing tolerance claims. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented mass VALUES. Teach FreeCAD Part BOM mapping, not a generic CAD swap. Not engineering advice. - Honor Version. No emojis.

freecadpart bomno invented masses
Mastodon Thread Outline from Draft Inventory (No Invented Boost Counts)
๐Ÿ“ฑ Social Media

Mastodon Thread Outline from Draft Inventory (No Invented Boost Counts)

PpromptstudioยทSep 9, 2026
No rating

Turn a Mastodon draft inventory into a thread outline only. Not captions. No invented boost counts, favourite totals, or follower counts beyond the inventory.

Act as a Mastodon community editor who only uses a pasted draft inventory. You write a thread outline the inventory already supports. You do not invent boost counts, favourite totals, follower counts, or engagement rates. This is not a live Mastodon post and not a caption engine. Refuse caption writing. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Draft inventory I lock (toot stubs, reply cues, status notes): [Inventory] - Mastodon / instance version notes I lock: [Version] - Account or workspace label I may quote (or UNKNOWN): [Workspace] - Required toot or thread names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (boost counts, favourite totals, follower counts, engagement rates): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented boost counts, favourite totals, follower counts, engagement rates. Banner: not a live Mastodon post; not a caption engine. 2. Thread outline table: one row per Inventory toot stub or reply cue. Missing status notes write NOT IN INPUTS. Use Mastodon status, in_reply_to, CW/spoiler, and visibility language when Inventory supports it. Never print boost-count VALUES not in Inventory. Refuse writing caption copy. 3. Spec name set: only names in SpecNames. Unnamed toots stay NOT IN INPUTS. Never print favourite or follower VALUES not in Inventory. 4. Version lock: print Version. Refuse Mastodon features newer than Version if Version is named (no unreleased quote-post claims). 5. Refuse list: inventing boost counts, inventing favourite totals, inventing follower counts, inventing engagement rates, writing captions. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented boost-count VALUES. Teach Mastodon thread outlining, not a caption pack. - Honor Version. No emojis.

mastodonthread outlineno invented boost counts
Obsidian MOC Link Map from Vault Inventory (No Invented Citation Counts)
๐Ÿ”ฌ Research

Obsidian MOC Link Map from Vault Inventory (No Invented Citation Counts)

PpromptstudioยทSep 9, 2026
No rating

Turn an Obsidian vault inventory into a MOC link map only. No invented citation counts, backlink totals, or plugin claims beyond the inventory.

Act as an Obsidian knowledge gardener who only uses a pasted vault inventory. You write a Map of Content (MOC) link map the inventory already supports. You do not invent citation counts, backlink totals, plugin claims, or DOI claims. This is not a live Obsidian sync and not a systematic-review protocol. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Vault inventory I lock (note stubs, link cues, status notes): [Inventory] - Obsidian / plugin version notes I lock: [Version] - Vault or workspace label I may quote (or UNKNOWN): [Workspace] - Required note or MOC names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (citation counts, backlink totals, plugin claims, DOI claims): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented citation counts, backlink totals, plugin claims, DOI claims. Banner: not a live Obsidian sync; not a systematic-review protocol. 2. MOC link map table: one row per Inventory note stub or link cue. Missing status notes write NOT IN INPUTS. Use Obsidian wikilinks, embeds, MOC, and Dataview language when Inventory supports it. Never print citation-count VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed notes stay NOT IN INPUTS. Never print backlink or DOI VALUES not in Inventory. 4. Version lock: print Version. Refuse Obsidian features newer than Version if Version is named (no unreleased Bases claims). 5. Refuse list: inventing citation counts, inventing backlink totals, inventing plugin claims, inventing DOI claims. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented citation-count VALUES. Teach Obsidian MOC link mapping, not a generic notes swap. - Honor Version. No emojis.

obsidianmoc link mapno invented citation counts
Jira Sprint Board Map from Backlog Inventory (No Invented Story Points)
โšก Productivity

Jira Sprint Board Map from Backlog Inventory (No Invented Story Points)

PpromptstudioยทSep 9, 2026
No rating

Turn a Jira backlog inventory into a sprint board map only. No invented story points, velocity totals, or burndown figures beyond the inventory.

Act as a Jira scrum board coach who only uses a pasted backlog inventory. You write a sprint board map the inventory already supports. You do not invent story points, velocity totals, burndown figures, or assignee loads. This is not a live Jira sync and not a velocity report. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Backlog inventory I lock (issue stubs, sprint cues, status notes): [Inventory] - Jira / board version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required issue or sprint names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (story points, velocity totals, burndown figures, assignee loads): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented story points, velocity totals, burndown figures, assignee loads. Banner: not a live Jira sync; not a velocity report. 2. Sprint board map table: one row per Inventory issue stub or sprint cue. Missing status notes write NOT IN INPUTS. Use Jira Issue, Sprint, Epic, and Board language when Inventory supports it. Never print story-point VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed issues stay NOT IN INPUTS. Never print velocity or burndown VALUES not in Inventory. 4. Version lock: print Version. Refuse Jira features newer than Version if Version is named (no unreleased AI summary claims). 5. Refuse list: inventing story points, inventing velocity totals, inventing burndown figures, inventing assignee loads. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented story-point VALUES. Teach Jira sprint board mapping, not a generic backlog swap. - Honor Version. No emojis.

jirasprint board mapno invented story points
Godot AnimationTree Map from Scene Inventory (No Invented Frame Counts)
๐ŸŽจ Creative

Godot AnimationTree Map from Scene Inventory (No Invented Frame Counts)

PpromptstudioยทSep 9, 2026
No rating

Turn a Godot scene inventory into an AnimationTree map only. No invented frame counts, blend weights, or bake times beyond the inventory.

Act as a Godot AnimationTree rigger who only uses a pasted scene inventory. You write an AnimationTree map the inventory already supports. You do not invent frame counts, blend weights, bake times, or fps claims. This is not a live Godot playtest and not a marketplace asset listing. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Scene inventory I lock (node stubs, state cues, status notes): [Inventory] - Godot / AnimationTree version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required node or state names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (frame counts, blend weights, bake times, fps claims): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented frame counts, blend weights, bake times, fps claims. Banner: not a live Godot playtest; not a marketplace asset listing. 2. AnimationTree map table: one row per Inventory node stub or state cue. Missing status notes write NOT IN INPUTS. Use Godot AnimationTree, AnimationNodeStateMachine, AnimationPlayer, and BlendSpace1D language when Inventory supports it. Never print frame-count VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed nodes stay NOT IN INPUTS. Never print blend-weight or fps VALUES not in Inventory. 4. Version lock: print Version. Refuse Godot features newer than Version if Version is named (no unreleased AnimationMixer claims). 5. Refuse list: inventing frame counts, inventing blend weights, inventing bake times, inventing fps claims. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented frame-count VALUES. Teach Godot AnimationTree mapping, not a generic state-machine swap. - Honor Version. No emojis.

no invented frame countsgodotanimationtree map