Can I vibe code Subflow?

Build a full-stack Subscription Management System using Next.js (App Router), Supabase (PostgreSQL), and Stripe Billing API.

1. Data Architecture:
- Create tables for `customers` (id, email, stripe_customer_id, created_at).
- Create `subscriptions` table (id, customer_id, stripe_subscription_id, status, current_period_start, current_period_end, cancel_at_period_end, plan_id).
- Create `subscription_items` table (id, subscription_id, stripe_price_id, quantity, product_name).
- Create `orders` table (id, subscription_id, status, amount_cents, shipping_address, created_at).

2. Core Functionality:
- Integrate Stripe Checkout for purchasing recurring products.
- Implement a Webhook Route (`/api/webhooks/stripe`) handling `customer.subscription.created`, `customer.subscription.updated`, `customer.subscription.deleted`, `invoice.payment_succeeded`, and `invoice.payment_failed`.
- Upon `invoice.payment_succeeded`, automatically generate an entry in the `orders` table for fulfillment dispatch.
- Build a Customer Portal UI allowing end-users to: view active plans, pause/resume subscription (updating Stripe subscription status), skip next billing cycle, update payment methods (via Stripe Portal session), and edit shipping address.
- Build an Admin Dashboard listing active subscribers, Monthly Recurring Revenue (MRR), subscriber churn status, and order creation logs.

3. Technical & Failure Handling:
- Webhooks must check for idempotency using Stripe event IDs stored in a `webhook_events` table before processing.
- Handle payment authorization failures (3DS / SCA) by sending an automated email notification via Resend with a direct billing fix URL.
- Ensure timezone consistency by storing all timestamps in UTC.

4. Out of Scope:
- Usage-based metering, multi-vendor marketplace split payments, and manual wire invoice handling.

$ each button prefixes agent-specific run instructions · build your own product, never copy proprietary code, trademarks or designs