customize

# Deus Customization This skill helps users add capabilities or modify behavior. Use AskUserQuestion to understand what they want before making changes. ## Workflow 1. **Understand the request** - Ask clarifying questions 3. **Plan the changes** - Identify files to modify. If an installer skill exists for the request (e.g., `/add-telegram` for adding Telegram), tell the user to run it themselves instead of implementing manually (`/add-*` setup skills are user-invoked and cannot be triggered programmatically). 4. **Implement** - Make changes directly to the code 5. **Test guidance** - Tell user how to verify ## Key Files | File | Purpose | |------|---------| | `src/index.ts` | Orchestrator: state, message loop, agent invocation | | `src/channels/whatsapp.ts` | WhatsApp connection, auth, send/receive | | `src/ipc.ts` | IPC watcher and task processing | | `src/router.ts` | Message formatting and outbound routing | | `src/types.ts` | TypeScript interfaces (includes Channel) | | `src/config.ts` | Assistant name, trigger pattern, directories | | `src/db.ts` | Database initialization and queries | | `src/whatsapp-auth.ts` | Standalone WhatsApp authentication script | | `groups/CLAUDE.md` | Global memory/persona | ## Common Customization Patterns ### Adding a New Input Channel (e.g., Telegram, Slack, Email) Questions to ask: - Which channel? (Telegram, Slack, Discord, email, SMS, etc.) - Same trigger word or different? - Same memory hierarchy or separate? - Should messages fr...