What problem does it solve? Deploying a Telegram bot to Railway risks message conflicts when local and live instances poll the same token, and broken builds when type errors slip through. This Skill enforces a disciplined pause → test → deploy → verify workflow to prevent those failures. ## Core Features & Use Cases - Conflict Prevention: Always pauses the live Railway service with railway down before local testing so two bot instances never fight over the same Telegram token. - Pre-Deploy Validation: Runs npx tsc --noEmit to catch TypeScript errors before pushing code. - Deployment & Verification: Deploys with railway up --detach and confirms health via railway logs, plus manages environment variables like TELEGRAM_BOT_TOKEN and GROQ_API_KEY. - Use Case: You fixed a bug in your Telegram bot locally. Use this Skill to pause the live bot, type-check, redeploy to Railway, and verify the logs show a clean startup. ## Quick Start Deploy my Gravity Claw bot to Railway using the standard pause, type-check, deploy, and verify cycle.