lovable-cleanup

Removes Lovable scaffolding, branding, and unused dependencies from exported Vite React projects.

1|Updated Jul 20, 2026
One-click install
npx skills add https://github.com/gonzoblasco/ai-developer-stack --skill lovable-cleanup-gonzoblasco
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: lovable-cleanup
Source: https://github.com/gonzoblasco/ai-developer-stack/tree/main/frontend-ui/lovable-cleanup
Command: npx skills add https://github.com/gonzoblasco/ai-developer-stack --skill lovable-cleanup-gonzoblasco

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Projects exported from Lovable (lovable.dev) ship with the platform's fingerprints baked in: the lovable-tagger dev dependency, generic titles and favicons, placeholder brand assets, generated markdown docs, and dozens of unused Radix UI packages. This Skill audits and strips all 14 areas of Lovable leftovers so the codebase ships as your own. ## Core Features & Use Cases - Full scaffolding audit: Runs a master grep scan across source, config, docs, and env files to locate every Lovable reference, then walks through removal in a safe execution order. - Dependency pruning: Diffs installed @radix-ui packages against actual imports to bulk-remove unused ones, while protecting @radix-ui/react-slot which shadcn/ui components require via the asChild prop. - Brand and docs cleanup: Replaces generic titles, favicons, and OG images, and flags generated files like CLEANUP_SUMMARY.md and DEPLOYMENT_GUIDE.md for deletion or repurposing. - Use Case: You exported a side project from Lovable and want to open-source it. Run the audit to remove lovable-tagger from vite.config.ts, rename the package, swap placeholder assets, prune 18 unused Radix packages, and verify with npm run build. ## Quick Start Ask the agent to audit your exported Lovable project and remove all Lovable scaffolding, branding, and unused dependencies, then verify the build passes.

Frequently Asked Questions about lovable-cleanup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I remove Lovable branding from my exported project?▼

Run a recursive grep for "lovable" across source, config, and markdown files, then follow the ordered cleanup: uninstall lovable-tagger, remove componentTagger from vite.config.ts, update the index.html title and favicon, and delete generated docs like CLEANUP_SUMMARY.md.

How do I remove lovable-tagger from a Vite project?▼

Run npm uninstall lovable-tagger, then delete the componentTagger import and its conditional call in the plugins array of vite.config.ts. If the lockfile still references it, delete node_modules and package-lock.json and reinstall.

Which Radix UI packages are safe to remove from a shadcn project?▼

Diff installed @radix-ui packages against actual imports in your source and uninstall the unused ones. Always keep @radix-ui/react-slot, since most shadcn/ui components depend on it internally through the asChild prop.

Why does my build fail after removing Radix packages?▼

The build fails because a removed package is still imported somewhere, often indirectly by a shadcn component in src/components/ui. Search those files for the missing @radix-ui import and reinstall that specific package.

Why does the browser tab still show the Lovable title after editing index.html?▼

A React-level title set by a Helmet or Head component in App.tsx or a layout wrapper overrides index.html at runtime. Update or remove that component to make the new title take effect.

What are the limitations of automated Lovable cleanup?▼

The cleanup does not create replacement brand assets like favicons or OG images, does not auto-fix components.json aliases, and does not cover Lovable backend integrations such as Supabase row-level security or edge functions.