Agent skill · Frontend

lovable-cleanup

Audits and strips Lovable scaffolding from Vite + React projects — removes lovable-tagger, swaps placeholder assets, prunes unused Radix deps, and cleans generated docs so the codebase ships as yours.

Nick44,086★ · +407/wk · 1 repos on radarProfile →
claude-codecodexcursorMIT
Install
npx skills add sickn33/agentic-awesome-skills --skill lovable-cleanup --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 13 KB
Bundled scripts: none
Declared author: whoisabhishekadhikari
Path: skills/lovable-cleanup/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 44,414 · +328 this week
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# lovable-cleanup > Remove every trace of Lovable scaffolding and ship the project as your own. > Made with [agentic-awesome-skills](https://github.com/sickn33/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 14 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 `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 --- ## Core Concepts ### What Lovable injects Lovable adds three categories of scaffolding that must be removed: 1. **Dependency** — `lovable-ta

What's inside
Steps it walks through
  1. Overview
  2. When to Use This Skill
  3. Core Concepts
  4. What Lovable injects
  5. Why the execution order matters
  6. Unused dep footprint
  7. Recommended Execution Order
  8. Step-by-Step Guide
  9. Area 1 · README.md
  10. Area 2 · package.json
  11. Area 3 · vite.config.ts
  12. Area 4 · index.html
  13. Area 5 · public/ assets
  14. Area 6 · Source files
Commands it runs
grep -n "lovable" package.json
grep -n "lovable\|componentTagger\|filter(Boolean)" vite.config.ts
grep -in "lovable\|generator" index.html
grep -rn "lovable\|Lovable" src/ --include="*.tsx" --include="*.ts"
npm uninstall lovable-tagger
grep "lovable-tagger" package-lock.json
grep -n '"lovable' package.json
grep -rin "lovable" .env .env.local .env.example 2>/dev/null \
grep -rln "lovable\|Lovable" *.md 2>/dev/null
grep -in "lovable" \
More from agentic-awesome-skills
All skills →
About this skill
What does the lovable-cleanup skill do?

Audits and strips Lovable scaffolding from Vite + React projects — removes lovable-tagger, swaps placeholder assets, prunes unused Radix deps, and cleans generated docs so the codebase ships as yours.

How do I install it?

Run `npx skills add sickn33/agentic-awesome-skills --skill lovable-cleanup --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From sickn33/agentic-awesome-skills, a repository with 44,414 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going