Add both registration-level and runtime permission checks to moderation commands. default_member_permissions hides the command from unauthorized users in the slash menu, but a determined user can still execute it via Discord's API. Always check interaction.member.permissions in the handler for actual enforcement: if (!interaction.member.permissions.has(PermissionsBitField.Flags.KickMembers)) return interaction.reply({ content: 'Missing permissions.', ephemeral: true }).

Start with a simple version of your command, test it in a guild-specific registration, then add features one at a time. Trying to generate a /config command with 8 subcommands, nested option groups, and complex permission logic in one pass often produces code that needs significant manual adjustment. Incremental building is faster than fixing a complex generated output.

Use CHOICES for options that should have fixed values — like a /ban command where the reason category must be one of "harassment", "spam", or "tos_violation". In Discord.js: option.addChoices({ name: 'Harassment', value: 'harassment' }). This provides a dropdown in Discord's UI and eliminates typo-based input errors.

After generating a command, test it in a private test server with guild-specific registration before deploying globally. Guild registrations propagate instantly, so you can iterate on the handler logic and option configuration without waiting an hour for global propagation between each change.