30 Claude Prompts That Build Discord Bots

You are a discord.js engineer who builds interactive game bots. <context> I want a trivia bot that asks multiple-choice questions with buttons, scores answers, and tracks a leaderboard. Deliver a runnable, self-contained artifact. </context> <inputs> - Runtime: [DISCORD.JS V14 / DISCORD.PY V2] - Question source: [BUILT-IN SAMPLE SET / OPEN TRIVIA DB API] - Categories/difficulty: [DESCRIBE OR ANY] - Answer time limit: [E.G. 15s] - Points: [E.G. FIRST CORRECT 3, OTHERS 1] - Storage for scores: [JSON / SQLITE] - Commands: [/trivia /trivia-leaderboard] </inputs> <task> Build the bot with /trivia that posts a question as an embed with four labeled buttons, disables them after the time limit, reveals the correct answer, awards points (bonus for first correct), and updates persistent scores. Prevent double-answering by the same user. Add /trivia-leaderboard for the top 10. If using an external API, include fetch with a graceful fallback to the built-in set on failure. Keep sample questions and settings editable at the top. </task> <constraints> - One self-contained, runnable file; correct button-interaction handling and timeouts. - One answer per user per question; scores persist across restarts. - No unhandled promise rejections on timeout or API failure. </constraints> <format> Return the complete bot code, then explain how to swap in your own question bank or the trivia API. </format>

You are a discord.js engineer who builds turn-based text games. <context> I want a hangman-style word-guessing game where players guess letters and the bot tracks progress per channel. Deliver a runnable, self-contained artifact. </context> <inputs> - Runtime: [DISCORD.JS V14 / DISCORD.PY V2] - Word list source: [BUILT-IN THEMED LIST / CATEGORY] - Max wrong guesses: [E.G. 6] - Play mode: [SLASH COMMAND TO START, GUESS VIA MESSAGES / BUTTONS] - Multiplayer: [ANYONE IN CHANNEL CAN GUESS / SINGLE PLAYER] - Win/lose messages: [DESCRIBE] </inputs> <task> Build the bot with /hangman to start a game in a channel (rejecting a second concurrent game there), a display of the masked word, guessed letters, and remaining lives (ASCII gallows optional), letter-guess handling (via messages or buttons), correct/incorrect feedback, and win/lose detection that ends the game and reveals the word. Store one active game per channel in memory. Keep the word list editable at the top. </task> <constraints> - One self-contained, runnable file; one game per channel; ignore duplicate letter guesses. - Handle non-letter input and already-guessed letters gracefully. - Clean up the game state when it ends. </constraints> <format> Return the complete bot code, then explain the per-channel game state and how to add themed word lists. </format>

You are a discord.js engineer who builds fun content bots. <context> I want a bot that fetches a random meme or image on command from an API or a curated list, with basic NSFW safety. Deliver a runnable, self-contained artifact. </context> <inputs> - Runtime: [DISCORD.JS V14 / DISCORD.PY V2] - Source: [MEME API (E.G. meme-api.com) / CURATED URL LIST / SUBREDDIT] - Commands: [/meme, OPTIONAL /meme category] - NSFW handling: [ONLY IN NSFW CHANNELS / ALWAYS FILTER OUT NSFW] - Cooldown per user: [E.G. 5s] - Attribution: [SHOW SOURCE/TITLE IN EMBED] </inputs> <task> Build the bot with /meme that fetches from the configured source, checks the NSFW flag against the channel type, and posts the image in an embed with title and source link. Add a per-user cooldown to prevent spam, graceful handling of API errors or empty responses, and an optional category argument. Keep the source URL and settings in one CONFIG block. </task> <constraints> - One self-contained, runnable file; real fetch code with timeout and error handling. - Never post NSFW content in non-NSFW channels; respect the cooldown. - Handle network failures with a friendly "try again" reply, not a crash. </constraints> <format> Return the complete bot code, then explain how to switch sources and how the NSFW gate is enforced. </format>

You are a discord.js engineer who builds lightweight fun-command packs. <context> I want a small pack of randomness commands: magic 8-ball, dice roller, coin flip, and a "who wins" picker. Deliver a runnable, self-contained artifact. </context> <inputs> - Runtime: [DISCORD.JS V14 / DISCORD.PY V2] - Commands: [/8ball question, /roll NdN, /flip, /choose a b c...] - 8-ball answer set: [CLASSIC / CUSTOM LIST] - Dice syntax: [SUPPORT 2d6, d20, MODIFIERS LIKE 2d6+3] - Output style: [PLAIN / EMBED] - Per-user cooldown: [OPTIONAL] </inputs> <task> Build the bot with: /8ball that returns a random answer and echoes the question; /roll that parses NdN(+/-mod) dice notation, validates it, rolls, and shows each die plus the total; /flip for heads/tails; and /choose that picks randomly from the supplied options. Use a fair RNG, validate inputs (reject 0 dice, absurd counts), and format results cleanly. Keep the 8-ball answers in one editable array. </task> <constraints> - One self-contained, runnable file including command registration. - Dice parser must reject invalid or abusive input (e.g. 9999d9999) with a clear message. - Fair, unbiased randomness; no crashes on malformed dice strings. </constraints> <format> Return the complete bot code, then explain the dice-notation parser and the input caps you set. </format>

You are a discord.js engineer who builds two-player button games. <context> I want a two-player tic-tac-toe (or connect four) game played entirely with a button grid, tracking turns and detecting wins. Deliver a runnable, self-contained artifact. </context> <inputs> - Runtime: [DISCORD.JS V14] - Game: [TIC-TAC-TOE 3x3 / CONNECT FOUR] - Start command: [/ttt @opponent] - Turn enforcement: [ONLY THE CURRENT PLAYER CAN MOVE] - Symbols/colors: [X vs O, OR TWO EMOJI] - On win/draw: [ANNOUNCE + DISABLE BOARD] </inputs> <task> Build the bot with /ttt @opponent that renders the board as a grid of buttons in an ActionRow layout. Enforce turn order (only the player whose turn it is can press, only the two players can play), update the pressed button's label/style to the current player's mark, disable used cells, and check for a win or draw after each move. On game end, announce the result and disable the whole board. Store one game per message. Handle the opponent being a bot or the same user with a clear rejection. </task> <constraints> - One self-contained, runnable file including command registration. - Correct win/draw detection; only valid players and turns accepted. - Respect the 5-buttons-per-row limit in the grid layout. </constraints> <format> Return the complete bot code, then explain the board state model and the win-check logic. </format>

You are a discord.js engineer who builds scheduling utilities. <context> I want a reminder bot where users set reminders in natural durations and get pinged when they are due, surviving restarts. Deliver a runnable, self-contained artifact. </context> <inputs> - Runtime: [DISCORD.JS V14 / DISCORD.PY V2] - Storage: [SQLITE / JSON] - Command: [/remind duration message, PLUS /reminders and /reminder-cancel] - Duration format: [E.G. 10m, 2h, 3d, MIX LIKE 1h30m] - Delivery: [DM / SAME CHANNEL MENTION] - Max reminders per user: [OPTIONAL CAP] </inputs> <task> Build the bot with /remind that parses the duration, stores {userId, channelId, message, dueAt}, and confirms with the resolved due time. A restart-safe scheduler fires due reminders (ping the user with their message via DM or channel), then deletes them. Add /reminders to list a user's pending reminders and /reminder-cancel to remove one by ID. On ready, reload and reschedule everything from storage, firing any that came due while offline. </task> <constraints> - One self-contained, runnable file; reminders must survive a restart and catch up on missed ones. - Robust duration parser (supports combined units) with clear errors. - Optional per-user cap enforced with a friendly message. </constraints> <format> Return the complete bot code, then explain the duration parser and how offline-missed reminders are handled on startup. </format>

You are a discord.js engineer who builds voting and poll tooling. <context> I want a poll bot using buttons (not reactions) with a live vote tally, single-vote enforcement, and an optional timed close. Deliver a runnable, self-contained artifact. </context> <inputs> - Runtime: [DISCORD.JS V14] - Command: [/poll question option1 option2 ... duration] - Max options: [E.G. UP TO 5] - Vote rule: [ONE VOTE PER USER, CHANGEABLE] - Show results: [LIVE PERCENT BARS / HIDDEN UNTIL CLOSE] - On close: [DISABLE BUTTONS + POST WINNER] </inputs> <task> Build the bot with /poll that creates an embed with the question and one button per option, tracks votes in memory keyed by message, enforces one vote per user (allow changing it), and updates the embed with a live text bar chart and percentages after each vote. If a duration is given, close the poll automatically: disable the buttons, freeze the tally, and announce the winner (handling ties). Support up to the configured option count. </task> <constraints> - One self-contained, runnable file including command registration. - Exactly one active vote per user per poll; vote-change must move the count correctly. - Handle the button limit and empty-option cases; no crash on close. </constraints> <format> Return the complete bot code, then explain the vote-tracking model and how the live bar chart is rendered in text. </format>

You are a discord.js engineer who builds scheduled-messaging systems. <context> I want a bot that posts announcements on a recurring schedule (daily standup ping, weekly recap, etc.) using cron expressions. Deliver a runnable, self-contained artifact. </context> <inputs> - Runtime: [DISCORD.JS V14 + node-cron] - Timezone: [E.G. AMERICA/NEW_YORK] - Scheduled jobs: [CRON EXPR -> CHANNEL -> MESSAGE/EMBED, LIST SEVERAL] - Management commands: [/schedule-list, /schedule-add, /schedule-remove] - Storage for dynamic jobs: [JSON / SQLITE] - Mention a role in some posts: [YES / NO] </inputs> <task> Build the bot: load a set of scheduled jobs (cron expression, target channel, message/embed, optional role ping) from config and from persistent storage, register them with node-cron in the given timezone, and post on schedule. Add slash commands to list, add, and remove jobs at runtime (persisting changes and re-registering cron tasks). Validate cron expressions on add and reject bad ones with a clear error. </task> <constraints> - One self-contained, runnable file; include the node-cron install line and timezone handling. - Dynamic jobs must persist and re-register on restart. - Validate cron syntax; never register an invalid job. </constraints> <format> Return the complete bot code, then give three example cron expressions (daily, weekday-only, weekly) with plain-English meanings. </format>

You are a discord.js engineer who builds team-coordination utilities. <context> My community is global. I want a bot that lets members save their timezone and shows everyone's local time, plus converts a time between members. Deliver a runnable, self-contained artifact. </context> <inputs> - Runtime: [DISCORD.JS V14 (USE luxon OR dayjs FOR TZ)] - Storage: [SQLITE / JSON of userId -> IANA timezone] - Commands: [/settz, /time @user, /times (whole server board), /convert time from-tz to-tz] - Board format: [GROUPED BY REGION / SIMPLE LIST] - Validate timezone input: [YES] </inputs> <task> Build the bot with /settz to save a member's IANA timezone (validated), /time to show a member's current local time, /times to render a board of all members who set a timezone with their current time, and /convert to translate a given time from one zone to another. Use a real timezone library, validate zone names, and handle DST correctly. Keep the stored data restart-safe. </task> <constraints> - One self-contained, runnable file; include the timezone-library install line. - Reject invalid IANA names with a helpful example; handle DST via the library, not manual offsets. - Board must stay readable if many members are listed (chunk if needed). </constraints> <format> Return the complete bot code, then explain how timezones are validated and how the board handles long member lists. </format>

You are a discord.js engineer who builds support-ticket systems. <context> I want a support-ticket bot: members open a private ticket via a button, staff handle it, and closing archives a transcript. Deliver a runnable, self-contained artifact. </context> <inputs> - Runtime: [DISCORD.JS V14] - Ticket style: [PRIVATE CHANNEL PER TICKET / PRIVATE THREAD] - Panel channel + button label: [DESCRIBE] - Staff role: [SUPPORT ROLE ID/NAME] - Category for ticket channels: [CATEGORY ID, IF CHANNEL STYLE] - On close: [POST TRANSCRIPT TO LOG CHANNEL + DELETE/ARCHIVE] </inputs> <task> Build the bot with a /setup-tickets command posting a panel with an "Open Ticket" button. On click, create a private channel or thread visible only to the opener and staff, ping staff, and add a "Close" button. Prevent a user from opening multiple open tickets. On close (staff or opener), generate a text transcript of the messages, post it to the log channel with metadata, and archive or delete the ticket. Keep role/category/log config at the top. </task> <constraints> - One self-contained, runnable file including command registration. - Correct permission overwrites so only the opener and staff see the ticket. - One open ticket per user; transcript generation must not crash on empty tickets. </constraints> <format> Return the complete bot code, then explain the permission-overwrite setup and the transcript format. </format>

You are a discord.js engineer who builds community feedback systems. <context> I want a suggestion board where members submit ideas that post as embeds with upvote/downvote buttons and a live score, and staff can approve or reject them. Deliver a runnable, self-contained artifact. </context> <inputs> - Runtime: [DISCORD.JS V14] - Submit method: [/suggest text / MODAL FORM] - Suggestions channel: [CHANNEL ID/NAME] - Vote buttons: [UPVOTE / DOWNVOTE with live net score] - Staff actions: [APPROVE / REJECT / CONSIDER, staff role gated] - Storage: [SQLITE / JSON] </inputs> <task> Build the bot with /suggest (or a modal) that posts the suggestion as an embed with the author, an incrementing suggestion ID, upvote/downvote buttons, and a running net score. Enforce one vote per user (changeable). Add staff-only buttons or a /suggestion-status command to mark a suggestion Approved/Rejected/Considered, recoloring the embed and appending a staff note. Persist votes and statuses across restarts. </task> <constraints> - One self-contained, runnable file including command registration. - One vote per user per suggestion; staff actions gated to the staff role. - Votes and statuses persist; embed updates in place, no duplicate posts. </constraints> <format> Return the complete bot code, then explain the vote and status data model and how staff actions recolor the embed. </format>

You are a discord.js engineer who builds highlight/starboard systems. <context> I want a starboard: when a message gets enough ⭐ reactions, the bot reposts it to a dedicated starboard channel and keeps the star count in sync. Deliver a runnable, self-contained artifact. </context> <inputs> - Runtime: [DISCORD.JS V14] - Star emoji: [⭐ OR CUSTOM] - Threshold: [E.G. 5 STARS] - Starboard channel: [CHANNEL ID/NAME] - Ignore self-stars: [YES / NO] - Storage: [SQLITE / JSON mapping original -> starboard message] </inputs> <task> Build the bot: on messageReactionAdd/Remove for the star emoji, count unique starrers (optionally excluding the author's self-star), and when the threshold is reached repost the message to the starboard as an embed showing the content, author, jump link, any attached image, and the star count. Update the count live as stars change; if it drops below threshold, optionally remove or keep the starboard entry. Prevent duplicate starboard posts for the same message. </task> <constraints> - One self-contained, runnable file; GuildMessageReactions intent and partials handled. - Never repost the same message twice; keep the original -> starboard mapping persistent. - Handle deleted originals and messages without text (image-only) gracefully. </constraints> <format> Return the complete bot code, then explain the dedupe mapping and how live count updates work. </format>

You are a discord.js engineer who builds giveaway and raffle systems. <context> I want a giveaway bot: staff start a timed giveaway, members enter by clicking a button, and the bot picks winners fairly when time is up. Deliver a runnable, self-contained artifact. </context> <inputs> - Runtime: [DISCORD.JS V14] - Command: [/giveaway prize duration winners] - Entry: [ENTER BUTTON with live entrant count] - Requirements: [OPTIONAL REQUIRED ROLE / MIN ACCOUNT AGE] - Storage: [SQLITE / JSON, restart-safe] - Extras: [/giveaway-reroll, /giveaway-end early] </inputs> <task> Build the bot with /giveaway that posts an embed showing prize, end time, and winner count with an Enter button; track unique entrants and update the count; enforce any role/age requirement on entry with a clear rejection. When the timer ends (restart-safe scheduler), pick the required number of unique random winners fairly, announce them with a mention and jump link, and handle the "not enough entrants" case. Add /giveaway-reroll and an early-end command. </task> <constraints> - One self-contained, runnable file including command registration. - Fair, unbiased winner selection with no duplicates; entries and timers persist across restarts. - Enforce requirements at entry time; handle zero/low entrants gracefully. </constraints> <format> Return the complete bot code, then explain the winner-selection fairness and how reroll excludes previous winners. </format>

You are a discord.js engineer who builds event-coordination bots. <context> I want an event bot: staff announce an event, members RSVP as Going / Maybe / Can't via buttons, and the bot shows live attendee lists and reminds attendees before it starts. Deliver a runnable, self-contained artifact. </context> <inputs> - Runtime: [DISCORD.JS V14] - Command: [/event title datetime description] - Datetime input: [E.G. ISO OR "2026-08-01 18:00" WITH TIMEZONE] - RSVP options: [GOING / MAYBE / CANT] - Reminder: [PING "GOING" LIST N MINUTES BEFORE] - Storage: [SQLITE / JSON] </inputs> <task> Build the bot with /event that posts an embed showing title, time (as a Discord timestamp so each user sees their local time), description, and three RSVP buttons with live counts and name lists. Track each member's single RSVP status (changeable). Store the event and, via a restart-safe scheduler, DM or ping the Going list a configurable time before start. Handle the event passing (lock RSVPs, mark as ended). Keep config at the top. </task> <constraints> - One self-contained, runnable file including command registration. - Use Discord's <t:unix:F> timestamp format so times auto-localize; one RSVP per user. - Reminders and event state persist across restarts; lock RSVPs after start. </constraints> <format> Return the complete bot code, then explain the datetime parsing, the Discord timestamp trick, and how the reminder is scheduled. </format>

You are a discord.js engineer who builds community-analytics bots. <context> I want a stats bot that tracks message and voice activity and shows a weekly leaderboard, plus a per-member stats card. Deliver a runnable, self-contained artifact. </context> <inputs> - Runtime: [DISCORD.JS V14 / DISCORD.PY V2] - Storage: [SQLITE preferred] - Tracked metrics: [MESSAGES, VOICE MINUTES, REACTIONS GIVEN] - Time windows: [ALL-TIME + ROLLING 7-DAY] - Commands: [/stats @user, /leaderboard metric window] - Exclude channels: [BOT-SPAM, ETC] </inputs> <task> Build the bot that increments per-user message counts on messageCreate (ignoring excluded channels and bots), tracks voice minutes via voiceStateUpdate (accumulating time between join and leave), and optionally counts reactions. Store timestamped events or rolling counters so a 7-day window is computable. Add /stats to show a member's card (messages, voice time, rank) and /leaderboard with a metric and window argument rendering the top 10 with text bars. Keep everything restart-safe. </task> <constraints> - One self-contained, runnable file; correct intents (GuildVoiceStates, GuildMessages). - Accurate voice-time accounting across join/leave/move; exclude bots and excluded channels. - Persistent storage; leaderboard queries must be efficient, not scan-everything-each-time if avoidable. </constraints> <format> Return the complete bot code, then explain the voice-time accounting and how the 7-day window is computed from storage. </format>