What problem does it solve? Adding subscription monetization to a Next.js app with Clerk authentication requires coordinating plan configuration, checkout UI, entitlement checks, and webhook lifecycle handling, and mistakes like creating plans in the wrong tab or using Stripe event names cause silent failures. ## Core Features & Use Cases - Subscription UI: Render <PricingTable /> and <CheckoutButton /> for in-app checkout, plus <UserProfile /> / <OrganizationProfile /> for self-service billing management with invoices and payment methods. - Plan and Feature Gating: Gate routes and capabilities with has({ plan }) and has({ feature }) from auth() or useAuth(), including B2B organization plans with seat limits. - Billing Webhooks: Handle Clerk's 16 billing events (subscription.created, subscriptionItem.canceled, subscriptionItem.pastDue, etc.) with correct payload shapes and signature verification. - Use Case: A B2B SaaS needs team subscriptions where each organization subscribes to a seat-limited plan; this Skill provides the org-level plan check, the <PricingTable for="organization" /> pricing page, and webhook handlers syncing subscription status to a database. ## Quick Start Ask the AI to add a pricing page with Clerk's PricingTable and protect a Pro-only dashboard route using has({ plan: 'pro' }).
