laragram-v4-dev

An AI agent skill that assists with building, debugging, and maintaining Telegram bots and applications using LaraGram v4 (laraxgram/laragram) — a Laravel-inspired PHP framework for Telegram bot development.

What this skill does

This skill turns your AI coding agent into a LaraGram-aware assistant. It knows when to activate (any mention of LaraGram, LaraXGram, laraxgram/laragram, or project files like listens/bot.php and LaraGram\Support\Facades\Bot), and — critically — it never guesses at APIs from memory. Instead, it always checks the live docs at laraxgram.github.io/v4 before writing or explaining LaraGram-specific code, since the framework ships versioned docs and evolves quickly.

Core behavior: never invent APIs

Before answering any LaraGram-specific question, the skill:

1. Identifies the relevant doc page(s) via references/doc-map.md.
2. Fetches the live page(s) from https://laraxgram.github.io/v4/<page>.html.
3. Bases all code, class names, namespaces, and method signatures strictly on what the fetched docs show.

This applies even when the answer "feels" familiar — LaraGram is Laravel-like in philosophy, but its APIs aren't guaranteed to map 1:1, and confident recall is exactly how invented APIs slip into generated code.

Supported workflows

• Coding requests — generating features, commands, routes, listeners, middleware, models, and migrations with correct file placement and config.
• Architecture requests — designing bot structure, folder layout, and data flow for new or growing projects.
• Debugging requests — diagnosing container, routing, and event errors, and flagging version mismatches when a doc-confirmed API doesn't match the error.
• Learning / documentation requests — explaining LaraGram concepts (listeners, conversations, Step Manager, Temple8 templates, MTProto, Luna/TMAs) grounded in the actual docs, with careful Laravel comparisons.
• Upgrade / migration requests — walking through breaking changes using upgrade.html and releases.html.

Version handling

Defaults to LaraGram v4 docs and PHP 8.3+. If the conversation suggests v3 (older composer.json constraints, mismatched class names, or explicit mention), the skill asks rather than assumes, since v3 and v4 docs live in separate trees on the same site.

Stable conventions

A small set of structural facts are treated as safe to state without re-fetching docs, including:

use LaraGram\Request\Request;
use LaraGram\Support\Facades\Bot;

Bot::onText('hello', function (Request $request) {
    $request->sendMessage(chat()->id, 'hi');
});

Install and common commands:

composer create-project laraxgram/laragram <app-name>
php laragram serve
php laragram webhook:set
php laragram migrate

Everything more specific than this is verified against the live documentation before being presented.

Files

• SKILL.md — the skill definition (triggers, workflow, and behavior rules).
• references/doc-map.md — a sitemap of LaraGram v4 docs by category, used to decide which page(s) to fetch for a given task.

Installation

This skill follows the standard Agent Skills format and can be installed with the skills.sh CLI:

npx skills add itsnyxdev/laragram-v4-dev

---

This skill was generated with Claude Sonnet 5 by Nyx. (Yeah I'm not a liar)