The zaileys orchestrator — handles ANY zaileys task (type-safe Node.js/TypeScript WhatsApp framework on Baileys). Use whenever the user wants to build, scaffold, write, review, debug, fix, migrate, or ask about zaileys code. Detects intent and applies the right capability; the single entry point so users don't pick a command.
Use to REVIEW / AUDIT / CHECK existing zaileys (Node.js/TypeScript WhatsApp framework WhatsApp framework) code against best practices, anti-patterns, and ban-safety — triggers on "review my bot", "cek kode", "is this correct", "best practice?", or before shipping/deploying a zaileys bot. Covers BOTH providers: unofficial WhatsApp Web and the official Meta Cloud API (webhook signatures, template-gating, 24h window, idempotency).
Use when a zaileys app throws an ERROR/exception/stack trace (or a `.code` like EMPTY_CONTENT, INVALID_OPTIONS, SEND_FAILED, STORE_NOT_AVAILABLE, UNSUPPORTED_ON_CLOUD, or a Graph code like 131047/132000) or hits a runtime PROBLEM ("kenapa error", "not working", "failed to", reconnect loop, QR keeps regenerating, "Cannot find module", session invalid/corrupted, webhook 401/403, template rejected) and wants it diagnosed and fixed. Covers BOTH providers — unofficial WhatsApp Web and the official Meta Cloud API. The zaileys (Node/TS WhatsApp framework) error doctor.
Use when the user wants to CREATE, BUILD, SCAFFOLD, or SET UP a NEW zaileys WhatsApp bot or project from scratch ("buatkan bot WhatsApp", "create a whatsapp bot", "set up zaileys", "new bot project", "bikin bot zaileys"). Supports BOTH providers — unofficial WhatsApp Web (QR/ pairing) and the official Meta Cloud API (provider:'cloud', token + webhook, templates/OTP). Generates a complete, runnable zaileys project with a clean, layered `src/` structure that is identical across sessions for the same spec.