What problem does it solve? When you consider leaving Lovable or moving to another platform, it is hard to know which parts of your project you actually own and which are trapped in the platform. This Skill scans your repository and produces a clear portability report instead of vague reassurance. ## Core Features & Use Cases - Component Classification: Labels every major component (React frontend, Supabase tables, Edge Functions, RLS policies, prompt history, builder state) as Portable, Partial, Locked, or Unknown. - Structured Scan Procedure: Reads supabase/config.toml, checks git tracking of .agents/skills/, and inspects migrations and functions directories to ground every verdict in evidence. - Risk Summary & Next Steps: Rates overall migration risk as Low, Medium, or High and lists concrete actions like connecting an external Supabase project or committing uncommitted skills. - Use Case: Before switching hosting providers, ask for a migration readiness check to learn that your code and database are portable but your Lovable chat history and visual builder state would be lost. ## Quick Start Ask the assistant to run a migration readiness scan and report what is portable versus locked if I leave Lovable.
