---
trigger: manual
---

# Workspace Rules: Laravel Telegram Bot

## 1. Project Context & Architecture
- This is a Laravel-based Telegram Bot project utilizing Blade for the web/admin interface.
- Architecture is modular: Controllers/Handlers manage specific bot actions. Never place multiple command logics in a single file.
- Look at the `structure_map.md` file first before making changes.

## 2. Shared Bot Components & Logic (CRITICAL)
- **Payment Methods:** The project already has 5 built-in payment flows (Card-to-Card, Online Gateways, Telegram Stars, Cryptocurrency, Wallet). Do NOT rewrite these logics; search for existing implementations and extend them.
- **Custom Emojis:** Use the pre-defined custom emojis and formatting rules for inline keyboards. Match the aesthetic of existing menus.
- **Localization:** Always use Laravel's localization system. Text strings must go into `lang/en/` and `lang/fa/`.

## 3. Execution & Efficiency
- Do NOT run `php artisan` commands (like serve, test, or migrate) automatically.
- Do NOT scan the entire `vendor/` or `node_modules/` folders.
- Write inline comments for new methods in Persian (`//`).

- **Database Context:** Do NOT try to connect to any remote MySQL database. Instead, always read the local SQL schema files or Laravel migrations inside the repository to understand the database structure and table relations.