How to Write Twitch Stream Rules and a Raid Welcome Pack
Raid welcomes invent partner badges. Quote the channel brief. Cap the character count.
The matching generator is the Twitch Stream Rules and Raid Welcome Pack from a Channel Brief (Twitch Stream Rules And Raid Welcome Pack From A Channel Brief) prompt. Browse related cards in the PromptDig library (Browse more prompts). When a filled run survives, share the version you actually use (Share a prompt).
Lock channel name and raid character max
Write Twitch stream rules and a raid welcome pack from a channel brief. Not a caption engine and not a title/panels pack. Start by filling Inputs, not by asking the model to remember last week's run. If a field is blank, write NONE or NOT IN INPUTS and leave it blank through Generate. The card is built so the model cannot honestly invent a number, owner, URL, or command that you did not paste.
Paste these fields before you hit run:
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]
That inventory is the honesty ledger. Anything that does not appear there is forbidden in the draft. If you catch yourself adding a nice-to-have after the run, you are no longer using the card. You are ghostwriting. Put the extra fact in Inputs and run again.
Write stream rules only from the brief
Generate is numbered on purpose. Do not skip a step because the first paragraph looked done. The early steps exist to stop later prose from smuggling claims.
Walk the Generate list in order:
- Honesty ledger: Brief nouns, N, Channel, RaidMax, Contacts, Lang.
- Purpose one-liner from Brief.
- Up to N stream rules with a short example each. Quote hard lines from Brief.
- Raid welcome text under RaidMax characters. Print character count. Use Channel only as given.
- About-panel pin: short rules summary for the channel About or rules panel.
- Escalation ladder using Contacts or CONTACT UNKNOWN.
- Refuse: caption packs, inventing partner badges, inventing Twitch ToS clause numbers, inventing sub counts.
- Compliance pass: Banned and Never. Format as Format.
If a step asks for a version lock, quote the version from Inputs in the output. If a step asks for a refuse list, keep the refuse list in the published artifact, not in a sidebar you delete. Reviewers should see what the model was not allowed to do.
Print raid welcome character count
Most failures are the same shape: a missing field gets a confident fill. A conversion rate appears. A Gradle task appears. A flash point appears. A caption appears on a job that asked for slide text only. Your review is to search the draft for numbers, names, and commands, then grep Inputs. No match means cut.
Honor the constraints as hard stops, not vibes:
- 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.
When the card says not legal advice, not certification, not an exam dump, or not a caption engine, that sentence belongs at the top of the output. Deleting it to look more finished is how you inherit risk.
Refuse invented partner status and ToS clauses
Finish with the compliance pass the prompt already asks for. Quote the banned-word hits. Cut them. Print character counts when the job has a cap. Print word counts when the job has a budget. List gaps as gaps. Five missing facts are more useful than one smooth paragraph.
Tags on the card (twitch stream rules pack, raid welcome from channel brief, twitch community guidelines draft) are a reminder of the job shape, not an invitation to wander into a neighboring cluster. If you need a different surface, open a different PromptDig card rather than stretching this one.
Fill the card, then run
Replace every bracket. Run on ChatGPT, Claude, or Gemini. Read the ledger first, then the artifact. If the model invents a commit, KPI, DOI, PEL, bid, or logo, discard the run. Tighten Inputs. Run again. Share the filled card that survived, not the first draft that sounded done.