gaelic-ghost Discord App Workflow
Workflow
- Choose a bot, user-installed app, guild-installed app, or Activity. Do not select Gateway when signed HTTP interactions are sufficient.
- Register the application and scope the requested permissions, OAuth installation, commands, and intents to the least access needed.
- For interactions, verify Discord's signature, answer the required initial interaction promptly, and use follow-ups or deferred responses for longer work.
- For Gateway usage, document intents, privileged-intent approval, reconnect/resume state, sharding threshold, and rate-limit behavior.
- Model commands, buttons, selects, and modals as explicit user actions with durable component state and authorization checks.
- Validate in a test guild/account with observed command registration, signature verification, retry/duplicate behavior, and permission denial.
Handoffs
Use webhook-and-event-lifecycle for request handling, conversation-state-human-handoff for state, and the target server stack skill for implementation. Consult the Discord application overview and Interactions documentation before asserting behavior.