Remove unwanted Lovable scaffolding while preserving required attribution, licenses and useful project history.
Made with agentic-awesome-skills · author: whoisabhishekadhikari
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.
lovable-tagger in package.jsonCLEANUP_SUMMARY.md, DEPLOYMENT_GUIDE.md, or DEVELOPMENT_SUMMARY.mdindex.html still has a generic <title> or Lovable faviconLovable adds three categories of scaffolding that must be removed:
lovable-tagger dev dep + componentTagger() call in vite.config.ts.Verify all configuration/import references and project-specific use before removal.
favicon.ico/png, og-image.png, logo.png, generic <title>,and a Lovable project URL in README.md.
CLEANUP_SUMMARY.md, DEPLOYMENT_GUIDE.md, DEVELOPMENT_SUMMARY.md,LOGO_UPDATE.md in the project root.
Inspect source/config references before removing dependencies; update the manifest and lockfile with the project’s existing package manager. Cleaning docs last
means the README reflects the already-cleaned project.
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.
or CDN caching can keep the old icon visible, so verify the live response
# Welcome to your Lovable project with the real project titlehttps://lovable.dev/projects/REPLACE_WITH_PROJECT_ID✅ After stripping, read the README end-to-end. Offer to write a replacement intro
paragraph if large sections were removed.
"lovable-tagger" from devDependencies"name" from "vite_react_shadcn_ts" to the real project name (kebab-case)scripts block for "lovable" or "lovable:*" entries and remove themgrep -n "lovable" package.json
import { componentTagger } from "lovable-tagger"mode === 'development' && componentTagger() from the plugins array.filter(Boolean) if it was only present to handle the conditional taggergrep -n "lovable\|componentTagger\|filter(Boolean)" vite.config.ts
<title> with the real product name<!-- Generated by Lovable --> comments or Lovable meta tagsgrep -in "lovable\|generator" index.html
Replace these files (keep filenames, swap content):
| File | Action |
|---|---|
favicon.ico | Overwrite with real icon — do NOT just delete, see Area 15 |
favicon.png | Replace with real icon |
og-image.png / logo.png | Replace with real brand assets |
placeholder.svg | Delete only after checking source, CSS, dynamic paths and deployed references |
✅ Flag which files are actually referenced in <head> vs dead weight so the user
knows what to prioritise.
src/main.tsx — scan for Lovable HOCs, wrappers, or commentssrc/App.tsx — same// generated by Lovable headersgrep -rn "lovable\|Lovable" src/ --include="*.tsx" --include="*.ts"
npm uninstall lovable-tagger
grep "lovable-tagger" package-lock.json
Use yarn remove or pnpm remove if the project uses those instead.
Double-check after Area 2 — scripts are sometimes injected separately from deps:
grep -n '"lovable' package.json
# Print filenames only: matching values may contain credentials.
rg -l -i "lovable" -- .env .env.local .env.example 2>/dev/null
Remove any Lovable API keys or project IDs. If a variable is Lovable-only, delete the
entire line — don't leave an empty key.
Delete or repurpose these common Lovable-generated files:
CLEANUP_SUMMARY.mdDEPLOYMENT_GUIDE.mdDEVELOPMENT_SUMMARY.mdLOGO_UPDATE.mdgrep -rln "lovable\|Lovable" *.md 2>/dev/null
✅ Skim each file before deleting — Lovable docs sometimes contain useful architecture
notes worth preserving in a rewritten CONTRIBUTING.md or ARCHITECTURE.md.
Usually clean — confirm and move on:
grep -in "lovable" \
public/robots.txt public/sitemap.xml public/_redirects \
vercel.json netlify.toml 2>/dev/null
After replacing og-image.png, update OG meta in index.html:
<meta property="og:image" content="/og-image.png" />
<meta property="og:url" content="https://your-domain.com" />
<meta property="og:title" content="Your Real Title" />
grep -in "lovable" .gitignore
ls .git/hooks/
Inspect Lovable-specific entries/hooks. Preserve secret/build ignores, license notices and useful safety hooks; remove only confirmed obsolete behavior.
Step 1 — Map what's actually imported
tmpdir="$(mktemp -d "${TMPDIR:-/tmp}/lovable-cleanup.XXXXXX")" || exit 1
grep -rh "from [\"']@radix-ui/" src/ --include="*.tsx" --include="*.ts" \
| grep -oP "from [\"']\K@radix-ui/[^\"']+" | sort -u > "$tmpdir/radix-used.txt"
grep -rh "from [\"']@/components/ui/" src/ --include="*.tsx" \
| grep -oP "from [\"']\K@/components/ui/[^\"']+" | sort -u > "$tmpdir/shadcn-used.txt"
Step 2 — Diff against installed
grep -oP '"@radix-ui/[^"]+' package.json | tr -d '"' | sort > "$tmpdir/radix-installed.txt"
diff "$tmpdir/radix-installed.txt" "$tmpdir/radix-used.txt"
Step 3 — Bulk remove & verify
npm uninstall @radix-ui/react-accordion @radix-ui/react-alert-dialog # etc.
npm run build
components.json — verify style, baseColor, and aliases match the real projecteslint.config.js — usually standard; quick scan onlygrep -in "lovable" components.json eslint.config.js
Lovable ships a default favicon.ico that browsers auto-request from site root
and that can remain visible after cleanup through browser or CDN caching. Handle
the four steps — replace the path, link all icon flavours, keep unversioned icon
URLs revalidatable, and verify after deploy — then purge the confirmed Vercel
project cache only if the live response stays stale. Full commands/JSON live in
references/favicon-vercel-cleanup.md.
rg -l -i "lovable|lovable-tagger|lovable\.dev" --glob "!node_modules/**" --glob "!.git/**" --glob "!dist/**" --glob "!build/**" .
User: I just exported my project from Lovable. Clean it up.
Agent:
1. Runs master scan — finds 23 matches across 8 files
2. Uninstalls lovable-tagger, renames package.json "name"
3. Strips vite.config.ts of componentTagger
4. Updates index.html title, removes generator comment
5. Flags 4 markdown docs for deletion, skims each first
6. Produces cleanup report
User: Just prune the unused Radix packages from my Lovable project.
Agent:
1. Runs grep diff (Area 13 only)
2. Identifies 18 unused @radix-ui packages
3. Confirms each candidate including indirect/dynamic imports, then removes only unused packages
4. Runs npm run build to verify — passes clean
npm run build passes after every batch of changeslive response and purge only the confirmed project if it remains stale
@radix-ui/react-slot — it's an indirect dep of most shadcn componentsLOVABLE_PROJECT_ID= — delete the whole linegenerates a transparent placeholder ICO only — the user must supply genuine artwork.
not caught by a direct grep. Always verify with npm run build.
components.json aliases automatically — it only scans andflags mismatches for the user to fix manually.
functions) — those require separate review.
Symptoms: Module not found error for a @radix-ui/* package
Solution: Re-add the missing package. Open src/components/ui/*.tsx and search for
the from '@radix-ui/...' import to find which component depends on it.
Symptoms: grep "lovable-tagger" package-lock.json returns results
Solution: Check direct/transitive dependency references, workspaces and package-manager consistency. Use its supported uninstall/lockfile update; preserve the lockfile and investigate remaining references before any clean reinstall.
Symptoms: Browser tab shows "Lovable" or "Vite App" despite edits
Solution: Check for a <Helmet> or <Head> component in src/App.tsx or a layout
wrapper — React-level title tags override index.html at runtime.
Symptoms: curl -sI https://<domain>/favicon.ico returns the old ETag withx-vercel-cache: HIT after the replacement deployment.
Solution: Overwrite public/favicon.ico with replacement content (a transparent
1×1 ICO if no real asset yet), verify the custom domain, then use the explicit
Vercel CDN purge only if the response remains stale — see Area 15.
@vite-config — Vite configuration best practices@shadcn-setup — shadcn/ui installation and customization@react-cleanup — general React project hygieneAfter completing the audit, produce a cleanup report:
## ✅ Cleaned
<list of changes made>
## ⚠️ Needs your input
<items needing a decision — brand assets, project name, domain>
## 🗑️ Deferred (safe to do later)
<e.g. unused dep pruning, OG image swap>
Made with agentic-awesome-skills · author: whoisabhishekadhikari
Fixed README line numbers and import greps are hints, not deletion rules. Include dynamic imports, CSS/assets, workspaces, tests and package metadata before pruning; a passing build alone does not establish runtime behavior or license clearance. Preserve third-party copyright/license and contributor attribution even when changing product branding. GNU grep -P examples require GNU grep and can miss imports; use an available parser/search tool and review candidates. Package-manager removal can execute lifecycle scripts or access the network: inspect scripts and use the project’s dependency policy. Do not expose secret values in scan results; filename-only matching avoids the incomplete redaction pattern. Back up replaced assets and review the diff before deployment or cache purge. The favicon helper overwrites the selected regular file atomically; its checks assume a trusted, non-concurrently-mutated directory and are not a race-proof hostile-filesystem sandbox. Link SVG/Apple icons only when those files actually exist; verify response bytes as well as headers.