📱 Social Media
WhatsApp Community Rules Pack from a Community Brief (Not Captions)
Write WhatsApp Community rules and escalation notes from a community brief. Not a caption engine and not a promo calendar.
0Reviews
Prompt
Act as a WhatsApp Community governance writer who only uses a pasted community brief. You write rules, examples, and escalation steps. You do not invent laws or moderation tooling features. This is not a caption engine, not Discord AutoMod, and not a marketing blast calendar. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Community brief (purpose, audience, hard lines): [Brief] - Rule count max: [N or 8] - Escalation contacts I allow (or UNKNOWN): [Contacts] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language: [Lang] - Languages allowed in chat: [ChatLang] Generate: 1. Honesty ledger: Brief, N, Contacts, ChatLang, Lang. 2. Purpose one-liner from Brief. 3. Up to N rules with a short example each. 4. Escalation ladder using Contacts or CONTACT UNKNOWN. 5. Refuse: caption packs, promo calendars, inventing WhatsApp feature flags. 6. Safety: no doxxing, no medical advice spam if Brief forbids. 7. ChatLang line. 8. Compliance pass: Banned and Never. Format as Format. Constraints: - WhatsApp Community rules from Brief. Not captions. - Never invent contacts or legal claims. - No emojis.
Instructions
Replace every [bracket] with your details before running. Works on ChatGPT, Claude, and Gemini.
Examples
Example Input
Brief: neighborhood tool-lending community; members share pickup windows; no political campaigns; no selling counterfeit goods; photos of tools OK; do not post street addresses in the main community announcements. N: 6 Contacts: moderators Maya and Omar as pasted; phone numbers UNKNOWN Banned: guaranteed legal advice, arrest threats, spammy CTA captions Never: invent phone numbers, invent WhatsApp Business API features, invent city ordinances Format: ledger + purpose + rules + escalation + refuse Lang: English ChatLang: English
Example Output
1. Ledger. Purpose: neighborhood tool-lending. Hard lines: no political campaigns; no counterfeit sales; no street addresses in main announcements. Photos of tools OK. Contacts Maya, Omar. Phones UNKNOWN. N 6. ChatLang English. Lang English. Forbidden: legal advice guarantees, arrest threats, spam captions, invent phones, invent Business API features, invent ordinances. 2. Purpose. A WhatsApp Community for neighbors to lend tools and share pickup windows. 3. Rules. 1. Keep posts about tool lending and pickup windows. Example: Drill available Saturday 10-12 at the library lot (no home address). 2. No political campaign posts. Example: remove party ads. 3. No selling counterfeit goods. Example: refuse fake-brand listings. 4. Tool photos allowed without doxxing. Example: photo of a ladder on a tarp, no house number. 5. Do not post street addresses in main community announcements. Example: use a public meetup point named in Brief style. 6. Be civil; no harassment. Example: disagree on timing without insults. 4. Escalation. 1) Reply with rule cite. 2) Mute as policy allows. 3) Contact moderators Maya or Omar. Phone numbers CONTACT UNKNOWN. 5. Refuse. Caption packs refused. Promo calendars refused. Business API invent refused. Ordinance invent refused. 6-7. Safety + ChatLang. English only as pasted. No medical advice spam requested. 8. Compliance. Banned cut. Format ledger+purpose+rules+escalation+refuse. Gaps: phone numbers, mute duration policy, announcement channel name, age gate, local law review. 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.