📱

Social Media

229 prompts in this category · Page 14 of 20

Twitch Channel Panels Checklist from Streamer Brief (Not Captions)
📱 Social Media

Twitch Channel Panels Checklist from Streamer Brief (Not Captions)

Ppromptstudio·Sep 6, 2026
No rating

Build a Twitch channel panels checklist from a streamer brief only. Not captions. No invented viewer counts, affiliate codes, or stream keys.

Act as a Twitch channel panels checklist writer who only uses a pasted streamer brief. You write a panels checklist the brief already supports. You do not invent viewer counts, affiliate codes, or stream keys absent from Inputs. This is not a caption pack and not a growth hacking plan. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Streamer brief I lock (panels, links, schedule cues noted): [Brief] - Twitch / panels version notes I lock: [Version] - Channel name I may quote (or UNKNOWN): [Channel] - Panel titles I may quote (or UNKNOWN): [Panels] - Schedule labels I may quote (or UNKNOWN): [Schedule] - Words I must not use: [Banned] - What I must never invent (viewer counts, affiliate codes, stream keys, Discord invites beyond Brief): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Brief nouns, Version, Channel, Panels, Schedule, Lang. Forbidden: invented viewer counts, affiliate codes, stream keys, Discord invites beyond Brief. Include Twitch channel panels terminology. 2. Panels checklist: one line per Brief panel cue. Missing viewer counts write NOT IN INPUTS. 3. Schedule lock: only Schedule named. Unnamed days stay NOT IN INPUTS. 4. Version lock: print Version. Refuse Twitch panel features newer than Version if Version is named. 5. Refuse list: inventing average viewers, inventing Amazon affiliate codes, inventing stream keys, inventing Discord invite codes beyond Brief. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Checklist from Brief only. Not captions. No invented viewer counts. - Honor Version. No emojis.

not captionstwitch channel panelsstreamer brief
Discord Server Role Permission Matrix from Role Inventory (Not Captions)
📱 Social Media

Discord Server Role Permission Matrix from Role Inventory (Not Captions)

Ppromptstudio·Sep 6, 2026
No rating

Build a Discord server role permission matrix from a role inventory only. Not captions. No invented member counts or token secrets.

Act as a Discord server role permission matrix writer who only uses a pasted role inventory. You write a permission matrix the inventory already supports. You do not invent member counts, bot tokens, or channel IDs absent from Inputs. This is not a caption pack and not a community marketing plan. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Role inventory I lock (roles, permissions, channels noted): [Inventory] - Discord / permission version notes I lock: [Version] - Server name I may quote (or UNKNOWN): [Server] - Channel names I may quote (or UNKNOWN): [Channels] - Bot role names I may quote (or UNKNOWN): [Bots] - Words I must not use: [Banned] - What I must never invent (member counts, bot tokens, channel snowflakes, invite codes): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Server, Channels, Bots, Lang. Forbidden: invented member counts, bot tokens, channel snowflakes, invite codes. Include Discord role permission terminology. 2. Permission matrix: one row per Inventory role. Columns: role, allow cues, deny cues. Missing member counts write NOT IN INPUTS. 3. Channels lock: only Channels named. Unnamed categories stay NOT IN INPUTS. 4. Version lock: print Version. Refuse Discord permission features newer than Version if Version is named. 5. Refuse list: inventing member counts, inventing bot tokens, inventing channel snowflake IDs, inventing invite vanity codes. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Matrix from Inventory only. Not captions. No invented member counts. - Honor Version. No emojis.

not captionsdiscord rolespermission matrix
YouTube Community Post Outline from Talking Points (No Invented Engagement)
📱 Social Media

YouTube Community Post Outline from Talking Points (No Invented Engagement)

Ppromptstudio·Sep 6, 2026
No rating

Outline a YouTube Community post from talking points only. No invented engagement, view counts, or comment quotes. Not a LinkedIn/TikTok/Instagram/Pinterest/Reddit/X caption engine.

Act as a YouTube Community post outliner who only uses pasted talking points. You write a Community post outline the talking points already support. You do not invent engagement rates, view counts, or comment quotes. This is not a growth guarantee and not a LinkedIn, TikTok, Instagram, Pinterest, Reddit, or X caption engine. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Talking points I lock (topics, CTAs, poll options noted): [Points] - YouTube / Community post version notes I lock: [Version] - Channel name I may quote (or UNKNOWN): [Channel] - Post type I may quote (text, image, poll, quiz) or UNKNOWN: [Type] - Poll options I may quote (or UNKNOWN): [Poll] - Words I must not use: [Banned] - What I must never invent (engagement, views, comment quotes, subscriber counts): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Points nouns, Version, Channel, Type, Poll, Lang. Forbidden: invented engagement, views, comment quotes, subscriber counts. Include YouTube Community terminology. Explicitly refuse LinkedIn/TikTok/Instagram/Pinterest/Reddit/X caption engines. 2. Community post outline: hook, body bullets from Points, CTA, poll block if Type/Poll support it. Missing fields write NOT IN INPUTS. 3. Poll lock: only Poll options named. Unnamed options stay NOT IN INPUTS. 4. Version lock: print Version. Refuse Community features newer than Version if Version is named. 5. Refuse list: inventing 4.2% engagement, inventing 50k views, inventing comment quotes, inventing subscriber counts, inventing cross-platform captions. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Outline from Points only. No invented engagement or views. - YouTube Community only. Honor Version. No emojis.

no invented engagementyoutube communitytalking points
Hootsuite Content Calendar Sketch from Topic Inventory (No Invented Engagement)
📱 Social Media

Hootsuite Content Calendar Sketch from Topic Inventory (No Invented Engagement)

Ppromptstudio·Sep 6, 2026
No rating

Sketch a Hootsuite content calendar from a topic inventory only. No invented engagement rates, follower counts, or post IDs.

Act as a Hootsuite content calendar sketcher who only uses a pasted topic inventory. You write a calendar sketch the inventory already supports. You do not invent engagement rates, follower counts, or post IDs. This is not a growth guarantee and not a caption-spam engine. 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 (topics, channels, cadence notes): [Inventory] - Hootsuite / planner version notes I lock: [Version] - Channel list I may quote (or UNKNOWN): [Channels] - Slot cap I lock: [Cap] - Words I must not use: [Banned] - What I must never invent (engagement, followers, post ids, dates beyond notes): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Channels, Cap, Lang. Forbidden: invented engagement, followers, post ids. Include Hootsuite calendar terminology. 2. Calendar table: at most Cap slots. Columns: topic, channel, note. Missing dates write NOT IN INPUTS. 3. Channel gaps: Channels unnamed in Inventory stay NOT IN INPUTS. 4. Version lock: print Version. Refuse planner features newer than Version if Version is named. 5. Refuse list: inventing 4.2% engagement, inventing 50k followers, inventing post ids, inventing viral claims. 6. Compliance pass: quote Banned and Never hits. Cut them. Print slot count. Format as Format. Constraints: - Sketch from Inventory only. No invented engagement or followers. - Honor Cap and Version. No emojis. Not a caption engine.

hootsuite calendartopic inventoryno invented engagement
Matrix Space Welcome Rules from Mod Brief (Not Legal Advice) (Domain Pack)
📱 Social Media

Matrix Space Welcome Rules from Mod Brief (Not Legal Advice) (Domain Pack)

Ppromptstudio·Sep 6, 2026
No rating

Draft Matrix space welcome and house rules from a mod brief. Not legal advice. No invented bans.

Act as a Matrix community moderator who only uses a locked mod brief. You draft space welcome text and house rules the brief already supports. This is not legal advice. You do not invent bans, legal citations, or moderation policies not in Inputs. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Mod brief I lock: [Brief] - Space or room name I lock: [Space] - Allowed topics I lock (or NONE): [Topics] - Escalation path I lock (or UNKNOWN): [Escalation] - Ban list seeds I lock (or NONE): [Bans] - Section cap I lock: [Cap] - Words I must not use: [Banned] - What I must never invent (legal advice, bans, citations): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Brief nouns, Space, Topics, Escalation, Bans, Cap, Lang. Forbidden: invented legal advice, bans, citations. Add one-line not-legal-advice banner. 2. Welcome + house rules outline: at most Cap sections from Brief only. 3. Rule bullets: Topics and Bans only. Missing rules NOT IN INPUTS. 4. Escalation card: Escalation only; else UNKNOWN. 5. Refuse list: inventing criminal bans, inventing statute cites, inventing mute durations, inventing ToS clauses. 6. Compliance pass: quote Banned and Never hits. Cut them. Print section count. Format as Format. Constraints: - Rules from Brief only. Not legal advice. No invented bans. - Honor Cap. No emojis.

not legal advicemod briefmatrix space rules
Circle.so Community Guidelines from Mod Brief (Not Captions, Not Legal Advice)
📱 Social Media

Circle.so Community Guidelines from Mod Brief (Not Captions, Not Legal Advice)

Ppromptstudio·Sep 6, 2026
No rating

Draft Circle.so community guidelines from a mod brief only. Not a caption engine. Not legal advice. No invented member counts or banned-word lists beyond the brief.

Act as a Circle.so community guidelines editor who only uses a pasted mod brief. You write space rules the brief already supports. You do not invent member counts, ban lists beyond the brief, or legal threats. This is not a caption engine, not marketing copy, and not legal advice. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Mod brief I lock (allowed topics, bans, tone): [Brief] - Space names I may quote (or UNKNOWN): [Spaces] - Rule cap I lock: [Cap] - Words I must not use: [Banned] - What I must never invent (member counts, extra bans, legal threats, fees): [Never] - Output format: [Format] - Language: [Lang] - Escalation contact I may quote (or UNKNOWN): [Escalation] Generate: 1. Honesty ledger: Brief nouns, Spaces, Cap, Escalation, Lang. Forbidden: invented member counts, extra bans, legal threats, fees. Banner: not legal advice; not captions. 2. Guidelines list: at most Cap rules grounded in Brief. Missing policies write NOT IN INPUTS. 3. Space-specific notes: only for Spaces named. Unnamed spaces stay NOT IN INPUTS. 4. Escalation: quote Escalation or UNKNOWN; do not invent a legal counsel email. 5. Refuse list: inventing 12k members, inventing a fine schedule, inventing caption CTAs, inventing Terms of Service clauses. 6. Compliance pass: quote Banned and Never hits. Cut them. Print rule count. Format as Format. Constraints: - Guidelines from Brief only. Not captions. Not legal advice. - Honor Cap. No emojis.

not captionsmod briefcircle.so guidelines
Mastodon Community Covenant from Values Brief (Not Legal Advice)
📱 Social Media

Mastodon Community Covenant from Values Brief (Not Legal Advice)

Ppromptstudio·Sep 5, 2026
No rating

Draft a Mastodon community covenant from a values brief. Not legal advice. No invented member counts or ban histories.

Act as an editor for this job: Mastodon Community Covenant from Values Brief (Not Legal Advice). Goal: Draft a Mastodon community covenant from a values brief. Not legal advice. No invented member counts or ban histories. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Source packet I lock: [Source] - Cap I lock: [Cap] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language: [Lang] - Escalation or UNKNOWN field: [Extra] Generate: 1. Honesty ledger: Source nouns, Cap, Extra, Lang. Forbidden items from Never. Add any required not-advice banner for the domain. 2. Main draft: deliver the titled job using Source only. Honor Cap. 3. Allowlist or checklist of items present in Source; missing items NOT IN INPUTS. 4. Escalation/gaps: quote Extra or UNKNOWN; list five owed fields. 5. Refuse list: inventing identifiers, inventing fees, inventing stats, inventing paths, exceeding Cap. 6. Compliance pass: quote Banned and Never hits. Cut them. Print counts. Format as Format. Constraints: - Stay inside the job boundary of Mastodon Community Covenant from Values Brief (Not Legal Advice). - No invented evidence. Honor Cap. No emojis.

mastodoncommunity covenantvalues brief
Twitch Stream Schedule Outline from Content Pillars (No Invented Viewers)
📱 Social Media

Twitch Stream Schedule Outline from Content Pillars (No Invented Viewers)

Ppromptstudio·Sep 5, 2026
No rating

Outline a Twitch stream schedule from content pillars. No invented viewer counts, revenue, or guest names.

Act as an editor for this job: Twitch Stream Schedule Outline from Content Pillars (No Invented Viewers). Goal: Outline a Twitch stream schedule from content pillars. No invented viewer counts, revenue, or guest names. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Source packet I lock: [Source] - Cap I lock: [Cap] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language: [Lang] - Escalation or UNKNOWN field: [Extra] Generate: 1. Honesty ledger: Source nouns, Cap, Extra, Lang. Forbidden items from Never. Add any required not-advice banner for the domain. 2. Main draft: deliver the titled job using Source only. Honor Cap. 3. Allowlist or checklist of items present in Source; missing items NOT IN INPUTS. 4. Escalation/gaps: quote Extra or UNKNOWN; list five owed fields. 5. Refuse list: inventing identifiers, inventing fees, inventing stats, inventing paths, exceeding Cap. 6. Compliance pass: quote Banned and Never hits. Cut them. Print counts. Format as Format. Constraints: - Stay inside the job boundary of Twitch Stream Schedule Outline from Content Pillars (No Invented Viewers). - No invented evidence. Honor Cap. No emojis.

twitchstream schedulecontent pillars
Discourse Forum Guidelines from Community Brief (Not Legal Advice)
📱 Social Media

Discourse Forum Guidelines from Community Brief (Not Legal Advice)

Ppromptstudio·Sep 5, 2026
No rating

Draft Discourse forum guidelines from a community brief. Not legal advice. No invented member counts or ban histories.

Act as an editor for this job: Discourse Forum Guidelines from Community Brief (Not Legal Advice). Goal: Draft Discourse forum guidelines from a community brief. Not legal advice. No invented member counts or ban histories. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Source packet I lock: [Source] - Cap I lock: [Cap] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language: [Lang] - Escalation or UNKNOWN field: [Extra] Generate: 1. Honesty ledger: Source nouns, Cap, Extra, Lang. Forbidden items from Never. Add any required not-advice banner for the domain. 2. Main draft: deliver the titled job using Source only. Honor Cap. 3. Allowlist or checklist of items present in Source; missing items NOT IN INPUTS. 4. Escalation/gaps: quote Extra or UNKNOWN; list five owed fields. 5. Refuse list: inventing identifiers, inventing fees, inventing stats, inventing paths, exceeding Cap. 6. Compliance pass: quote Banned and Never hits. Cut them. Print counts. Format as Format. Constraints: - Stay inside the job boundary of Discourse Forum Guidelines from Community Brief (Not Legal Advice). - No invented evidence. Honor Cap. No emojis.

community briefdiscourseforum guidelines
Slack Channel Guidelines from Community Brief (Not Legal Advice)
📱 Social Media

Slack Channel Guidelines from Community Brief (Not Legal Advice)

Ppromptstudio·Sep 5, 2026
No rating

Draft Slack channel guidelines from a community brief. Not legal advice. No invented member counts or ban histories.

Act as an editor for this job: Slack Channel Guidelines from Community Brief (Not Legal Advice). Goal: Draft Slack channel guidelines from a community brief. Not legal advice. No invented member counts or ban histories. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Source packet I lock: [Source] - Cap I lock: [Cap] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language: [Lang] - Escalation or UNKNOWN field: [Extra] Generate: 1. Honesty ledger: Source nouns, Cap, Extra, Lang. Forbidden items from Never. Add any required not-advice banner for the domain. 2. Main draft: deliver the titled job using Source only. Honor Cap. 3. Allowlist or checklist of items present in Source; missing items NOT IN INPUTS. 4. Escalation/gaps: quote Extra or UNKNOWN; list five owed fields. 5. Refuse list: inventing identifiers, inventing fees, inventing stats, inventing paths, exceeding Cap. 6. Compliance pass: quote Banned and Never hits. Cut them. Print counts. Format as Format. Constraints: - Stay inside the job boundary of Slack Channel Guidelines from Community Brief (Not Legal Advice). - No invented evidence. Honor Cap. No emojis.

community briefslackchannel guidelines
YouTube Channel About from Creator Notes (No Invented Subscriber Counts)
📱 Social Media

YouTube Channel About from Creator Notes (No Invented Subscriber Counts)

Ppromptstudio·Sep 4, 2026
No rating

Draft a YouTube Channel About section from creator notes. No invented subscriber counts, view stats, or brand deals.

Act as an editor for this job: YouTube Channel About from Creator Notes (No Invented Subscriber Counts). Goal: Draft a YouTube Channel About section from creator notes. No invented subscriber counts, view stats, or brand deals. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Source packet I lock: [Source] - Cap I lock: [Cap] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language: [Lang] - Escalation or UNKNOWN field: [Extra] Generate: 1. Honesty ledger: Source nouns, Cap, Extra, Lang. Forbidden items from Never. Add any required not-advice banner for the domain. 2. Main draft: deliver the titled job using Source only. Honor Cap. 3. Allowlist or checklist of items present in Source; missing items NOT IN INPUTS. 4. Escalation/gaps: quote Extra or UNKNOWN; list five owed fields. 5. Refuse list: inventing identifiers, inventing fees, inventing stats, inventing paths, exceeding Cap. 6. Compliance pass: quote Banned and Never hits. Cut them. Print counts. Format as Format. Constraints: - Stay inside the job boundary of YouTube Channel About from Creator Notes (No Invented Subscriber Counts). - No invented evidence. Honor Cap. No emojis.

youtube aboutchannel descriptioncreator notes
Bluesky Starter Pack Copy from Niche Notes (No Invented Follower Counts) with example still
📱 Social Media

Bluesky Starter Pack Copy from Niche Notes (No Invented Follower Counts) with example still

Ppromptstudio·Sep 4, 2026
No rating

Draft Bluesky starter pack copy from niche notes. No invented follower counts, handles, or engagement stats.

Act as an editor for this job: Bluesky Starter Pack Copy from Niche Notes (No Invented Follower Counts). Goal: Draft Bluesky starter pack copy from niche notes. No invented follower counts, handles, or engagement stats. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Source packet I lock: [Source] - Cap I lock: [Cap] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language: [Lang] - Escalation or UNKNOWN field: [Extra] Generate: 1. Honesty ledger: Source nouns, Cap, Extra, Lang. Forbidden items from Never. Add any required not-advice banner for the domain. 2. Main draft: deliver the titled job using Source only. Honor Cap. 3. Allowlist or checklist of items present in Source; missing items NOT IN INPUTS. 4. Escalation/gaps: quote Extra or UNKNOWN; list five owed fields. 5. Refuse list: inventing identifiers, inventing fees, inventing stats, inventing paths, exceeding Cap. 6. Compliance pass: quote Banned and Never hits. Cut them. Print counts. Format as Format. Constraints: - Stay inside the job boundary of Bluesky Starter Pack Copy from Niche Notes (No Invented Follower Counts). - No invented evidence. Honor Cap. No emojis.

blueskystarter packniche notes