메뉴
Add a new teloxide update handler (Message, EditedMessage, CallbackQuery, ChatMemberUpdated, MyChatMember) routed through the dispatcher tree. Use when adding bot reactions to a Telegram event.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | add-telegram-handler |
| description | Add a new teloxide update handler (Message, EditedMessage, CallbackQuery, ChatMemberUpdated, MyChatMember) routed through the dispatcher tree. Use when adding bot reactions to a Telegram event. |
Read first:
AppError, inspect_err for graceful degradation.server/src/telegram/handlers/{name}.rs.server/src/telegram/dispatcher.rs.server/tests/telegram_{name}.rs or #[cfg(test)] mod tests.#[tracing::instrument(skip(bot, state), fields(chat_id = %update.chat.id, user_id))]
pub async fn handle_x(bot: Bot, update: Message, state: AppState) -> Result<()> {
// ...
Ok(())
}
handlers/{name}.rs with one pub async fn per update kind.dispatcher.rs under the matching Update::filter_* chain.#[tracing::instrument]; record chat_id, user_id, message kind.Bot or DB-backed integration tests.chat_id membership inside the handler.bot.answer_callback_query(q.id) within ~30s, even with no text. Telegram greys out the button forever otherwise.bot.send_*().await shouldn't kill the handler. Use .inspect_err(|e| tracing::warn!(?e, "send failed"))? (or swallow with let _ = ...) where graceful degradation matters more than the bubble-up.state.verified.get((chat_id, user_id)), 10min TTL) before issuing a captcha — avoids re-challenging an already-verified user.i64. Never i32 (supergroup IDs -100… overflow), never u64..unwrap() on bot.*() calls. Network failures aren't bugs.cargo test --lib telegram::handlers.cargo clippy --all-targets -- -D warnings.add-slash-command — /-prefixed commands with BotCommands derive.captcha-pipeline — captcha-issue + solve flow.spam-rule — message-classification cascade.tracing-spans — how to wire spans + structured fields.Bump the patch version in server/Cargo.toml or website/package.json after completing a major change. Use when the user asks to bump/release a version, or when CLAUDE.md's rule about version bumps after major changes applies.
Before a non-trivial change, list affected systems — DB schema, API contract, Telegram handlers, jobs, TS types, docs. Catch ripple effects upfront, not after CI fails. Use when planning a feature, migration, refactor, or any cross-module touch.
Self-review before push — read the diff as a reader, scan for vixen footguns (token leaks, PII, idempotency, captcha asset overwrites), run validation pipeline, no surprise files. Use before "git push", before opening a PR, or when the user says "ready to commit".
Write a git commit message for vixen-rs following the project's Conventional Commits convention. Use when the user asks to commit, create a commit, or write a commit message.
Reproduce → bisect → root cause → fix → verify. Don't speculate, don't "add more error handling" as a guess. Use when something is broken, when a test fails intermittently, when the user says "this isn't working" or "investigate why".
Write small, fast, reproducible Dockerfiles for the vixen-rs server (Rust) and website (bun) using multi-stage builds, cache mounts, distroless/alpine runtime images, and non-root users. Use when editing server/Dockerfile, website/Dockerfile, docker-compose.yml, or when the user asks to shrink an image or speed up a Docker build.