Agent skill · software engineering · sickn33
lovable-cleanup
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.
Why this skill is useful
Adds a series of specific commands and procedures to clean up Lovable scaffolding that the AI wouldn't generate on its own.
What it needs
Requires react, vite installed locally. About 8k tokens when loaded. Last updated 2026-08-07. 44,571 stars on the source repository.
What this skill does
lovable-cleanup Remove every trace of Lovable scaffolding and ship the project as your own. Made with agentic-awesome-skills · author: whoisabhishekadhikari --- Overview Lovable (lovable.dev) bootstraps Vite + React + shadcn/ui projects with its own tagger dependency, branding, placeholder assets, and generated markdown docs baked in. Most developers export from Lovable and want a clean, ownable codebase before shipping or open-sourcing. This skill covers all 15 areas where Lovable leaves fingerprints. --- When to Use This Skill 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 CLEANUPSUMMARY.md, DEPLOYMENTGUIDE.md, or DEVELOPMENTSUMMARY.md index.html still has a generic <title> or Lovable favicon User wants to audit a Vite/React project for scaffolding leftovers before shipping --- Core Concepts What Lovable injects Lovable adds three categories of scaffolding that must be removed: 1. Dependency — lovable-tagger dev dep + componentTagger() call in vite.config.ts. This is the only runtime hook; removing it is always safe. 2. Branding artifacts — favicon.ico/png, og-image.png, logo.png, generic <title>, and a Lovable project URL in README.md. 3. Generated docs — CLEANUPSUMMARY.md, DEPLOYMENTGUIDE.md, DEVELOPMENTSUMMARY.md, LOGOUPDATE.md in the project root. Why the execution order matters Removing deps before editing source files avoids lockfile conflicts. Cleaning docs last means the README reflects the already-cleaned project. Unused dep footprint Lovable pre-installs the full shadcn/ui component set (~29 components) and all Radix UI primitives (~30 packages). Most projects use 5–10. The unused ones are safe to remove but @radix-ui/react-slot must be kept — it is an indirect dep used internally by many shadcn components via the asChild prop. --- Recommended Execution Order 1. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sickn33/lovable-cleanup--71a240