Telegram Bot UX

Router for Telegram bot UX skills. Picks the right sub-skill based on the UX concern. USE FOR: bot UX, user experience, telegram bot copy, telegram bot design, "make the bot feel right", "what should the bot say", "how should the bot behave" — even if the user doesn't say "UX" or "Telegram" explicitly. DO NOT USE FOR: keyboard wiring mechanics (see telegram-bot-ui), Bot API ground truth (see telegram-bot-api-fundamentals), flow patterns (see telegram-bot-flow-patterns), or session persistence (see telegram-bot-sessions). Triggers: bot UX, user experience, telegram bot copy, telegram bot design, make the bot feel right, what should the bot say, how should the bot behave.

agntdev Updated

File contents

telegram-bot-ux — router

The UX bundle for Telegram bots is split across four skills. Pick based on the concern:

  • Strings and timings (microcopy, error/loading UX, media UX, chat-type UX, performance budgets) → telegram-bot-ux-rules
  • Multi-step conversation patterns (wizard, branching menu, search-then-pick, multi-step form, undo, checklist, rich message, streaming AI) → telegram-bot-flow-patterns
  • First 30–60 seconds with a user (/start hero, /help, empty state, Mini App graduation) → telegram-bot-onboarding
  • Pre-ship review pass (20 anti-patterns + 21-item UX checklist) → telegram-bot-anti-patterns

For keyboard wiring mechanics, see telegram-bot-ui. For the Bot API foundation, see telegram-bot-api-fundamentals.

Built for the agntdev pipeline. See agnt-cli-builder for the build loop.

agntdev/skills commit 9de1c81691

Frequently asked questions

npx get-skill add agntdev/telegram-bot-ux