📱 Social Media
Discourse Category Moderation Rules Pack from a Brief (Not Captions)
Write Discourse category rules and escalation notes from a community brief. Not a caption engine and not a profile bio pack.
0Reviews
Prompt
Act as a Discourse governance writer who only uses a pasted community brief. You write category rules, examples, and an escalation ladder. You do not invent laws or Discourse plugin flags. This is not a caption engine, not a Reddit wiki clone, and not a Twitter/X playbook. 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] - Category name I allow: [Category] - 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, Category, Contacts, Lang. 2. Purpose one-liner from Brief. 3. Up to N rules with a short example each. Quote hard lines from Brief. 4. Escalation ladder using Contacts or CONTACT UNKNOWN. 5. Category pin text: short version for the Discourse category description. 6. Refuse: caption packs, inventing city ordinances, inventing Discourse SSO claims. 7. Off-topic examples: only if Brief states them; else OFF-TOPIC EXAMPLES NOT IN INPUTS. 8. Compliance pass: Banned and Never. Format as Format. Constraints: - Discourse rules from Brief only. Not captions and not Reddit. - Never invent laws or plugin flags. - 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: Maker forum for open hardware. Hard lines: no sales spam, no doxxing, stay kind in critique. Audience: hobbyists and small shops. N: 5 Category: General Contacts: UNKNOWN Banned: guaranteed ban appeal, invent GDPR fine Never: invent laws, invent Discourse plugins, invent moderator names, invent ban counts Format: ledger + purpose + rules + escalation + pin + gaps Lang: English
Example Output
1. Ledger. Brief: open hardware maker forum; no sales spam; no doxxing; kind critique; hobbyists and small shops. N=5. Category General. Contacts UNKNOWN. Lang English. Forbidden: invent laws, invent plugins, invent moderator names, invent ban counts, guaranteed ban appeal, invent GDPR fine. 2. Purpose. A Discourse category for open hardware makers (hobbyists and small shops) to discuss builds with kind critique. 3. Rules. 1) No sales spam. Example: do not post affiliate store floods in General. 2) No doxxing. Example: do not paste private addresses. 3) Kind critique. Example: critique the design choice, not the person. 4) Stay on open hardware topics. Example: prefer BOM and firmware threads over unrelated life blogs. 5) Assume hobbyist and small-shop context. Example: mark commercial manufacturing questions clearly. 4. Escalation. CONTACT UNKNOWN. Ladder: remind -> warn -> mute suggestion for mods -> escalate when Contacts provided. 5. Pin. General: open hardware talk; no spam; no doxxing; kind critique. 6. Refuse. Caption packs refused. Ordinance invent refused. SSO invent refused. 7. Off-topic. OFF-TOPIC EXAMPLES NOT IN INPUTS beyond sales spam. 8. Compliance. Banned cut. Gaps: moderator contacts, ban appeal path, plugin list, language policy, NSFW policy. 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.