silvioventre

silvioventre/lovable-skills

Skill Claude CodeCodex

Use when . Describe the boundaries too, meaning what this skill does NOT cover.

silvioventre/lovable-skills

Skill Claude CodeCodex

Perform a two-phase codebase rationalization on a Lovable project — a comprehensive read-only audit to find dead code, unused code, obsolete dependencies, duplicated implementations, and maintainability risks, followed by a strictly-scoped, approval-gated cleanup of only the batches the user explicitly approves. Use…

silvioventre/lovable-skills

Skill Claude CodeCodex

Use when the user wants to run part or all of their app outside Lovable Cloud, or is weighing whether to — "can I self-host this", "deploy to Netlify or Vercel or Cloudflare", "host it on AWS", "generate a Dockerfile", "move my backend to Supabase", "export my data", "am I locked in", "what happens if I stop using…

silvioventre/lovable-skills

Skill Claude CodeCodex

Use when the user is about to publish, deploy, ship, launch, or go live with a project, or has already published and something about the live site is wrong — "publish this", "make it live", "deploy it", "am I ready to launch", "my changes aren't showing on the live site", "who can see this", "make it private", "share…

silvioventre/lovable-skills

Skill Claude CodeCodex

Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers landing pages, marketing sites, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty…

silvioventre/lovable-skills

Skill Claude CodeCodex

Use when the user wants an app, site, page, or component to work correctly on every screen size — "make it responsive", "fix it on mobile", "it breaks on my phone", "it doesn't look right on tablet", "there's horizontal scrolling", "the layout overflows", "make it work on small screens", "test it at different…

silvioventre/lovable-skills

Skill Claude CodeCodex

Use when the user asks about the security of their app, wants a security review or audit, is about to publish or go live, or is building anything that handles credentials, payments, personal data, roles, or permissions — "is this secure", "review my security", "check for vulnerabilities", "am I safe to publish"…

silvioventre/lovable-skills

Skill Claude CodeCodex

Use when something in the project is broken, failing, or behaving unexpectedly — a build error, a red error message, a blank or white preview, a feature that stopped working, a component that disappeared, data that will not load, an edge function or permission failure, an error that keeps coming back after repeated…