mode-creator

# Mode Creator Create a useful note-taking system, not merely a valid JSON file. Interview the user, propose a small taxonomy, obtain approval, install it durably, configure optional alerts, restart the worker, and prove the active mode appears in startup context. ## Ground rules - Use the available interactive question tool (`AskUserQuestion`, `request_user_input`, or equivalent) for the interview. Ask in small batches and wait for each response. - Explain observation types as mutually exclusive kinds of notes and concepts as reusable tags. Avoid jargon unless the user uses it first. - Inspect existing bundled and user modes before inventing a new one. Reuse or remix a close match when that serves the user better. - Do not edit a plugin cache or bundled mode. Install custom files under the resolved claude-mem data directory's `modes/` folder. - Do not expose a Telegram token in chat, command arguments, logs, or tool output. Treat it like a password. - Preserve unrelated settings and existing Telegram triggers. The helpers make timestamped backups and merge requested triggers. - Custom modes are supported by the local worker runtime. If `CLAUDE_MEM_RUNTIME` is `server`, explain that this workflow cannot safely install a per-user mode into the shared server and stop before mutation. - Existing observations keep their original types. The new mode applies to future observation generation. ## 1. Open with the purpose Begin with this message inside the first interactive quest...