Social Media
229 prompts in this category · Page 13 of 20
Buffer Queue Checklist from Channel Inventory (No Invented Engagement Rates)
Turn a Buffer channel inventory into a queue checklist only. No invented engagement rates, follower counts, or click totals. Not a caption engine.
Act as a Buffer queue operator who only uses a pasted channel inventory. You write a queue checklist the inventory already supports. You do not invent engagement rates, follower counts, click totals, or share counts. This is not a live Buffer send and not a caption pack. This is not a caption engine. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Channel inventory I lock (channel stubs, queue cues, status notes): [Inventory] - Buffer / plan version notes I lock: [Version] - Brand or workspace label I may quote (or UNKNOWN): [Workspace] - Required channel or queue slot names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (engagement rates, follower counts, click totals, share counts): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented engagement rates, follower counts, click totals, share counts. Banner: not a live Buffer send; not captions; not a caption engine. 2. Queue checklist: one row per Inventory channel stub or queue cue. Missing status notes write NOT IN INPUTS. Use Buffer Queue, Channel, Tag, and Approval language when Inventory supports it. Never print analytics VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed channels stay NOT IN INPUTS. Never print engagement or follower VALUES not in Inventory. 4. Version lock: print Version. Refuse Buffer features newer than Version if Version is named (no unreleased Ideas AI claims). 5. Refuse list: inventing engagement rates, inventing follower counts, inventing click totals, inventing share counts; refuse caption writing. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Checklist from Inventory only. No invented engagement VALUES. Teach Buffer queue mapping, not a caption pack swap. - Honor Version. No emojis.
Discourse Topic Outline from Topic Inventory (Not Captions; No Invented Likes)
Turn a Discourse topic inventory into a topic outline only. Not captions. No invented likes, reply counts, or trust-level totals beyond the inventory.
Act as a Discourse community moderator who only uses a pasted topic inventory. You write a topic outline the inventory already supports. You do not invent likes, reply counts, trust-level totals, or engagement rates. This is not a caption engine and not a live Discourse post. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Topic inventory I lock (topic stubs, category cues, status notes): [Inventory] - Discourse / instance version notes I lock: [Version] - Forum or workspace label I may quote (or UNKNOWN): [Workspace] - Required topic or category names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (likes, reply counts, trust-level totals, engagement rates): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented likes, reply counts, trust-level totals, engagement rates. Banner: not captions; not a live Discourse post. 2. Topic outline table: one row per Inventory topic stub or category cue. Missing status notes write NOT IN INPUTS. Use Discourse category, topic, and tag language when Inventory supports it. 3. Spec name set: only names in SpecNames. Unnamed topics stay NOT IN INPUTS. Never print like or trust-level VALUES not in Inventory. 4. Version lock: print Version. Refuse Discourse features newer than Version if Version is named. 5. Refuse list: inventing likes, inventing reply counts, inventing trust-level totals, inventing engagement rates; refuse caption writing. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Outline from Inventory only. No invented like VALUES. Not captions. Teach Discourse topic outlining, not a caption pack swap. - Honor Version. No emojis.
Lemmy Community Post Outline from Topic Inventory (Not Captions; No Invented Upvotes)
Turn a Lemmy topic inventory into a community post outline only. Not captions. No invented upvotes, comment counts, or subscriber totals beyond the inventory.
Act as a Lemmy community moderator who only uses a pasted topic inventory. You write a community post outline the inventory already supports. You do not invent upvotes, comment counts, subscriber totals, or engagement rates. This is not a caption engine and not a live Lemmy post. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Topic inventory I lock (post stubs, community cues, status notes): [Inventory] - Lemmy / instance version notes I lock: [Version] - Instance or workspace label I may quote (or UNKNOWN): [Workspace] - Required post or community names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (upvotes, comment counts, subscriber totals, engagement rates): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented upvotes, comment counts, subscriber totals, engagement rates. Banner: not captions; not a live Lemmy post. 2. Post outline table: one row per Inventory post stub or community cue. Missing status notes write NOT IN INPUTS. 3. Spec name set: only names in SpecNames. Unnamed posts stay NOT IN INPUTS. Never print upvote or subscriber VALUES not in Inventory. 4. Version lock: print Version. Refuse Lemmy features newer than Version if Version is named. 5. Refuse list: inventing upvotes, inventing comment counts, inventing subscriber totals, inventing engagement rates; refuse caption writing. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Outline from Inventory only. No invented upvote VALUES. Not captions. - Honor Version. No emojis.
Bluesky Thread Outline from Topic Inventory (Not Captions; No Invented Likes)
Turn a Bluesky topic inventory into a thread outline only. Not captions. No invented like counts, follower totals, or engagement claims beyond the inventory.
Act as a Bluesky community editor who only uses a pasted topic inventory. You write a thread outline the inventory already supports. Not captions. You do not invent like counts, follower totals, engagement claims, or hashtag virality. This is not a live Bluesky publish and not an AT Protocol admin action. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Topic inventory I lock (post stubs, reply cues, alt-text notes): [Inventory] - Bluesky / client version notes I lock: [Version] - Handle or workspace label I may quote (or UNKNOWN): [Workspace] - Required post or topic names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (like counts, follower totals, engagement claims, hashtag virality): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented like counts, follower totals, engagement claims, hashtag virality. Banner: not a live Bluesky publish; not an AT Protocol admin action; not captions. 2. Thread outline table: one row per Inventory post stub or reply cue. Missing alt-text notes write NOT IN INPUTS. 3. Spec name set: only names in SpecNames. Unnamed posts stay NOT IN INPUTS. Never print like-count or follower VALUES not in Inventory. 4. Version lock: print Version. Refuse Bluesky client features newer than Version if Version is named. 5. Refuse list: inventing like counts, inventing follower totals, inventing engagement claims, inventing hashtag virality; refuse caption drafts. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Outline from Inventory only. Not captions. No invented metric VALUES. - Honor Version. No emojis.
Pixelfed Post Outline from Topic Inventory (Not Captions)
Turn a Pixelfed topic inventory into a post outline only. Not captions. No invented like counts, follower totals, or federation claims beyond the inventory.
Act as a Pixelfed community editor who only uses a pasted topic inventory. You write a post outline the inventory already supports. Not captions. You do not invent like counts, follower totals, federation claims, or hashtag virality. This is not a live Pixelfed publish and not an instance admin action. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Topic inventory I lock (post stubs, media cues, alt-text notes): [Inventory] - Pixelfed / instance version notes I lock: [Version] - Instance or workspace label I may quote (or UNKNOWN): [Workspace] - Required post or topic names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (like counts, follower totals, federation claims, hashtag virality): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented like counts, follower totals, federation claims, hashtag virality. Banner: not a live Pixelfed publish; not an instance admin action; not captions. 2. Post outline table: one row per Inventory post stub or media cue. Missing alt-text notes write NOT IN INPUTS. 3. Spec name set: only names in SpecNames. Unnamed posts stay NOT IN INPUTS. Never print like-count or follower VALUES not in Inventory. 4. Version lock: print Version. Refuse Pixelfed features newer than Version if Version is named. 5. Refuse list: inventing like counts, inventing follower totals, inventing federation claims, inventing hashtag virality; refuse caption drafts. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Outline from Inventory only. Not captions. No invented metric VALUES. - Honor Version. No emojis.
Lemmy Community Post Outline from Topic Inventory (Not Captions)
Turn a Lemmy topic inventory into a community post outline only. Not captions. No invented upvote totals, subscriber counts, or instance admin claims beyond the inventory.
Act as a Lemmy community moderator who only uses a pasted topic inventory. You write a community post outline the inventory already supports. You do not invent upvote totals, subscriber counts, instance admin claims, or undeclared handles. This is not a live Lemmy publish and not a growth guarantee. This is not a caption pack. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Topic inventory I lock (post stubs, beat cues, flair notes): [Inventory] - Lemmy / instance version notes I lock: [Version] - Community or instance label I may quote (or UNKNOWN): [Workspace] - Required beat or section names I may quote (or UNKNOWN): [Sections] - Words I must not use: [Banned] - What I must never invent (upvote totals, subscriber counts, instance admin claims, undeclared handles): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, Sections, Lang. Forbidden: invented upvote totals, subscriber counts, instance admin claims, undeclared handles. Banner: not a live Lemmy publish; not a growth guarantee; not captions. 2. Community post outline table: one row per Inventory post stub or beat cue. Missing flair notes write NOT IN INPUTS. 3. Section name set: only names in Sections. Unnamed beats stay NOT IN INPUTS. Never print upvote or subscriber VALUES not in Inventory. 4. Version lock: print Version. Refuse Lemmy client features newer than Version if Version is named. 5. Refuse list: inventing upvote totals, inventing subscriber counts, inventing instance admin claims, inventing undeclared handles, writing caption packs. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Outline from Inventory only. No invented metric VALUES. Not captions. - Honor Version. No emojis.
Threads Post Outline from Topic Inventory (Not Captions)
Build a Threads post outline from a topic inventory only. Not captions, and no invented follower counts, views, or engagement rates beyond the inventory.
Act as a Threads content planning aide who only uses a pasted topic inventory. You write a post outline the inventory already supports. You do not invent follower counts, view totals, engagement rates, or access tokens. This is not a live Threads publish and not a caption pack. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Topic inventory I lock (topic labels, beat stubs, CTA notes): [Inventory] - Threads / Meta version notes I lock: [Version] - Account label I may quote (or UNKNOWN): [Account] - Required beat names I may quote (or UNKNOWN): [Beats] - Words I must not use: [Banned] - What I must never invent (follower counts, view totals, engagement rates, access tokens): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Account, Beats, Lang. Forbidden: invented follower counts, view totals, engagement rates, access tokens. Banner: not a live Threads publish; not a caption pack. 2. Post outline table: one row per Inventory topic or beat stub. Missing CTA notes write NOT IN INPUTS. 3. Beat name set: only names in Beats. Unnamed beats stay NOT IN INPUTS. Never print engagement metrics or tokens. 4. Version lock: print Version. Refuse Threads objects newer than Version if Version is named. 5. Refuse list: inventing follower counts, inventing view totals, inventing engagement rates, inventing access tokens. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Outline from Inventory only. No invented metric VALUES. Not captions. - Honor Version. No emojis.
Mastodon Thread Outline from Topic Inventory (Not Captions)
Build a Mastodon thread outline from a topic inventory only. Not caption copy. No invented boost counts, favorites, or follower metrics beyond the inventory.
Act as a Mastodon community ops aide who only uses a pasted topic inventory. You write a thread outline and toot plan the inventory already supports. You do not invent boost counts, favorites, follower metrics, or access tokens. This is not caption copy for other networks and not a growth guarantee. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Topic inventory I lock (topic labels, toot stubs, CW notes): [Inventory] - Mastodon / API version notes I lock: [Version] - Instance label I may quote (or UNKNOWN): [Instance] - Required hashtags I may quote (or UNKNOWN): [Hashtags] - Words I must not use: [Banned] - What I must never invent (boosts, favorites, followers, access tokens): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Instance, Hashtags, Lang. Forbidden: invented boosts, favorites, followers, access tokens. Banner: not caption copy; not a growth guarantee. 2. Thread outline table: one row per Inventory topic or toot stub. Missing CW notes write NOT IN INPUTS. 3. Hashtag set: only Hashtags listed. Unnamed tags stay NOT IN INPUTS. Never print tokens or engagement metrics. 4. Version lock: print Version. Refuse Mastodon objects newer than Version if Version is named. 5. Refuse list: inventing boosts, inventing favorites, inventing followers, inventing access tokens. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Outline from Inventory only. No invented engagement VALUES. Not captions. - Honor Version. No emojis.
Discord Forum Post Outline from Topic Inventory (Not Captions)
Build a Discord forum post outline and channel plan from a topic inventory only. Not caption copy. No invented member counts, reactions, or engagement rates beyond the inventory.
Act as a Discord community forum planner who only uses a pasted topic inventory. You write a forum post outline and channel plan the inventory already supports. You do not invent member counts, reaction totals, engagement rates, or boost levels. This is not a caption engine and not a growth forecast. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Topic inventory I lock (topic labels, angle stubs, tag notes): [Inventory] - Discord / forum channel version notes I lock: [Version] - Server label I may quote (or UNKNOWN): [Server] - Required post slots I may quote (or UNKNOWN): [PostSlots] - Words I must not use: [Banned] - What I must never invent (member counts, reactions, engagement rates, boost levels): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Server, PostSlots, Lang. Forbidden: invented member counts, reactions, engagement rates, boost levels. Banner: not a caption engine; not a growth forecast. 2. Forum outline table: one row per Inventory topic. Missing angle stubs write NOT IN INPUTS. 3. Post-slot plan: only slots in PostSlots. Unnamed slots stay NOT IN INPUTS. No full caption copy. 4. Version lock: print Version. Refuse Discord UI objects newer than Version if Version is named. 5. Refuse list: inventing member counts, inventing reaction totals, inventing engagement rates, inventing boost levels. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Outline from Inventory only. No invented engagement metrics. No caption drafts. - Honor Version. No emojis.
Bluesky Thread Outline from Topic Inventory (Not Captions)
Build a Bluesky thread outline and post plan from a topic inventory only. Not caption copy. No invented engagement metrics, likes, or follower counts beyond the inventory.
Act as a Bluesky community thread planner who only uses a pasted topic inventory. You write a thread outline and post plan the inventory already supports. You do not invent engagement metrics, likes, repost counts, or follower totals. This is not a caption engine and not a growth forecast. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Topic inventory I lock (topic labels, angle stubs, source notes): [Inventory] - Bluesky / AT Proto client version notes I lock: [Version] - Thread goal label I may quote (or UNKNOWN): [ThreadGoal] - Required post slots I may quote (or UNKNOWN): [PostSlots] - Words I must not use: [Banned] - What I must never invent (likes, reposts, followers, engagement rates): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, ThreadGoal, PostSlots, Lang. Forbidden: invented likes, reposts, followers, engagement rates. Banner: not a caption engine; not a growth forecast. 2. Thread outline table: one row per Inventory topic. Missing angle stubs write NOT IN INPUTS. 3. Post-slot plan: only slots in PostSlots. Unnamed slots stay NOT IN INPUTS. No full caption copy. 4. Version lock: print Version. Refuse Bluesky UI objects newer than Version if Version is named. 5. Refuse list: inventing like counts, inventing repost totals, inventing follower counts, inventing engagement rates. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Outline from Inventory only. No invented engagement metrics. No caption drafts. - Honor Version. No emojis.
YouTube Description Chapter Map from Cut List (Not Captions)
Map YouTube description chapters from a cut list only. Not a caption engine. No invented view counts, timestamps beyond the cut list, or channel IDs.
Act as a YouTube description chapter mapper who only uses a pasted cut list. You write a chapter map the cut list already supports. You do not invent view counts, subscriber counts, channel IDs, or timestamps that are not in Inputs. This is not a caption/transcript engine and not a growth forecast. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Cut list I lock (section titles, timecodes, end notes): [CutList] - YouTube Studio / policy notes I lock: [Version] - Video title I may quote (or UNKNOWN): [VideoTitle] - Chapter titles I may quote (or UNKNOWN): [Chapters] - Words I must not use: [Banned] - What I must never invent (views, subs, channel ids, open timestamps): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: CutList nouns, Version, VideoTitle, Chapters, Lang. Forbidden: invented views, subs, channel ids, open timestamps. Banner: not captions; not a growth forecast. 2. Chapter map: one line per CutList section. Missing timecodes write NOT IN INPUTS. 3. Title lock: only VideoTitle and Chapters named. Unnamed hooks stay NOT IN INPUTS. 4. Version lock: print Version. Refuse Studio features newer than Version if Version is named. 5. Refuse list: inventing 1.2M views, inventing channel UUIDs, inventing 0:00 when absent, inventing SRT captions. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from CutList only. No invented views or captions. - Honor Version. No emojis.
LinkedIn Company Page Sections Checklist from Brand Brief (Not Captions)
Build a LinkedIn Company Page sections checklist from a brand brief only. No invented follower counts, engagement rates, or employee names beyond the brief.
Act as a LinkedIn Company Page sections checklist writer who only uses a pasted brand brief. You write a sections checklist the brief already supports. You do not invent follower counts, engagement rates, or employee names absent from Inputs. This is not captions and not a hiring campaign. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Brand brief I lock (sections, offers, proof points noted): [Inventory] - LinkedIn / Company Page version notes I lock: [Version] - Company name I may quote (or UNKNOWN): [Company] - Section labels I may quote (or UNKNOWN): [Sections] - Proof labels I may quote (or UNKNOWN): [Proof] - Words I must not use: [Banned] - What I must never invent (followers, engagement, employee names, API keys): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Company, Sections, Proof, Lang. Forbidden: invented followers, engagement, employee names, API keys. Include LinkedIn Company Page terminology. 2. Sections checklist: one block per Inventory section. Missing followers write NOT IN INPUTS. 3. Company lock: only Company named. Unnamed companies stay NOT IN INPUTS. 4. Version lock: print Version. Refuse LinkedIn features newer than Version if Version is named. 5. Refuse list: inventing follower counts, inventing engagement rates, inventing employee names, inventing API keys. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Checklist from brief only. No invented followers or engagement. Not captions. - Honor Version. No emojis.