Run any Skill in Manus with one click

lovable-checkout

Stars0

Forks0

UpdatedMay 28, 2026 at 10:22

Paste-in SolvaPay hosted checkout for Lovable-generated apps (Vite + React + TypeScript + shadcn/ui + Supabase). Backend is Supabase Edge Functions — no Node server to add. Use when the user says "lovable", "vite checkout", "shadcn checkout", "supabase edge checkout", "solvapay in lovable", "paste this into lovable", or "@preview". Pinned to the floating `@preview` tag and the SolvaPay dev backend (`https://api-dev.solvapay.com`). Not for production. Use `website-checkout` for Next.js / production web apps, or `sdk-integration` for general SDK wiring.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

solvapay

solvapay/cursor-plugin

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

4 files

SKILL.md

readonly

name

lovable-checkout

description

Lovable Checkout (preview)

Self-contained guide for wiring SolvaPay hosted checkout into a Lovable app. The whole guide is designed to be pasted into the Lovable chat to bias its agent toward a working integration on turn zero.

Quick Start

Read guide.md end-to-end before generating code. The guide owns environment setup, Supabase edge function templates, the @preview install commands, and the Lovable-specific guardrails.
Cross-reference reference.md for the package + hook map.

Guardrails

Never put SOLVAPAY_SECRET_KEY in .env, VITE_*, import.meta.env, or any file the browser can reach. The secret lives only as a Supabase edge function secret.
Never hand-roll fetch against https://api-dev.solvapay.com from the browser. All SolvaPay backend calls go through Supabase edge functions.
Always install with the @preview tag: @solvapay/react@preview, @solvapay/react-supabase@preview. Never pin an exact preview version.
Always set SOLVAPAY_API_BASE_URL=https://api-dev.solvapay.com as a Supabase edge function secret — production keys are rejected by api-dev.
Not for production. The @preview tag is unstable by design.

More from this repository

same repository

create-mcp-app

solvapay/cursor-plugin

Create or scaffold a SolvaPay-monetized MCP server on Cloudflare Workers — from OpenAPI / Swagger or from scratch. Use when the user says "create mcp app", "scaffold mcp", "new mcp server", "openapi to mcp", "wrap rest api as mcp", "npm create solvapay", or wants a greenfield paid MCP worker. For humans at a terminal, point to `npm create solvapay@latest my-mcp -- --type mcp`. For agents, use describe.mjs + scaffold.mjs (intent-driven clustering requires an LLM).

2026-05-280

sdk-integration

solvapay/cursor-plugin

Integrate the SolvaPay TypeScript SDK into an existing app -- Next.js, React, Express, Supabase Edge Functions, Deno, or an MCP server that already exists. Use when the user says "integrate sdk", "protect api", "paywall my api", "usage events", "webhooks", "add solvapay to existing mcp", "supabase edge functions", "npx solvapay init", or wants account-management UI (CurrentPlanCard, LaunchCustomerPortalButton, usePaymentMethod). Covers paywall enforcement, usage tracking, hosted checkout, customer portal, plan activation / cancellation / reactivation, and webhook signature verification. Use the `create-mcp-app` skill instead when scaffolding a brand-new paid MCP server.

2026-05-280

solvapay

solvapay/cursor-plugin

Router and disambiguation entry point for the SolvaPay skill family. Use only when the user's intent is vague ("add solvapay to my project", "where do I start with solvapay", "what can solvapay do") and no specific surface skill has triggered. Owns the shared documentation-discovery preference and the cross-skill guardrails; routes the agent to exactly one of `create-mcp-app`, `sdk-integration`, `website-checkout`, or `lovable-checkout`. For specific intents (paywall, checkout, paid MCP, Lovable, SDK, webhooks, usage metering), the surface skills should auto-trigger -- use them directly.

2026-05-280

website-checkout

solvapay/cursor-plugin

Add SolvaPay hosted checkout and customer portal to a web app with minimal PCI surface. Use when the user says "add checkout to website", "hosted checkout", "customer portal", "nextjs checkout", "checkout session", or wants a server-side checkout-session route plus a return-URL handler. Next.js is fully supported; React (no Next.js) gets partial guidance. Use the `sdk-integration` skill instead for usage metering, Express, MCP server wiring, or webhook-heavy flows; use `lovable-checkout` for Lovable / Vite / Supabase Edge apps.

2026-05-280

name

lovable-checkout

description

Lovable Checkout (preview)

Quick Start

Read guide.md end-to-end before generating code. The guide owns environment setup, Supabase edge function templates, the @preview install commands, and the Lovable-specific guardrails.
Cross-reference reference.md for the package + hook map.

Guardrails

Never put SOLVAPAY_SECRET_KEY in .env, VITE_*, import.meta.env, or any file the browser can reach. The secret lives only as a Supabase edge function secret.
Never hand-roll fetch against https://api-dev.solvapay.com from the browser. All SolvaPay backend calls go through Supabase edge functions.
Always install with the @preview tag: @solvapay/react@preview, @solvapay/react-supabase@preview. Never pin an exact preview version.
Always set SOLVAPAY_API_BASE_URL=https://api-dev.solvapay.com as a Supabase edge function secret — production keys are rejected by api-dev.
Not for production. The @preview tag is unstable by design.