How to Design a Discord Role and Channel Tree from a Community Brief
Discord trees rot when they add MEE6 and a 10k member claim. Bots was NONE. Voice was NONE. Draw the tree you were given. Not Slack.
The matching generator is the Discord Role and Channel Tree from a Community Brief 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).
Roles only the ones in the brief
Design a Discord role and channel tree from a community brief. No invented bots, Nitro perks, or member counts. 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:
Server name and audience: [Server]
Roles I allow (name + who gets it): [Roles]
Categories and channels I want: [Tree]
Permissions I can prove (view, send, manage): [Perms]
Bots I already run (or NONE): [Bots]
Rules I may pin: [Rules]
What must never be a channel: [Never]
Words I must not use: [Banned]
Onboarding I can prove (or NONE): [Onboard]
Voice I allow (or NONE): [Voice]
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.
Categories and channels from Tree
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:
- Honesty ledger: server, roles, channels, bots, voice. Forbidden: bots, member counts, and channels not listed.
- Role table: name, hoist yes/no only if Inputs said, who grants it. No @everyone extra powers unless Perms said so.
- Channel tree: categories then channels from Tree. Prefix # or voice as Voice allows.
- Perms: map Perms onto roles. Missing map writes NOT IN INPUTS, do not copy another server's template.
- Bots: only Bots. If NONE, no MEE6, no Carl, no invented verification bot.
- Onboard: only Onboard. If NONE, skip membership screening copy.
- Never: channels you will not create.
- Compliance pass: quote Banned words, Slack names, invented bots, invented 10k members. Cut them.
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.
If Bots is NONE, omit bots
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 role and channel tree. Not a Discord announcement, not Slack, not an AMA kit.
- Never invent a bot, Nitro perk, or member count.
- If Bots is NONE, omit bots.
- If Voice is NONE, no voice channels.
- No emojis unless Rules already use 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.
Not a Discord announcement and not Slack
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 role channel tree, discord server information architecture, no invented discord bots) 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.