Can I vibe code Fairing?

Build a post-purchase survey system for Shopify using a Checkout UI Extension frontend and a Next.js serverless backend.

1. ARCHITECTURE & DATA MODEL
- Database schema for PostgreSQL storing: surveys (id, store_id, title, questions_json, active), responses (id, order_id, customer_id, survey_id, answers_json, created_at).
- Questions structure must support single-select, multi-select, and open-text inputs with conditional follow-up branching based on key selected.

2. FRONTEND (Shopify Checkout UI Extension)
- Create a Checkout UI extension targeted to `purchase.thank-you.block.render` using React.
- Retrieve `orderId`, `customerId`, and store origin from the Shopify extension context.
- Fetch active survey schema from the backend API.
- Render responsive input forms styled according to Shopify Polaris primitives.
- On submit, post response data payload `{ orderId, customerId, surveyId, answers: [...] }` to the ingestion endpoint.
- Implement local storage/session guard to prevent submission re-triggers on browser refresh.

3. BACKEND API & INTEGRATIONS
- Endpoint `/api/survey/active`: Returns JSON definition of current active survey for the requesting store.
- Endpoint `/api/survey/respond`: Validates payload, stores response in DB, and executes asynchronous tasks:
  a. Updates Shopify Order Metafields with the primary response under namespace `attribution.how_did_you_hear`.
  b. Sends a profile update request to Klaviyo API attaching custom profile properties corresponding to survey responses.
  c. Dispatches a GA4 Measurement Protocol event `post_purchase_survey_submitted` containing response parameters.

4. FAILURE MODES & EDGE CASES
- Handle null or guest checkout `customerId` gracefully by keying responses solely to `orderId`.
- Implement fallback UI states (silent collapse) if backend endpoint returns 5xx errors or network timeout occurs.
- Guarantee webhook payload idempotency using unique constraint on `order_id` + `survey_id` in database.

5. OUT OF SCOPE
- Complex enterprise role-based access control.
- Multi-language localization engines (hardcode English support only).

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