Can I vibe code Attentive?

Build a production-grade multi-channel SMS automation engine for Shopify using Node.js, PostgreSQL, Prisma, and Redis.

CORE ARCHITECTURE & DATA MODEL:
1. Define Prisma schema for:
   - Merchant: ID, Shopify domain, access token, carrier API keys (Twilio/Telnyx API credentials), status.
   - Subscriber: ID, MerchantID, phone (E.164 format), email, optInStatus (SUBSCRIBED, UNSUBSCRIBED), consentSource, opticalConsentTimestamp, doubleOptInCompleted (boolean).
   - Campaign: ID, MerchantID, name, channel (SMS/MMS), messageTemplate, status (DRAFT, SCHEDULED, SENDING, COMPLETED), scheduledAt.
   - Flow: ID, MerchantID, triggerEvent (e.g., 'CHECKOUT_ABANDONED', 'ORDER_CREATED'), nodes (JSON workflow tree), isActive.
   - MessageLog: ID, SubscriberID, CampaignID/FlowID, carrierMessageId, status (QUEUED, SENT, DELIVERED, FAILED), failureReason, cost, sentAt.
   - OptOutLog: ID, phone, bodyReceived, keyword, processedAt.

INTEGRATIONS & WEBHOOKS:
1. Shopify Webhooks: Implement HMAC-verified endpoints for `checkouts/create`, `checkouts/update`, `orders/create`, and `customers/redact`. Process events through BullMQ Redis queues to evaluate Flow triggers.
2. Carrier Integration (Twilio/Telnyx):
   - Wrap API client to dispatch outbound SMS/MMS.
   - Build a webhooks receiver for carrier delivery status updates (DLVs) updating MessageLog status asynchronously.
   - Build inbound SMS webhook to handle real-time compliance keyword parsing.

CRITICAL COMPLIANCE ENGINE (TCPA/10DLC Rules):
1. Inbound Keyword Processor: Intercept every incoming message. If the normalized body matches strict opt-out keywords (`STOP`, `UNSUBSCRIBE`, `CANCEL`, `QUIT`, `END`), instantly update Subscriber.optInStatus to `UNSUBSCRIBED`, write to OptOutLog, and emit a mandatory compliance response text: "You have been unsubscribed and will receive no further messages."
2. Opt-in Guard: Every outbound message queue worker MUST perform an atomic check against `Subscriber.optInStatus == SUBSCRIBED` and verify against global suppression tables prior to making carrier API calls.
3. Quiet Hours Enforcer: Evaluate recipient's local timezone. Do not dispatch promotional SMS between 9:00 PM and 8:00 AM in the target user's local timezone. Hold jobs in Redis until the quiet window expires.

FRONTEND & TWO-TAP SIGN-UP:
1. Build a fast, lightweight mobile pop-up script embeddable on Shopify stores.
2. Implement Two-Tap Opt-in logic for mobile safari/chrome: Render a CTA that opens the native SMS client pre-populated with a target shortcode/toll-free number and a pre-formatted opt-in keyword (e.g., "JOIN").
3. React Admin Dashboard: Visual drag-and-drop workflow canvas using React Flow for setting up delay nodes, conditional split nodes (e.g., cart value > $100), and message send nodes.

OUT OF SCOPE:
- Email rendering engines or SMTP sending infrastructure.
- Complex machine-learning copy generation.
- Direct short code carrier provisioning portal (assume carrier numbers are pre-provisioned in Twilio/Telnyx account).

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