How to Write Discord Server Rules and an AutoMod Pack
Rules packs wander into Instagram captions and a #memes channel. Brief had four channels and a warn-timeout-kick ladder. No ban step.
The matching generator is the Discord Server Rules and AutoMod Pack from a Community Brief (Not a Caption Engine) (Discord Server Rules And Automod Pack From Community Brief Not Caption Engine) 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).
Refuse caption engines in the banner
Write Discord server rules and an AutoMod pack from a community brief. Not a caption engine and not a role-tree card. 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:
Community brief (who the server is for, hard lines): [Brief]
Age gate I allow (or UNKNOWN): [Age]
Channels I may mention: [Channels]
Keywords I may block: [Block]
Mention limit I allow (or UNKNOWN): [Mentions]
Words I must not use: [Banned]
What I must never invent: [Never]
Output format: [Format]
Language: [Lang]
Escalation steps I allow: [Ladder]
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.
Rules only for channels in 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:
- Banner: not a caption engine, not a role tree, not legal advice. Refuse LinkedIn/TikTok/Instagram/X caption packs.
- Honesty ledger: Brief nouns, Age, Channels, Block, Mentions, Ladder, Lang. Forbidden: extra channels, extra slurs not in Block, fake member counts.
- Rules: numbered. Each rule maps to Brief. No rule for a channel not in Channels.
- AutoMod: keyword list = Block only. Mention spam: quote Mentions or UNKNOWN. Do not invent a regex that targets a person not in Brief.
- Timeout ladder: only Ladder steps. If Ladder is warn then timeout then kick, do not add ban unless pasted.
- Age: quote Age or UNKNOWN. Do not invent 18+ if UNKNOWN.
- Never: do not write a welcome caption pack for Instagram.
- Compliance pass: quote Banned and Never hits. Cut them. 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.
AutoMod keywords only from the block list
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:
- Discord rules and AutoMod from Brief. Not a caption engine and not a role-tree card.
- Only Channels, Block, and Ladder named in Inputs.
- Not legal advice.
- No emojis unless Brief includes them.
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.
Do not add ban if the ladder stopped at kick
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 (discord server rules pack, discord automod from brief, not a caption engine) 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.