agentleFS
Sign inStart free
daniilganievdaniilganiev/telegram-dev/skills/new-mini-app/SKILL.md

new-mini-app

Skill0 starsChanged 36 days agoMITView on GitHub

Scaffold a Telegram Mini App with a backend that validates initData, optionally with a TON contract and TON Connect via Acton. Pass the project name and optionally "ton".

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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:

    Ask one question: what the app does in one sentence.

    line 12
  2. Very specific:

    Without ton: start from an official Telegram Mini Apps template on @tma.js/sdk (check the current list in its docs) and add a small …

    line 14
  3. Very specific:

    With ton: check acton --version (1.2.0+) and node --version (22.12+).

    line 17
  4. Distinctive:

    Add the Telegram layer: SDK init, theme variables, safe areas, back button, and a visible "TESTNET" badge when a wallet is involved.

    line 20

≈ “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

New Telegram Mini App

Arguments: $ARGUMENTS. The first word is the project name (ask if missing). Add ton when the app needs a TON contract.

  1. Ask one question: what the app does in one sentence. Use the telegram-dev skill to decide surfaces, payment method and the on-chain split; write PRODUCT.md.
  2. Without ton: start from an official Telegram Mini Apps template on @tma.js/sdk (check the current list in its docs) and add a small backend in the user's language with the initData validation from telegram-mini-app/references/init-data-validation.md.
  3. With ton: check acton --version (1.2.0+) and node --version (22.12+). On Windows Acton needs WSL; if it is missing, say so and stop rather than installing system tools. Then acton new <name> --template counter --app, acton build, acton test, npm ci.
  4. Add the Telegram layer: SDK init, theme variables, safe areas, back button, and a visible "TESTNET" badge when a wallet is involved.
  5. Wire the front end to the backend: send raw initData with each request and reject anything that fails validation.
  6. For ton, replace the counter contract step by step, keeping tests green after each step.
  7. Finish with what the user does by hand: BotFather /newapp or menu button, HTTPS hosting or a tunnel, TON Center testnet key if a wallet is used, testnet coins from a faucet.

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