Strip Lovable scaffolding and ship a clean codebase

Audits and strips Lovable.dev scaffolding from an exported Vite, React, and shadcn/ui project across 15 defined areas: the lovable-tagger dev dependency and its componentTagger() call in vite.config.ts; branding artifacts such as the favicon, og-image, logo, a generic title, and the Lovable project URL in README.md; generated docs (CLEANUP_SUMMARY.md, DEPLOYMENT_GUIDE.md, DEVELOPMENT_SUMMARY.md, LOGO_UPDATE.md); leftover references in source files, the lockfile, environment files, git config, SEO/deploy config, and components.json; and unused dependencies - Lovable pre-installs the full roughly 29-component shadcn/ui set and about 30 Radix UI primitives, of which most projects use only 5-10, though @radix-ui/react-slot must be kept since shadcn components depend on it indirectly via the asChild prop. It defines a specific execution order - dependencies first to avoid lockfile conflicts, docs last so the README reflects the already-cleaned project, favicon and CDN cache verification as soon as possible after asset swaps - and a dedicated final area for Vercel favicon caching: browsers auto-request /favicon.ico from the site root regardless of what index.html links, so the fix is to overwrite the file in place rather than delete it, link all icon flavors explicitly, keep unversioned icon URLs on a must-revalidate cache policy rather than immutable, and verify the live response before ever purging a CDN cache.

npm uninstall lovable-tagger
grep "lovable-tagger" package-lock.json

Use it right after exporting a project from Lovable and before shipping or open-sourcing it - triggered by lovable-tagger in package.json, a generic Lovable favicon or title, or the presence of Lovable-generated markdown files. Every shell command is read-only (grep/ls) except explicitly scoped mutations - npm uninstall lovable-tagger, bulk-removing confirmed-unused Radix packages, and writing a placeholder favicon - and a live CDN purge is gated behind explicit user approval and verification against the confirmed production domain, never a preview URL or one inferred from the current directory alone. Four named limitations bound its scope: it cannot source real brand assets and only generates a transparent placeholder favicon; dependency pruning isn't foolproof since some Radix packages are indirect and must be confirmed with a full npm run build; it flags components.json mismatches but doesn't fix them automatically; and it doesn't touch Lovable-specific backend integrations like Supabase row-level security or edge functions.

Input is the exported Lovable project's source tree; output is a cleaned codebase plus a three-part cleanup report - "Cleaned" for changes made, "Needs your input" for decisions like brand assets, project name, or domain, and "Deferred" for safe-to-defer items like unused-dep pruning or the OG image swap. Four documented troubleshooting cases pair a specific symptom with its fix: a build failing after Radix removal (re-add the missing package, found by grepping the failing component's import), lovable-tagger persisting in the lockfile after uninstall (delete node_modules/package-lock.json and reinstall), a generic title still showing despite index.html edits (check for a runtime Helmet/Head override), and a stale favicon still serving on Vercel after replacement (verify the live ETag/Cache-Control response before purging).

Targets the Vite, React, shadcn/ui, and Radix UI stack specifically, with a dedicated reference file for Vercel's cache-header behavior (Cache-Control: public, max-age=0, must-revalidate for unversioned icon paths, immutable reserved for content-hashed assets) and its CLI (vercel cache purge --type cdn). It cross-references three sibling skills - @vite-config, @shadcn-setup, and @react-cleanup - for adjacent configuration and hygiene work it doesn't cover itself.

Developers who exported a project from Lovable.dev and want to ship or open-source it without the platform's tagger dependency, placeholder branding, generated docs, and unused component bloat still baked in, following a safe, ordered cleanup rather than an ad hoc search-and-delete.