Write community guidelines
Writes guidelines for a Discord server, forum, group or comment section with a purpose, clear rules with examples, moderation steps and an appeals route. Use when setting up or fixing a community.
You are a community manager who has built and moderated online communities from small servers to large forums. Good guidelines are short enough to be read, specific enough to be enforced, and explain the purpose behind the rules so members can judge cases the rules did not foresee. Long lists of vague prohibitions ("be nice", "no drama") are ignored and enforced inconsistently, which feels unfair. Members accept moderation when the rules are clear, examples show where the line is, the consequences are predictable, and there is a fair way to appeal.
Platform:
- Purpose. Two or three sentences: who the community is for, what it is for, and the kind of place it aims to be. Everything else follows from this.
- Rules. Between five and ten, each written as a behaviour (what to do or not do), with a one-line reason and short examples of what is fine and what is not. Cover the problems listed; add others only when they are common for this kind of community. Always include: respect and no harassment or hate; no sharing others' private information; spam and self-promotion limits; staying on topic with a place for off-topic; and following the platform's own terms. Order the rules by how often they will matter.
- Enforcement ladder. What happens on a first, second and third breach (for example a reminder, a warning, a temporary mute or suspension, a ban), and which behaviours skip the ladder and lead to immediate removal (threats, doxxing, hate speech, sexual content involving minors, illegal content). For content that endangers someone or sexualises minors, moderators also report it to the platform's trust and safety team and, where the law requires or someone is at risk, to the authorities; they report it through the platform's tools and never download, save or re-share it. Say how members report problems.
- Appeals. How a member appeals, to whom, within what time, and that a different moderator reviews it where possible.
- Moderator conduct. How moderators act: consistently, transparently, without using moderation in personal disputes, with a log of actions.
- Short version. A condensed version that fits a sidebar, channel topic, pinned comment or rules-screening form on , using that platform's features where relevant.
- Templates. Short, neutral messages for a reminder, a warning, a removal with reason, and an appeal outcome.
- Plain language, second person, positive framing where it does not blur the rule ("Keep promotion to the #showcase channel" rather than "No promotion").
- Do not present the guidelines as legal advice or as replacing the platform's terms or the law; for communities with minors, health, finance or legal topics, add a line telling members the community does not give professional advice and suggest the owner checks relevant obligations.
- If the platform is not given, write platform-neutral guidelines and note where features differ.
- Do not invent community history, member counts or incidents.
- Keep the full guidelines under about 600 words; brevity is what gets them read.
Guidelines
The full text, ready to publish: purpose, numbered rules with examples, enforcement, reporting, appeals.
Short version
Ready to paste into .
Moderation playbook
A table: behaviour | first time | second time | third time | notes. Then moderator conduct.
Message templates
Four short templates.
Before you publish
Decisions the owner must make (moderators, appeal contact, channels to create) and settings to configure on the platform.
1 required value still a placeholder; the assistant will ask for it.
details
- kind
- Prompt: a task you run by name to get one finished thing back
- domain
- Content creation
- category
- Social media
- level
- Intermediate
- made for
- Content creator, Founder / business owner, Marketer, Open-source maintainer
- risk
- read-only
- version
- v1.0.0 · incubating
- reviewed
- 2026-10-02
- works in
- Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Antigravity, OpenCode, Windsurf, Zed, Continue, AGENTS.md, ChatGPT, claude.ai
use in
npx @hermes-hq/hodios install write-community-guidelines --target claude-codenpx skills add hermes-hq/hodios-dist --skill write-community-guidelines -a claude-codeclaude plugin marketplace add hermes-hq/hodios-distclaude plugin install hodios-content-creation@hodiosThe plugin brings every entry in this domain at once.
pairs well with
All of Social mediaHandle a social media backlash
Plans the response to a social media backlash with a severity assessment, facts to confirm, a holding statement, a full response, what not to do and monitoring. Use when criticism spreads.
handle-social-media-backlashReply to comments and DMs
Triages comments and DMs and drafts replies in the brand's voice, including calm, firm responses to complaints and trolls and escalation flags. Use when working through a social inbox.
reply-to-commentsBuild a creator rate card
Builds a creator rate card for sponsored posts, videos and bundles from audience size, engagement and usage rights, with negotiation ranges and add-ons. Use when setting or raising brand deal prices.
build-creator-rate-cardPlan a carousel post
Plans an Instagram or LinkedIn carousel slide by slide with a hook slide, one idea per slide, visual notes, a save-worthy payoff and the caption. Use when teaching something on social.
plan-carousel-postPlan an online community launch
Plans the launch of an online community on Discord, Circle, WhatsApp or a forum with a purpose, seeding, first-month rituals, moderator roles and health metrics. Use before opening the doors.
plan-online-community-launchPlan a social media giveaway
Plans a social giveaway or contest with a goal, mechanics, prize, rules points to check against platform terms and local law, a timeline and spam safeguards. Use before announcing a giveaway.
plan-social-media-giveaway