Telegram용 챗봇 제작 Skill

The parts the demo skips: the real choice between long polling and a webhook made against your infrastructure, a token that never touches version control, per-chat state that survives a restart, and update handling that does not silently double-reply.

It works with you in your editor. Loaded into Claude Code or Cursor it reads your project, asks about your stack and deploy target, then writes the bot with you. You still review every change and take responsibility for what ships. It is a pair, not a generator.

It asks where the bot runs before answering. A server or container you control needs no public URL, so long polling is simpler and the right default. A serverless or auto-scaling deploy cannot sit waiting, so a webhook with a public HTTPS endpoint and a secret token is the honest answer there instead.

Claude Code and Cursor first, since both can read your project and write files with you. It also works pasted into Claude, ChatGPT or Gemini if you describe your project instead. Any assistant that accepts a long instruction file will follow it.

One instruction file you put in your project, delivered the moment the order goes through. It carries the architecture, the build order, the code your assistant writes with you and the failure modes for this stack. No subscription and no expiry.

Yes. Thirty days, money back, no questions asked. Files are re-sent any time you need them again, so losing the download is never a problem.