Can I vibe code WooCommerce?

Build a headless, ultra-fast ecommerce core API and customer storefront using Next.js 14 App Router, TypeScript, Tailwind CSS, Prisma ORM, and PostgreSQL. 

DATA MODEL & ENTITIES:
- Store: id, name, currency, domain.
- Product: id, store_id, title, slug, description, status (draft/published), created_at.
- ProductVariant: id, product_id, title, sku, price_in_cents, inventory_quantity, attributes (JSONB, e.g., {"color": "Blue", "size": "L"}).
- Cart: id, store_id, session_token, created_at, updated_at.
- CartItem: id, cart_id, variant_id, quantity.
- Order: id, store_id, customer_email, total_in_cents, status (pending, paid, fulfilled, cancelled), shipping_address (JSONB), created_at.
- OrderItem: id, order_id, variant_id, unit_price_in_cents, quantity.

CORE INTEGRATIONS & APIS:
1. Stripe Payments API:
   - Implement POST /api/checkout/create-intent using Stripe PaymentIntents.
   - Implement POST /api/webhooks/stripe handling 'payment_intent.succeeded' to set Order status to 'paid' and decrement ProductVariant.inventory_quantity within a database transaction.
2. Storefront REST APIs (Next.js Route Handlers):
   - GET /api/products (cached listing with pagination and SKU filter).
   - POST /api/cart (creates or updates cart session with line items).
   - POST /api/orders (converts active cart to a pending order and returns Stripe Client Secret).

FAILURE MODES & RACE CONDITIONS TO HANDLE:
- Race condition on inventory decrement: Use PostgreSQL pessimistic locking (`SELECT FOR UPDATE`) or atomic SQL queries (`UPDATE product_variants SET inventory_quantity = inventory_quantity - $1 WHERE id = $2 AND inventory_quantity >= $1`) when finalizing payments.
- Idempotent Stripe Webhooks: Store processed webhook event IDs in an `EventLog` table to prevent duplicate order processing and double-inventory decrement on re-sent webhooks.

EXPLICITLY OUT OF SCOPE:
- WordPress / PHP compatibility layer or WP-Admin UI.
- Plugin hook/filter system (`do_action` / `apply_filters`).
- Legacy legacy MySQL `wp_posts` / `wp_postmeta` schema mapping.
- Multi-vendor marketplace capabilities.

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