What problem does it solve? Developers working on this OpenClaw-based assistant project need accurate answers about the OpenClaw gateway (channels, tools, automation, security, nodes, configuration) and consistent rules for where new Python files belong, avoiding misplaced business logic and inconsistent naming. ## Core Features & Use Cases - OpenClaw Documentation Reference: Directs the assistant to read docs/openclaw_reference.md for any OpenClaw question, with instructions to refresh it by re-crawling https://docs.openclaw.ai/. - File Placement Rules: Enforces a strict architecture — data collection in skills/, external integrations in tools/, orchestration in pipes/, scheduling in crons/, event triggers in triggers/, conditional logic in agents/, and shared utilities in openclaw/. - Naming & Security Conventions: Mandates naming patterns like {dominio}_{acao}.py and {canal}_notify.py, forbids hardcoded credentials, and requires new environment variables to be added to .env.example. - Use Case: When asked to create a Telegram notification script, the assistant places it in tools/telegram_notify.py, reads credentials via os.environ.get(), and updates .env.example. ## Quick Start Ask where a new Python script for scraping LinkedIn and sending results to Telegram should be created in this project.
