- Home
- Skills
- Omer Metin
- Skills For Antigravity
- Discord Bot Architect
discord-bot-architect_skill
- Python
21
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill omer-metin/skills-for-antigravity --skill discord-bot-architect- SKILL.md1.6 KB
Overview
This skill helps you design and build production-ready Discord bots using Discord.js (JavaScript) and Pycord (Python). It emphasizes modern interaction patterns—slash commands and components—while enforcing safe, scalable practices for intents, rate limiting, and sharding. The guidance is practical and focused on deployable patterns and failure modes.
How this skill works
The skill inspects bot architecture choices and validates them against proven patterns for interactions, gateway intents, rate limits, and sharding. It checks command design (slash vs message parsing), interaction acknowledgement timing, required intents, backoff behavior, and readiness for sharding and component-driven UX. It also flags critical failure modes and offers corrective recommendations.
When to use it
- Building a new Discord bot that must be production-ready and scalable
- Converting legacy message-parsing bots to slash commands and components
- Designing bots that will serve many guilds or require sharding
- Ensuring compliance with gateway intents and minimizing privileged scopes
- Diagnosing frequent rate-limit or interaction-timeout failures
Best practices
- Prefer slash commands and component interactions over parsing message content
- Acknowledge interactions within 3 seconds; defer responses for long tasks
- Request only the gateway intents you actually need; avoid privileged intents unless required
- Handle rate limits with exponential backoff and retry windows, not busy loops
- Plan for sharding from the start if you expect growth toward ~2,500+ guilds
- Test commands as guild-level first; promote to global once stable
Example use cases
- A support bot using slash commands, buttons, and modals for ticket workflows
- A moderation bot that only requests necessary intents and shards predictably
- A game or economy bot using interactive components and deferred responses
- A notification/service bot designed to handle rate limits smartly across many guilds
- Migrating an old bot to modern interactions while avoiding privileged intents
FAQ
Plan sharding when you approach thousands of guilds; practical thresholds start around 2,500 guilds. Design for sharding early to avoid architecture rework.
How fast must I respond to interactions?
Acknowledge interactions within 3 seconds. Use deferred responses if processing will take longer, so users see progress and the gateway stays satisfied.
How do I handle rate limits safely?
Implement exponential backoff and respect retry-after headers. Avoid tight retry loops and centralize rate-limit handling to prevent cross-shard cascades.