Can I vibe code NopCommerce?

1. SYSTEM ARCHITECTURE & DATA MODEL
Build an ASP.NET Core 8 Web API for a custom ecommerce store engine using Entity Framework Core and PostgreSQL. Define entities: Product (Id, SKU, Name, Description, Price, StockQuantity, IsPublished, CreatedAt), Category (Id, Name, ParentCategoryId), Customer (Id, Email, PasswordHash, Role), Order (Id, CustomerId, TotalAmount, Status, ShippingAddressJson, PaymentStatus, CreatedAt), and OrderItem (Id, OrderId, ProductId, Quantity, UnitPrice).

2. CORE LOGIC & ENDPOINTS
Implement REST API endpoints:
- Auth: Customer registration, JWT login, role-based access control (Admin, Customer).
- Catalog: GET /products (with pagination, filtering by CategoryId, search query), GET /products/{id}, POST/PUT/DELETE /admin/products.
- Cart & Order Processing: POST /cart/checkout (validates stock, calculates total, integrates with Stripe PaymentIntents API, creates Order record with 'Pending' status upon authorization).
- Webhooks: POST /webhooks/stripe to listen for payment_intent.succeeded and update Order.PaymentStatus to 'Paid' and decrement Product.StockQuantity transactionally.

3. FAILURE MODES & EDGE CASES
- Concurrency Control: Use database row locking or optimistic concurrency tokens on Product.StockQuantity to prevent overselling during high-traffic checkout.
- Transaction Isolation: Wrap order creation and stock reduction inside an EF Core database transaction. Roll back completely if payment authorization or stock decrement fails.
- Input Validation: Strict model validation on incoming payload fields (e.g. non-negative prices, valid email formats).

4. OUT OF SCOPE
Do not build a full monolith UI, multi-tenant architecture, plugin extension system, dynamic theme engine, or complex B2B tier-pricing matrices in this initial MVP.

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