sell

Convert a Vibes app into a multi-tenant SaaS with Clerk authentication.

134|5|Updated Dec 24, 2025
One-click install
npx skills add https://github.com/popmechanic/vibes-cli --skill sell
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sell
Source: https://github.com/popmechanic/vibes-cli/tree/main/skills/sell
Command: npx skills add https://github.com/popmechanic/vibes-cli --skill sell

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill transforms a standalone Vibes app into a self-contained multi-tenant SaaS, wiring in subdomain-based routing, Clerk authentication, and subscription gating to deliver a ready-to-use SaaS experience.

Core Features & Use Cases

  • Unified app generation: produces a single index.html that handles landing, tenant routing, and admin dashboard.
  • Tenant isolation: each subdomain gets its own Fireproof namespace and tenant context for data separation.
  • Clerk integration & billing: supports passkeys, sign-in, and Clerk Billing to gate access per subscription.
  • Use Case: convert a wedding-photo app into a rent-ready SaaS with a landing page and per-tenant spaces.

Quick Start

Invoke the sell flow with /vibes:sell, provide Clerk and domain details, then run the assembly and deploy steps. The skill generates and deploys a unified app automatically.

Frequently Asked Questions about sell

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert a Vibes app into a multi-tenant SaaS?

To convert a Vibes app into a multi-tenant SaaS, this skill automates generating a unified index.html that handles subdomain-based tenant routing, Clerk authentication, and subscription gating. You provide Clerk credentials and a Cloudflare Workers domain to deploy the ready-to-use SaaS application.

What is subdomain-based tenant routing and how does it isolate data?

Subdomain-based tenant routing isolates data by assigning each subdomain its own Fireproof namespace and tenant context. This ensures strict data separation for different tenants within a single deployed application, keeping each tenant's information self-contained and secure.

Does this SaaS assembly skill require Clerk credentials and a Cloudflare Workers domain?

Yes, this SaaS assembly skill requires Clerk credentials and a configured Cloudflare Workers domain to deploy the unified application. These prerequisites are necessary to enforce authentication, manage passkeys, handle Clerk Billing, and execute subdomain routing correctly.

Can I use Clerk Billing to gate access per subscription in a multi-tenant app?

Yes, you can use Clerk Billing to gate access per subscription in a multi-tenant app. The skill integrates Clerk authentication and billing directly to enforce subscription-based access controls across the generated tenant subdomains and admin dashboards.

What is the best way to generate a unified index.html for landing pages and admin dashboards?

The best way to generate a unified index.html for landing pages and admin dashboards is using this assembly skill, which produces a single self-contained file. It automatically handles single-page landing, tenant routing, and admin dashboard interfaces across subdomains.

What are the limitations of turning a standalone app into SaaS using subdomains?

Limitations of turning a standalone app into SaaS using subdomains include a strict dependency on Clerk credentials and a configured Cloudflare Workers domain. The app must also conform to a single-page index.html structure to properly enforce tenancy and webhook integrations.