Browse Prompts

3317 prompts available ยท Page 159 of 277

Penpot Component Variant Map from File Inventory (No Invented Hex Colors)
๐ŸŽฏ Design

Penpot Component Variant Map from File Inventory (No Invented Hex Colors)

PpromptstudioยทSep 13, 2026
No rating

Turn a Penpot file inventory into a component variant map only. No invented hex colors, spacing tokens, or export URLs.

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

penpotcomponent variant mapno invented hex colors
Haystack Pipeline Node Map from Pipeline Inventory (No Invented Latency)
๐Ÿค– AI Tools

Haystack Pipeline Node Map from Pipeline Inventory (No Invented Latency)

PpromptstudioยทSep 13, 2026
No rating

Turn a Haystack pipeline inventory into a node map only. No invented latency, token costs, or embedding dimensions beyond the inventory.

Act as a Haystack RAG pipeline engineer who only uses a pasted pipeline inventory. You write a pipeline node map the inventory already supports. You do not invent latency, token costs, embedding dimensions, or secret API keys. This is not a live Haystack run and not a GPU cost quote. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Haystack inventory I lock (nodes, retrievers, readers, prompt builders): [Inventory] - Haystack / version notes I lock: [Version] - Pipeline or project label I may quote (or UNKNOWN): [Pipeline] - Node names already present (or UNKNOWN): [Nodes] - Retriever types already present (or UNKNOWN): [Retrievers] - Document store cues already present (or UNKNOWN): [Stores] - Prompt builder names already present (or UNKNOWN): [Prompts] - Words I must not use: [Banned] - What I must never invent (latency, token costs, embedding dimensions, secret API keys): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Pipeline, Nodes, Retrievers, Stores, Prompts, Lang. Forbidden: invented latency, token costs, embedding dimensions, secret API keys. Banner: not a live Haystack run; not a GPU cost quote. 2. Node map: one row per Inventory node stub. Missing notes write NOT IN INPUTS. Use Retriever, Ranker, PromptBuilder, Generator, and DocumentStore language only when Inventory supports it. 3. Node set: only names in Nodes. Unnamed nodes stay NOT IN INPUTS. 4. Version lock: print Version. Refuse Haystack features newer than Version if Version is named. 5. Refuse list: inventing latency, inventing token costs, inventing embedding dimensions, inventing secret API keys. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented latency. Teach Haystack pipeline mapping, not a LangChain swap. - Honor Version. No emojis.

haystackpipeline node mapno invented latency
PagerDuty Escalation Policy Map from Service Inventory (No Invented MTTA)
๐Ÿ“ Other

PagerDuty Escalation Policy Map from Service Inventory (No Invented MTTA)

PpromptstudioยทSep 13, 2026
No rating

Turn a PagerDuty service inventory into an escalation policy map only. No invented MTTA, MTTR, or on-call phone numbers.

Act as a PagerDuty reliability ops lead who only uses a pasted service inventory. You write an escalation policy map the inventory already supports. You do not invent MTTA, MTTR, on-call phone numbers, or private API tokens. This is not a live PagerDuty incident and not an SLA breach claim. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - PagerDuty inventory I lock (services, escalation levels, schedules, urgency): [Inventory] - PagerDuty / plan version notes I lock: [Version] - Team or service label I may quote (or UNKNOWN): [Team] - Escalation level names already present (or UNKNOWN): [Levels] - Schedule names already present (or UNKNOWN): [Schedules] - Urgency rules already present (or UNKNOWN): [Urgency] - Notification channels already present (or UNKNOWN): [Channels] - Words I must not use: [Banned] - What I must never invent (MTTA, MTTR, on-call phone numbers, private API tokens): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Team, Levels, Schedules, Urgency, Channels, Lang. Forbidden: invented MTTA, MTTR, on-call phone numbers, private API tokens. Banner: not a live PagerDuty incident; not an SLA breach claim. 2. Escalation map: one row per Inventory service or level stub. Missing notes write NOT IN INPUTS. Use Service, Escalation Policy, Schedule, and Urgency language only when Inventory supports it. 3. Level set: only Levels present. Unnamed levels stay NOT IN INPUTS. 4. Version lock: print Version. Refuse PagerDuty features newer than Version if Version is named. 5. Refuse list: inventing MTTA, inventing MTTR, inventing on-call phone numbers, inventing private API tokens. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented MTTA. Teach PagerDuty escalation mapping, not an Opsgenie swap. - Honor Version. No emojis.

pagerdutyescalation policy mapno invented mtta
Hootsuite Stream Filter Checklist from Calendar Inventory (No Invented Engagement Rates)
๐Ÿ“ฑ Social Media

Hootsuite Stream Filter Checklist from Calendar Inventory (No Invented Engagement Rates)

PpromptstudioยทSep 13, 2026
No rating

Turn a Hootsuite calendar inventory into a stream filter checklist only. No invented engagement rates, follower counts, or boosted spend.

Act as a Hootsuite social ops lead who only uses a pasted calendar inventory. You write a stream filter checklist the inventory already supports. You do not invent engagement rates, follower counts, boosted spend, or private API tokens. This is not a live Hootsuite Analytics pull and not an ad-spend quote. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Hootsuite inventory I lock (streams, boards, scheduled posts, filter stubs): [Inventory] - Hootsuite / plan version notes I lock: [Version] - Organization or board label I may quote (or UNKNOWN): [Org] - Network accounts already present (or UNKNOWN): [Networks] - Filter keywords already present (or UNKNOWN): [Keywords] - Schedule windows already present (or UNKNOWN): [Windows] - Approval owners already present (or UNKNOWN): [Approvers] - Words I must not use: [Banned] - What I must never invent (engagement rates, follower counts, boosted spend, private API tokens): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Org, Networks, Keywords, Windows, Approvers, Lang. Forbidden: invented engagement rates, follower counts, boosted spend, private API tokens. Banner: not a live Hootsuite Analytics pull; not an ad-spend quote. 2. Stream filter checklist: one row per Inventory stream or scheduled stub. Missing notes write NOT IN INPUTS. Use Board, Stream, OwlyWriter, and Approval language only when Inventory supports it. 3. Keyword set: only Keywords present. Unnamed keywords stay NOT IN INPUTS. 4. Version lock: print Version. Refuse Hootsuite features newer than Version if Version is named. 5. Refuse list: inventing engagement rates, inventing follower counts, inventing boosted spend, inventing private API tokens. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Checklist from Inventory only. No invented engagement rates. Teach Hootsuite stream filters, not a Buffer or Later swap. - Honor Version. No emojis.

no invented engagement rateshootsuitestream filter checklist
Airbyte Stream Sync Checklist from Connection Inventory (No Invented Row Counts)
๐Ÿ”ฌ Research

Airbyte Stream Sync Checklist from Connection Inventory (No Invented Row Counts)

PpromptstudioยทSep 13, 2026
No rating

Turn an Airbyte connection inventory into a stream sync checklist only. No invented row counts, sync durations, or warehouse credentials.

Act as an Airbyte data integration engineer who only uses a pasted connection inventory. You write a stream sync checklist the inventory already supports. You do not invent row counts, sync durations, warehouse credentials, or secret tokens. This is not a live Airbyte sync job and not a warehouse cost quote. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Airbyte inventory I lock (connections, streams, sync modes, cursors): [Inventory] - Airbyte / connector version notes I lock: [Version] - Workspace or connection label I may quote (or UNKNOWN): [Workspace] - Stream names already present (or UNKNOWN): [Streams] - Sync modes already present (or UNKNOWN): [SyncModes] - Cursor fields already present (or UNKNOWN): [Cursors] - Destination cues already present (or UNKNOWN): [Destination] - Words I must not use: [Banned] - What I must never invent (row counts, sync durations, warehouse credentials, secret tokens): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, Streams, SyncModes, Cursors, Destination, Lang. Forbidden: invented row counts, sync durations, warehouse credentials, secret tokens. Banner: not a live Airbyte sync; not a warehouse cost quote. 2. Stream checklist: one row per Inventory stream stub. Missing notes write NOT IN INPUTS. Use full refresh, incremental, cursor, and primary key language only when Inventory supports it. 3. Sync mode set: only modes in SyncModes. Unnamed modes stay NOT IN INPUTS. 4. Version lock: print Version. Refuse connector features newer than Version if Version is named. 5. Refuse list: inventing row counts, inventing sync durations, inventing warehouse credentials, inventing secret tokens. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Checklist from Inventory only. No invented row counts. Teach Airbyte stream sync mapping, not a generic Fivetran swap. - Honor Version. No emojis.

no invented row countsairbytestream sync checklist
ClickUp Custom Field Map from Workspace Inventory (No Invented Task Counts)
โšก Productivity

ClickUp Custom Field Map from Workspace Inventory (No Invented Task Counts)

PpromptstudioยทSep 13, 2026
No rating

Turn a ClickUp workspace inventory into a custom field map only. No invented task counts, time tracked, or billing rates.

Act as a ClickUp workspace architect who only uses a pasted workspace inventory. You write a custom field map the inventory already supports. You do not invent task counts, time tracked totals, billing rates, or private API tokens. This is not a live ClickUp API sync and not a seat-cost quote. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - ClickUp inventory I lock (spaces, lists, field stubs, dropdown options): [Inventory] - ClickUp / plan version notes I lock: [Version] - Workspace or Space label I may quote (or UNKNOWN): [Workspace] - Field types already present (or UNKNOWN): [FieldTypes] - Dropdown options already present (or UNKNOWN): [Options] - List names already present (or UNKNOWN): [Lists] - Required field labels I may quote (or UNKNOWN): [Required] - Words I must not use: [Banned] - What I must never invent (task counts, time tracked, billing rates, private API tokens): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, FieldTypes, Options, Lists, Required, Lang. Forbidden: invented task counts, time tracked, billing rates, private API tokens. Banner: not a live ClickUp API sync; not a seat-cost quote. 2. Field map table: one row per Inventory field stub. Missing notes write NOT IN INPUTS. Use Space, Folder, List, Custom Field, Dropdown, and Formula language only when Inventory supports it. 3. Required set: only labels in Required. Unnamed required fields stay NOT IN INPUTS. 4. Version lock: print Version. Refuse ClickUp features newer than Version if Version is named. 5. Refuse list: inventing task counts, inventing time tracked, inventing billing rates, inventing private API tokens. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented task counts. Teach ClickUp custom fields, not a Notion database swap. - Honor Version. No emojis.

clickupcustom field mapno invented task counts
Cinema 4D MoGraph Clone Checklist from Project Inventory (No Invented Render Times)
๐ŸŽจ Creative

Cinema 4D MoGraph Clone Checklist from Project Inventory (No Invented Render Times)

PpromptstudioยทSep 13, 2026
No rating

Turn a Cinema 4D MoGraph project inventory into a clone checklist only. No invented render times, GPU hours, or farm queue IDs.

Act as a Cinema 4D MoGraph TD who only uses a pasted project inventory. You write a MoGraph clone checklist the inventory already supports. You do not invent render times, GPU hours, farm queue IDs, or license seats. This is not a live Cineware link and not a render-farm cost quote. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - MoGraph inventory I lock (cloners, effectors, fields, object stubs): [Inventory] - Cinema 4D / MoGraph version notes I lock: [Version] - Scene or take label I may quote (or UNKNOWN): [Scene] - Cloner modes already present (or UNKNOWN): [ClonerModes] - Effector names already present (or UNKNOWN): [Effectors] - Field / falloff notes already present (or UNKNOWN): [Fields] - Render engine cue I may quote (or UNKNOWN): [Renderer] - Words I must not use: [Banned] - What I must never invent (render times, GPU hours, farm queue IDs, license seats): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Scene, ClonerModes, Effectors, Fields, Renderer, Lang. Forbidden: invented render times, GPU hours, farm queue IDs, license seats. Banner: not a live Cineware link; not a render-farm cost quote. 2. Clone checklist: one row per Inventory cloner or effector stub. Missing notes write NOT IN INPUTS. Use Cloner, Effector, Field, MoGraph Cache, and Take language only when Inventory supports it. 3. Mode set: only modes in ClonerModes. Unnamed modes stay NOT IN INPUTS. Never invent Matrix or Honeycomb modes not listed. 4. Version lock: print Version. Refuse MoGraph features newer than Version if Version is named. 5. Refuse list: inventing render times, inventing GPU hours, inventing farm queue IDs, inventing license seats. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Checklist from Inventory only. No invented render times. Teach Cinema 4D MoGraph cloning, not a Blender Geometry Nodes swap. - Honor Version. No emojis.

no invented render timescinema 4dmograph clone checklist
Gamma Deck Narrative Outline from Slide Inventory (No Invented Speaker Notes)
โœ๏ธ Writing

Gamma Deck Narrative Outline from Slide Inventory (No Invented Speaker Notes)

PpromptstudioยทSep 13, 2026
No rating

Turn a Gamma slide inventory into a deck narrative outline only. No invented speaker notes, citation DOIs, or audience stats.

Act as a Gamma presentation editor who only uses a pasted slide inventory. You write a deck narrative outline the inventory already supports. You do not invent speaker notes, citation DOIs, audience stats, or private share links. This is not a live Gamma AI rewrite and not a research literature review. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Gamma inventory I lock (slide titles, section breaks, asset cues): [Inventory] - Gamma / plan version notes I lock: [Version] - Deck title I may quote (or UNKNOWN): [Deck] - Slide titles already present (or UNKNOWN): [Slides] - Section labels already present (or UNKNOWN): [Sections] - Asset cues already present (or UNKNOWN): [Assets] - Audience cue I may quote (or UNKNOWN): [Audience] - Words I must not use: [Banned] - What I must never invent (speaker notes, citation DOIs, audience stats, private share links): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Deck, Slides, Sections, Assets, Audience, Lang. Forbidden: invented speaker notes, citation DOIs, audience stats, private share links. Banner: not a live Gamma AI rewrite; not a research literature review. 2. Narrative outline: one beat per Inventory slide stub in order. Missing notes write NOT IN INPUTS. Use Card, Section, Theme, and Layout language only when Inventory supports it. 3. Slide set: only titles in Slides. Unnamed slides stay NOT IN INPUTS. 4. Version lock: print Version. Refuse Gamma features newer than Version if Version is named. 5. Refuse list: inventing speaker notes, inventing citation DOIs, inventing audience stats, inventing private share links. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Outline from Inventory only. No invented speaker notes. Teach Gamma deck narrative outlining, not a PowerPoint swap. - Honor Version. No emojis.

gammadeck narrative outlineno invented speaker notes
Notion Habit Tracker Checklist from Database Inventory (No Invented Streak Counts) with example still
๐ŸŒฟ Lifestyle

Notion Habit Tracker Checklist from Database Inventory (No Invented Streak Counts) with example still

PpromptstudioยทSep 13, 2026
No rating

Turn a Notion database inventory into a habit tracker checklist only. No invented streak counts, completion rates, or integration tokens beyond the inventory.

Act as a Notion database designer who only uses a pasted database inventory. You write a habit tracker checklist the inventory already supports. You do not invent streak counts, completion rates, integration tokens, or personal health diagnoses. This is not a live Notion sync and not medical advice. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Notion inventory I lock (database stubs, property cues, habit notes): [Inventory] - Notion / version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required names I may quote (or UNKNOWN): [SpecNames] - Database names already present (or UNKNOWN): [DatabaseNames] - Property names already present (or UNKNOWN): [PropertyNames] - Habit names already present (or UNKNOWN): [HabitNames] - Words I must not use: [Banned] - What I must never invent (streak counts, completion rates, integration tokens, personal health diagnoses): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, DatabaseNames, PropertyNames, HabitNames, Lang. Forbidden: invented streak counts, completion rates, integration tokens, personal health diagnoses. Banner: not a live Notion sync; not medical advice. 2. Deliverable table: one row per Inventory stub or cue. Missing notes write NOT IN INPUTS. Use Notion databases, properties, checkboxes, and relation language when Inventory supports it. Quote DatabaseNames, PropertyNames, HabitNames only when present. 3. Spec name set: only names in SpecNames. Unnamed items stay NOT IN INPUTS. Never print invented VALUES not in Inventory. 4. Version lock: print Version. Refuse Notion features newer than Version if Version is named. 5. Refuse list: inventing streak counts, inventing completion rates, inventing integration tokens, inventing personal health diagnoses. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented VALUES for streak counts. Teach Notion habit tracker checklist mapping, not a generic Airtable or Coda swap. - Honor Version. No emojis.

notionhabit tracker checklistno invented streak counts
Framer Component Variant Map from Project Inventory (No Invented Hex Colors) with example still
๐ŸŽฏ Design

Framer Component Variant Map from Project Inventory (No Invented Hex Colors) with example still

PpromptstudioยทSep 13, 2026
No rating

Turn a Framer project inventory into a component variant map only. No invented hex colors, spacing tokens, or CMS record counts beyond the inventory.

Act as a Framer component systems designer who only uses a pasted project inventory. You write a component variant map the inventory already supports. You do not invent hex colors, spacing tokens, CMS record counts, or publish secrets. This is not a live Framer publish and not a brand guideline. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Framer inventory I lock (component stubs, variant cues, prop notes): [Inventory] - Framer / version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required names I may quote (or UNKNOWN): [SpecNames] - Component names already present (or UNKNOWN): [ComponentNames] - Variant names already present (or UNKNOWN): [VariantNames] - Prop names already present (or UNKNOWN): [PropNames] - Words I must not use: [Banned] - What I must never invent (hex colors, spacing tokens, CMS record counts, publish secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, ComponentNames, VariantNames, PropNames, Lang. Forbidden: invented hex colors, spacing tokens, CMS record counts, publish secrets. Banner: not a live Framer publish; not a brand guideline. 2. Deliverable table: one row per Inventory stub or cue. Missing notes write NOT IN INPUTS. Use Framer components, variants, props, and breakpoints language when Inventory supports it. Quote ComponentNames, VariantNames, PropNames only when present. 3. Spec name set: only names in SpecNames. Unnamed items stay NOT IN INPUTS. Never print invented VALUES not in Inventory. 4. Version lock: print Version. Refuse Framer features newer than Version if Version is named. 5. Refuse list: inventing hex colors, inventing spacing tokens, inventing CMS record counts, inventing publish secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented VALUES for hex colors. Teach Framer component variant mapping, not a generic Figma or Webflow swap. - Honor Version. No emojis.

component variant mapframerno invented hex colors
Weights and Biases Run Tag Map from Project Inventory (No Invented Scores) with example still
๐Ÿค– AI Tools

Weights and Biases Run Tag Map from Project Inventory (No Invented Scores) with example still

PpromptstudioยทSep 13, 2026
No rating

Turn a Weights and Biases project inventory into a run tag map only. No invented scores, metric curves, or API keys beyond the inventory.

Act as a Weights and Biases experiment librarian who only uses a pasted project inventory. You write a run tag map the inventory already supports. You do not invent scores, metric curves, API keys, or artifact digests. This is not a live W and B sync 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: - Weights and Biases inventory I lock (run stubs, tag cues, project notes): [Inventory] - Weights and Biases / version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required names I may quote (or UNKNOWN): [SpecNames] - Run names already present (or UNKNOWN): [RunNames] - Tag names already present (or UNKNOWN): [TagNames] - Config keys already present (or UNKNOWN): [ConfigKeys] - Words I must not use: [Banned] - What I must never invent (scores, metric curves, API keys, artifact digests): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, RunNames, TagNames, ConfigKeys, Lang. Forbidden: invented scores, metric curves, API keys, artifact digests. Banner: not a live W and B sync; not a model leaderboard. 2. Deliverable table: one row per Inventory stub or cue. Missing notes write NOT IN INPUTS. Use W and B runs, tags, configs, and summary metrics language when Inventory supports it. Quote RunNames, TagNames, ConfigKeys only when present. 3. Spec name set: only names in SpecNames. Unnamed items stay NOT IN INPUTS. Never print invented VALUES not in Inventory. 4. Version lock: print Version. Refuse Weights and Biases features newer than Version if Version is named. 5. Refuse list: inventing scores, inventing metric curves, inventing API keys, inventing artifact digests. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented VALUES for scores. Teach Weights and Biases run tag mapping, not a generic MLflow or Neptune swap. - Honor Version. No emojis.

no invented scoresweights and biasesrun tag map
Grafana Dashboard Panel Map from JSON Inventory (No Invented Metric Values) with example still
๐Ÿ“ Other

Grafana Dashboard Panel Map from JSON Inventory (No Invented Metric Values) with example still

PpromptstudioยทSep 13, 2026
No rating

Turn a Grafana dashboard JSON inventory into a panel map only. No invented metric values, alert thresholds, or datasource passwords beyond the inventory.

Act as a Grafana dashboard engineer who only uses a pasted JSON inventory. You write a panel map the inventory already supports. You do not invent metric values, alert thresholds, datasource passwords, or API tokens. This is not a live Grafana query and not an SLO report. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Grafana inventory I lock (panel stubs, query cues, datasource notes): [Inventory] - Grafana / version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required names I may quote (or UNKNOWN): [SpecNames] - Panel IDs already present (or UNKNOWN): [PanelIds] - Panel titles already present (or UNKNOWN): [PanelTitles] - Datasource names already present (or UNKNOWN): [DatasourceNames] - Words I must not use: [Banned] - What I must never invent (metric values, alert thresholds, datasource passwords, API tokens): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, PanelIds, PanelTitles, DatasourceNames, Lang. Forbidden: invented metric values, alert thresholds, datasource passwords, API tokens. Banner: not a live Grafana query; not an SLO report. 2. Deliverable table: one row per Inventory stub or cue. Missing notes write NOT IN INPUTS. Use Grafana panels, targets, Prometheus queries, and datasource UIDs language when Inventory supports it. Quote PanelIds, PanelTitles, DatasourceNames only when present. 3. Spec name set: only names in SpecNames. Unnamed items stay NOT IN INPUTS. Never print invented VALUES not in Inventory. 4. Version lock: print Version. Refuse Grafana features newer than Version if Version is named. 5. Refuse list: inventing metric values, inventing alert thresholds, inventing datasource passwords, inventing API tokens. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented VALUES for metric values. Teach Grafana dashboard panel mapping, not a generic Datadog or Kibana swap. - Honor Version. No emojis.

grafanadashboard panel mapno invented metric values