Describe a command, get a command.

The AI Command Builder turns a plain-English sentence into a working slash command — logic, permissions, replies — that deploys to your server with one click.

How it works

You open the AI Builder from Build → AI Builder in the dashboard, write a prompt describing what you want, and Nexus generates a full command spec: trigger, options, the conditional logic, and the reply. You review the preview, edit anything that doesn't match, then click deploy.

Under the hood we use a structured prompt against Claude with a tight schema for the output, so the generation never returns something that won't actually run as a Discord slash command. You always see the generated logic before it goes live — there's no black-box "ship it" button.

Prompts that work well

Specific verbs and clear conditions beat vague descriptions. A few examples:

/warn — warn a member; ban them after 3 warnings.

/announce — post in #announcements; require Manage Server role;
            ping @everyone only if I add a "ping" flag.

/poll — create a poll with up to 6 options, 24h auto-close,
        show live vote counts in the message.

/level — show the user's current XP and rank; if they pass me
         a "@user" arg, show that member's instead.

Behind the scenes each of these expands into a fully configured slash command — permission gates, option types, response templates. You can see and edit all of it after generation.

What it can and can't do

It can: build moderation commands (warn, kick, ban, mute), informational commands (rank, server info, member stats), poll and giveaway-style commands, conditional reply flows ("if user has role X, say A; else say B"), and commands that read/write to a small bot-side counter (warnings, violations, etc.).

It can't: write code that runs on your own server, call arbitrary external APIs without you first storing credentials in Settings → API Keys, or generate commands that violate Discord's API terms (raid tooling, mass DMing, etc.).

For the in-between cases (HTTP webhook actions, custom logic you've sketched out), use the visual builder under Build → Commands. The AI Builder is a starting point — you'll often generate, then refine.

When to use the AI Builder vs. visual builder

Rule of thumb:

  • AI Builder when you can describe what you want in one or two sentences and you want the boilerplate out of the way. Especially good for moderation and informational commands.
  • Visual builder when the logic has many branches, requires precise external API calls, or you're iterating on an existing command. Drag-and-drop nodes, no AI credit cost.

Most servers end up using both — AI for the first draft, visual for the refinement.

Related