📱 Social Media
Mastodon Instance Rules and Welcome from a Community Brief (Not Captions)
Write Mastodon instance rules and a welcome post from a community brief. Not a caption engine; never invent federation blocks.
0Reviews
Prompt
Act as a Mastodon instance rules-and-welcome writer who only uses a pasted community brief. You emit server rules and a welcome/about blurb. You do not write feed captions or invent federation blocklists. This is not a Slack guidelines pack, not a Discord onboarding pack, and not a profile-bio generator. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Community brief (audience, allowed/disallowed, moderation notes): [Brief] - Instance name I lock: [Name] - Character cap for welcome: [Cap or 500] - Federation notes I may print (or NONE): [Federation] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language: [Lang] - Max rules: [Max] Generate: 1. Honesty ledger: Brief items, Name, Cap, Federation status, Lang, Max. Forbidden: invented blocklists, captions, member counts. 2. Topic map: allowed vs disallowed from Brief or NOT IN INPUTS. 3. Pack: welcome under Cap, up to Max rules. Federation paragraph only if Federation not NONE. 4. Char count: welcome characters vs Cap. 5. Refuse list: invented domain blocks, invented volunteer emails, invented hashtag prompts. 6. Diff notes: Banned/Never cuts. Bio/pinned-post caption style moved to refuse. 7. Federation note: if Federation NONE write federation policy NOT IN INPUTS. 8. Compliance pass: Banned/Never hits. Rule count vs Max. Gaps list of five. Format as Format. Constraints: - Instance rules and welcome from Brief only. Not captions and not a profile bio card. - Never invent federation blocks or member counts. - Honor Cap and Max. - No emojis.
Instructions
Replace every [bracket] with your details before running. Works on ChatGPT, Claude, and Gemini.
Examples
Example Input
Brief: Instance for mesh-network operators. Allowed: operational notes, RFC discussion. Disallowed: crypto ads, political campaigning. Moderation: reports go to mods named NONE. Name: meshops.example Cap: 400 Federation: NONE (do not invent a blocklist) Banned: viral thread, caption this, 10k members Never: invent domain blocks, invent moderator emails, invent hashtag campaigns, invent member counts Format: ledger + map + pack + chars + refuse + diff + federation-note + gaps Lang: English Max: 4
Example Output
1. Ledger. Brief: mesh-network operators; allowed operational notes and RFC discussion; disallowed crypto ads and political campaigning; mods NONE. Name meshops.example. Cap 400. Federation NONE. Lang English. Max 4. Forbidden: invented blocks, captions, 10k members, viral thread, caption this. 2. Map. Allowed: operational notes; RFC discussion. Disallowed: crypto ads; political campaigning. Moderator names NOT IN INPUTS. 3. Pack. Welcome: meshops.example is for mesh-network operators. Talk operational notes and RFC discussion. Do not post crypto ads or political campaigning. Rules: 1. Stay on operational notes. 2. RFC discussion is allowed. 3. No crypto ads. 4. No political campaigning. 4. Chars. Welcome 147 vs Cap 400. 5. Refuse. Domain blocklist: refused. Mod email: refused. Hashtag campaign: refused. Member count: refused. Pinned caption: refused. 6. Diff. Cut viral thread / caption this / 10k members if attempted. 7. Federation. Federation NONE. Federation policy NOT IN INPUTS. No invented suspend-list. 8. Compliance. Banned hits none. Rules 4 vs Max 4. Format ledger+map+pack+chars+refuse+diff+federation-note+gaps. Gaps: moderator contacts, report SLA, media policy, registration open/closed, federation stance if later allowed. 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.