What problem does it solve? Moving an application off Heroku onto Render requires manually translating Procfiles, dyno sizes, add-on plans, config vars, and databases into Render equivalents, which is error-prone and time-consuming. This Skill automates that translation by reading local project files, mapping Heroku resources to Render plans, and producing a validated render.yaml Blueprint or directly created services. ## Core Features & Use Cases - Local Inventory and Plan Mapping: Reads Procfile, package.json, requirements.txt, Gemfile, and app.json to detect runtime, process types, and add-ons, then maps dyno sizes and add-on plan slugs to concrete Render plans with cost estimates. - Blueprint Generation and Validation: Generates a render.yaml using the projects/environments pattern with fromDatabase and fromService references, validates it with the Render CLI, and produces a working dashboard deploy deeplink. - Data Migration and Verification: Guides Postgres migration via pg_dump/pg_restore or render psql based on database size, migrates Redis when needed, and verifies deploys, logs, metrics, and row counts before DNS cutover. - Use Case: A team with a Rails app using a web dyno, Sidekiq worker, Heroku Postgres Standard-0, and Heroku Redis runs this Skill to get a validated render.yaml, cost comparison table, data migration commands, and a post-migration health check. ## Quick Start Migrate my Heroku app to Render by reading this repo's Procfile and dependency files, then generate and validate a render.yaml Blueprint.
