📱 Social Media
Twitch Stream Rules and Raid Welcome Pack from a Channel Brief
Write Twitch stream rules and a raid welcome pack from a channel brief. Not a caption engine and not a title/panels pack.
0Reviews
Prompt
Act as a Twitch community ops writer who only uses a pasted channel brief. You write stream rules, a short raid welcome, and a pin-ready summary. You do not invent partner status, subscriber counts, or Twitch policy URLs. This is not a caption engine, not a stream title generator, and not a panels copy pack. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Channel brief (purpose, audience, hard lines, content vibe): [Brief] - Rule count max: [N or 8] - Channel display name I allow: [Channel] - Raid welcome length max (chars): [RaidMax or 280] - Escalation contacts I allow (or UNKNOWN): [Contacts] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Brief nouns, N, Channel, RaidMax, Contacts, Lang. 2. Purpose one-liner from Brief. 3. Up to N stream rules with a short example each. Quote hard lines from Brief. 4. Raid welcome text under RaidMax characters. Print character count. Use Channel only as given. 5. About-panel pin: short rules summary for the channel About or rules panel. 6. Escalation ladder using Contacts or CONTACT UNKNOWN. 7. Refuse: caption packs, inventing partner badges, inventing Twitch ToS clause numbers, inventing sub counts. 8. Compliance pass: Banned and Never. Format as Format. Constraints: - Twitch rules and raid welcome from Brief only. Not captions and not title/panels packs. - Never invent partner status, viewer counts, or policy URLs. - Keep Contacts UNKNOWN when blank. - No emojis.
Instructions
Replace every [bracket] with your details before running. Works on ChatGPT, Claude, and Gemini.
Examples
Example Input
Brief: Cozy indie game nights. Hard lines: no spoilers without spoiler tags, no hate speech, no backseating unless the streamer asks. Audience: casual players and lurkers. Vibe: calm, friendly. N: 5 Channel: PixelKettle RaidMax: 240 Contacts: UNKNOWN Banned: guaranteed partner, invent 12k followers, invent Twitch ToS section Never: invent partner status, invent viewer counts, invent Twitch policy URLs, invent moderator names, invent ban counts Format: ledger + purpose + rules + raid + pin + escalation + refuse + gaps Lang: English
Example Output
1. Ledger. Brief: cozy indie game nights; no spoilers without tags; no hate speech; no backseating unless asked; casual players and lurkers; calm friendly vibe. N=5. Channel PixelKettle. RaidMax 240. Contacts UNKNOWN. Lang English. Forbidden: invent partner status, invent viewer counts, invent Twitch policy URLs, invent moderator names, invent ban counts, guaranteed partner, invent 12k followers, invent Twitch ToS section. 2. Purpose. A Twitch stream rules and raid welcome pack for PixelKettle cozy indie nights (casual players and lurkers). 3. Rules. 1) Spoiler tags required. Example: mark ending talk with spoiler tags before typing plot points. 2) No hate speech. Example: do not attack people for identity or origin. 3) No backseating unless asked. Example: wait for the streamer to invite tips before giving walkthrough steps. 4) Keep the calm vibe. Example: prefer supportive chat over rage bait. 5) Stay on indie-night topics. Example: game talk and chill chat over unrelated spam floods. 4. Raid welcome (chars=178/240). Welcome raiders to PixelKettle cozy indie nights. Spoilers need tags. No hate speech. Please skip backseating unless we ask. Lurkers welcome. Glad you are here. 5. Pin. PixelKettle: cozy indie nights; spoiler tags; no hate; no unsolicited backseating; calm chat. 6. Escalation. CONTACT UNKNOWN. Ladder: remind -> warn -> timeout suggestion for mods -> escalate when Contacts provided. 7. Refuse. Caption packs refused. Partner invent refused. ToS clause invent refused. Sub-count invent refused. 8. Compliance. Banned cut. Gaps: moderator contacts, ban appeal path, language policy, NSFW policy, schedule note. Missing-data policy: if a field was blank, write NOT IN INPUTS rather than guessing. Lock any tool version named in Inputs; if unnamed, write unknown. No invented testimonials, star ratings, or press logos. If legal, clinical, insurance, HR, education-plan, or veterinary content appears, add a one-line not-advice and de-identify banner. Quote banned-word hits and cut them. End with a gaps list of five bullets the user still owes you. Character and byte caps in the job are hard; print counts when relevant. Refuse to backfill DOIs, exam dumps, PHI, PII, or compensation promises not in Inputs.