`/setup`

Requires: Manage Server

/setup does two jobs. On a brand-new server it runs a short first-run flow — four questions and one atomic save. Every run after that opens a health dashboard that keeps your configuration honest.

First run — four questions

Rather than a long wizard, first-run asks only what it can't infer, previews every change, then writes it all in a single save:

What is this server for? — pick one or more archetypes: ⚔️ Moderation (audit and enforce), 💰 Economy (track the guild's coin), 🏘️ Community (engage members). Your choices pick smart presets for everything else.
Where should alerts go? — your alerts channel. This is the one genuinely required field.
Who is staff? — the roles that can approve requests, plus treasurer roles if you track a currency.
Do you track a currency? — the economy opt-in. Skipped automatically if you picked the 💰 Economy archetype.

Before anything is saved you see a preview of every change. The presets fill in the rest, so you're never hunting through settings just to get started.

The health dashboard

Once first-run is done, /setup becomes a live diagnostic of your server — not a wizard you repeat:

Diagnostics with one-click fixes — each finding (a missing channel, an absent staff role) comes with an inline button to fix it on the spot.
Quick-enable rows — turn on off-by-default features like anti-spam in a single press.
Permission preflight — confirms the bot actually holds the permissions your configuration needs.
Test-alert fire — send a live test alert to check routing end to end.
Guided tour — walk the command surface without leaving Discord.

The dashboard only ever enables things and never touches your economy settings — that stays in /ledger.

Where settings live afterward

/setup gets you going and keeps you healthy; /config is the permanent home for every setting, organized into six domains. Anything first-run chose can be revisited there at any time.