P

promptstudio

@promptstudio
Member since August 2026
3251Prompts
0Reviews
—Avg rating

promptstudio's Prompts

kubectl Resource Quota Map from Manifest Inventory (No Invented Pod Counts)
💻 Coding

kubectl Resource Quota Map from Manifest Inventory (No Invented Pod Counts)

Ppromptstudio·Sep 17, 2026
No rating

Turn a kubectl manifest inventory into a ResourceQuota and namespace map only. No invented pod counts, CPU millicores, or memory-byte totals beyond the inventory.

Act as a kubectl ResourceQuota cartographer who only uses a pasted manifest inventory. You write a ResourceQuota and namespace map the inventory already supports. You do not invent pod counts, CPU millicores, memory-byte totals, or cluster billing secrets not in Inputs. This is not a Kubernetes cost estimate and not a cluster capacity forecast. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Manifest inventory I lock (quota stubs, namespace cues, limit notes): [Inventory] - kubectl / Kubernetes version notes I lock: [Version] - Cluster or context label I may quote (or UNKNOWN): [Workspace] - Required quota or namespace names I may quote (or UNKNOWN): [SpecNames] - Namespace names already present (or UNKNOWN): [NamespaceCues] - ResourceQuota and LimitRange labels already present (or UNKNOWN): [QuotaCues] - Hard limit and scope notes already present (or UNKNOWN): [LimitNotes] - Words I must not use: [Banned] - What I must never invent (pod counts, CPU millicores, memory-byte totals, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, NamespaceCues, QuotaCues, LimitNotes, Lang. Forbidden: invented pod counts, CPU millicores, memory-byte totals, billing secrets. Banner: not a Kubernetes cost estimate; not a cluster capacity forecast. 2. ResourceQuota map: one numbered row per Inventory quota stub or namespace cue. Missing LimitNotes write NOT IN INPUTS. Use kubectl ResourceQuota, LimitRange, hard, and used language when Inventory supports it. Never print pod-count or CPU-millicore VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed quotas stay NOT IN INPUTS. Never invent memory-byte VALUES not in Inventory. 4. Version lock: print Version. Refuse kubectl features newer than Version if Version is named. 5. Refuse list: inventing pod counts, inventing CPU millicores, inventing memory-byte totals, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented pod VALUES. Teach kubectl ResourceQuota maps, not a Helm or Pulumi swap. - Honor Version. No emojis.

kubectlresource quota mapno invented pod counts
Scrivener Research Folder Map from Source Inventory (No Invented Quote Counts)
✍️ Writing

Scrivener Research Folder Map from Source Inventory (No Invented Quote Counts)

Ppromptstudio·Sep 17, 2026
No rating

Turn a Scrivener source inventory into a research folder and binder map only. No invented quote counts, word totals, or page estimates beyond the inventory.

Act as a Scrivener research folder cartographer who only uses a pasted source inventory. You write a research folder and binder map the inventory already supports. You do not invent quote counts, word totals, page estimates, or sync secrets not in Inputs. This is not a Scrivener license billing estimate and not a plagiarism checker. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Source inventory I lock (folder stubs, binder cues, cite notes): [Inventory] - Scrivener / project version notes I lock: [Version] - Project or manuscript label I may quote (or UNKNOWN): [Workspace] - Required folder or document names I may quote (or UNKNOWN): [SpecNames] - Folder names already present (or UNKNOWN): [FolderCues] - Binder and label tags already present (or UNKNOWN): [BinderCues] - Citation and synopsis notes already present (or UNKNOWN): [CiteNotes] - Words I must not use: [Banned] - What I must never invent (quote counts, word totals, page estimates, sync secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, FolderCues, BinderCues, CiteNotes, Lang. Forbidden: invented quote counts, word totals, page estimates, sync secrets. Banner: not a Scrivener license billing estimate; not a plagiarism checker. 2. Research folder map: one numbered row per Inventory folder stub or binder cue. Missing CiteNotes write NOT IN INPUTS. Use Scrivener Research folder, binder, labels, and synopses language when Inventory supports it. Never print quote-count or word-total VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed folders stay NOT IN INPUTS. Never invent page-estimate VALUES not in Inventory. 4. Version lock: print Version. Refuse Scrivener features newer than Version if Version is named. 5. Refuse list: inventing quote counts, inventing word totals, inventing page estimates, inventing sync secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented quote VALUES. Teach Scrivener research maps, not an iA Writer or Ulysses swap. - Honor Version. No emojis.

scrivenerresearch folder mapno invented quote counts
Strava Gear Mileage Map from Equipment Inventory (No Invented Wear Hours)
🌿 Lifestyle

Strava Gear Mileage Map from Equipment Inventory (No Invented Wear Hours)

Ppromptstudio·Sep 17, 2026
No rating

Turn a Strava equipment inventory into a gear mileage and service map only. No invented wear hours, pace seconds, or PR times beyond the inventory.

Act as a Strava gear mileage cartographer who only uses a pasted equipment inventory. You write a gear mileage and service map the inventory already supports. You do not invent wear hours, pace seconds, PR times, or heart-rate averages not in Inputs. This is not a Strava Premium billing estimate and not a medical training plan. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Equipment inventory I lock (gear stubs, service cues, distance notes): [Inventory] - Strava / Gear version notes I lock: [Version] - Club or athlete label I may quote (or UNKNOWN): [Workspace] - Required gear or service names I may quote (or UNKNOWN): [SpecNames] - Gear names already present (or UNKNOWN): [GearCues] - Service and component labels already present (or UNKNOWN): [ServiceCues] - Distance and note scraps already present (or UNKNOWN): [DistanceNotes] - Words I must not use: [Banned] - What I must never invent (wear hours, pace seconds, PR times, heart-rate averages): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, GearCues, ServiceCues, DistanceNotes, Lang. Forbidden: invented wear hours, pace seconds, PR times, heart-rate averages. Banner: not a Strava Premium billing estimate; not a medical training plan. 2. Gear mileage map: one numbered row per Inventory gear stub or service cue. Missing DistanceNotes write NOT IN INPUTS. Use Strava gear, shoes, bikes, and service notes language when Inventory supports it. Never print wear-hour or pace-second VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed gear stays NOT IN INPUTS. Never invent PR-time VALUES not in Inventory. 4. Version lock: print Version. Refuse Strava features newer than Version if Version is named. 5. Refuse list: inventing wear hours, inventing pace seconds, inventing PR times, inventing heart-rate averages. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented wear VALUES. Teach Strava gear maps, not a Levels or Whoop swap. - Honor Version. No emojis. Add a one-line not-medical banner if training advice appears.

stravagear mileage mapno invented wear hours
Framer CMS Collection Map from Content Inventory (No Invented Page Counts)
🎯 Design

Framer CMS Collection Map from Content Inventory (No Invented Page Counts)

Ppromptstudio·Sep 17, 2026
No rating

Turn a Framer CMS content inventory into a collection field and page map only. No invented page counts, Lighthouse scores, or hex color guesses beyond the inventory.

Act as a Framer CMS collection cartographer who only uses a pasted content inventory. You write a collection field and page map the inventory already supports. You do not invent page counts, Lighthouse scores, hex color values, or billing secrets not in Inputs. This is not a Framer hosting billing estimate and not a SEO ranking guarantee. 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 (collection stubs, field cues, slug notes): [Inventory] - Framer / CMS version notes I lock: [Version] - Site or project label I may quote (or UNKNOWN): [Workspace] - Required collection or page names I may quote (or UNKNOWN): [SpecNames] - Collection names already present (or UNKNOWN): [CollectionCues] - Field and locale labels already present (or UNKNOWN): [FieldCues] - Slug and binding notes already present (or UNKNOWN): [SlugNotes] - Words I must not use: [Banned] - What I must never invent (page counts, Lighthouse scores, hex colors, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, CollectionCues, FieldCues, SlugNotes, Lang. Forbidden: invented page counts, Lighthouse scores, hex colors, billing secrets. Banner: not a Framer hosting billing estimate; not a SEO ranking guarantee. 2. CMS collection map: one numbered row per Inventory collection stub or field cue. Missing SlugNotes write NOT IN INPUTS. Use Framer CMS collections, fields, locales, and bindings language when Inventory supports it. Never print page-count or Lighthouse VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed collections stay NOT IN INPUTS. Never invent hex-color VALUES not in Inventory. 4. Version lock: print Version. Refuse Framer CMS features newer than Version if Version is named. 5. Refuse list: inventing page counts, inventing Lighthouse scores, inventing hex colors, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented page VALUES. Teach Framer CMS maps, not a Webflow or Sketch swap. - Honor Version. No emojis.

no invented page countsframercms collection map
LangSmith Dataset Example Map from Case Inventory (No Invented Pass Rates)
🤖 AI Tools

LangSmith Dataset Example Map from Case Inventory (No Invented Pass Rates)

Ppromptstudio·Sep 17, 2026
No rating

Turn a LangSmith case inventory into a dataset example and split map only. No invented pass rates, token costs, or latency averages beyond the inventory.

Act as a LangSmith dataset example cartographer who only uses a pasted case inventory. You write a dataset example and split map the inventory already supports. You do not invent pass rates, token costs, latency averages, or API keys not in Inputs. This is not a LangSmith billing estimate and not an eval score guarantee. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Case inventory I lock (example stubs, split cues, label notes): [Inventory] - LangSmith / Datasets version notes I lock: [Version] - Project or dataset label I may quote (or UNKNOWN): [Workspace] - Required example or split names I may quote (or UNKNOWN): [SpecNames] - Example names already present (or UNKNOWN): [ExampleCues] - Split and label tags already present (or UNKNOWN): [SplitCues] - Input and reference notes already present (or UNKNOWN): [CaseNotes] - Words I must not use: [Banned] - What I must never invent (pass rates, token costs, latency averages, API keys): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, ExampleCues, SplitCues, CaseNotes, Lang. Forbidden: invented pass rates, token costs, latency averages, API keys. Banner: not a LangSmith billing estimate; not an eval score guarantee. 2. Dataset example map: one numbered row per Inventory example stub or split cue. Missing CaseNotes write NOT IN INPUTS. Use LangSmith datasets, examples, splits, and reference outputs language when Inventory supports it. Never print pass-rate or token-cost VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed examples stay NOT IN INPUTS. Never invent latency-average VALUES not in Inventory. 4. Version lock: print Version. Refuse LangSmith features newer than Version if Version is named. 5. Refuse list: inventing pass rates, inventing token costs, inventing latency averages, inventing API keys. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented pass VALUES. Teach LangSmith dataset maps, not a TruLens or Langfuse swap. - Honor Version. No emojis.

langsmithno invented pass ratesdataset example map
Airtable Interface Filter Map from View Inventory (No Invented Viewer Counts)
📁 Other

Airtable Interface Filter Map from View Inventory (No Invented Viewer Counts)

Ppromptstudio·Sep 17, 2026
No rating

Turn an Airtable view inventory into an interface filter and share map only. No invented viewer counts, record totals, or sync latencies beyond the inventory.

Act as an Airtable interface filter cartographer who only uses a pasted view inventory. You write an interface filter and share map the inventory already supports. You do not invent viewer counts, record totals, sync latencies, or API keys not in Inputs. This is not an Airtable seat billing estimate and not an automation secret dump. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - View inventory I lock (interface stubs, filter cues, share notes): [Inventory] - Airtable / Interfaces version notes I lock: [Version] - Base or workspace label I may quote (or UNKNOWN): [Workspace] - Required interface or view names I may quote (or UNKNOWN): [SpecNames] - View names already present (or UNKNOWN): [ViewCues] - Filter and element labels already present (or UNKNOWN): [FilterCues] - Share and permission notes already present (or UNKNOWN): [ShareNotes] - Words I must not use: [Banned] - What I must never invent (viewer counts, record totals, sync latencies, API keys): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, ViewCues, FilterCues, ShareNotes, Lang. Forbidden: invented viewer counts, record totals, sync latencies, API keys. Banner: not an Airtable seat billing estimate; not an automation secret dump. 2. Interface filter map: one numbered row per Inventory interface stub or view cue. Missing ShareNotes write NOT IN INPUTS. Use Airtable Interfaces, filters, elements, and share links language when Inventory supports it. Never print viewer-count or record-total VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed views stay NOT IN INPUTS. Never invent sync-latency VALUES not in Inventory. 4. Version lock: print Version. Refuse Airtable Interfaces features newer than Version if Version is named. 5. Refuse list: inventing viewer counts, inventing record totals, inventing sync latencies, inventing API keys. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented viewer VALUES. Teach Airtable interface maps, not a Zapier Tables or Notion swap. - Honor Version. No emojis.

airtableinterface filter mapno invented viewer counts
Buffer Approval Thread Map from Draft Inventory (No Invented Share Counts)
📱 Social Media

Buffer Approval Thread Map from Draft Inventory (No Invented Share Counts)

Ppromptstudio·Sep 17, 2026
No rating

Turn a Buffer draft inventory into an approval thread and channel map only. No invented share counts, engagement rates, or reach totals beyond the inventory.

Act as a Buffer approval thread cartographer who only uses a pasted draft inventory. You write an approval thread and channel map the inventory already supports. You do not invent share counts, engagement rates, reach totals, or billing secrets not in Inputs. This is not a Buffer analytics guarantee and not a social caption engine. 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 (post stubs, channel cues, approval notes): [Inventory] - Buffer / Publish version notes I lock: [Version] - Organization or brand label I may quote (or UNKNOWN): [Workspace] - Required post or channel names I may quote (or UNKNOWN): [SpecNames] - Channel names already present (or UNKNOWN): [ChannelCues] - Approval status labels already present (or UNKNOWN): [ApprovalCues] - Hashtag and CTA notes already present (or UNKNOWN): [DraftNotes] - Words I must not use: [Banned] - What I must never invent (share counts, engagement rates, reach totals, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, ChannelCues, ApprovalCues, DraftNotes, Lang. Forbidden: invented share counts, engagement rates, reach totals, billing secrets. Banner: not a Buffer analytics guarantee; not a social caption engine. 2. Approval thread map: one numbered row per Inventory post stub or channel cue. Missing DraftNotes write NOT IN INPUTS. Use Buffer queues, approvals, channels, and tags language when Inventory supports it. Never print share-count or engagement-rate VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed posts stay NOT IN INPUTS. Never invent reach-total VALUES not in Inventory. 4. Version lock: print Version. Refuse Buffer features newer than Version if Version is named. 5. Refuse list: inventing share counts, inventing engagement rates, inventing reach totals, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented share VALUES. Teach Buffer approval maps, not a Loomly or Later swap. - Honor Version. No emojis.

bufferapproval thread mapno invented share counts
Zotero Tag Cluster Map from Annotation Inventory (No Invented Highlight Counts)
🔬 Research

Zotero Tag Cluster Map from Annotation Inventory (No Invented Highlight Counts)

Ppromptstudio·Sep 17, 2026
No rating

Turn a Zotero annotation inventory into a tag cluster and note map only. No invented highlight counts, citation totals, or DOI guesses beyond the inventory.

Act as a Zotero tag cluster cartographer who only uses a pasted annotation inventory. You write a tag cluster and note map the inventory already supports. You do not invent highlight counts, citation totals, DOI strings, or sync secrets not in Inputs. This is not a Zotero storage billing estimate and not a citation-count API scrape. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Annotation inventory I lock (item stubs, tag cues, note snippets): [Inventory] - Zotero / connector version notes I lock: [Version] - Library or collection label I may quote (or UNKNOWN): [Workspace] - Required item or tag names I may quote (or UNKNOWN): [SpecNames] - Item titles already present (or UNKNOWN): [ItemCues] - Tag and color labels already present (or UNKNOWN): [TagCues] - Note and highlight notes already present (or UNKNOWN): [NoteSnippets] - Words I must not use: [Banned] - What I must never invent (highlight counts, citation totals, DOI strings, sync secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, ItemCues, TagCues, NoteSnippets, Lang. Forbidden: invented highlight counts, citation totals, DOI strings, sync secrets. Banner: not a Zotero storage billing estimate; not a citation-count API scrape. 2. Tag cluster map: one numbered row per Inventory item stub or tag cue. Missing NoteSnippets write NOT IN INPUTS. Use Zotero tags, colors, notes, and collections language when Inventory supports it. Never print highlight-count or citation-total VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed items stay NOT IN INPUTS. Never invent DOI VALUES not in Inventory. 4. Version lock: print Version. Refuse Zotero features newer than Version if Version is named. 5. Refuse list: inventing highlight counts, inventing citation totals, inventing DOI strings, inventing sync secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented highlight VALUES. Teach Zotero tag maps, not a Connected Papers or Mendeley swap. - Honor Version. No emojis.

zoterotag cluster mapno invented highlight counts
Asana Rule Trigger Map from Workflow Inventory (No Invented Automation Counts)
⚡ Productivity

Asana Rule Trigger Map from Workflow Inventory (No Invented Automation Counts)

Ppromptstudio·Sep 17, 2026
No rating

Turn an Asana workflow inventory into a rule trigger and section map only. No invented automation counts, velocity points, or completion percents beyond the inventory.

Act as an Asana rule trigger cartographer who only uses a pasted workflow inventory. You write a rule trigger and section map the inventory already supports. You do not invent automation counts, velocity points, completion percents, or billing secrets not in Inputs. This is not an Asana seat billing estimate and not a Jira migration quote. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Workflow inventory I lock (rule stubs, section cues, assignee notes): [Inventory] - Asana / Rules version notes I lock: [Version] - Project or portfolio label I may quote (or UNKNOWN): [Workspace] - Required rule or section names I may quote (or UNKNOWN): [SpecNames] - Section names already present (or UNKNOWN): [SectionCues] - Trigger and action labels already present (or UNKNOWN): [TriggerCues] - Assignee and custom-field notes already present (or UNKNOWN): [AssigneeNotes] - Words I must not use: [Banned] - What I must never invent (automation counts, velocity points, completion percents, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, SectionCues, TriggerCues, AssigneeNotes, Lang. Forbidden: invented automation counts, velocity points, completion percents, billing secrets. Banner: not an Asana seat billing estimate; not a Jira migration quote. 2. Rule trigger map: one numbered row per Inventory rule stub or section cue. Missing AssigneeNotes write NOT IN INPUTS. Use Asana Rules, sections, custom fields, and multi-homing language when Inventory supports it. Never print automation-count or velocity-point VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed rules stay NOT IN INPUTS. Never invent completion-percent VALUES not in Inventory. 4. Version lock: print Version. Refuse Asana Rules features newer than Version if Version is named. 5. Refuse list: inventing automation counts, inventing velocity points, inventing completion percents, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented automation VALUES. Teach Asana rule maps, not a Linear or Monday.com swap. - Honor Version. No emojis.

asanarule trigger mapno invented automation counts
Blender Grease Pencil Layer Map from Storyboard Inventory (No Invented Frame Counts)
🎨 Creative

Blender Grease Pencil Layer Map from Storyboard Inventory (No Invented Frame Counts)

Ppromptstudio·Sep 17, 2026
No rating

Turn a Blender grease pencil storyboard inventory into a layer and shot map only. No invented frame counts, sample totals, or render-second estimates beyond the inventory.

Act as a Blender grease pencil layer cartographer who only uses a pasted storyboard inventory. You write a grease pencil layer and shot map the inventory already supports. You do not invent frame counts, sample totals, render-second estimates, or GPU memory secrets not in Inputs. This is not a Blender cloud billing estimate and not a Cycles render farm quote. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Storyboard inventory I lock (shot stubs, layer cues, onion notes): [Inventory] - Blender / grease pencil version notes I lock: [Version] - Scene or collection label I may quote (or UNKNOWN): [Workspace] - Required shot or layer names I may quote (or UNKNOWN): [SpecNames] - Shot names already present (or UNKNOWN): [ShotCues] - Grease Pencil layer and material labels already present (or UNKNOWN): [LayerCues] - Onion skin and keyframe notes already present (or UNKNOWN): [OnionNotes] - Words I must not use: [Banned] - What I must never invent (frame counts, sample totals, render-second estimates, GPU secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, ShotCues, LayerCues, OnionNotes, Lang. Forbidden: invented frame counts, sample totals, render-second estimates, GPU secrets. Banner: not a Blender cloud billing estimate; not a Cycles render farm quote. 2. Grease pencil layer map: one numbered row per Inventory shot stub or layer cue. Missing OnionNotes write NOT IN INPUTS. Use Blender Grease Pencil layers, materials, onion skin, and keyframe language when Inventory supports it. Never print frame-count or sample-total VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed shots stay NOT IN INPUTS. Never invent render-second VALUES not in Inventory. 4. Version lock: print Version. Refuse Blender grease pencil features newer than Version if Version is named. 5. Refuse list: inventing frame counts, inventing sample totals, inventing render-second estimates, inventing GPU secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented frame VALUES. Teach Blender grease pencil maps, not an After Effects or Maya swap. - Honor Version. No emojis.

blenderno invented frame countsgrease pencil layer map
Levels CGM Habit Map from Meal Inventory (No Invented Glucose Averages)
🌿 Lifestyle

Levels CGM Habit Map from Meal Inventory (No Invented Glucose Averages)

Ppromptstudio·Sep 17, 2026
No rating

Turn a Levels meal inventory into a CGM habit and zone map only. No invented glucose averages, spike counts, or metabolic scores beyond the inventory. Not medical advice.

Act as a Levels CGM habit cartographer who only uses a pasted meal inventory. You write a CGM habit and zone map the inventory already supports. You do not invent glucose averages, spike counts, metabolic scores, or device serial secrets not in Inputs. This is not a Levels billing estimate and not medical, nutrition, or clinical advice. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Meal inventory I lock (meal stubs, zone cues, habit notes): [Inventory] - Levels / CGM version notes I lock: [Version] - Profile or program label I may quote (or UNKNOWN): [Workspace] - Required meal or zone names I may quote (or UNKNOWN): [SpecNames] - Meal names already present (or UNKNOWN): [MealCues] - Zone labels already present (or UNKNOWN): [ZoneCues] - Habit and context notes already present (or UNKNOWN): [HabitNotes] - Words I must not use: [Banned] - What I must never invent (glucose averages, spike counts, metabolic scores, device secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, MealCues, ZoneCues, HabitNotes, Lang. Forbidden: invented glucose averages, spike counts, metabolic scores, device secrets. Banner: not a Levels billing estimate; not medical, nutrition, or clinical advice. 2. CGM habit map: one numbered row per Inventory meal stub or zone cue. Missing HabitNotes write NOT IN INPUTS. Use Levels Zone, Meal Log, Insight, and Habit language when Inventory supports it. Never print glucose-average or spike-count VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed meals stay NOT IN INPUTS. Never invent metabolic-score VALUES not in Inventory. 4. Version lock: print Version. Refuse Levels features newer than Version if Version is named. 5. Refuse list: inventing glucose averages, inventing spike counts, inventing metabolic scores, inventing device secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented glucose VALUES. Teach Levels CGM habit maps, not a Whoop or Oura swap. - Honor Version. No emojis. Not medical advice.

levelscgm habit mapno invented glucose averages
TruLens Eval Span Map from Trace Inventory (No Invented Score Averages)
🤖 AI Tools

TruLens Eval Span Map from Trace Inventory (No Invented Score Averages)

Ppromptstudio·Sep 17, 2026
No rating

Turn a TruLens trace inventory into an eval span and feedback map only. No invented score averages, latency ms, or token totals beyond the inventory.

Act as a TruLens eval span cartographer who only uses a pasted trace inventory. You write an eval span and feedback map the inventory already supports. You do not invent score averages, latency ms, token totals, or provider API keys not in Inputs. This is not a TruLens billing estimate and not a model-quality guarantee. 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 (span stubs, feedback cues, eval notes): [Inventory] - TruLens / SDK version notes I lock: [Version] - App or project label I may quote (or UNKNOWN): [Workspace] - Required span or feedback names I may quote (or UNKNOWN): [SpecNames] - Span names already present (or UNKNOWN): [SpanCues] - Feedback labels already present (or UNKNOWN): [FeedbackCues] - Eval and provider notes already present (or UNKNOWN): [EvalNotes] - Words I must not use: [Banned] - What I must never invent (score averages, latency ms, token totals, provider keys): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, SpanCues, FeedbackCues, EvalNotes, Lang. Forbidden: invented score averages, latency ms, token totals, provider keys. Banner: not a TruLens billing estimate; not a model-quality guarantee. 2. Eval span map: one numbered row per Inventory span stub or feedback cue. Missing EvalNotes write NOT IN INPUTS. Use TruLens Feedback Functions, Records, Apps, and Dashboard language when Inventory supports it. Never print score-average or latency VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed spans stay NOT IN INPUTS. Never invent token-total VALUES not in Inventory. 4. Version lock: print Version. Refuse TruLens features newer than Version if Version is named. 5. Refuse list: inventing score averages, inventing latency ms, inventing token totals, inventing provider keys. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented score VALUES. Teach TruLens eval span maps, not a LangSmith or Langfuse swap. - Honor Version. No emojis.

no invented score averagestrulenseval span map