agentleFS
Sign inStart free
daniilganievdaniilganiev/telegram-dev/skills/add-ton-connect/SKILL.md

add-ton-connect

Skill0 starsChanged 37 days agoMITView on GitHub

Add TON Connect to an existing Telegram Mini App — manifest, connect button, wallet login with ton_proof verified on the backend, and binding the wallet to the Telegram user. Testnet by default.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read the project: front-end framework, backend language, how initData is validated today.

    line 8
  2. Very specific:

    If it isn't validated on the server yet, fix that first (telegram-mini-app).

    line 9
  3. Very specific:

    Ask why the wallet is needed (login, payouts, owning NFTs or tokens, deposits).

    line 10

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Add TON Connect

  1. Read the project: front-end framework, backend language, how initData is validated today. If it isn't validated on the server yet, fix that first (telegram-mini-app).
  2. Ask why the wallet is needed (login, payouts, owning NFTs or tokens, deposits). If the answer is "to pay for in-app items", stop and explain the Stars rule (telegram-payments).
  3. Front end: the current TON Connect SDK for the framework (AppKit or @tonconnect/ui-react; check the docs), a public tonconnect-manifest.json over HTTPS, twaReturnUrl set to the bot or app link, a network badge.
  4. Backend, following telegram-ton/references/ton-proof-auth.md:
    • an endpoint that issues a one-time nonce with a short expiry, tied to the Telegram user;
    • verification of the proof: domain, timestamp, network, public key from walletStateInit, address match, nonce used once;
    • store the binding Telegram user id ↔ wallet address only after both initData and the proof pass.
  5. Tests for: reused nonce, wrong domain, expired proof, testnet proof on a mainnet config, address mismatch.
  6. Report what the user does by hand: host the manifest and icon, TON Center testnet key in the backend env, a testnet wallet for manual testing.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free