Agent skills that get your app paid — Creem, Paddle, license keys, launch.

Adds Creem payments to a Next.js (App Router) app end to end. Covers products, one-time and subscription checkout, webhook signature verification, three-layer idempotency (event id, resend key, grant key), a tested entitlement state machine with stale and out-of-order guards, customer portal and in-product cancellation, refunds and chargebacks revoking access, Vitest and Playwright test-card tests, and go-live. Ships 3 slash commands (/add-creem-paywall, /debug-creem-webhook, /payment-audit). Use when the user wants to sell with Creem (creem.io), add a paywall, subscriptions or a lifetime deal, wire Creem webhooks, fix "webhook signature invalid", or handle refunds and access revocation.

A complete, working Next.js 16 SaaS starter that takes payments through Creem (merchant of record) - Better Auth email-code login, Drizzle + SQLite, Creem checkout for monthly / yearly / lifetime plans, a signed and deduplicated webhook that grants and revokes access, Manage billing and in-product cancel, a gated page and API route, a Dockerfile, the three Creem slash commands, and an end-to-end test that runs the whole purchase against a mock Creem. Use when the user wants to start a new paid web app, a SaaS boilerplate with payments, or a Creem example project that already works, rather than adding payments to an existing app (use creem-checkout for that).

Server-side feature gating and paid-content delivery that works with any payment provider (Creem, Paddle, Stripe, Polar, Lemon Squeezy, manual grants). Covers a scope model (all / plan / pack / single item), expired vs revoked vs never-bought decisions, numeric plan limits, update windows for one-time purchases, blocking double purchases, short-lived signed download links that re-check access, and a Gate server component. Pure core with tests. Use when the user needs to lock features or files behind a plan, add a Pro tier, sell packs or bundles, add plan limits, or protect paid downloads in a Next.js app.

Adds license keys to a paid desktop app, CLI, plugin or self-hosted product. Covers key generation, hashed storage, device activation with an activation limit, same-device reinstall, deactivation to move devices, revocation on refund or chargeback, expiry, and signed offline leases. Ships a runnable zero-dependency server and client with tests, and explains when to use Creem's built-in license keys (proxied through your backend) instead. Use when the user asks for license keys, activation codes, serial numbers, "limit to N devices", offline licensing, or revoking a refunded customer's key.

Plans and runs a move from Stripe, Polar or Lemon Squeezy to Creem (or to Paddle) without cutting off paying customers. Covers the product map, importing existing buyers as legacy grants so access continues, stopping renewals on the old provider at period end, dual-running both webhooks, invitations to re-subscribe, and a cut-over checklist. Ships plan_migration.mjs (plan, Markdown, SQL) with tests. Use when the user wants to switch payment providers, leave Stripe, Polar or Lemon Squeezy for a merchant of record, or asks how to move subscribers to Creem.

Pre-launch audit for a website or SaaS - checks SEO tags (title, description, canonical, lang, Open Graph), robots.txt, sitemap.xml, favicon and apple-touch-icon, real 404 status, HTTPS redirect, legal pages (privacy, terms, refund), image alt text, page weight and response time, plus a payment self-check (webhook signature, raw body, idempotency, refunds, secrets, success-page grants), then lists the problems and fixes them in the codebase. Ships a no-dependency crawler script (audit_site.py) that produces a pass/warn/fail report. Use when the user says they are about to launch, ship, go live, submit to Product Hunt or AI directories, or asks "is my site ready", "SEO check", "why is my site not indexed", or wants a launch checklist, or asks whether their payment or webhook setup is safe.

Drafts a Privacy Policy, Terms of Service and Refund Policy for a SaaS, digital product or website from a short questionnaire, adapted to the payment provider (Creem, Paddle, Lemon Squeezy as Merchant of Record, or Stripe/direct) and to where users are (EU/UK GDPR, California CCPA/CPRA, China PIPL notes), then renders them as Markdown, HTML or Next.js pages and links them in the footer. Output is a starting template, NOT legal advice - the user must review it and have it checked by a qualified lawyer. Use when the user needs privacy policy, terms, refund policy, legal pages, or a payment provider (Paddle/Creem/Lemon Squeezy/Stripe) review asks for them.

Generates Open Graph / Twitter (X) share images for every page of a website and wires up the og:* and twitter:* meta tags, then verifies the social preview. Supports Next.js App Router (opengraph-image.tsx with next/og ImageResponse), Astro (build-time PNGs via satori + resvg) and any static site (Pillow script). Use when the user asks for OG images, social share cards, link previews, "my link looks bad on X/Slack/LinkedIn/WeChat", twitter:card, or before launching a site.

Creates or upgrades a repository's AGENTS.md (read by Codex, Cursor, and other agents) and a CLAUDE.md that imports it, so Claude Code, Codex, Cursor and Gemini CLI share one set of project rules. Scans the repo to detect languages, package manager, real build/test/lint commands, framework, directory layout and existing rule files (.cursorrules, .cursor/rules, CLAUDE.md, copilot-instructions), then writes a concise, verified rules file. Use when the user asks to set up AGENTS.md or CLAUDE.md, "project rules", "make Claude Code and Codex follow the same conventions", onboard an agent to a repo, or migrate .cursorrules.