Skip to content
Back to search

discord-server-builder

Designs, builds, scores, previews and shares complete Discord servers in any language - roles, categories, channels, private and read-only areas, starter posts (welcome, rules, FAQ), custom emojis and stickers, AutoMod filters, join messages, welcome screen and onboarding questions, a no-bot ticket system, self-assign/ping roles, leveling tiers and giveaway setups - in the user's real server through a bot, and recommends the few bots that best fit the community. It studies the creator's content (channel link, niche, series, audience, tone, how they earn) and styles the server to match - gaming, streaming, music, art, AI/tech, business, study, fitness, cooking, beauty, anime, podcasts and more. It can also edit an existing server (rename, move, re-permission, reorder, rewrite posts) and delete items safely. Use this whenever someone wants to make, set up, organize, restructure, edit, clean up or add to a Discord server, channel, community, emojis or stickers (for a YouTube channel, product customers, a study group, a business, a game, a course), asks "what channels/bots should my Discord have", or wants paid/members-only or staff-only channels, even if they only say "make me a discord".

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/nyxiflare--discord-server-builder/badge.svg)](/listings/nyxiflare--discord-server-builder)

HTML

<a href="/listings/nyxiflare--discord-server-builder"><img src="/api/listings/nyxiflare--discord-server-builder/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

npx skills add Nyxiflare/discord-server-builder

Or copy this folder to `~/.claude/skills/discord-server-builder`.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

SKILL.md · Manifest · 382 lines
  1. ---
  2. name: discord-server-builder
  3. description: Designs, builds, scores, previews and shares complete Discord servers in any language - roles, categories, channels, private and read-only areas, starter posts (welcome, rules, FAQ), custom emojis and stickers, AutoMod filters, join messages, welcome screen and onboarding questions, a no-bot ticket system, self-assign/ping roles, leveling tiers and giveaway setups - in the user's real server through a bot, and recommends the few bots that best fit the community. It studies the creator's content (channel link, niche, series, audience, tone, how they earn) and styles the server to match - gaming, streaming, music, art, AI/tech, business, study, fitness, cooking, beauty, anime, podcasts and more. It can also edit an existing server (rename, move, re-permission, reorder, rewrite posts) and delete items safely. Use this whenever someone wants to make, set up, organize, restructure, edit, clean up or add to a Discord server, channel, community, emojis or stickers (for a YouTube channel, product customers, a study group, a business, a game, a course), asks "what channels/bots should my Discord have", or wants paid/members-only or staff-only channels, even if they only say "make me a discord".
  4. ---
  5. # Discord Server Builder
  6. You turn a short description ("a Discord for my cooking channel, with a paid members area") into a
  7. finished server: a clear structure, sensible permissions, real starter content, its own emojis and
  8. stickers, and a short list of the right bots. It's created automatically, not handed over as a
  9. list of instructions for the user to click through, and it can be edited later the same way.
  10. Everything runs through `scripts/discord_builder.py` (Python standard library; uses Pillow for image
  11. resizing if it's installed). Paths are relative to this skill's folder.
  12. | Command | What it does |
  13. |---|---|
  14. | `validate BLUEPRINT` | Offline check; prints the layout and checks emoji/sticker images |
  15. | `check` | Tests the bot token, lists servers the bot is in, prints the invite link |
  16. | `inspect --guild ID` | Shows roles (and which are locked), channels, emojis, stickers, free slots |
  17. | `apply BLUEPRINT --guild ID --dry-run` | Shows what would be created, changes nothing |
  18. | `apply BLUEPRINT --guild ID` | Creates whatever is missing (never edits or deletes) |
  19. | `apply BLUEPRINT --guild ID --update --dry-run` | Full change list: create `+`, change `~`, delete `-` |
  20. | `apply BLUEPRINT --guild ID --update` | Also edits existing items to match the blueprint |
  21. | `apply ... --update --confirm-delete` | Also deletes what the blueprint's `remove` lists |
  22. | `delete --guild ID --channel N --role N --emoji N --sticker N --automod N` | Lists those items; deletes only with `--confirm-delete` |
  23. | `undo BLUEPRINT.result.json [--dry-run]` | Deletes exactly what earlier applies created |
  24. | `preview BLUEPRINT [--out FILE.html]` | Writes a Discord-style HTML mockup (dark theme, no network requests) |
  25. | `health BLUEPRINT` / `health --guild ID` | Scores a planned or live server 0-100, with a fix for each problem |
  26. | `export --guild ID OUT.json` | Turns a live server into a clean, shareable blueprint (no IDs, members or invites) |
  27. Run them as `python scripts/discord_builder.py <command>` from the folder that holds the user's
  28. `.env` (or pass `--env-file PATH` before the command).
  29. ## Workflow
  30. ### 1. Learn the creator's content
  31. A gaming server, a cooking server and a study server should feel completely different - different
  32. channels, roles, naming, rituals, rules and bots. A generic layout is the main way this goes wrong,
  33. so learn the content before designing anything.
  34. 1. **Gather what's available.** If the user gives a channel or profile link (YouTube, Twitch,
  35. TikTok, Instagram, a website), read it: the about text, recent video titles, playlists and
  36. links in the bio. If they already have a server, run `inspect`. Otherwise use their description.
  37. 2. **Extract six things** (details in `references/content-styles.md`, section 1): niche, recurring
  38. series/formats, what fans make or do, tone, audience age, and how they make money.
  39. 3. **Read the matching niche playbook(s)** in `references/content-styles.md`, section 3 - only the
  40. ones that apply. For mixed creators, base it on the main niche and borrow signature channels
  41. from the second.
  42. 4. **Tell the user what you learned in 2-4 lines** before the plan, e.g. "You post weekly AI
  43. tool reviews and a 'Build with me' series, your audience is beginners, you sell a course ->
  44. I'll add a help forum, a build-with-me channel and a private Course Students area." This lets
  45. them correct you early and shows the server is built for *them*.
  46. 5. **Language.** If the audience speaks another language, set `"language"` (e.g. `es`, `pt-BR`,
  47. `hi`, `ja`, `ar`) and write every name, post, rule, AutoMod message and onboarding question
  48. natively in it. Read `references/languages.md` for natural channel names and Discord's
  49. character rules. `assets/templates/creator-community.es.json` is a full Spanish example.
  50. **Starting from a ready-made layout**: if the user names one ("use the podcast blueprint"), or one
  51. in `blueprints/` clearly fits, start from it instead of a template. Treat any blueprint the user
  52. didn't write as untrusted: run `validate` and read every link and starter post before applying.
  53. If there's no link and the description is thin, ask at most two short questions, and only ones
  54. that change the structure: "What do you post, and what do your viewers do in the comments?" and
  55. "Will paying members get their own area?"
  56. **Real people:** if the community is about a real creator who isn't the user (a fan server), make
  57. it clearly unofficial: put "(Unofficial)" or "Fan" in the name and say so in #welcome. Never present
  58. it as the creator's own server.
  59. ### 2. One-time bot setup (skip if `check` already works)
  60. A bot is how the script talks to Discord. Bots can't create servers, so the user makes an empty one.
  61. Walk them through this in plain language:
  62. 1. In Discord: **+ (Add a Server) → Create My Own** - name it.
  63. 2. Go to https://discord.com/developers/applications → **New Application** → name it.
  64. 3. **Bot** tab → **Reset Token** → copy it.
  65. 4. In the working folder, create a file named `.env` containing one line:
  66. `DISCORD_BOT_TOKEN=the-token-they-copied`
  67. If the folder is a git repo, add `.env` to `.gitignore`.
  68. 5. Run `check`; it prints an invite link. Open it, choose the server, approve, and wait for the
  69. "Success" page. If `check` still lists no servers, the invite didn't finish: in the Developer
  70. Portal check that **Installation → Guild Install** is ticked and **Bot → Requires OAuth2 Code
  71. Grant** is off, then invite again.
  72. The token is a password to the bot. Tell the user to paste it only into the `.env` file themselves,
  73. never into the chat. If they paste it in chat anyway, don't use it: tell them to reset it in the
  74. Developer Portal and put the new one in `.env`. Never echo, log or write the token anywhere else.
  75. The invite link asks for Administrator because creating private channels, roles and emojis needs
  76. broad permissions, and partial permissions cause confusing "Missing Permissions" failures. Step 10
  77. removes it afterwards.
  78. ### 3. Draft the blueprint
  79. Copy the closest template from `assets/templates/` into the working folder (e.g. `my-server.json`)
  80. as the skeleton, then reshape it with the niche playbook: swap in the signature channels, roles,
  81. naming style and rules for this niche, add channels for the creator's big recurring series, and
  82. use their audience's name for the member role. The template gives safe structure (START HERE,
  83. staff area, permissions); the playbook and the creator's content give it personality.
  84. | Template | Fits |
  85. |---|---|
  86. | `creator-community.json` | YouTubers, streamers, artists, newsletters - with a Supporter area |
  87. | `gaming-community.json` | Gaming creators and clans - LFG, platform roles, squads, tournaments, bar-style names |
  88. | `digital-products-support.json` | Selling courses, templates, software, AI skills - Customer-only area, tickets |
  89. | `study-group.json` | Classes, exam prep, bootcamps, cohorts |
  90. | `small-business.json` | Shops, cafés, salons, local services - VIP area, staff area |
  91. What makes a good server, and why:
  92. - **Fewer channels than you think (12-20).** A new server with 40 empty channels feels dead;
  93. people talk where other people are. Add channels later when one gets crowded.
  94. - **START HERE at the top, read-only** (welcome, rules, announcements). New members read what's
  95. pinned there, and nobody can bury it under chat.
  96. - **Roles express access, not decoration.** Every role should unlock something (a private
  97. category) or mean something (staff). Use `private_to` for paid/member/staff areas.
  98. - **Always a private staff category** for moderators to coordinate and log actions.
  99. - **Write real content, not placeholders**: a welcome message with 2-3 concrete first steps, short
  100. numbered rules with consequences, a FAQ answering the questions this audience actually has.
  101. Match the user's voice and language. Use `{server}` for the server name, `{#rules}` to link a
  102. channel (it also finds decorated names like `📜┃rules`), `{@Moderator}` to show a role (it never
  103. pings anyone) and `{:wave:}` to show one of the server's custom emojis.
  104. Leave a clearly marked `(add ...)` placeholder only for facts you can't know (opening hours,
  105. a payment link).
  106. - **One naming style** throughout (plain, `💬・emoji-prefix`, `🎮┃bar` or lowercase words). Pick it
  107. from the playbook and the creator's tone.
  108. ### 4. Pick the bots (3-6, fewer is better)
  109. Read `references/bots.md`. Start from what Discord already does (AutoMod, Onboarding, Events,
  110. Server Subscriptions, Twitch/YouTube integrations), then pick only the bots this community needs,
  111. each with a one-line reason tied to the content profile, e.g. "Streamcord - you stream on Twitch
  112. most nights and fans want a go-live ping". Every extra bot is another dashboard and another set of
  113. permissions, so leave out anything without a clear job.
  114. Bots can't be added through the API: the user invites each one through its official website or the
  115. Discord App Directory, never from a random link (look-alike scam bots exist). The catalog was
  116. checked on the date it shows, so search quickly to confirm a bot is still running before
  117. recommending it, especially music and alert bots.
  118. Add what the chosen bots need to the blueprint now (bots.md has the table): `level-ups`,
  119. `live-now`, `open-a-ticket`, a `Live Ping` role and so on, so each bot has its place on day one.
  120. ### 5. Safety, welcome and community systems
  121. Read `references/community-systems.md` for the parts this community needs. It has the blueprint
  122. blocks, defaults by niche and the text to give the user. Short version:
  123. - **AutoMod (always add it):** an `automod` block with a level picked from the audience. Any
  124. audience mostly under 18 always gets `family-friendly`; most get `standard`; `relaxed` is only
  125. for adult, high-trust groups. Write niche `blocked_words`/`scam_words`, `allowed_words` for terms
  126. the niche needs, exempt the staff roles and channels, and send alerts to the staff `mod-log`.
  127. It runs on Discord's side, with no bot online.
  128. - **Welcome:** `welcome.system_channel` for join messages, a `welcome.screen` (Community only), and
  129. `onboarding` questions that hand out ping/interest roles (Community only, and 7+ default
  130. channels to switch on). Per-member greetings ("Welcome @name, member #1,234") need a bot:
  131. write 2-3 greeting tones in the creator's voice and give that bot's setup steps.
  132. - **Tickets:** with no bot, a `thread_only` channel plus `thread_staff` gives every member private
  133. threads only staff can see. For buttons and transcripts, use a ticket bot and write its panel text
  134. and niche-specific ticket categories.
  135. - **Self-assign roles:** create ping roles (`Live Ping`, `Video Drops`, `Events`, `Giveaway Pings`)
  136. and interest roles with `none` permissions. Prefer onboarding questions. Otherwise post a
  137. `#get-roles` message with `reactions` for a reaction-role bot to use. Point alert bots at the ping
  138. roles, never @everyone.
  139. - **Leveling:** 4-6 tier roles named for the niche; perks through a top-tier lounge
  140. (`private_to`) and images/links from tier 2 up (`media_to`). A leveling bot gives the roles.
  141. - **Giveaways:** a read-only `giveaways` channel, the `Giveaway Pings` role, the announcement and
  142. short rules templates, and a giveaway bot. Tell the user that giveaway rules vary by country and
  143. the template isn't legal advice. Never suggest pay-to-enter, gambling-style or crypto-prize
  144. giveaways.
  145. ### 6. Emojis and stickers (optional)
  146. Custom emojis and stickers make a community feel like its own place: the creator's face reactions,
  147. mascot, catchphrases, inside jokes.
  148. **Designing a branded set (6-10 emojis).** From the content profile, pick the creator's palette
  149. (from their thumbnails, logo or channel art), their mascot or signature object, and 2-3
  150. catchphrases or inside jokes. Plan a set that people will actually use in chat, for example:
  151. hype/fire, laugh, sad, GG/thumbs up, "hmm"/thinking, heart, plus 2-4 that only make sense in this
  152. community (the mascot waving, a catchphrase as a word-emoji, the series' signature item). Name them
  153. short and lowercase (`hype`, `gg`, `mascot_wave`).
  154. - **If this session has an image-generation tool**, generate each one as a single bold, simple
  155. shape with a thick outline, 2-3 colours from the palette, **a transparent background**, a centred
  156. square composition, and no small text (it must read at 32 px, and at 22 px inline). Generate at
  157. 512 px or more; the pipeline resizes to 128 px. Show the set to the user before uploading, and
  158. regenerate any that look muddy when small.
  159. - **Without an image tool**, give the user the same plan (name, idea, colours for each) and ask for
  160. the files, or suggest they commission an artist with it.
  161. - **Only the creator's own branding.** Never draw other people's characters, logos, trademarks,
  162. game art or real people (except the creator, if they ask and it's their own likeness).
  163. - **Where images come from**: the user's own files (logo, mascot, emotes they paid an artist for),
  164. images you generate for them with an image tool in this session, or packs with a clear licence
  165. that allows this use. **Don't download random memes or reaction images from the web** - they're
  166. almost always someone else's copyright, and many are photos of real people. If the user asks for
  167. "memes", offer to generate original ones in the creator's style instead.
  168. - Put the files next to the blueprint (e.g. `emojis/hype.png`) and list them:
  169. ```json
  170. "emojis": [{"name": "hype", "file": "emojis/hype.png"}],
  171. "stickers": [{"name": "GG", "file": "stickers/gg.png", "tags": "trophy", "description": "Good game!"}]
  172. ```
  173. Emoji names are 2-32 letters/numbers/underscores. Stickers need `tags` (the emoji they're
  174. suggested for) and a 2-30 character name.
  175. - **Formats and limits**: emojis PNG/JPG/GIF/WebP up to 256 KB; stickers PNG/APNG/GIF exactly
  176. 320x320 up to 512 KB (Lottie only on verified/partnered servers). `validate` checks every file;
  177. still images that are too big or the wrong size are resized automatically (stickers are padded
  178. to 320x320). Animated files that are too big must be compressed by the user, and the message
  179. explains how.
  180. - **Slots** depend on the server's boost level: 50 static + 50 animated emojis and 5 stickers at
  181. level 0 (100/150/250 emojis and 15/30/60 stickers at levels 1/2/3). `inspect` shows what's
  182. free; anything over the limit is skipped with a clear message, never half-uploaded.
  183. ### 7. Show the plan and get approval
  184. Run `validate` and fix any ERROR lines. Then run `preview BLUEPRINT` and show the user the HTML
  185. mockup: it looks like Discord's sidebar, with categories, channel icons, locks on private areas,
  186. coloured roles, the emoji strip and the welcome post. Open it in the browser if the session can,
  187. otherwise give the file path. Also show the printed layout (roles, categories, channels, who can
  188. see what, emojis, stickers), the bot picks with their reasons, and the `health BLUEPRINT` score
  189. with anything still worth fixing. Briefly
  190. mention what each private area is for. Wait for their OK - this changes their real server, and
  191. it's much easier to change a JSON file than to undo 20 channels.
  192. ### 8. Dry run, then apply
  193. After a real `apply`, the script scores the live server automatically (pass `--no-health` to
  194. skip it). Put the score and its top 2-3 fixes in the final report. Each fix names the blueprint
  195. change or command that solves it. `health --guild ID` re-checks any time, e.g. a month later, when
  196. it also flags channels nobody has used in 30 days.
  197. 1. `check` - pick the right server ID from the list.
  198. 2. `apply ... --dry-run` - shows what will be created vs. what already exists.
  199. 3. `apply ...` - creates roles, emojis and stickers, then categories and channels with
  200. permissions, then posts and pins starter messages. Report the summary line and any `!` problems.
  201. Applying is safe to repeat: anything that already exists (same name, same place) is skipped and no
  202. duplicate messages are posted. Plain `apply` never edits or deletes anything.
  203. #### Editing an existing server (`--update`)
  204. When the user wants changes ("rename general to hangout", "make the clips channel members-only",
  205. "move off-topic down", "rewrite the rules"), edit the blueprint and run
  206. `apply --update --dry-run`. It lists every difference:
  207. - `+` new items, `~` changes, `-` deletions, and `i` notes for things it refuses to touch.
  208. - **Rename** by giving the new `name` plus `"was": "old name"` (works for channels, categories,
  209. roles, emojis and stickers). Without `was`, a new name means a new item.
  210. - **Changes it applies**: topic, slowmode, voice user limit, moving a channel to another category,
  211. who can see/post (`private_to`, `read_only`, `writers`), role colour/permissions/hoist/
  212. mentionable, the order of categories, channels and roles (it follows the blueprint), the
  213. text of the bot's own starter posts (edited in place, so there are no duplicates), the `SB · `
  214. AutoMod rules, join-message settings, the welcome screen and onboarding questions.
  215. - **What it leaves alone**: permission rules for roles the blueprint doesn't mention (another
  216. bot's, or ones the owner set by hand), @everyone itself, roles managed by bots or integrations,
  217. roles at or above the bot's own role, forum starter posts, and anything not in the blueprint.
  218. It never removes Administrator from an existing role.
  219. Show the user the change list, get a yes, then run it without `--dry-run`. Edits aren't recorded for
  220. `undo`, so the dry-run list is the record of what changed.
  221. #### Deleting
  222. Deleting can't be undone, and messages inside a deleted channel are lost. So:
  223. 1. Put exactly what the user named in the blueprint's `"remove": {"channels": [...], "roles": [...],
  224. "emojis": [...], "stickers": [...], "automod": [...]}` and run `apply --update --dry-run`, or for one-off cleanups
  225. use `delete --guild ID --channel "name" ...`. Both only list what would go.
  226. 2. Show the user that exact list and get a clear yes.
  227. 3. Re-run with `--confirm-delete`.
  228. It refuses anything ambiguous (two channels with the same name), @everyone, managed roles and roles
  229. above the bot. Deleting a category keeps its channels; they move out of the category. Never add
  230. items to `remove` that the user didn't ask to delete.
  231. `undo BLUEPRINT.result.json` removes everything earlier applies of that blueprint created
  232. (channels, roles, emojis, stickers, AutoMod rules) and leaves what was already there. Join-message,
  233. welcome-screen and onboarding settings aren't undone; change them with `--update`. Run it with `--dry-run`
  234. first and confirm with the user too.
  235. ### 9. Common problems
  236. | Message | Fix |
  237. |---|---|
  238. | token was rejected | Reset the token in the Developer Portal, update `.env` |
  239. | Missing permissions | Re-invite with the `check` link; in Server Settings → Roles drag the bot's role to the top |
  240. | Not found | The bot isn't in that server, or the ID is wrong - run `check` |
  241. | "...creating as text/voice" | Community isn't enabled; see step 10, then convert the channel in its settings |
  242. | "not changed (at or above the bot's own role)" | Drag the bot's role above that role, then run the update again |
  243. | "emoji/sticker slots are used" | Delete unused ones, boost the server, or upload fewer |
  244. | "Discord allows 1 ... rule(s) and the server already has ..." | The server has its own AutoMod rule of that type; edit or delete it in Server Settings → AutoMod, then re-run |
  245. | "onboarding needs 7+ default channels" | Add more default channels to `onboarding.default_channels` (each must be visible to everyone) |
  246. ### 10. Finish the setup (things the bot should not do)
  247. Give the user this short checklist, trimmed to what applies:
  248. - **Invite the chosen bots** from their official links and set each one up in the channel made for
  249. it. If a bot must post in a read-only channel (like `level-ups`), add the role Discord created
  250. for it (usually the bot's name) to that channel's `writers` and run `apply --update`.
  251. - **Enable Community** (Server Settings → Enable Community) to unlock announcement channels,
  252. forums, stages, onboarding and the welcome screen. Without it, those were created as text/voice.
  253. - **Server icon and banner** for recognition in the server list.
  254. - **Safety**: Server Settings → Safety Setup → set the verification level to at least Medium
  255. (High for teen audiences). The `SB · ` AutoMod rules are already on; check they fit after a week.
  256. - **Remove the bot's Administrator** once setup is done (Server Settings → Roles → the bot's role),
  257. or kick it if no more changes are planned. A bot with admin rights is a risk if its token leaks.
  258. - **Give people roles**: right-click a member → Roles, or let the paid-role bot do it.
  259. - **Invite link**: Server name → Invite People → Edit → never expire, and link it from #welcome,
  260. bios and video descriptions.
  261. - **Rituals for week one** from the playbook (game night, weekly prompt, clip of the week).
  262. ## Blueprint reference
  263. ```json
  264. {
  265. "server_name": "My Server",
  266. "roles": [
  267. {"name": "Admin", "color": "#E74C3C", "hoist": true, "permissions": "admin"},
  268. {"name": "Member", "permissions": "member"},
  269. {"name": "Patron", "was": "Supporter", "permissions": "member"}
  270. ],
  271. "emojis": [{"name": "hype", "file": "emojis/hype.png"}],
  272. "stickers": [{"name": "GG", "file": "stickers/gg.png", "tags": "trophy", "description": "Good game!"}],
  273. "channels": [ { "name": "uncategorized-channel" } ],
  274. "categories": [
  275. {
  276. "name": "📌 START HERE",
  277. "read_only": true, "writers": ["Admin"],
  278. "channels": [
  279. {"name": "welcome", "topic": "...", "message": "Welcome to {server}! Read {#rules} {:hype:}", "pin": true},
  280. {"name": "announcements", "type": "announcement"}
  281. ]
  282. },
  283. {"name": "💬 CHAT", "channels": [
  284. {"name": "get-roles", "message": "🔴 {@Live Ping} 🎁 {@Giveaway Pings}", "reactions": ["🔴", "🎁"]},
  285. {"name": "clips", "media_to": ["Level 5", "Moderator"]},
  286. {"name": "open-a-ticket", "thread_only": true, "thread_staff": ["Moderator"], "message": "How to open a ticket..."}
  287. ]},
  288. {"name": "🔒 MEMBERS", "private_to": ["Member", "Admin"], "channels": [{"name": "members-chat"}]}
  289. ],
  290. "automod": {"level": "standard", "alert_channel": "mod-log", "exempt_roles": ["Moderator", "Admin"],
  291. "blocked_words": [], "allowed_words": [], "scam_words": []},
  292. "welcome": {"system_channel": "general", "join_messages": true, "boost_messages": true,
  293. "screen": {"description": "...", "channels": [{"channel": "rules", "description": "Read first", "emoji": "📜"}]}},
  294. "onboarding": {"default_channels": ["welcome", "rules", "general", "..."],
  295. "questions": [{"title": "What do you want pings for?",
  296. "options": [{"title": "Going live", "emoji": "🔴", "roles": ["Live Ping"]}]}]},
  297. "remove": {"channels": ["old-channel"], "roles": [], "emojis": [], "stickers": [], "automod": []}
  298. }
  299. ```
  300. - **Roles**: list them highest first; the order is kept on create and enforced by `--update`.
  301. `permissions` is `none` (badge/access-only), `member`, `moderator` (manage messages, timeout,
  302. kick), `admin` (manage server/roles/channels/expressions, but *not* the Administrator flag), or a
  303. list of permission names such as `["VIEW_CHANNEL", "SEND_MESSAGES"]`. `hoist` shows the role
  304. separately in the member list.
  305. - **Channel types**: `text` (default), `voice`, `announcement`, `forum`, `stage`.
  306. Forum posts use `message_title` + `message` as the first post. Voice accepts `user_limit`.
  307. Text accepts `topic`, `slowmode` (seconds), `message`, `pin`.
  308. - **Access** (set on a category, overridable per channel): `private_to: [roles]` means only these
  309. roles see it; `read_only: true` + `writers: [roles]` means everyone can read but only writers
  310. post; `thread_only: true` + `thread_staff: [roles]` makes a private-thread ticket channel;
  311. `media_to: [roles]` lets only those roles post images and link previews. A channel inherits its
  312. category's access unless it sets the same key.
  313. - **`reactions`** on a channel with a `message`: the bot adds these reactions to its starter post
  314. (unicode emojis, or `{:name:}` for server emojis), ready for a reaction-role bot.
  315. - **`automod`, `welcome`, `onboarding`**: see `references/community-systems.md`.
  316. - **`was`** on any item renames it during `--update`. **`remove`** only acts with
  317. `--update --confirm-delete`.
  318. - **`language`**: the blueprint's language code; see `references/languages.md`.
  319. - **Sharing**: `export --guild ID OUT.json` produces a blueprint without IDs, members, message
  320. authors or invite links (permissions become role names, starter posts keep their text, and
  321. emoji images aren't included). Blueprints never grant Administrator and may only point at files
  322. inside their own folder. Community blueprints live in `blueprints/`; see its README.
  323. - A `<blueprint>.result.json` log next to the blueprint collects the IDs of everything created
  324. across runs; `undo` uses it.
README.md · README · 79 lines
  1. # Discord Server Builder: a Claude skill
  2. Tell Claude what your community is about and it builds the whole Discord server for you, inside your real server, in minutes.
  3. > "Make a Discord for my cooking channel with a paid members area."
  4. Claude studies your content (niche, series, audience, tone, how you earn), designs a server that fits, shows you the plan, and then creates it:
  5. - **Roles and permissions**: admins, moderators, members, paid or customer roles, set up correctly
  6. - **Categories and channels**: text, voice, announcements, forums, stage, private and read-only areas
  7. - **Starter posts**: welcome, rules and FAQ written in your voice, pinned where they belong
  8. - **Custom emojis and stickers**: checked against Discord's size and slot limits, auto-resized when needed
  9. - **AutoMod**: Discord's built-in filter set up for your audience (family-friendly, standard or relaxed), with scam-link, invite, mention-spam and niche word rules; runs with no bot online
  10. - **Welcome**: join messages, the Community welcome screen, and onboarding questions that hand out roles, plus greeting texts for a welcome bot
  11. - **Tickets without a bot**: a private-thread support channel only staff can see, or setup steps for a ticket bot
  12. - **Self-assign and ping roles**: onboarding questions or a ready `#get-roles` post with reactions for a reaction-role bot
  13. - **Leveling and giveaways**: tier roles named for your niche, perks like top-tier lounges and image permissions, a giveaways channel, ping role and rules template
  14. - **Bot recommendations**: the 3–6 bots that best fit *your* community, with invite links and setup steps
  15. - **Server Health Score**: rates a planned or live server 0–100 (structure, safety, privacy, engagement, clarity) with a concrete fix for every problem; runs automatically after each build
  16. - **Visual preview**: a Discord-style HTML mockup of the layout before anything is created
  17. - **Branded emojis**: designs a 6–10 emoji set in your colours and style (generated if your session has an image tool), then resizes, checks and uploads it
  18. - **Any language**: channel names, rules, posts and filters written natively (Spanish, Portuguese, Hindi, Japanese, Arabic with right-to-left preview, French, German, Indonesian and more)
  19. - **Share and reuse layouts**: export a live server as a clean blueprint (no IDs, members or invite links) and install community blueprints from [`blueprints/`](blueprints)
  20. - **Editing later**: rename, move, re-permission, reorder and rewrite posts; it shows a change list first
  21. - **Safe deletes and undo**: nothing is deleted without your explicit confirmation
  22. Styles for gaming, streaming, music, art, AI/tech, business, study, fitness, cooking, beauty, anime, podcasts and more. Templates included: creator community, gaming community, digital-product customers, study group, small business.
  23. ## Install
  24. ```bash
  25. npx skills add Nyxiflare/discord-server-builder
  26. ```
  27. Or copy this folder to `~/.claude/skills/discord-server-builder`.
  28. ## Quick start
  29. 1. Create a server in Discord (or use an existing one).
  30. 2. Create a bot at the [Discord Developer Portal](https://discord.com/developers/applications) → **Bot** → **Reset Token**.
  31. 3. Put the token in a file called `.env` in your working folder:
  32. ```
  33. DISCORD_BOT_TOKEN=your-token-here
  34. ```
  35. Never paste the token into a chat or commit it. This repo's `.gitignore` already excludes `.env`.
  36. 4. Ask Claude: *"Set up my Discord server for my YouTube channel about ..."*
  37. Claude gives you the bot's invite link, shows you a preview of the layout, runs a dry run, and builds the server only after you approve.
  38. ## Ready-made blueprints
  39. Say *"Use the podcast-community blueprint for my server"* and Claude adapts it to you. Blueprints in
  40. [`blueprints/`](blueprints): indie game dev, podcast community, fitness challenge. The templates
  41. in `assets/templates` (creator, gaming, digital products, study group, small business, Spanish
  42. creator community) work the same way. To share your own server's layout, run `export` and open a
  43. pull request; [blueprints/README.md](blueprints/README.md) explains how.
  44. ## Requirements
  45. - Claude Code (or any agent that supports skills)
  46. - Python 3.9+ (standard library only; Pillow is optional, for auto-resizing emoji images)
  47. ## What still needs a bot
  48. The skill builds the structure. A few things only work with an always-online bot, and the skill
  49. recommends one and writes its setup for you: per-member welcome greetings, ticket button panels,
  50. classic emoji reaction roles, XP leveling, and running giveaway draws. Welcome screen and
  51. onboarding need Discord's Community setting turned on.
  52. ## Safety
  53. - The token is read from `.env` and never printed.
  54. - `apply` only creates things unless you pass `--update`. Deletes need `--confirm-delete`.
  55. - Every run can be previewed with `--dry-run`, and `undo` removes exactly what a run created.
  56. - After setup, you can remove the bot's Administrator permission.
  57. ## License
  58. MIT. See [LICENSE](LICENSE).

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.