lovable
Integration skill for Lovable.dev projects. Activates when working with: - Lovable.dev projects with GitHub sync - Supabase Edge Functions that need deployment - Database migrations for Lovable Cloud - Projects with supabase/ directory structure - Any mention of "Lovable", "deploy edge function", "a…
Install / Use
npx skills add aiskillstore/marketplace --skill lovableInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
OperationsSupported Platforms
Our assessment of lovable
lovable scores 90/100 on our quality scale, 339th of 760 Operations skills we index (top 45%).
Its SKILL.md is 10 KB long, well organised into 33 sections with 11 code examples: a thorough specification that gives an agent plenty to work with.
It has 428 GitHub stars, a meaningful sign that others use it.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so lovable is actively maintained.
- Our last check on 2026-10-30 found the source still online.
- No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
- Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
ReviewOur scan of the whole file found 3 patterns worth reviewing before you install lovable. An AI review of the same text found nothing harmful.
- mediumDisables the agent's permission promptsline 264
## Yolo Mode - Automated Deployments (Beta) - mediumDisables the agent's permission promptsline 277
### When Yolo Mode Activates - mediumDisables the agent's permission promptsline 283
### Configure Yolo Mode
AI review by kimi-k2.7-code on 2026-10-07. Automated pattern scan on 2026-10-07. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
lovable compared with similar skills
All 4 of these similar skills score higher than lovable; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| lovable (this skill)by aiskillstore | 90 | 428 | 55d ago | SKILL.md |
| Agent-Reachby Panniantong | 100 | 113.0k | 10d ago | CLAUDE.md |
| algorithmic-artby anthropics | 100 | 177.9k | 57d ago | SKILL.md |
| pptxby anthropics | 100 | 177.9k | 57d ago | SKILL.md |
| prospectingby coreyhaines31 | 100 | 60.1k | 7d ago | SKILL.md |
Frequently asked questions
- How do I install lovable?
- Run
npx skills add aiskillstore/marketplace --skill lovable. The install tabs above show the steps for each supported agent. - Which AI agents does lovable work with?
- It is written for Claude Code, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is lovable safe to use?
- Our scan of the whole file found 3 patterns worth reviewing before you install lovable. An AI review of the same text found nothing harmful. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is lovable still maintained?
- The repository was last updated about 2 months ago, so lovable is actively maintained.
Skill content
View source on GitHubname: lovable description: | Integration skill for Lovable.dev projects. Activates when working with:
- Lovable.dev projects with GitHub sync
- Supabase Edge Functions that need deployment
- Database migrations for Lovable Cloud
- Projects with supabase/ directory structure
- Any mention of "Lovable", "deploy edge function", "apply migration"
Provides exact Lovable prompts for backend operations that can't be done via GitHub alone.
Lovable Integration Skill
This skill enables Claude Code to work effectively with Lovable.dev projects while respecting Lovable's deployment requirements.
When to Use This Skill
Activate when:
- User mentions "Lovable" or "lovable.dev"
- Project has
supabase/directory with Edge Functions - User asks to deploy edge functions
- User creates database migrations
- User asks about Lovable Cloud or backend deployment
- Project appears to be a Lovable project (React + Supabase structure)
Project Architecture Types
Lovable supports two architectures. Always detect which one you're working with before giving advice.
Detecting Architecture
Check the root directory of the user's project:
app.config.tspresent → TanStack Start (new, SSR — post-April 2026)vite.config.tspresent → Vite SPA (legacy, CSR — pre-April 2026)
Both are fully supported. Old projects remain on Vite and receive no forced migration.
Vite SPA Architecture (Legacy)
Projects created before April 2026. Client-side rendering only.
What Syncs Automatically (Vite SPA)
✅ Edit freely and push to main:
src/- All React components, pages, hooks, utilspublic/- Static assets- Config files -
vite.config.ts,tailwind.config.js,tsconfig.json package.json- Dependenciessupabase/functions/*/index.ts- Edge Function code (not deployment)supabase/migrations/*.sql- Migration files (not application)
What Requires Lovable Deployment (Vite SPA)
⚠️ After editing, provide Lovable prompt:
| Change Type | Lovable Prompt |
|-------------|----------------|
| Edge Function code | "Deploy the [name] edge function" |
| All Edge Functions | "Deploy all edge functions" |
| New migration file | "Apply pending Supabase migrations" |
| New table needed | "Create a [name] table with columns: [list]" |
| RLS policy | "Enable RLS on [table] allowing [who] to [what]" |
| Storage bucket | "Create a [public/private] bucket called [name]" |
| Secret/env var | Manual: Cloud → Secrets → Add |
TanStack Start Architecture (New Projects)
Projects created after April 2026. Full server-side rendering (SSR) via TanStack Start.
Key Differences from Vite SPA
- Routes are file-based in
app/routes/(not React Router insrc/App.tsx) - Config file is
app.config.ts(notvite.config.ts) - Server functions (
createServerFn) let server-side logic live directly in component files — no edge function needed for simple server logic - Files named
*.server.tsare server-only and never sent to the browser - Pages are rendered as complete HTML on the server before reaching the browser
What Syncs Automatically (TanStack Start)
✅ Edit freely and push to main:
app/- All routes, components, server functions, layoutsapp/routes/- File-based route pagespublic/- Static assetsapp.config.ts,tailwind.config.js,tsconfig.json- Config filespackage.json- Dependenciesapp/**/*.server.ts- TanStack server functions (auto-deploys, no Lovable prompt needed)supabase/functions/*/index.ts- Supabase Edge Function code (not deployment)supabase/migrations/*.sql- Migration files (not application)
What Requires Lovable Deployment (TanStack Start)
⚠️ After editing, provide Lovable prompt:
| Change Type | Lovable Prompt |
|-------------|----------------|
| Supabase Edge Function code | "Deploy the [name] edge function" |
| All Supabase Edge Functions | "Deploy all edge functions" |
| New migration file | "Apply pending Supabase migrations" |
| New table needed | "Create a [name] table with columns: [list]" |
| RLS policy | "Enable RLS on [table] allowing [who] to [what]" |
| Storage bucket | "Create a [public/private] bucket called [name]" |
| Secret/env var | Manual: Cloud → Secrets → Add |
Note: TanStack server functions (
createServerFn) are not Supabase Edge Functions. They live inapp/and deploy automatically via GitHub sync — no Lovable prompt needed. Onlysupabase/functions/requires manual deployment.
TanStack Start File Structure
project/
├── app/ # ✅ Safe - auto-syncs
│ ├── routes/ # File-based routing
│ │ ├── __root.tsx # Root layout
│ │ ├── index.tsx # Home page (/)
│ │ └── [route].tsx # Other pages
│ ├── components/ # Shared UI components
│ ├── lib/ # Utilities and helpers
│ └── *.server.ts # ✅ Server functions (auto-deploy)
├── app.config.ts # TanStack Start config
├── public/ # Static assets
├── supabase/
│ ├── functions/ # ✅ Edit code, ⚠️ needs deploy
│ └── migrations/ # ✅ Create files, ⚠️ needs apply
└── CLAUDE.md # Project context
Core Concept (Both Architectures)
Lovable uses two-way GitHub sync on the main branch only:
- Frontend and server-side code (including TanStack server functions) sync automatically
- Supabase Edge Functions and database migrations require Lovable prompts after code changes
Response Format
When backend deployment is needed, always output:
📋 **LOVABLE PROMPT:**
> "[exact prompt to copy-paste]"
For destructive operations, add:
⚠️ **Warning**: [explanation of risk]
File Structure Reference
Vite SPA (Legacy — vite.config.ts present)
project/
├── src/ # ✅ Safe - auto-syncs
│ ├── components/
│ ├── pages/
│ ├── hooks/
│ ├── lib/
│ └── integrations/supabase/
│ ├── client.ts # ⚠️ Has Supabase URLs
│ └── types.ts
├── supabase/
│ ├── functions/ # ✅ Edit code, ⚠️ needs deploy
│ │ └── [function-name]/
│ │ └── index.ts
│ ├── migrations/ # ✅ Create files, ⚠️ needs apply
│ │ └── YYYYMMDDHHMMSS_*.sql
│ └── config.toml # ⚠️ Lovable Cloud manages
├── .env # Local only - Lovable ignores
└── CLAUDE.md # Project context
TanStack Start (New — app.config.ts present)
project/
├── app/ # ✅ Safe - auto-syncs
│ ├── routes/ # File-based routing
│ │ ├── __root.tsx # Root layout
│ │ ├── index.tsx # Home route (/)
│ │ └── [name].tsx # Named routes
│ ├── components/ # Shared components
│ ├── lib/ # Utilities
│ ├── integrations/supabase/ # Supabase client + types
│ └── *.server.ts # ✅ Server functions (auto-deploy, no prompt needed)
├── app.config.ts # TanStack Start config
├── public/ # Static assets
├── supabase/
│ ├── functions/ # ✅ Edit code, ⚠️ needs deploy via Lovable
│ │ └── [function-name]/
│ │ └── index.ts
│ ├── migrations/ # ✅ Create files, ⚠️ needs apply via Lovable
│ │ └── YYYYMMDDHHMMSS_*.sql
│ └── config.toml # ⚠️ Lovable Cloud manages
├── .env # Local only - Lovable ignores
└── CLAUDE.md # Project context
Backend Types
Lovable Cloud
- Backend managed entirely by Lovable
- No Supabase dashboard access
- All operations via Lovable prompts
- Secrets in Cloud → Secrets UI
Own Supabase
- Direct Supabase dashboard access
- Can use Supabase CLI:
supabase functions deploy - More flexibility but manual setup
Quick Prompts Reference
Edge Functions
"Deploy all edge functions"
"Deploy the send-email edge function"
"Create an edge function called [name] that [description]"
"Show logs for [name] edge function"
"The [name] edge function returns [error]. Fix it"
Database
"Create a [name] table with columns: id (uuid), name (text), created_at (timestamp)"
"Add a [column] column of type [type] to [table]"
"Add foreign key from [table1].[col] to [table2].id"
"Apply pending Supabase migrations"
RLS Policies
"Enable RLS on [table]"
"Add RLS policy on [table] allowing authenticated users to read all rows"
"Add RLS policy on [table] allowing users to only access their own rows"
Storage
"Create a public storage bucket called [name]"
"Create a private storage bucket called [name]"
"Allow authenticated users to upload to [bucket]"
Auth
"Enable Google authentication"
"Enable GitHub authentication"
"When user signs up, create row in profiles table"
Branch Rules
- Only
mainsyncs with Lovable - Feature branches don't deploy until merged
- Lovable syncs within 1-2 minutes of push
Yolo Mode - Automated Deployments (Beta)
When yolo_mode: on in CLAUDE.md, deployments are automated via browser automation:
How It Works
Instead of showing manual prompts, the yolo skill (/skills/yolo/SKILL.md) takes over:
- Automatically navigates to Lovable.dev
- Submits deployment prompts
- Monitors for success/failure
- Runs verification tests (if enabled)
- Reports deployment summary
When Yolo Mode Activates
- During
/lovable:deploy-edgecommand - During
/lovable:apply-migrationcommand - When
yolo_mode: onin CLAUDE.md
Configure Yolo Mode
/lovable:yolo on # Enable with testing
/lovable:yolo on --no-testing # Enable without testing
/lovable:yolo on --debug # Enable with verbose logs
/lovable:yolo off # Disable
Beta Status
⚠️ Yolo mode is in beta:
- Requires Claude in Chrome extension
- May have bugs or UI compatibility issues
- Always has manual fallback
- See
/skills/yolo/SKILL.mdfor details
Debugging Checklist
-
Frontend not updating?
- On
mainbranch? - Changes pushed?
- Wait 1-2 min
- On
-
Edge Function not working?
- Deployed via Lovable (or yolo mode)?
- Secrets set in Cloud UI?
- Check logs in Lovable
-
Database query failing?
- Migration applied (via Lovable or yolo mode)?
- RLS policies correct?
- Table exists?
-
Yolo mode not working?
- Check
yolo_mode: onin CLAUDE.md - Chrome extension installed?
- Logged into Lovable?
- See yolo skill for troubleshooting
- Check
Related Skills
Agent-Reach
113.0kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
pptx
177.9kUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an em…
prospecting
60.1kWhen the user wants to find and qualify prospects for outbound, or asks who to target first, which signal to prioritize, or where to spot buyers with the problem: buying signals, enrichment, verification, account research.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
