Skip to content

aiskillstore/marketplace / skills/10k-digital/lovable

lovable

Unverified

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.

FileKindSize
SKILL.mdskill md11.0 KB
references/CLAUDE-template.mdmarkdown11.2 KB
references/codebase-map.mdmarkdown11.7 KB
references/prompts.mdmarkdown6.8 KB
references/secret-detection.mdmarkdown11.9 KB
skill-report.jsonconfig189.3 KB

references/CLAUDE-template.md

View on GitHub
# CLAUDE.md - Lovable Project Context

> This file is generated by `/init-lovable`. Edit to match your project.

## Project Overview

- **Name**: [PROJECT_NAME]
- **Production URL**: [PRODUCTION_URL]
- **Lovable Project URL**: [LOVABLE_PROJECT_URL]
- **GitHub**: [GITHUB_URL]
- **Backend**: [Lovable Cloud / Own Supabase]
- **Supabase Ref**: [SUPABASE_REF] (if own Supabase)
- **Architecture**: [Vite SPA (CSR) / TanStack Start (SSR)]

## Project Structure Map

> Quick navigation guide - run `/lovable:map --update` to refresh

<!-- FOR VITE SPA PROJECTS (vite.config.ts): use this layout -->
### Directory Layout
```
src/
├── components/    # [COMPONENT_PATTERN] ([COMPONENT_COUNT] components)
│   └── ui/        # shadcn/ui primitives
├── pages/         # Route pages ([PAGE_COUNT] pages)
├── hooks/         # Custom React hooks ([HOOK_COUNT] hooks)
├── lib/           # Utilities and helpers
├── integrations/  # External integrations
│   └── supabase/  # Supabase client and generated types
[ADDITIONAL_DIRS]

supabase/
├── functions/     # Supabase Edge Functions ([FUNCTION_COUNT]) — needs deploy
└── migrations/    # Database migrations ([MIGRATION_COUNT] migrations)
```

### Key Files
| File | Purpose |
|------|---------|
| `src/App.tsx` | Main app entry, routing |
| `src/lib/utils.ts` | Shared utilities |
| `src/integrations/supabase/client.ts` | Supabase client |
[ADDITIONAL_KEY_FILES]

### Patterns
- **Components**: [COMPONENT_PATTERN_DESC]
- **State**: [STATE_MANAGEMENT]
- **Data Flow**: Pages → Hooks → Supabase Client → Edge Functions

### Quick Lookup
| Looking for... | Check here |
|----------------|------------|
| UI components | `src/components/ui/` |
| Page routes | `src/pages/` or `src/App.tsx` |
| API calls | `src/hooks/` or `src/integrations/` |
| Types | `src/integrations/supabase/types.ts` |
| Supabase Edge functions | `supabase/functions/[name]/index.ts` |

<!-- FOR TANSTACK START PROJECTS (app.config.ts): replace above with this layout -->
<!--
### Directory Layout
```
app/
├── routes/        # File-based routes ([ROUTE_COUNT] routes)
│   ├── __root.tsx # Root layout
│   └── *.tsx      # Page routes (filename = URL path)
├── components/    # [COMPONENT_PATTERN] ([COMPONENT_COUNT] components)
│   └── ui/        # shadcn/ui primitives
├── lib/           # Utilities and helpers
├── integrations/  # External integrations
│   └── supabase/  # Supabase client and generated types
[ADDITIONAL_DIRS]

supabase/
├── functions/     # Supabase Edge Functions ([FUNCTION_COUNT]) — needs deploy
└── migrations/    # Database migrations ([MIGRATION_COUNT] migrations)
```

### Key Files
| File | Purpose |
|------|---------|
| `app/routes/__root.tsx` | Root layout (wraps all pages) |
| `app/routes/index.tsx` | Home page (/) |
| `app/lib/utils.ts` | Shared utilities |
| `app/integrations/supabase/client.ts` | Supabase client |
| `app.config.ts` | TanStack Start configuration |
[ADDITIONAL_KEY_FILES]

### Patterns
- **Architecture**: SSR — HTML rendered server-side before browser
- **Routing**: File-based (app/routes/*.tsx = URL routes)
- **Server functions**: *.server.ts files auto-deploy — no Lovable prompt needed
- **Components**: [COMPONENT_PATTERN_DESC]
- **State**: [STATE_MANAGEMENT]
- **Data Flow**: Routes (loaders) → Supabase Client → Edge Functions

### Quick Lookup
| Looking for... | Check here |
|----------------|------------|
| UI components | `app/components/ui/` |
| Page routes | `app/routes/` (file = route) |
| Root layout | `app/routes/__root.tsx` |
| Server functions | `app/**/*.server.ts` (auto-deploy) |
| API calls | `app/lib/` or `app/integrations/` |
| Types | `app/integrations/supabase/types.ts` |
| Supabase Edge functions | `supabase/functions/[name]/index.ts` |
```
-->

*Map generated: [MAP_TIMESTAMP]*

---

## 🚨 IMPORTANT: Always Commit and Push to GitHub

**This is critical:** Lovable syncs changes FROM GitHub. If you don't commit and push your changes, they won't sync back to Lovable!

### ✅ ALWAYS do this:
1. Make changes to your code
2. **Commit changes**: `git add . && git commit -m "description"`
3. **Push to main**: `git push origin main`
4. Wait 1-2 minutes for Lovable to sync
5. Verify changes in Lovable

**Without pushing to GitHub, your changes are stuck in Claude Code and won't reach Lovable or your team.**

### 🔄 GitHub → Lovable Sync Flow

```
Your changes in Claude Code
    ↓
git add . && git commit -m "Your message"
    ↓
git push origin main  ← REQUIRED!
    ↓
Lovable automatically syncs (1-2 minutes)
    ↓
Changes live in Lovable
```

---

## Workflow Rules

<!-- If Architecture: Vite SPA, use these rules -->
### ✅ Safe to edit and push to `main`:
- All files in `src/` (components, pages, hooks, utils)
- Config files (`vite.config.ts`, `tailwind.config.js`)
- Package.json dependencies
- Edge Function **code** in `supabase/functions/`
- Migration **files** in `supabase/migrations/`

### ⚠️ After editing, provide Lovable prompt:
- **Edge Functions**: `"Deploy the [name] edge function"`
- **Migrations**: `"Apply pending Supabase migrations"`

### ❌ Must go through Lovable:
- Create/modify database tables
- Set up RLS policies
- Add secrets (Cloud → Secrets UI)
- Create storage buckets
- Deploy Supabase Edge Functions

<!-- If Architecture: TanStack Start, replace the above with:

### ✅ Safe to edit and push to `main`:
- All files in `app/` (routes, components, lib, integrations)
- TanStack server functions (`app/**/*.server.ts`) — auto-deploy via GitHub, no prompt needed
- Config files (`app.config.ts`, `tailwind.config.js`)
- Package.json dependencies
- Supabase Edge Function **code** in `supabase/functions/`
- Migration **files** in `supabase/migrations/`

### ⚠️ After editing, provide Lovable prompt:
- **Supabase Edge Functions**: `"Deploy the [name] edge function"`
- **Migrations**: `"Apply pending Supabase migrations"`

> Note: TanStack server functions (`*.server.ts` in `app/`) are NOT Supabase Edge Functions.
> They deploy automatically with the rest of your app — no Lovable prompt needed.

### ❌ Must go through Lovable:
- Create/modify database tables
- Set up RLS policies
- Add secrets (Cloud → Secrets UI)
- Create storage buckets
- Deploy Supabase Edge Functions
-->

## Secrets

| Name | Purpose | Status | Used In |
|------|---------|--------|---------|
| OPENAI_API_KEY | AI features | ⚠️ Not configured | chat-completion |
| STRIPE_SECRET_KEY | Payments | ⚠️ Not configured | process-payment |
| RESEND_API_KEY | Emails | ✅ In Lovable Cloud | send-email, send-welcome |

**Legend:**
- ✅ In Lovable Cloud - Secret already configured
- ⚠️ Not configured - Needs setup in Cloud → Secrets

**To add secrets:**
1. Go to Cloud → Secrets in Lovable
2. Click "Add secret"
3. Enter name and value
4. Run: `"Redeploy edge functions to pick up new secrets"`

## Edge Functions

| Function | Purpose | Required Secrets | Status |
|----------|---------|------------------|--------|
| send-email | Send transactional emails | RESEND_API_KEY | ✅ Secret configured |
| process-payment | Handle Stripe webhooks | STRIPE_SECRET_KEY | ⚠️ Secret not configured |

**Warning:** Functions marked with ⚠️ will fail until secrets are added in Cloud → Secrets.

## Database Tables

| Table | Purpose |
|-------|---------|
| profiles | User profiles |
| projects | User projects |

## Project Conventions

- Use shadcn/ui components
- Follow existing naming patterns
- Don't modify auth logic without discussion

## Yolo Mode Configuration (Beta)

> ⚠️ Beta feature - auto-submits Lovable prompts via MCP or browser automation

- **Status**: [on / off]
- **Deployment Method**: [auto / mcp / browser]  # auto tries MCP first, then browser
- **Auto-Deploy**: [on / off]  # Auto-deploy to Lovable after git push (no manual command needed)
- **Deployment Testing**: [on / off]  # Run verification tests after Lovable deployments
- **Auto-run Tests**: [on / off]  # Run project tests after every git push
- **Debug Mode**: [on / off]  # Verbose logging of automation steps
- **Last Updated**: [timestamp]
- **Operations Covered**:
  - Automatic deployment detection after git push
  - Edge function deployment with verification
  - Migration application with verification
  - Automated code testing after every git push

**Configure:** Run `/lovable:yolo on/off [--mcp|--browser|--auto] [--testing|--no-testing] [--debug]`
**Connect MCP:** Run `/lovable:connect-mcp` for faster, more reliable automation

**Deployment methods:**
- **MCP** (recommended): Sends prompts via Lovable API - faster, no Chrome extension needed
  - Setup: `/lovable:connect-mcp`
- **Browser** (fallback): Navigates to Lovable UI - requires Chrome extension

**How it works:**
- **Deployment Method: auto** - Tries MCP first, falls back to browser if not connected
- **Deployment Method: mcp** - Uses Lovable MCP only (best performance)
- **Deployment Method: browser** - Uses browser automation (legacy)
- Auto-Deploy: Automatically deploys backend changes after git push - no need to run `/deploy-edge`
- Deployment testing verifies deployments (3 levels: basic, console errors, functional)
- Always has manual fallback if automation fails

**Auto-Deploy Flow:**
```
git push origin main → Claude detects backend changes → Automatic deployment starts (MCP or browser)
```

## Preview Testing Configuration

> 🧪 Beta - tests the app in Lovable Preview mode via browser automation.
> Test workspace: `.claude/lovable-claude/test/` (plans, profiles, results).

- **Status**: [on / off]
- **Preview URL**: [https://preview--app-name.lovable.app - WITHOUT token]
- **Access Method**: [token / browser-login]
- **Token Captured**: [date] (valid ~7 days - renew with `/lovable:test-init --refresh-token`)
- **Test After Implementation**: [on / off]  # run affected test plans after each feature
- **Test After Deploy**: [off / smoke / all]  # run after yolo auto-deploy
- **Last Test Sync**: [commit hash]

**Commands:**
- `/lovable:test-run [TP-NNN | --all | --changed | --smoke]` - run tests in Preview
- `/lovable:test-sync` - update test plans for new/changed features
- `/lovable:test-init` - re-run setup wizard / refresh token

**Maintenance rule:** when implementing a new feature, also add/update unit tests and
test plans covering it (or run `/lovable:test-sync`). Keep plans' `covers:` paths accurate.

> 🔐 The preview token is stored ONLY in `.claude/lovable-claude/test/preview-token.local`
> (gitignored). Never write it to this file or commit it.

## Quick Prompts Reference

| Task | Lovable Prompt |
|------|----------------|
| Deploy all functions | `"Deploy all edge functions"` |
| Deploy specific | `"Deploy the [name] edge function"` |
| Apply migrations | `"Apply pending Supabase migrations"` |
| Check logs | `"Show logs for [name] edge function"` |
| Fix function | `"The [name] edge function returns [error]. Fix it"` |
| Create table | `"Create a [name] table with columns: [list]"` |
| Add RLS | `"Enable RLS on [table] allowing [who] to [what]"` |
| Add secret | ⚠️ Manual: Cloud → Secrets |

## Branch Rules

- **Only `main` syncs** with Lovable
- Feature branches don't deploy until merged
- Lovable syncs within 1-2 minutes of push

---
*Template from lovable-integration plugin. Run `/init-lovable` to customize.*
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 323kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall