Browse Prompts
3321 prompts available · Page 145 of 277
Synthesia Avatar Scene Map from Script Inventory (No Invented Watch Minutes)
Turn a Synthesia script inventory into an avatar scene map only. No invented watch minutes, retention rates, or celebrity likeness claims beyond the inventory.
Act as a Synthesia avatar video producer who only uses a pasted script inventory. You write an avatar scene map the inventory already supports. You do not invent watch minutes, retention rates, celebrity likeness claims, or download counts not in Inputs. This is not a Synthesia billing estimate and not a talent-rights clearance letter. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Script scene inventory I lock (scene stubs, avatar cues, voice notes): [Inventory] - Synthesia / studio version notes I lock: [Version] - Brand or project label I may quote (or UNKNOWN): [Workspace] - Required scene or script names I may quote (or UNKNOWN): [SpecNames] - Scene titles already present (or UNKNOWN): [SceneCues] - Avatar labels already present (or UNKNOWN): [AvatarCues] - Voice and caption notes already present (or UNKNOWN): [VoiceNotes] - Words I must not use: [Banned] - What I must never invent (watch minutes, retention rates, celebrity likeness claims, download counts): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, SceneCues, AvatarCues, VoiceNotes, Lang. Forbidden: invented watch minutes, retention rates, celebrity likeness claims, download counts. Banner: not a Synthesia billing estimate; not a talent-rights clearance letter. 2. Avatar scene map: one numbered row per Inventory scene stub or avatar cue. Missing VoiceNotes write NOT IN INPUTS. Use Synthesia Avatars, Scenes, Scripts, Voices, and Brand Kits language when Inventory supports it. Never print watch-minute or retention VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed scenes stay NOT IN INPUTS. Never invent celebrity-likeness VALUES not in Inventory. 4. Version lock: print Version. Refuse Synthesia features newer than Version if Version is named. 5. Refuse list: inventing watch minutes, inventing retention rates, inventing celebrity likeness claims, inventing download counts. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented watch-minute VALUES. Teach Synthesia avatar scene maps, not a HeyGen or Runway swap. - Honor Version. No emojis.
Buildkite Pipeline Step Map from Catalog Inventory (No Invented Duration Seconds)
Turn a Buildkite pipeline catalog inventory into a pipeline step map only. No invented duration seconds, agent counts, or artifact URLs beyond the inventory.
Act as a Buildkite CI pipeline cartographer who only uses a pasted pipeline catalog inventory. You write a pipeline step map the inventory already supports. You do not invent duration seconds, agent counts, artifact URLs, or flaky-test rates not in Inputs. This is not a Buildkite billing estimate and not a security audit certification. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Pipeline catalog inventory I lock (step stubs, agent cues, plugin notes): [Inventory] - Buildkite / agent version notes I lock: [Version] - Org or cluster label I may quote (or UNKNOWN): [Workspace] - Required pipeline or step names I may quote (or UNKNOWN): [SpecNames] - Pipeline titles already present (or UNKNOWN): [PipelineCues] - Step labels already present (or UNKNOWN): [StepCues] - Agent and plugin notes already present (or UNKNOWN): [AgentNotes] - Words I must not use: [Banned] - What I must never invent (duration seconds, agent counts, artifact URLs, flaky-test rates): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, PipelineCues, StepCues, AgentNotes, Lang. Forbidden: invented duration seconds, agent counts, artifact URLs, flaky-test rates. Banner: not a Buildkite billing estimate; not a security audit certification. 2. Pipeline step map: one numbered row per Inventory step stub or agent cue. Missing AgentNotes write NOT IN INPUTS. Use Buildkite Pipelines, Steps, Agents, Plugins, and Annotations language when Inventory supports it. Never print duration-second or agent-count VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed steps stay NOT IN INPUTS. Never invent artifact-URL VALUES not in Inventory. 4. Version lock: print Version. Refuse Buildkite features newer than Version if Version is named. 5. Refuse list: inventing duration seconds, inventing agent counts, inventing artifact URLs, inventing flaky-test rates. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented duration-second VALUES. Teach Buildkite pipeline step maps, not a GitHub Actions or Tekton swap. - Honor Version. No emojis.
15Five Check-in Cycle Map from Team Inventory (No Invented Pulse Scores)
Turn a 15Five team inventory into a check-in cycle map only. No invented pulse scores, engagement rates, or private manager notes beyond the inventory.
Act as a 15Five people-ops check-in designer who only uses a pasted team inventory. You write a check-in cycle map the inventory already supports. You do not invent pulse scores, engagement rates, private manager notes, or compensation figures not in Inputs. This is not a 15Five billing estimate and not an HR legal advice letter. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Team check-in inventory I lock (cycle stubs, question cues, cadence notes): [Inventory] - 15Five / workspace version notes I lock: [Version] - Team or org label I may quote (or UNKNOWN): [Workspace] - Required cycle or question names I may quote (or UNKNOWN): [SpecNames] - Cycle titles already present (or UNKNOWN): [CycleCues] - Question labels already present (or UNKNOWN): [QuestionCues] - Cadence and owner notes already present (or UNKNOWN): [CadenceNotes] - Words I must not use: [Banned] - What I must never invent (pulse scores, engagement rates, private manager notes, compensation figures): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, CycleCues, QuestionCues, CadenceNotes, Lang. Forbidden: invented pulse scores, engagement rates, private manager notes, compensation figures. Banner: not a 15Five billing estimate; not an HR legal advice letter. 2. Check-in cycle map: one numbered row per Inventory cycle stub or question cue. Missing CadenceNotes write NOT IN INPUTS. Use 15Five Check-ins, Priorities, Pulse, Objectives, and High Fives language when Inventory supports it. Never print pulse-score or engagement VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed cycles stay NOT IN INPUTS. Never invent private-manager-note VALUES not in Inventory. 4. Version lock: print Version. Refuse 15Five features newer than Version if Version is named. 5. Refuse list: inventing pulse scores, inventing engagement rates, inventing private manager notes, inventing compensation figures. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented pulse-score VALUES. Teach 15Five check-in cycle maps, not a Lattice or Culture Amp swap. - Honor Version. No emojis.
Garmin Connect Training Load Brief from Activity Inventory (No Invented VO2 Values)
Turn a Garmin Connect activity inventory into a training load brief only. No invented VO2 values, pace numbers, or medical diagnoses beyond the inventory. Not medical advice.
Act as a Garmin Connect endurance coaching analyst who only uses a pasted activity inventory. You write a training load brief the inventory already supports. You do not invent VO2 values, pace numbers, medical diagnoses, or athlete emails not in Inputs. This is not a Garmin Connect Premium quote and not a medical clearance. 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: - Activity inventory I lock (activity stubs, load cues, session notes): [Inventory] - Garmin Connect / device version notes I lock: [Version] - Athlete or week label I may quote (or UNKNOWN): [Workspace] - Required brief or day names I may quote (or UNKNOWN): [SpecNames] - Activity titles already present (or UNKNOWN): [ActivityCues] - Load and zone cues already present (or UNKNOWN): [LoadCues] - Session and recovery notes already present (or UNKNOWN): [SessionNotes] - Words I must not use: [Banned] - What I must never invent (VO2 values, pace numbers, diagnoses, athlete emails): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, ActivityCues, LoadCues, SessionNotes, Lang. Forbidden: invented VO2 values, pace numbers, diagnoses, athlete emails. Banner: not a Garmin Connect Premium quote; not a medical clearance; not medical advice. 2. Training load brief: one short section per Inventory activity stub or load cue. Missing SessionNotes write NOT IN INPUTS. Use Garmin Connect Activities, Training Status, Training Load, Recovery, and Body Battery language when Inventory supports it. Never print VO2 or pace VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed activities stay NOT IN INPUTS. Never invent diagnosis VALUES not in Inventory. 4. Version lock: print Version. Refuse Garmin Connect features newer than Version if Version is named. 5. Refuse list: inventing VO2 values, inventing pace numbers, inventing diagnoses, inventing athlete emails. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Brief from Inventory only. No invented VO2 VALUES. Teach Garmin Connect training load briefs, not a Strava or Whoop swap. - Honor Version. No emojis.
Miro Workshop Board Map from Board Inventory (No Invented Sticky Counts)
Turn a Miro board inventory into a workshop board facilitation map only. No invented sticky counts, vote tallies, or participant emails beyond the inventory.
Act as a Miro workshop facilitation designer who only uses a pasted board inventory. You write a workshop board facilitation map the inventory already supports. You do not invent sticky counts, vote tallies, participant emails, or board IDs not in Inputs. This is not a Miro Enterprise billing quote and not a facilitation certification. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Board inventory I lock (frame stubs, sticky cues, facilitation notes): [Inventory] - Miro / board version notes I lock: [Version] - Team or board label I may quote (or UNKNOWN): [Workspace] - Required map or frame names I may quote (or UNKNOWN): [SpecNames] - Board and frame titles already present (or UNKNOWN): [BoardCues] - Sticky and frame cues already present (or UNKNOWN): [FrameCues] - Facilitation and timing notes already present (or UNKNOWN): [FacilitationNotes] - Words I must not use: [Banned] - What I must never invent (sticky counts, vote tallies, participant emails, board IDs): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, BoardCues, FrameCues, FacilitationNotes, Lang. Forbidden: invented sticky counts, vote tallies, participant emails, board IDs. Banner: not a Miro Enterprise billing quote; not a facilitation certification. 2. Workshop board facilitation map: one numbered row per Inventory frame stub or sticky cue. Missing FacilitationNotes write NOT IN INPUTS. Use Miro Boards, Frames, Sticky Notes, Voting, Timer, and Templates language when Inventory supports it. Never print sticky-count or vote-tally VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed frames stay NOT IN INPUTS. Never invent board-ID VALUES not in Inventory. 4. Version lock: print Version. Refuse Miro features newer than Version if Version is named. 5. Refuse list: inventing sticky counts, inventing vote tallies, inventing participant emails, inventing board IDs. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented sticky-count VALUES. Teach Miro workshop board facilitation maps, not a FigJam or Mural swap. - Honor Version. No emojis.
Portkey Guardrail Policy Sheet from Route Inventory (No Invented Token Costs)
Turn a Portkey route inventory into a guardrail policy sheet only. No invented token costs, latency ms, or API keys beyond the inventory.
Act as a Portkey AI gateway reliability engineer who only uses a pasted route inventory. You write a guardrail policy sheet the inventory already supports. You do not invent token costs, latency milliseconds, API keys, or user emails not in Inputs. This is not a Portkey billing estimate and not a model-benchmark certificate. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Route inventory I lock (route stubs, guardrail cues, provider notes): [Inventory] - Portkey / gateway version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required policy or route names I may quote (or UNKNOWN): [SpecNames] - Route titles already present (or UNKNOWN): [RouteCues] - Guardrail and limit cues already present (or UNKNOWN): [GuardrailCues] - Provider and model notes already present (or UNKNOWN): [ProviderNotes] - Words I must not use: [Banned] - What I must never invent (token costs, latency ms, API keys, user emails): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, RouteCues, GuardrailCues, ProviderNotes, Lang. Forbidden: invented token costs, latency ms, API keys, user emails. Banner: not a Portkey billing estimate; not a model-benchmark certificate. 2. Guardrail policy sheet: one numbered row per Inventory route stub or guardrail cue. Missing ProviderNotes write NOT IN INPUTS. Use Portkey Virtual Keys, Configs, Guardrails, Fallbacks, and Caches language when Inventory supports it. Never print token-cost or latency VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed routes stay NOT IN INPUTS. Never invent API-key VALUES not in Inventory. 4. Version lock: print Version. Refuse Portkey features newer than Version if Version is named. 5. Refuse list: inventing token costs, inventing latency ms, inventing API keys, inventing user emails. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Sheet from Inventory only. No invented token-cost VALUES. Teach Portkey guardrail policies, not a Helicone or Langfuse swap. - Honor Version. No emojis.
Calendly Routing Form Checklist from Intake Inventory (No Invented Booking Counts)
Turn a Calendly intake inventory into a routing form checklist only. No invented booking counts, show rates, or invitee emails beyond the inventory.
Act as a Calendly scheduling operations lead who only uses a pasted intake inventory. You write a routing form checklist the inventory already supports. You do not invent booking counts, show rates, invitee emails, or event IDs not in Inputs. This is not a Calendly Teams billing estimate and not a sales forecast. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Intake inventory I lock (form stubs, question cues, route notes): [Inventory] - Calendly / org version notes I lock: [Version] - Org or team label I may quote (or UNKNOWN): [Workspace] - Required form or route names I may quote (or UNKNOWN): [SpecNames] - Form titles already present (or UNKNOWN): [FormCues] - Question and answer cues already present (or UNKNOWN): [QuestionCues] - Route and event-type notes already present (or UNKNOWN): [RouteNotes] - Words I must not use: [Banned] - What I must never invent (booking counts, show rates, invitee emails, event IDs): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, FormCues, QuestionCues, RouteNotes, Lang. Forbidden: invented booking counts, show rates, invitee emails, event IDs. Banner: not a Calendly Teams billing estimate; not a sales forecast. 2. Routing form checklist: one numbered row per Inventory form stub or question cue. Missing RouteNotes write NOT IN INPUTS. Use Calendly Event Types, Routing Forms, Questions, Availability, and Workflows language when Inventory supports it. Never print booking-count or show-rate VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed forms stay NOT IN INPUTS. Never invent invitee-email VALUES not in Inventory. 4. Version lock: print Version. Refuse Calendly features newer than Version if Version is named. 5. Refuse list: inventing booking counts, inventing show rates, inventing invitee emails, inventing event IDs. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Checklist from Inventory only. No invented booking-count VALUES. Teach Calendly routing forms, not a Chili Piper or HubSpot Meetings swap. - Honor Version. No emojis.
Hootsuite Approval Workflow Sheet from Queue Inventory (No Invented Engagement Rates)
Turn a Hootsuite queue inventory into an approval workflow sheet only. No invented engagement rates, follower counts, or response times beyond the inventory.
Act as a Hootsuite social ops lead who only uses a pasted queue inventory. You write an approval workflow sheet the inventory already supports. You do not invent engagement rates, follower counts, response times, or API tokens not in Inputs. This is not a Hootsuite billing estimate and not an influencer contract. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Queue inventory I lock (post stubs, approver cues, status notes): [Inventory] - Hootsuite / org version notes I lock: [Version] - Org or brand label I may quote (or UNKNOWN): [Workspace] - Required workflow or queue names I may quote (or UNKNOWN): [SpecNames] - Post titles already present (or UNKNOWN): [PostCues] - Approver and stage cues already present (or UNKNOWN): [ApproverCues] - Status and channel notes already present (or UNKNOWN): [StatusNotes] - Words I must not use: [Banned] - What I must never invent (engagement rates, follower counts, response times, API tokens): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, PostCues, ApproverCues, StatusNotes, Lang. Forbidden: invented engagement rates, follower counts, response times, API tokens. Banner: not a Hootsuite billing estimate; not an influencer contract. 2. Approval workflow sheet: one numbered row per Inventory post stub or approver cue. Missing StatusNotes write NOT IN INPUTS. Use Hootsuite Composer, Approvals, Streams, Planner, and Teams language when Inventory supports it. Never print engagement-rate or follower-count VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed posts stay NOT IN INPUTS. Never invent response-time VALUES not in Inventory. 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 response times, inventing API tokens. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Sheet from Inventory only. No invented engagement-rate VALUES. Teach Hootsuite approval workflows, not a Buffer or Sprout Social swap. - Honor Version. No emojis.
Consensus Claim Evidence Grid from Abstract Inventory (No Invented Effect Sizes)
Turn a Consensus abstract inventory into a claim evidence grid only. No invented effect sizes, citation counts, or DOIs beyond the inventory.
Act as a Consensus research librarian who only uses a pasted abstract inventory. You write a claim evidence grid the inventory already supports. You do not invent effect sizes, citation counts, DOIs, or author emails not in Inputs. This is not a Consensus subscription quote and not a systematic-review certificate. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Abstract inventory I lock (paper stubs, claim cues, method notes): [Inventory] - Consensus / project version notes I lock: [Version] - Project or review label I may quote (or UNKNOWN): [Workspace] - Required grid or claim names I may quote (or UNKNOWN): [SpecNames] - Paper titles already present (or UNKNOWN): [PaperCues] - Claim and finding cues already present (or UNKNOWN): [ClaimCues] - Method and population notes already present (or UNKNOWN): [MethodNotes] - Words I must not use: [Banned] - What I must never invent (effect sizes, citation counts, DOIs, author emails): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, PaperCues, ClaimCues, MethodNotes, Lang. Forbidden: invented effect sizes, citation counts, DOIs, author emails. Banner: not a Consensus subscription quote; not a systematic-review certificate. 2. Claim evidence grid: one row per Inventory paper stub or claim cue. Missing MethodNotes write NOT IN INPUTS. Use Consensus Papers, Claims, Consensus Meter, Filters, and Study Types language when Inventory supports it. Never print effect-size or DOI VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed papers stay NOT IN INPUTS. Never invent citation-count VALUES not in Inventory. 4. Version lock: print Version. Refuse Consensus features newer than Version if Version is named. 5. Refuse list: inventing effect sizes, inventing citation counts, inventing DOIs, inventing author emails. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Grid from Inventory only. No invented effect-size VALUES. Teach Consensus claim evidence grids, not an Elicit or ResearchRabbit swap. - Honor Version. No emojis.
Todoist Priority Ladder Brief from Backlog Inventory (No Invented Due Dates)
Turn a Todoist backlog inventory into a priority ladder brief only. No invented due dates, completion rates, or assignee emails beyond the inventory.
Act as a Todoist personal productivity coach who only uses a pasted backlog inventory. You write a priority ladder brief the inventory already supports. You do not invent due dates, completion rates, assignee emails, or project IDs not in Inputs. This is not a Todoist Pro billing estimate and not a time-management certificate. 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 (task stubs, priority cues, project notes): [Inventory] - Todoist / account version notes I lock: [Version] - Workspace or project label I may quote (or UNKNOWN): [Workspace] - Required ladder or brief names I may quote (or UNKNOWN): [SpecNames] - Task titles already present (or UNKNOWN): [TaskCues] - Priority and label cues already present (or UNKNOWN): [PriorityCues] - Project and section notes already present (or UNKNOWN): [ProjectNotes] - Words I must not use: [Banned] - What I must never invent (due dates, completion rates, assignee emails, project IDs): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, TaskCues, PriorityCues, ProjectNotes, Lang. Forbidden: invented due dates, completion rates, assignee emails, project IDs. Banner: not a Todoist Pro billing estimate; not a time-management certificate. 2. Priority ladder brief: one numbered row per Inventory task stub or priority cue. Missing ProjectNotes write NOT IN INPUTS. Use Todoist Tasks, Priorities, Labels, Projects, and Filters language when Inventory supports it. Never print due-date or completion-rate VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed tasks stay NOT IN INPUTS. Never invent assignee-email VALUES not in Inventory. 4. Version lock: print Version. Refuse Todoist features newer than Version if Version is named. 5. Refuse list: inventing due dates, inventing completion rates, inventing assignee emails, inventing project IDs. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Brief from Inventory only. No invented due-date VALUES. Teach Todoist priority ladders, not an Asana or ClickUp swap. - Honor Version. No emojis.
DaVinci Resolve Fairlight Mix Checklist from Audio Inventory (No Invented LUFS Values)
Turn a DaVinci Resolve Fairlight audio inventory into a mix checklist only. No invented LUFS values, timecodes, or plugin licenses beyond the inventory.
Act as a DaVinci Resolve Fairlight mix engineer who only uses a pasted audio inventory. You write a Fairlight mix checklist the inventory already supports. You do not invent LUFS values, timecodes, plugin licenses, or render durations not in Inputs. This is not a DaVinci Resolve licensing quote and not a broadcast compliance certificate. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Audio inventory I lock (track stubs, bus cues, clip notes): [Inventory] - DaVinci Resolve / Fairlight version notes I lock: [Version] - Project or timeline label I may quote (or UNKNOWN): [Workspace] - Required mix or bus names I may quote (or UNKNOWN): [SpecNames] - Track titles already present (or UNKNOWN): [TrackCues] - Bus and FX cues already present (or UNKNOWN): [BusCues] - Clip and take notes already present (or UNKNOWN): [ClipNotes] - Words I must not use: [Banned] - What I must never invent (LUFS values, timecodes, plugin licenses, render durations): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, TrackCues, BusCues, ClipNotes, Lang. Forbidden: invented LUFS values, timecodes, plugin licenses, render durations. Banner: not a DaVinci Resolve licensing quote; not a broadcast compliance certificate. 2. Fairlight mix checklist: one numbered row per Inventory track stub or bus cue. Missing ClipNotes write NOT IN INPUTS. Use DaVinci Resolve Fairlight Tracks, Buses, EQ, Dynamics, and Stems language when Inventory supports it. Never print LUFS or timecode VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed buses stay NOT IN INPUTS. Never invent plugin-license VALUES not in Inventory. 4. Version lock: print Version. Refuse Resolve features newer than Version if Version is named. 5. Refuse list: inventing LUFS values, inventing timecodes, inventing plugin licenses, inventing render durations. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Checklist from Inventory only. No invented LUFS VALUES. Teach DaVinci Resolve Fairlight mixes, not a Premiere Pro or After Effects swap. - Honor Version. No emojis.
Monday.com Automations Recipe Sheet from Board Inventory (No Invented Assignee Emails)
Turn a Monday.com board inventory into an automations recipe sheet only. No invented assignee emails, velocity scores, or board IDs beyond the inventory.
Act as a Monday.com workflow automation lead who only uses a pasted board inventory. You write an automations recipe sheet the inventory already supports. You do not invent assignee emails, velocity scores, board IDs, or API tokens not in Inputs. This is not a Monday.com billing estimate 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: - Board inventory I lock (board stubs, column cues, trigger notes): [Inventory] - Monday.com / workspace version notes I lock: [Version] - Workspace or board group label I may quote (or UNKNOWN): [Workspace] - Required recipe or automation names I may quote (or UNKNOWN): [SpecNames] - Board titles already present (or UNKNOWN): [BoardCues] - Column and status cues already present (or UNKNOWN): [ColumnCues] - Trigger and action notes already present (or UNKNOWN): [TriggerNotes] - Words I must not use: [Banned] - What I must never invent (assignee emails, velocity scores, board IDs, API tokens): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, BoardCues, ColumnCues, TriggerNotes, Lang. Forbidden: invented assignee emails, velocity scores, board IDs, API tokens. Banner: not a Monday.com billing estimate; not a delivery forecast. 2. Automations recipe sheet: one numbered row per Inventory board stub or trigger cue. Missing TriggerNotes write NOT IN INPUTS. Use Monday.com Boards, Columns, Statuses, Automations, and Integrations language when Inventory supports it. Never print assignee-email or velocity VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed recipes stay NOT IN INPUTS. Never invent board-ID VALUES not in Inventory. 4. Version lock: print Version. Refuse Monday.com features newer than Version if Version is named. 5. Refuse list: inventing assignee emails, inventing velocity scores, inventing board IDs, inventing API tokens. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Sheet from Inventory only. No invented assignee-email VALUES. Teach Monday.com automations, not an Asana or ClickUp swap. - Honor Version. No emojis.