agntdev
- 14 skills
- 0 followers
- 11 hours ago last updated
- ▌ Tgw · agntdev bundletgw CLI — TON blockchain from the terminal. Wallet info, transfers, jettons, NFTs, .ton DNS, prices, DEX swaps, and agent wallets. Package: @tongateway/cli
- ▌ Telegram Bot UI · agntdev bundleWire Telegram keyboards — the mechanics. Covers inline buttons, callback routing, reply_markup, grammY attach syntax, the inlined toolkit's UI builders (inlineButton, urlButton, inlineKeyboard, menuKeyboard, confirmKeyboard, paginate), ForceReply markup, custom keyboards for typed input (RequestContact, RequestLocation, RequestUser, RequestChat, RequestManagedBot), copy_text buttons, web_app buttons. USE FOR: inline buttons, keyboard, telegram menu, bot UI, callback buttons, pagination, reply_markup, ForceReply, copy_text, web_app, callback_data, prefix routing, regex routing — even if the user doesn't say "inline" or "keyboard" explicitly. DO NOT USE FOR: microcopy / flow patterns / error UX / onboarding / anti-patterns (see telegram-bot-ux router), or the Bot API foundation (see telegram-bot-api-fundamentals). Triggers: inline buttons, keyboard, telegram menu, bot UI, callback buttons, pagination, reply_markup, ForceReply, copy_text, web_app, callback_data, prefix routing, regex routing.
- ▌ Telegram Bot UX · agntdevRouter 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.
- ▌ Agnt CLI Builder · agntdev bundleBuild a whole_bot 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 bot-building patterns themselves (see telegram-bot-api-fundamentals, telegram-bot-ui, telegram-bot-ux-rules), or the deploy/runtime contract (see telegram-bot-deploy). Triggers: connect code, build the bot, ship the bot, agnt project show, agnt project blueprint, gh pr create, gh pr list, npm test, npm ci, npm run build, agnt whoami, agnt connect, agnt login, agnt bot show, agnt bot logs, agnt project rebuild.
- ▌ Telegram Bot Deploy · agntdevMake 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 (BOT_TOKEN vs BOT_TOKEN_FILE, Redis state, no webhook / no health port), and the inlined toolkit pattern. USE FOR: deploy bot, dist/index.js, BOT_TOKEN_FILE, REDIS_URL, Dockerfile, fly.io, docker compose, VPS, container_state, bot won't start, crash loop, bot starter template, inlined toolkit, agnt bot logs — even if the user doesn't say "deploy" or "Docker" explicitly. DO NOT USE FOR: Bot API foundation (see telegram-bot-api-fundamentals), session persistence (see telegram-bot-sessions), session FSM patterns (see telegram-bot-flow-patterns). Triggers: deploy bot, production ready, deploy pipeline, BOT_TOKEN_FILE, REDIS_URL, redis, Dockerfile, fly.io, docker compose, VPS, bot container, container_state, bot won't start, crash loop, inlined toolkit, agnt bot logs.
- ▌ Telegram Test Specs · agntdevWrite 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 specs, harness, command coverage, BotSpec JSON, tests/specs/*.json, tests/commands/*.json, GATE verdict, coverage gate — even if the user doesn't say "specs" or "test" explicitly. DO NOT USE FOR: programmatic vitest tests with mocks and edge-case fixtures (see telegram-test-advanced), or session persistence (see telegram-bot-sessions). Triggers: write bot tests, dialog specs, harness, command coverage, BotSpec JSON, tests/specs/*.json, tests/commands/*.json, GATE verdict, coverage gate.
- ▌ Telegram Bot Sessions · agntdevImplement 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, conversation flow, ctx.session.step, ctx.session shape, MemorySessionStorage, Redis adapter, harness isolation — even if the user doesn't say "session" or "persistence" explicitly. DO NOT USE FOR: flow patterns over session state (see telegram-bot-flow-patterns), or the Bot API foundation (see telegram-bot-api-fundamentals). Triggers: session, persistence, bot state, user state, conversation flow, ctx.session.step, ctx.session shape, MemorySessionStorage, Redis adapter, harness isolation.
- ▌ Telegram Bot UX Rules · agntdevShape the strings and timings a Telegram bot shows the user (microcopy, error UX, loading UX, media UX, chat-type UX, performance budgets). USE FOR: microcopy, button label, error message, loading state, sendChatAction, typing indicator, has_spoiler, sendPhoto, privacy mode, message_thread_id, performance budget, throttle, edits per minute, bot copy, error UX, loading UX — even if the user doesn't say "UX" or "error" explicitly. DO NOT USE FOR: flow patterns (see telegram-bot-flow-patterns), onboarding (see telegram-bot-onboarding), anti-patterns (see telegram-bot-anti-patterns), keyboard wiring (see telegram-bot-ui). Triggers: microcopy, button label, error message, loading state, sendChatAction, typing indicator, has_spoiler, sendPhoto, privacy mode, message_thread_id, performance budget, throttle, edits per minute, bot copy, error UX, loading UX.
- ▌ Telegram Test Advanced · agntdevEscape 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 telegram-test-specs. USE FOR: mock bot dependencies, test error paths, rate limit test, blocked user test, programmatic bot test, handleUpdate test, simulate api failure, payment test, vitest, vitest + grammy, mocked DB, mocked HTTP, edge-case Update fixtures — even if the user doesn't say "vitest" or "mock" explicitly. DO NOT USE FOR: declarative BotSpec JSON dialog tests (see telegram-test-specs — programmatic tests do NOT count toward the command-coverage gate). Triggers: mock bot dependencies, test error paths, rate limit test, blocked user test, programmatic bot test, handleUpdate test, simulate api failure, payment test, vitest, vitest + grammy, mocked DB, mocked HTTP, edge-case Update fixtures.
- ▌ Telegram Bot Onboarding · agntdevDesign 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, empty state, /help, follow-up, frequency cap, quiet hours, Mini App graduation, web_app button, welcome flow, new user flow — even if the user doesn't say "onboarding" or "Mini App" explicitly. DO NOT USE FOR: button wiring (see telegram-bot-ui), flow patterns (see telegram-bot-flow-patterns), microcopy rules (see telegram-bot-ux-rules). Triggers: onboarding, /start hero, first-run, empty state, /help, follow-up, frequency cap, quiet hours, Mini App graduation, web_app button, welcome flow, new user flow.
- ▌ Telegram Bot Anti Patterns · agntdev bundleFinal 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 (references/ux-review-checklist.md) for a final pre-ship sweep. USE FOR: code review, anti-pattern, ux review, completeness review, pre-ship, lint, don't, never, ship checklist, lint pass, review pass — even if the user doesn't say "review" or "anti-pattern" explicitly. DO NOT USE FOR: the underlying rules the anti-patterns break (see telegram-bot-ux-rules), or button wiring (see telegram-bot-ui). Triggers: code review, anti-pattern, ux review, completeness review, pre-ship, lint, don't, never, ship checklist, lint pass, review pass.
- ▌ Telegram Bot Flow Patterns · agntdevImplement a multi-step Telegram bot conversation. Covers five session-FSM primitives (typed step enum, cancel, per-step handler, flow-timeout sweeper, back/undo) and seven reusable patterns (linear wizard, branching menu, search-then-pick, multi-step form, undo, checklist flow, rich message flow, streaming AI). USE FOR: flow pattern, wizard, branching menu, search-then-pick, multi-step form, undo, checklist flow, rich message flow, streaming AI, FSM, ctx.session.step, multi-step conversation, bot flow design — even if the user doesn't say "flow" or "FSM" explicitly. DO NOT USE FOR: button wiring (see telegram-bot-ui), Bot API foundation (see telegram-bot-api-fundamentals), session persistence (see telegram-bot-sessions), microcopy / error UX (see telegram-bot-ux-rules). Triggers: flow pattern, wizard, branching menu, search-then-pick, multi-step form, undo, checklist flow, rich message flow, streaming AI, FSM, ctx.session.step, multi-step conversation, bot flow design.
- ▌ Telegram Bot API Fundamentals · agntdevWire 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 (callback_data 64 BYTES, message 4096 chars), parse_mode (HTML default, MarkdownV2 escape), and message entities. USE FOR: building a Telegram bot, grammY bot, bot entry point, bot token, long polling, webhook, callback_data limit, parse_mode, HTML, MarkdownV2, message entity, createBot, makeBot, Bot API limits — even if the user doesn't say "inline" or "keyboard" explicitly. DO NOT USE FOR: Rich Messages / Checklists / chat types / media (see telegram-bot-api-rich-messages), keyboard wiring (see telegram-bot-ui), UX rules (see telegram-bot-ux-rules). Triggers: build telegram bot, grammY bot, bot entry point, bot token, long polling, webhook, callback_data limit, parse_mode, HTML, MarkdownV2, message entity, createBot, makeBot, Bot API limits.
- ▌ Telegram Bot API Rich Messages · agntdevGo 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, message_thread_id, inline button, web_app button, copy_text, sendPhoto, sendDocument, sendPaidMedia, webhook, Mini App — even if the user doesn't say "rich" or "Telegram" explicitly. DO NOT USE FOR: HTTP / grammY / toolkit foundation (see telegram-bot-api-fundamentals), keyboard wiring (see telegram-bot-ui), UX rules (see telegram-bot-ux-rules). Triggers: rich message, sendRichMessage, sendRichMessageDraft, streaming AI, checklist, sendChecklist, chat types, message_thread_id, inline button, web_app button, copy_text, sendPhoto, sendDocument, sendPaidMedia, webhook, Mini App.