Can I vibe code Help Scout?

Build a shared customer support inbox MVP for an e-commerce brand using Next.js App Router, Tailwind CSS, PostgreSQL, and Prisma ORM.

CORE DATA MODELS:
- User (id, name, email, role [ADMIN, AGENT], status)
- Inbox (id, name, emailAddress, signature)
- Customer (id, email, name, phone, shopifyCustomerId)
- Conversation (id, inboxId, customerId, status [OPEN, PENDING, CLOSED], assignedUserId, threadId, createdAt, updatedAt)
- Message (id, conversationId, senderType [AGENT, CUSTOMER, SYSTEM], senderId, bodyText, bodyHtml, messageIdHeader, inReplyToHeader, createdAt)
- SavedReply (id, title, shortcut, content)
- Tag (id, name, color)
- ConversationTag (conversationId, tagId)

KEY FEATURES TO IMPLEMENT:
1. Multi-tenant Inbox View:
   - Sidebar showing inboxes, assigned tickets, unassigned tickets, and custom status filters.
   - Conversation list displaying customer name, subject snippet, last updated timestamp, and status badge.
   - Real-time active viewer presence (show which agent is currently viewing a conversation to prevent collision).

2. Threaded Message Interface:
   - Main conversation panel displaying chronological messages with distinct styling for customer vs agent replies vs internal notes.
   - Rich text editor for agent responses supporting inline images, formatting, and shortcut insertion for Saved Replies (e.g., typing `/shipping` populates text).
   - "Send & Close", "Send & Pending", or "Note Only" submit buttons.

3. E-commerce Sidebar Integration (Shopify Mock):
   - Sidebar panel on the right side of the active conversation fetching customer data by email.
   - Display total spend, order count, and a list of recent 3 orders (order ID, date, status, total, tracking link).
   - Action buttons: "Copy Tracking Link", "View Order in Shopify".

4. Automation Rules Engine (Basic Workflows):
   - Admin UI to define simple logic: IF subject/body contains keyword X THEN assign to User Y and apply Tag Z.
   - Execution pipeline triggered when a new Message entity is created.

INBOUND/OUTBOUND EMAIL ARCHITECTURE:
- Expose a webhook endpoint `/api/webhooks/inbound-email` designed for Postmark/SendGrid inbound parse payloads.
- Correctly parse `Message-ID`, `In-Reply-To`, and `References` headers to thread incoming emails into existing `Conversation` records or create new ones.
- Outbound responses must use Postmark API (or Nodemailer) sending with structured `In-Reply-To` headers targeting the previous message's `Message-ID`.

OUT OF SCOPE:
- Live Chat JavaScript widget deployment.
- Voice/SMS channel integrations.
- Complex HIPAA audit logging or SSO SAML integration.

CRITICAL FAILURE MODES TO AVOID:
- Infinite email auto-responder loops: Do not trigger automated workflow replies if incoming email header contains `Auto-Submitted: auto-replied` or `X-Autoreply: yes`.
- Conversation collision: Show clear visual indicators if two agents are drafting replies to the same ticket simultaneously.

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