The 7-Phase Forge
VeloKit uses a unique 7-phase construction process to ensure your bot architecture is perfectly tailored to your needs.
Phase 1: Identity
This is where you set the foundation.
- Project Name: The folder name and
package.jsonidentity. - Bot Token: Optional at this stage, but if provided, it's pre-injected into your
.env.
Phase 2: Soul Selection
Choose the primary "focus" of your bot. This determines which core engine components are injected.
- Music: Injects Lavalink/NodeLink listeners.
- AI: Injects provider-specific templates.
- Moderation: Injects community management tools.
Phase 3: Engine Deep-Dive
If you selected a complex soul (like Music or AI), VeloKit asks for technical specifics:
- Music Engines: Lavalink vs NodeLink credentials.
- AI Providers: Gemini, Groq, or OpenAI keys.
Phase 4: Extra Injections
Layer additional command sets onto your core. You can add Moderation, Utility, or Owner-only tools regardless of your primary "Soul."
Phase 5: Infrastructure
Configure the backbone of your bot.
- Database: Choose between MongoDB (Mongoose) or PostgreSQL (Prisma).
- Intents: VeloKit automatically calculates required Gateway Intents.
- Docker: Generate production-ready container configurations.
Phase 6: Assembly
The CLI forges the code, copies templates, and replaces placeholders with your configuration.
Phase 7: Finalization
VeloKit runs a dependency sync and provides a detailed dashboard of your new bot architecture.