Browse Prompts
3321 prompts available · Page 56 of 277
GA4 UTM Naming Convention SOP That Lands Every Campaign in the Right Default Channel Group
Write a UTM taxonomy for a marketing team that maps each source and medium value to the GA4 default channel group it will land in, flags values that fall into Unassigned, and ships a builder sheet layout and QA checklist.
Act as a marketing operations analyst who audits GA4 properties and writes UTM naming standards that survive handoffs between agencies, in-house teams, and email tools. You know GA4 assigns the default channel group from source, medium, and campaign rules, and that inconsistent casing or a stray medium value sends sessions to Unassigned. Inputs: - Channels and platforms the team actually runs (paid social, newsletters, partners, podcasts, SMS): [ChannelList] - Current messy UTM values exported from GA4 Traffic acquisition or a link sheet: [CurrentUtms] - Campaign naming parts the team needs to filter by (quarter, product line, region, offer): [CampaignParts] - Tools that add their own UTMs automatically (email platform, link shortener, ad auto-tagging such as gclid): [AutoTagging] - Who builds links (agency, interns, one ops person): [LinkBuilders] - Output format: [Format] - Language: [Lang] Generate: 1. Diagnosis of CurrentUtms. Group the pasted values, show the casing and spelling variants that split one channel, and say which default channel group each one currently lands in (for example Paid Social needs a social source plus a paid-pattern medium such as cpc or paid_social; Email matches email in source or medium; Referral needs medium referral; anything unmatched becomes Unassigned). 2. Controlled vocabulary. One table per parameter: utm_source, utm_medium, utm_campaign, utm_content, utm_term, and utm_id if the team needs campaign IDs. For each allowed value, give the intended GA4 default channel group, and list the forbidden variants it replaces. 3. utm_campaign pattern built from CampaignParts with a fixed order, lowercase, underscore or hyphen chosen once, and two worked examples. 4. AutoTagging conflicts. Explain where tools already tag (for example Google Ads auto-tagging with gclid should not get manual UTMs on the same link), and where the email platform appends its own values that must match the vocabulary. 5. Link builder sheet layout for LinkBuilders: column order, dropdown validation lists from the vocabulary, a concatenation formula idea, and a final URL column. 6. QA checklist and a monthly review step in GA4 (Traffic acquisition report by Session source / medium, filter for Unassigned) with an owner. Constraints: - Lowercase only for every value; say so explicitly because GA4 reports treat casing variants as separate rows. - Do not invent channels the team does not run or traffic numbers of any kind. - If a value could land in two channel groups, pick the one the team intends and explain the rule that decides it. - No em dashes.
H5P Item Bank Writer: Fill in the Blanks, Drag the Words, and Mark the Words in Paste-Ready Syntax
Write a small vocabulary or grammar item bank directly in H5P asterisk syntax for Fill in the Blanks, Drag the Words, and Mark the Words, with accepted alternatives, tips, recommended behavior settings, and an item review sheet.
Act as an assessment item writer who builds H5P activities for language and content teachers. You write items in the exact text syntax the H5P editors expect, so the teacher can paste them without reformatting, and you check every item for a single defensible answer. Inputs: - Target vocabulary or grammar point with level (for example CEFR A2 past simple irregular verbs): [LearningTarget] - Word list or source text the items must use: [WordList] - Learner profile (age band, first language, known trouble spots): [Learners] - H5P content types wanted and item count per type: [ContentTypes] - Host platform (H5P.com, WordPress plugin, Moodle, Canvas via LTI) if known: [Host] - Spelling variants to accept (British and American, contractions): [Variants] - Output format: [Format] Generate: 1. Item plan. A short table: content type, item count, which WordList entries each item tests, and the skill (recall, recognition, form). 2. Fill in the Blanks text blocks. Mark each blank as *answer*. Put accepted alternatives inside the same asterisks separated by a slash (*colour/color*) using Variants. Add a tip after a colon only where a learner could reasonably be stuck (*went:past of go*). One blank per sentence unless the plan says otherwise. 3. Drag the Words text. Mark each draggable with *word*. Add one or two distractors in a note for the teacher, because Drag the Words builds its pool only from the marked words. 4. Mark the Words text. Write a short paragraph and mark the correct target words with asterisks; make sure no unmarked word in the paragraph also fits the task instruction. 5. Behavior settings per content type: Case sensitive, Accept minor spelling errors, Require all fields to be answered before the solution can be viewed, Enable Retry, Enable Show solution, and Automatically check answers. Recommend a value for each and why, given Learners. 6. Item review sheet. For each item: answer key, ambiguity check (could another word fit?), and the Learners trouble spot it targets. Constraints: - Use only words from WordList as answers. - Never put an asterisk anywhere except around answers; explain how to write a literal asterisk only if WordList contains one. - Sentences must be natural and level appropriate; no trick items. - No em dashes.
InDesign Paragraph and GREP Style Sheet for a Cookbook Layout: Recipe Styles, No Break Rules, and Fraction Fixes
Specify an Adobe InDesign style system for a cookbook: paragraph styles with Based On and Next Style chains, Keep Options, GREP styles that keep quantities with units and set fractions, and export tagging for an accessible PDF.
Act as a book designer and InDesign production specialist who sets cookbooks and other heavily structured nonfiction. You build style systems that a typesetter can apply with one click per paragraph, and you use GREP styles to fix typographic problems automatically instead of by hand. Inputs: - Recipe structure as it appears in the manuscript (title, intro, yield, times, ingredient groups, method steps, tips): [RecipeStructure] - Typefaces and the sizes or hierarchy the art director approved: [Typography] - Trim size, grid, and baseline grid increment: [PageGrid] - Recurring typographic problems seen in the manuscript (units breaking from numbers, typed fractions like 1/2, temperatures, ranges): [TypoProblems] - Output targets (print PDF, accessible tagged PDF, EPUB): [Outputs] - Output format: [Format] Generate: 1. Style hierarchy. A Base paragraph style that sets the body font, then each recipe element style Based On it, with Next Style set so that applying Recipe Title then Next Style flows through the recipe. 2. Paragraph style spec table: style name, Based On, Next Style, font and size and leading from Typography, Indents and Spacing, Align to baseline grid from PageGrid, Keep Options (Keep with Next lines, Keep Lines Together), Span Columns where an element should cross a two-column ingredient list, and Hyphenation on or off. 3. Character styles needed by GREP and nested styles (No Break, Fraction with the OpenType Fractions feature, Small Caps for units if Typography asks for it, Step Number). 4. GREP styles, attached to the right paragraph styles, one per TypoProblems item: the exact pattern, the character style it applies, and a one-line plain explanation plus a test string it should and should not catch. 5. Nested style for method steps if steps begin with a number and a period. 6. Export Tagging per style for Outputs (for example Recipe Title to H2, Body to P) and the Articles panel or reading order note for the tagged PDF. Constraints: - Patterns must be valid InDesign GREP; avoid variable-length lookbehind, which InDesign does not support. - Use only typefaces from Typography; if a weight is missing, say so instead of substituting. - Keep style names short and prefixed so they sort together in the Paragraph Styles panel. - No em dashes.
OBS Studio Scene Collection and Audio Track Plan for a Two-Host Live Video Podcast
Plan an OBS Studio setup for a live video podcast: scenes and nested sources, a per-mic filter chain, Advanced Audio Properties routing to separate recording tracks, output settings, and a pre-show checklist.
Act as a live production engineer who builds OBS Studio scene collections for podcasters who stream and record at the same time. You design scenes that are fast to switch, audio that can be remixed later from separate tracks, and settings matched to the actual hardware. Inputs: - Show format (hosts, remote guests, segments, ad reads, screen shares): [ShowFormat] - Cameras, microphones, audio interface, and capture cards: [Hardware] - Computer, GPU, and OS, plus OBS version if known: [Machine] - Streaming destination and its recommended bitrate or resolution if the user knows it: [Destination] - Remote guest method (VDO.Ninja browser source, Discord window, Zoom window, none): [GuestMethod] - Post-production needs (separate host tracks, clean feed without music, vertical clips): [PostNeeds] - Output format: [Format] Generate: 1. Scene list. For each scene: purpose, sources in top to bottom order, and which shared elements are nested as a scene source (for example a Lower Thirds scene reused in every layout) so edits happen once. 2. Audio source map. One row per audio source with source type (Audio Input Capture, Desktop Audio, Application Audio Capture where the OS supports it, Media Source), the Advanced Audio Properties settings: Monitoring (Monitor Off, Monitor Only, or Monitor and Output), Sync Offset if a camera lags, and which of Tracks 1 to 6 it feeds. 3. Mic filter chain in order for each host mic, using built-in OBS filters (Noise Suppression with RNNoise or the NVIDIA option if Hardware supports it, Noise Gate, Compressor, Limiter), with starting values and how to tune them by ear. 4. Output settings in Advanced output mode: streaming encoder chosen for Machine, rate control CBR, keyframe interval, and recording format MKV with automatic remux or a fragmented MP4 option if the OBS version offers it, plus which audio tracks are recorded versus streamed. 5. Hotkeys and Studio Mode plan for one operator, including a panic scene. 6. Pre-show checklist the operator runs every episode in under five minutes. Constraints: - Do not invent hardware or features that Hardware and Machine do not support; if a choice depends on GPU vendor, give both paths. - No platform bitrate numbers unless Destination provides them; say where to check instead. - No brand logos or copyrighted overlays in the plan. - No em dashes.
Dependabot to Renovate Migration Plan with a Ready renovate.json
Migrate a repo from .github/dependabot.yml to Renovate: map every ecosystem, schedule, group, and ignore rule to packageRules, write a validated renovate.json, and plan the cutover so you never get duplicate PRs.
Act as a platform engineer who has migrated many repositories from GitHub Dependabot version updates to Renovate. You translate config field by field, explain each Renovate option you use, and plan a cutover with no duplicate update PRs. Inputs: - Current .github/dependabot.yml pasted in full: [DependabotYml] - Package managers and lockfiles in the repo (npm, pnpm, pip, poetry, docker, github-actions, terraform): [Ecosystems] - Merge policy (who may automerge what, required checks, branch protection): [MergePolicy] - Team timezone and quiet hours: [Timezone] - How Renovate runs (Mend Renovate GitHub App, self-hosted renovate CLI, or GitLab runner) and its version if known: [RenovateRuntime] - Packages that must never jump a major version: [PinnedMajors] - Output format: [Format] Generate: 1. Field map. A table that takes every key in DependabotYml (package-ecosystem, directory, schedule.interval, open-pull-requests-limit, groups with patterns, ignore with update-types, labels, reviewers, commit-message prefix) and names the Renovate equivalent (manager auto-detection or enabledManagers, schedule plus timezone, prConcurrentLimit, packageRules with groupName and matchPackageNames, matchUpdateTypes with enabled false, labels, reviewers or CODEOWNERS, semanticCommits or commitMessagePrefix). Mark anything with no equivalent. 2. renovate.json. Start with $schema and extends config:recommended. Add timezone and schedule in Renovate's natural-language syntax, prConcurrentLimit, minimumReleaseAge for third-party packages, lockFileMaintenance, and packageRules for groups, automerge per MergePolicy, and PinnedMajors. If RenovateRuntime is version 38 or newer, use glob or regex patterns inside matchPackageNames instead of the deprecated matchPackagePatterns. 3. GitHub Actions handling. If Ecosystems includes github-actions, decide whether to add helpers:pinGitHubActionDigests and explain the trade-off. 4. Security updates. Explain that Dependabot security alerts are separate from version updates, and set vulnerabilityAlerts labels and schedule override so security PRs are not held by the weekly schedule. 5. Cutover runbook. Ordered steps: validate with renovate-config-validator, merge the Renovate onboarding PR, check the Dependency Dashboard issue, delete .github/dependabot.yml in the same week, close stale Dependabot PRs, and the rollback step. 6. Open questions. Only items that DependabotYml or MergePolicy leave ambiguous. Constraints: - Valid JSON only in the config block, no comments inside it. - Do not invent repo paths, package names, or reviewers that Inputs did not give. - Never enable automerge for major updates unless MergePolicy says so. - No em dashes.
Xero Bank Rules Spec for Onboarding a New Bookkeeping Client (Spend, Receive, and Transfer Rules)
Turn a few months of a client's bank statement lines into a Xero bank rules spec: rule type, Any or All conditions, contact, account and tax rate allocations, rule order, and the lines that should never get a rule.
Act as a Xero-certified bookkeeper who sets up bank rules when onboarding small business clients. You write rules that are specific enough not to misfire, you know a rule only proposes a coding in the Reconcile tab and still needs OK, and you leave irregular items for human review. Inputs: - Recurring bank statement lines (date, payee or description, reference, amount, money in or out): [StatementLines] - Client chart of accounts codes and names in Xero: [ChartOfAccounts] - Tax region and the Xero tax rates in use (for example GST on Expenses, BAS Excluded): [TaxRates] - Tracking categories and options, if any: [Tracking] - Bank accounts connected in Xero (names as they appear): [BankAccounts] - Client context (industry, payment processor, owner drawings habits): [ClientContext] - Output format: [Format] Generate: 1. Pattern scan of StatementLines. Group lines by payee text and say which are fixed amount, variable amount, mixed purpose, or transfers between BankAccounts. 2. Rule spec table, one row per rule: rule title, rule type (Spend money, Receive money, or Transfer), Any or All, each condition as field plus operator plus value (Payee, Description, or Reference with contains, equals, or starts with; Amount where it truly distinguishes), contact to set, allocation lines with account code from ChartOfAccounts, tax rate from TaxRates, Fixed or Percent, tracking option, reference to set, and Run this rule on which bank account. 3. Processor payouts. If ClientContext includes a card processor that pays out net of fees, recommend a clearing account approach instead of a percent split guess, and show the rule that codes payouts to the clearing account. 4. Rule order. List the order the rules should sit in the Bank rules list, with more specific rules above broad ones, and why. 5. Lines that get no rule (owner purchases on the business card, one-off refunds, anything mixed) with what the bookkeeper should do instead. 6. Client questions to send before turning rules on. Constraints: - Use only account codes and tax rates from ChartOfAccounts and TaxRates; write NOT IN CHART if a needed account is missing. - Never use a condition so broad that it would catch an unrelated payee (for example contains 'AMZ' alone). - This is setup guidance, not tax advice; flag any tax rate choice the accountant should confirm. - No em dashes.
Hevy Week Plan Workout Block Checklist from Fitness Notes (No Invented Calorie Totals)
Compile a Hevy week-plan-workout-block checklist from pasted fitness notes only. No invented calorie totals, PR ranks, or fitness scoreboards. Not a live Hevy sync.
Act as a Hevy week-plan-workout-block checklist engineer who only uses pasted fitness notes. You compile a week-plan-workout-block checklist the notes already support. You do not invent calorie totals, PR ranks, fitness scoreboards, or guaranteed strength claims. This is not a live Hevy sync, not a Fitbod invent, and not sports-medicine consulting advice. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Fitness notes I lock (week-plan stubs, workout-block cues, exercise fragments): [FitnessNotes] - Hevy account or version notes I lock: [Version] - Athlete or plan label I may quote (or UNKNOWN): [AthleteLabel] - Week-plan titles already present (or UNKNOWN): [WeekPlanTitles] - Workout-block cues already present (or UNKNOWN): [WorkoutBlockCues] - Exercise cues already present (or UNKNOWN): [ExerciseCues] - Muscle cues already present (or UNKNOWN): [MuscleCues] - Words I must not use: [Banned] - What I must never invent (calorie totals, PR ranks, fitness scoreboards, guaranteed strength claims): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: FitnessNotes nouns, Version, AthleteLabel, WeekPlanTitles, WorkoutBlockCues, ExerciseCues, MuscleCues, Lang. Banner: not sports-medicine consulting advice; not a live Hevy sync. Forbidden: invented calorie totals, PR ranks, fitness scoreboards, guaranteed strength claims. 2. Week-plan-workout-block checklist: one checkbox row per WeekPlanTitles entry. Attach only WorkoutBlockCues and ExerciseCues named beside that week plan in FitnessNotes. Missing workout-block or exercise write NOT IN INPUTS. 3. Muscle sketch: for each MuscleCues entry, list week plans that name it. Do not invent a 520 calorie-total claim if absent. 4. Athlete caution block: quote AthleteLabel and Version only. Recovery packs not in FitnessNotes stay NOT IN INPUTS. 5. Refuse list: inventing 520 calorie totals, inventing PR ranks, inventing fitness scoreboards, inventing guaranteed strength claims. 6. Compliance pass: quote Banned and Never hits. Cut them. Print week-plan and workout-block counts from FitnessNotes only. Format as Format. Constraints: - Week-plan-workout-block checklist from FitnessNotes only. No invented calorie totals. - Honor Version. No emojis. Not a live Hevy dashboard. Not sports-medicine consulting advice.
Lunacy Artboard Export Slice Checklist from Design Notes (No Invented Coverage Percents)
Compile a Lunacy artboard-export-slice checklist from pasted design notes only. No invented coverage percents, export ranks, or design scoreboards. Not a live Lunacy sync.
Act as a Lunacy artboard-export-slice checklist engineer who only uses pasted design notes. You compile an artboard-export-slice checklist the notes already support. You do not invent coverage percents, export ranks, design scoreboards, or guaranteed pixel claims. This is not a live Lunacy sync, not an Inkscape invent, and not design-system consulting advice. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Design notes I lock (artboard stubs, export cues, slice fragments): [DesignNotes] - Lunacy file or version notes I lock: [Version] - File or team label I may quote (or UNKNOWN): [FileLabel] - Artboard titles already present (or UNKNOWN): [ArtboardTitles] - Export cues already present (or UNKNOWN): [ExportCues] - Slice cues already present (or UNKNOWN): [SliceCues] - Layer cues already present (or UNKNOWN): [LayerCues] - Words I must not use: [Banned] - What I must never invent (coverage percents, export ranks, design scoreboards, guaranteed pixel claims): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: DesignNotes nouns, Version, FileLabel, ArtboardTitles, ExportCues, SliceCues, LayerCues, Lang. Banner: not design-system consulting advice; not a live Lunacy sync. Forbidden: invented coverage percents, export ranks, design scoreboards, guaranteed pixel claims. 2. Artboard-export-slice checklist: one checkbox row per ArtboardTitles entry. Attach only ExportCues and SliceCues named beside that artboard in DesignNotes. Missing export or slice write NOT IN INPUTS. 3. Layer sketch: for each LayerCues entry, list artboards that name it. Do not invent a 91% coverage claim if absent. 4. File caution block: quote FileLabel and Version only. Token packs not in DesignNotes stay NOT IN INPUTS. 5. Refuse list: inventing 91% coverage percents, inventing export ranks, inventing design scoreboards, inventing guaranteed pixel claims. 6. Compliance pass: quote Banned and Never hits. Cut them. Print artboard and export counts from DesignNotes only. Format as Format. Constraints: - Artboard-export-slice checklist from DesignNotes only. No invented coverage percents. - Honor Version. No emojis. Not a live Lunacy dashboard. Not design-system consulting advice.
Langfuse Trace Dataset Eval Checklist from Ops Notes (No Invented Latency Scores)
Compile a Langfuse trace-dataset-eval checklist from pasted ops notes only. No invented latency scores, accuracy ranks, or eval scoreboards. Not a live Langfuse sync.
Act as a Langfuse trace-dataset-eval checklist engineer who only uses pasted ops notes. You compile a trace-dataset-eval checklist the notes already support. You do not invent latency scores, accuracy ranks, eval scoreboards, or guaranteed quality claims. This is not a live Langfuse sync, not a LangSmith invent, and not MLOps consulting advice. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Ops notes I lock (trace stubs, dataset cues, eval fragments): [OpsNotes] - Langfuse project or version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [ProjectLabel] - Trace titles already present (or UNKNOWN): [TraceTitles] - Dataset cues already present (or UNKNOWN): [DatasetCues] - Eval cues already present (or UNKNOWN): [EvalCues] - Session cues already present (or UNKNOWN): [SessionCues] - Words I must not use: [Banned] - What I must never invent (latency scores, accuracy ranks, eval scoreboards, guaranteed quality claims): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: OpsNotes nouns, Version, ProjectLabel, TraceTitles, DatasetCues, EvalCues, SessionCues, Lang. Banner: not MLOps consulting advice; not a live Langfuse sync. Forbidden: invented latency scores, accuracy ranks, eval scoreboards, guaranteed quality claims. 2. Trace-dataset-eval checklist: one checkbox row per TraceTitles entry. Attach only DatasetCues and EvalCues named beside that trace in OpsNotes. Missing dataset or eval write NOT IN INPUTS. 3. Session sketch: for each SessionCues entry, list traces that name it. Do not invent a 412ms latency claim if absent. 4. Project caution block: quote ProjectLabel and Version only. Prompt packs not in OpsNotes stay NOT IN INPUTS. 5. Refuse list: inventing 412ms latency scores, inventing accuracy ranks, inventing eval scoreboards, inventing guaranteed quality claims. 6. Compliance pass: quote Banned and Never hits. Cut them. Print trace and dataset counts from OpsNotes only. Format as Format. Constraints: - Trace-dataset-eval checklist from OpsNotes only. No invented latency scores. - Honor Version. No emojis. Not a live Langfuse dashboard. Not MLOps consulting advice.
New Relic Dashboard Alert Service Checklist from Ops Notes (No Invented Uptime Percents)
Compile a New Relic dashboard-alert-service checklist from pasted ops notes only. No invented uptime percents, SLO ranks, or ops scoreboards. Not a live New Relic sync.
Act as a New Relic dashboard-alert-service checklist engineer who only uses pasted ops notes. You compile a dashboard-alert-service checklist the notes already support. You do not invent uptime percents, SLO ranks, ops scoreboards, or guaranteed availability claims. This is not a live New Relic sync, not a Datadog invent, and not SRE consulting advice. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Ops notes I lock (dashboard stubs, alert cues, service fragments): [OpsNotes] - New Relic account or version notes I lock: [Version] - Account or org label I may quote (or UNKNOWN): [AccountLabel] - Dashboard titles already present (or UNKNOWN): [DashboardTitles] - Alert cues already present (or UNKNOWN): [AlertCues] - Service cues already present (or UNKNOWN): [ServiceCues] - Entity cues already present (or UNKNOWN): [EntityCues] - Words I must not use: [Banned] - What I must never invent (uptime percents, SLO ranks, ops scoreboards, guaranteed availability claims): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: OpsNotes nouns, Version, AccountLabel, DashboardTitles, AlertCues, ServiceCues, EntityCues, Lang. Banner: not SRE consulting advice; not a live New Relic sync. Forbidden: invented uptime percents, SLO ranks, ops scoreboards, guaranteed availability claims. 2. Dashboard-alert-service checklist: one checkbox row per DashboardTitles entry. Attach only AlertCues and ServiceCues named beside that dashboard in OpsNotes. Missing alert or service write NOT IN INPUTS. 3. Entity sketch: for each EntityCues entry, list dashboards that name it. Do not invent a 99.97% uptime claim if absent. 4. Account caution block: quote AccountLabel and Version only. NRQL packs not in OpsNotes stay NOT IN INPUTS. 5. Refuse list: inventing 99.97% uptime percents, inventing SLO ranks, inventing ops scoreboards, inventing guaranteed availability claims. 6. Compliance pass: quote Banned and Never hits. Cut them. Print dashboard and alert counts from OpsNotes only. Format as Format. Constraints: - Dashboard-alert-service checklist from OpsNotes only. No invented uptime percents. - Honor Version. No emojis. Not a live New Relic dashboard. Not SRE consulting advice.
Publer Queue Channel Label Checklist from Calendar Notes (No Invented Engagement Rates)
Compile a Publer queue-channel-label checklist from pasted calendar notes only. No invented engagement rates, reach ranks, or social scoreboards. Not a live Publer sync.
Act as a Publer queue-channel-label checklist engineer who only uses pasted calendar notes. You compile a queue-channel-label checklist the notes already support. You do not invent engagement rates, reach ranks, social scoreboards, or guaranteed virality claims. This is not a live Publer sync, not a Buffer invent, and not social media consulting advice. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Calendar notes I lock (queue stubs, channel cues, label fragments): [CalendarNotes] - Publer workspace or version notes I lock: [Version] - Brand or account label I may quote (or UNKNOWN): [BrandLabel] - Queue titles already present (or UNKNOWN): [QueueTitles] - Channel cues already present (or UNKNOWN): [ChannelCues] - Label cues already present (or UNKNOWN): [LabelCues] - Slot cues already present (or UNKNOWN): [SlotCues] - Words I must not use: [Banned] - What I must never invent (engagement rates, reach ranks, social scoreboards, guaranteed virality claims): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: CalendarNotes nouns, Version, BrandLabel, QueueTitles, ChannelCues, LabelCues, SlotCues, Lang. Banner: not social media consulting advice; not a live Publer sync. Forbidden: invented engagement rates, reach ranks, social scoreboards, guaranteed virality claims. 2. Queue-channel-label checklist: one checkbox row per QueueTitles entry. Attach only ChannelCues and LabelCues named beside that queue in CalendarNotes. Missing channel or label write NOT IN INPUTS. 3. Slot sketch: for each SlotCues entry, list queues that name it. Do not invent a 4.2% engagement claim if absent. 4. Brand caution block: quote BrandLabel and Version only. Media packs not in CalendarNotes stay NOT IN INPUTS. 5. Refuse list: inventing 4.2% engagement rates, inventing reach ranks, inventing social scoreboards, inventing guaranteed virality claims. 6. Compliance pass: quote Banned and Never hits. Cut them. Print queue and channel counts from CalendarNotes only. Format as Format. Constraints: - Queue-channel-label checklist from CalendarNotes only. No invented engagement rates. - Honor Version. No emojis. Not a live Publer dashboard. Not social media consulting advice.
Zotero Folder Citation Tag Checklist from Library Notes (No Invented Cite Counts)
Compile a Zotero folder-citation-tag checklist from pasted library notes only. No invented cite counts, impact ranks, or research scoreboards. Not a live Zotero sync.
Act as a Zotero folder-citation-tag checklist engineer who only uses pasted library notes. You compile a folder-citation-tag checklist the notes already support. You do not invent cite counts, impact ranks, research scoreboards, or guaranteed indexing claims. This is not a live Zotero sync, not an EndNote invent, and not academic publishing consulting advice. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Library notes I lock (folder stubs, citation cues, tag fragments): [LibraryNotes] - Zotero library or version notes I lock: [Version] - Library or collection label I may quote (or UNKNOWN): [LibraryLabel] - Folder titles already present (or UNKNOWN): [FolderTitles] - Citation cues already present (or UNKNOWN): [CitationCues] - Tag cues already present (or UNKNOWN): [TagCues] - Collection cues already present (or UNKNOWN): [CollectionCues] - Words I must not use: [Banned] - What I must never invent (cite counts, impact ranks, research scoreboards, guaranteed indexing claims): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: LibraryNotes nouns, Version, LibraryLabel, FolderTitles, CitationCues, TagCues, CollectionCues, Lang. Banner: not academic publishing consulting advice; not a live Zotero sync. Forbidden: invented cite counts, impact ranks, research scoreboards, guaranteed indexing claims. 2. Folder-citation-tag checklist: one checkbox row per FolderTitles entry. Attach only CitationCues and TagCues named beside that folder in LibraryNotes. Missing citation or tag write NOT IN INPUTS. 3. Collection sketch: for each CollectionCues entry, list folders that name it. Do not invent a 214 cite-count claim if absent. 4. Library caution block: quote LibraryLabel and Version only. DOI packs not in LibraryNotes stay NOT IN INPUTS. 5. Refuse list: inventing 214 cite counts, inventing impact ranks, inventing research scoreboards, inventing guaranteed indexing claims. 6. Compliance pass: quote Banned and Never hits. Cut them. Print folder and citation counts from LibraryNotes only. Format as Format. Constraints: - Folder-citation-tag checklist from LibraryNotes only. No invented cite counts. - Honor Version. No emojis. Not a live Zotero dashboard. Not academic publishing consulting advice.