Can I vibe code Noibu?

Build a full-stack e-commerce error tracking and revenue impact system using Next.js, ClickHouse, and a lightweight vanilla JS client snippet.

1. DATA MODEL & SCHEMA:
Create ClickHouse tables for error_events and sessions.
- error_events: id, session_id, timestamp, error_message, stack_trace, url, user_agent, cart_value (Float64), currency, error_fingerprint (String), http_status (Nullable(UInt16)).
- sessions: session_id, started_at, updated_at, max_cart_value (Float64), converted (Boolean), checkout_step (String).

2. CLIENT-SIDE JS TELEMETRY SNIPPET:
Write an un-opinionated lightweight JS script (< 10KB) injected into checkout:
- Listen to window.onerror and unhandledrejection events.
- Intercept fetch and XMLHttpRequest calls to log non-2xx API failures.
- Read current cart value from Shopify/e-commerce window global (e.g., window.Shopify.cart.total_price).
- STRICT DATA MASKING: Strip all input values matching input[type="password"], input[name*="card"], input[name*="cvv"], or inputs wrapped in sensitive containers prior to transmission.
- Send batched payloads to POST /api/v1/telemetry using navigator.sendBeacon.

3. BACKEND INGESTION & REVENUE CORRELATION (Next.js API Routes):
- Ingest telemetry payloads, process fingerprints via md5(error_message + cleaned_stack), and asynchronously insert into ClickHouse.
- Create an endpoint GET /api/v1/dashboard/impact:
  - Query total distinct sessions that encountered an error_fingerprint and DID NOT convert.
  - Aggregate lost_revenue_estimate = SUM(max_cart_value) for failed, non-converting sessions where the error occurred in the checkout funnel.
  - Group issues by error_fingerprint, sorted by highest lost_revenue_estimate.

4. FAILURE MODES & SAFETY:
- Never block the main UI thread during network capture or DOM inspection.
- Handle rate-limiting gracefully on high traffic: drop trace frames if local memory queue exceeds 100 items.
- Fallback gracefully if sendBeacon fails.

5. OUT OF SCOPE:
Do not build DOM session video recording or full DOM snapshot trees in this phase. Keep telemetry purely text-based (JS errors, API responses, console errors, breadcrumbs).

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