blessed_moon@studio
studio: Blessed Moon Studio
founder: Benito Pedro Xavier · Solo studio
discipline: Strategy · Design · Engineering
stack: Next.js · Tailwind · WebGL
scene: ASCII moon · 5 keyframes
type: Space Grotesk / JetBrains Mono
accent: #ff6a1f
sound: muted
status: ready
B / S / MCASE_23 / 26

— Case study 23

Benibot

Discord community tools, organised into small, independently configurable modules

All work
benibot.capture● verified
Benibot architecture illustration based on source: Discord commands routed to help, social, leveling and autoslash cogs, with PostgreSQL configuration; bot offline

project overview

A self-hosted Discord bot built on Red-DiscordBot, with custom help menus, community interactions, member levels and automatic slash-command registration. The case study documents the source; the bot remains offline.

shipped outcome

The repository contains custom help, social, leveling and autoslash modules plus container deployment scripts. The illustration maps those source modules; it is not a Discord session or a claim of current uptime.

Role
Custom bot development and deployment setup
Timeline
2026 — source-reviewed case study; bot offline
Year
2026
Team
Solo
The problem01

Community features become difficult to discover and maintain when every command grows inside one bot file. Moderators also need controls that apply to their own server.

The approach02

Red supplies the command framework and configuration backend. Separate custom cogs implement a category-based help browser, social interactions, XP with cooldowns and slash-command synchronisation. Configuration is scoped to the server or member as appropriate.

The result03

The repository contains custom help, social, leveling and autoslash modules plus container deployment scripts. The illustration maps those source modules; it is not a Discord session or a claim of current uptime.

— Delivery process

From operating constraint to shipped system

The work is sequenced around risk. Domain rules and failure states come before interface polish; automation arrives before handoff.

01

Build on the command framework

Use Red for permissions, configuration and cog loading rather than rebuilding the bot framework.

02

Make commands discoverable

A selectable help menu navigates from category to cog, command and syntax, with a way back.

03

Keep server state separate

Store engagement settings per server and XP per member; ignore bot messages and apply a cooldown.

04

Sync only when commands change

AutoSlash compares command signatures before syncing, avoiding unnecessary global registration calls.

— System architecture

Clear boundaries, explicit responsibilities

Each layer has one job and a narrow contract. That keeps external services replaceable and product behavior testable.

PythonRed-DiscordBotdiscord.pyPostgreSQLDocker
benibot.syssystem schematic

command / discover

$help

  1. category → cog
  2. command → syntax
  3. back to previous menu

source map · bot offline

cogs / isolated concerns

  1. help navigation
  2. social interactions
  3. XP with cooldown
  4. sync changed slash commands

configuration per server / member

Entry

Discord commands and events

Prefix and hybrid commands enter Red’s permission and dispatch system.

Framework

Red-DiscordBot

Loads cogs and provides configuration scoped to servers and members.

Custom modules

Help · social · leveling · autoslash

Independent modules handle discovery, interactions, XP and command registration.

Persistence

PostgreSQL configuration

The configured Red backend stores settings outside the bot process.

— What shipped

Product capabilities

01

Navigable help

Select menus expose categories, modules and command syntax without a long flat command list.

02

Member progression

XP, rank and leaderboards use server settings and an anti-spam cooldown.

03

Hybrid command registration

Slash-capable commands are enabled and synced automatically when the available set changes.

— Engineering pressure

Challenges resolved

01

Command visibility has limits

Only hybrid commands can become slash commands; prefix-only framework commands keep their original form.

02

Avoid repeated global syncs

Persisting the last command signature avoids spending Discord registration calls on unchanged restarts.

03

Keep the evidence honest

No bot was started for this case study. Source-backed architecture replaces an invented chat screenshot.

verified project destinations

next case studyInsta2Figma

next transmission

Need a system this deliberate?

Bring the operating problem. We will shape it into a clear product brief and a buildable next step.

Start a project