domains / families / software-engineering / lovable-cleanup
lovable-cleanup
authentic
Audits and strips Lovable scaffolding from Vite + React projects — removes lovable-tagger, swaps placeholder assets, prunes unused Radix deps, cleans generated docs, and neutralizes stale favicon/CDN caching so the codebase ships as yours.
When to use
- User says "clean up my Lovable project" or "remove Lovable branding"
- User says "de-Lovable", "I exported from Lovable", or "audit for Lovable leftovers"
- Project contains `lovable-tagger` in `package.json`
- Project contains `CLEANUP_SUMMARY.md`, `DEPLOYMENT_GUIDE.md`, or `DEVELOPMENT_SUMMARY.md`
- `index.html` still has a generic `<title>` or Lovable favicon
- User wants to audit a Vite/React project for scaffolding leftovers before shipping
When not to use
- This skill does not create or source real brand assets (favicons, OG images). Area 15
- Dep pruning (Area 13) is safe but not foolproof — some Radix packages are indirect deps
- The skill does not modify `components.json` aliases automatically — it only scans and
- Does not cover Lovable-specific backend integrations (Supabase row-level security, edge
Skill page
Source