Build a wholebot via the agntdev CLI (agnt). USE FOR: a one-time connect code in the prompt, a request to "build the bot" / "look at this project", an agnt project show report, or gh pr create against an agntdev bot repo — even if the user doesn't say "build" or "bot" explicitly. DO NOT USE FOR: the Telegram…
Final review pass before shipping a Telegram bot. Covers the 21 most common ways bots get rejected by the completeness review or fail UX review. Each anti-pattern is one file under references/ (read individually when you suspect you might be doing it). Also includes the 21-item UX review checklist…
Wire up the Telegram Bot API foundation. Covers how the HTTP client works (long polling vs webhook), how grammY wraps it (Bot instance, ctx, command routing, callback queries, middleware), the agntdev inlined toolkit (createBot / makeBot), the hard limits (callbackdata 64 BYTES, message 4096 chars), parsemode (HTML…
Go beyond plain text in a Telegram bot. Covers Rich Messages (Bot API 10.1), Checklists (Bot API 9.1), chat types, inline button types, media types, and the webhook contract. USE FOR: rich message, sendRichMessage, sendRichMessageDraft, streaming AI, checklist, chat types, messagethreadid, inline button, webapp…
Make an agntdev bot repo deployable, debug why a deployed bot won't start, or decide what build/deploy files to commit. Covers the build contract (dist/index.js, Node 20), the runtime contract (BOTTOKEN vs BOTTOKENFILE, Redis state, no webhook / no health port), and the inlined toolkit pattern. USE FOR: deploy bot…
Design a Telegram bot's first 30–60 seconds with a user. Covers /start hero and menu wiring, /help pattern, empty-state copy for first-run features, follow-up sequences (easy-exit, frequency caps, quiet hours), and the decision tree for graduating to a Telegram Mini App. USE FOR: onboarding, /start hero, first-run…
Implement user session persistence in a Telegram bot. Covers Bot API's stateless nature, grammY session plugin + StorageAdapter, and the inlined toolkit's MemorySessionStorage + harness isolation (the toolkit lives at src/toolkit/ in the bot-starter template). USE FOR: session, persistence, bot state, user state…
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…
Escape hatch when declarative BotSpec JSON runs out of road. Covers mocking external dependencies (DB / HTTP / payments), simulating Telegram API failures (429 rate limit, blocked user, message-not-modified), and writing raw handleUpdate tests with direct assertions. Assumes the tokenless harness model from…
Write dialog test specs for a Telegram bot. Covers why tokenless testing exists, how the harness replays Updates and captures API calls, BotSpec JSON format, coverage rules, and the test harness CLI. Tests are the objective publish gate — all specs must pass for the bot to publish. USE FOR: write bot tests, dialog…
★not rated 1▲
+1 4mo agoA189 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: