📱 Social Media
Mastodon Instance Rules Pack from a Community Brief (Not Captions)
Write Mastodon instance rules and escalation notes from a community brief. Not a caption engine and not a profile bio.
0Reviews
Prompt
Act as a Mastodon instance governance writer who only uses a pasted community brief. You write server rules, examples, and an escalation ladder. You do not invent laws, federation blocks, or Mastodon feature flags. This is not a caption engine, not a profile bio pack, 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] - Escalation contacts I allow (or UNKNOWN): [Contacts] - Federation notes I allow (or UNKNOWN): [Federation] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language: [Lang] - Languages allowed on the instance: [ChatLang] Generate: 1. Honesty ledger: Brief nouns, N, Contacts, Federation, ChatLang, 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. Federation: only Federation. If UNKNOWN, write FEDERATION UNKNOWN; do not invent defederation lists. 6. Refuse: caption packs, profile bio drafts, inventing Mastodon API scopes, inventing city ordinances. 7. ChatLang line. 8. Compliance pass: Banned and Never. Format as Format. Constraints: - Mastodon instance rules from Brief. Not captions and not a profile bio. - Never invent contacts, federation blocks, or legal claims. - No emojis.
Instructions
Replace every [bracket] with your details before running. Works on ChatGPT, Claude, and Gemini.
Examples
Example Input
Brief: regional crafts instance for makers who post process photos; no shop spam in local timeline; no political campaign ads; CW required for graphic workshop injuries; English and Spanish welcome. N: 6 Contacts: moderators Rio and Sam as pasted; emails UNKNOWN Federation: UNKNOWN (do not invent a blocklist) Banned: guaranteed legal advice, arrest threats, spammy CTA captions, profile bio pack Never: invent emails, invent defederation lists, invent Mastodon 5.x flags, invent city ordinances Format: ledger + purpose + rules + escalation + federation + refuse Lang: English ChatLang: English and Spanish as pasted
Example Output
1. Ledger. Purpose: regional crafts instance for makers and process photos. Hard lines: no shop spam in local; no political campaign ads; CW for graphic workshop injuries. Contacts Rio, Sam. Emails UNKNOWN. Federation UNKNOWN. N 6. ChatLang English and Spanish. Lang English. Forbidden: legal advice guarantees, arrest threats, spam captions, profile bio pack, invent emails, invent blocklists, invent 5.x flags, invent ordinances. 2. Purpose. A Mastodon instance for regional makers who share process photos, with English and Spanish welcome. 3. Rules. 1. Keep local timeline about making and process. Example: a lathe setup photo is on-topic; a buy-now flood is not. 2. No shop spam in the local timeline. Example: one shop link in a process post is not licensed here unless Brief says so (it does not); treat bulk ads as spam. 3. No political campaign ads. Example: remove party ads. 4. Content warn graphic workshop injuries. Example: CW plus blur for a cut photo. 5. English and Spanish are both allowed. Example: a Spanish process thread is in-policy. 6. Be civil; no harassment. Example: critique a joint without insults. 4. Escalation. 1) Reply with rule cite. 2) Limit as policy allows. 3) Contact moderators Rio or Sam. Emails CONTACT UNKNOWN. 5. Federation. FEDERATION UNKNOWN. No invented defederation list. No invented silence list. 6. Refuse. Caption packs refused. Profile bio drafts refused. Mastodon API scope invent refused. Ordinance invent refused. 7. ChatLang. English and Spanish as pasted. 8. Compliance. Banned cut. Format ledger+purpose+rules+escalation+federation+refuse. Gaps: moderator emails, report form URL, media retention, CW vocabulary, federation policy date. 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.