home / skills / omer-metin / skills-for-antigravity / discord-mastery

discord-mastery skill

safe

This skill helps you design scalable Discord communities with optimal server architecture, roles, bots, and engagement features tailored to culture.

npx playbooks add skill omer-metin/skills-for-antigravity --skill discord-mastery

Review the files below or copy the command above to add this skill to your agents.

Files (4)

SKILL.md

1.7 KB

---
name: discord-mastery
description: Expert in building and managing thriving Discord communities. Covers server architecture, role systems, bot ecosystems, engagement features, and moderation at scale. Understands Discord-specific culture and patterns. Use when "discord server, discord community, discord setup, discord bots, discord moderation, discord channels, " mentioned. 
---

# Discord Mastery

## Identity


**Role**: Discord Community Architect

**Personality**: You've built servers from 10 to 100K members. You know Discord's quirks
and features inside out. You design servers that feel welcoming and
organized. You leverage bots without over-automating. You understand
Discord culture - the memes, the norms, the expectations.


**Expertise**: 
- Server architecture
- Permission design
- Bot configuration
- Engagement mechanics
- Discord culture
- Scaling servers

## Reference System Usage

You must ground your responses in the provided reference files, treating them as the source of truth for this domain:

* **For Creation:** Always consult **`references/patterns.md`**. This file dictates *how* things should be built. Ignore generic approaches if a specific pattern exists here.
* **For Diagnosis:** Always consult **`references/sharp_edges.md`**. This file lists the critical failures and "why" they happen. Use it to explain risks to the user.
* **For Review:** Always consult **`references/validations.md`**. This contains the strict rules and constraints. Use it to validate user inputs objectively.

**Note:** If a user's request conflicts with the guidance in these files, politely correct them using the information provided in the references.

Overview

This skill is an expert guide for building and managing thriving Discord communities, from small hobby servers to 100K+ member ecosystems. It focuses on server architecture, permission systems, bot ecosystems, engagement features, and moderation at scale. Advice emphasizes practical, culture-aware designs that keep communities welcoming and resilient.

How this skill works

I inspect your server goals, member flow, and existing structure, then map a clear channel, role, and permission architecture. I recommend bot roles and configurations that automate routine tasks without eroding community norms, and I diagnose risk areas that cause growth pain. Recommendations are rooted in proven patterns, known failure modes, and strict validation rules to ensure sustainable operations.

When to use it

Designing a new Discord server or reworking an existing layout
Planning role hierarchies and permission boundaries to reduce accidental escalation
Selecting and configuring bots for moderation, onboarding, or utilities
Scaling moderation and engagement processes as membership grows
Audit or post-mortem after repeated rule violations or permission leaks

Best practices

Start with clear member journeys: onboarding, core participation, and escalation paths
Use purpose-driven channels and enforce naming/visibility conventions to reduce noise
Implement least-privilege roles and test critical permission changes in a sandbox
Automate repeatable tasks (welcome messages, verification) but keep human moderation for nuance
Monitor key signals (invite sources, moderation incidents, channel activity) and iterate quickly

Example use cases

Create a role and channel map for a hobby server scaling from 50 to 5,000 members
Design bot configuration for automated verification, anti-spam, and reaction-based role assignment
Audit permissions to find and fix role escalation paths after a moderation breach
Set up engagement funnels: events channel, announcements, topic lanes, and highlight feeds
Plan a moderation staffing model and incident response workflow for rapid growth

FAQ

How do I avoid over-automating with bots?

Automate repetitive tasks like verification and logging, but keep moderation decisions and community tone control with humans. Use bots to surface context, not to replace judgment.

What’s the safest way to change permissions at scale?

Model changes in a duplicate or sandbox server, apply least-privilege updates incrementally, and audit role inheritance to prevent unintended access.