Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

sdk-integration

Sterne0

Forks0

Aktualisiert28. Mai 2026 um 10:22

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.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

solvapay

solvapay/cursor-plugin

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

SoftwareentwicklerInformatik- und Mathematikberufe·SOC 15-1252

Datei-Explorer

10 Dateien

SKILL.md

readonly

name

sdk-integration

description

SDK Integration

Add SolvaPay to an existing TypeScript / JavaScript app via the @solvapay/* packages.

Quick Start

Read guide.md — the entry point with stack detection, clarifying questions, and the implementation order (init → auth mapping → paywall → webhooks → sandbox).
Run npx -y solvapay@latest init to authenticate and install base packages (@solvapay/server, @solvapay/core, @solvapay/auth).
Follow the matching stack guide:
- nextjs/guide.md
- react/guide.md
- express/guide.md
- mcp-server/guide.md — fetch-first MCP server already in place (Cloudflare Workers, Supabase Edge, Deno)
- supabase-edge/guide.md
Use reference.md for package map and API operations; webhooks.md for signature verification.

Guardrails

Never expose SOLVAPAY_SECRET_KEY to client code or public env vars.
Never build custom card collection if hosted checkout satisfies requirements.
Always prefer official SolvaPay SDK helpers over ad-hoc raw HTTP calls.
Always keep paywall checks server-side or tool-handler-side (never browser-only).
Always include a failure-path test in sandbox before calling implementation complete.

When NOT to use this skill

Scaffolding a brand-new paid MCP server from OpenAPI or from scratch — use create-mcp-app instead.
Pasting hosted checkout into a Lovable app — use lovable-checkout instead.
Adding hosted checkout to a brand-new Next.js / React web app with no other SDK needs — website-checkout covers the minimal slice.

Mehr aus diesem Repository

gleiches 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

lovable-checkout

solvapay/cursor-plugin

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.

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

sdk-integration

description

SDK Integration

Add SolvaPay to an existing TypeScript / JavaScript app via the @solvapay/* packages.

Quick Start

Read guide.md — the entry point with stack detection, clarifying questions, and the implementation order (init → auth mapping → paywall → webhooks → sandbox).
Run npx -y solvapay@latest init to authenticate and install base packages (@solvapay/server, @solvapay/core, @solvapay/auth).
Follow the matching stack guide:
- nextjs/guide.md
- react/guide.md
- express/guide.md
- mcp-server/guide.md — fetch-first MCP server already in place (Cloudflare Workers, Supabase Edge, Deno)
- supabase-edge/guide.md
Use reference.md for package map and API operations; webhooks.md for signature verification.

Guardrails

Never expose SOLVAPAY_SECRET_KEY to client code or public env vars.
Never build custom card collection if hosted checkout satisfies requirements.
Always prefer official SolvaPay SDK helpers over ad-hoc raw HTTP calls.
Always keep paywall checks server-side or tool-handler-side (never browser-only).
Always include a failure-path test in sandbox before calling implementation complete.

When NOT to use this skill

Scaffolding a brand-new paid MCP server from OpenAPI or from scratch — use create-mcp-app instead.
Pasting hosted checkout into a Lovable app — use lovable-checkout instead.
Adding hosted checkout to a brand-new Next.js / React web app with no other SDK needs — website-checkout covers the minimal slice.