Can I vibecode Superhuman?

Build a closest honest personal substitute for Superhuman in an empty repository.
Use Tauri 2, React, TypeScript, SQLite, IMAP, SMTP, and OAuth where available; do not offer alternative stacks.
The core loop is: connect an existing mailbox through a blazing-fast keyboard-first IMAP client, index messages locally for instantaneous search (under 100ms response time), provide a focused split inbox, and send through the account's normal SMTP service.
You must incorporate an exceptionally premium UI design: use a curated, harmonious dark mode color palette (e.g., HSL-tailored sleek dark shades) with vibrant accent colors. Utilize modern typography (such as Inter, Roboto, or Outfit) instead of browser defaults. Implement glassmorphism for modal overlays, smooth micro-animations for all interactive elements (hover effects, selection transitions, sending animations), and ensure the overall aesthetic screams premium, state-of-the-art software. Avoid generic plain colors at all costs.
Implement advanced features inspired by the original: lightning-fast keyboard shortcuts mimicking an entirely mouseless workflow, a Split Inbox to intelligently categorize incoming mail (e.g., Team, VIPs, Updates), and simulated AI triage capabilities (using simple local heuristics or an optional local LLM integration) to prioritize urgent messages and draft quick replies via text snippets.
Make the first run work locally with one documented command. Store all user data locally by default and make export straightforward. Put secrets in .env, ship .env.example, and never commit credentials.
Support one IMAP and SMTP account with credentials stored only in the OS keychain.
Index headers and message bodies locally with resumable sync and a beautifully animated, visible status page.
Implement standards-based threading, folders, labels, archive, snooze, drafts, undo send, scheduling, and lightning-fast search.
Render HTML email in a locked-down sandbox and block remote images by default. Send multipart messages with attachments and preserve a local copy of every draft.
Include clear empty, loading, success, and recoverable error states with premium placeholder illustrations or animations.
Add export, local cache reset, account reconnect, diagnostics, safe logging, input validation, and graceful handling of unavailable APIs.
Write focused tests for the core transformation and one end-to-end happy path. Create a README with setup, architecture, permissions, data location, and backup steps.
Do not add accounts, billing, telemetry, analytics, or a hosted control plane. Deliberately leave out running a public mail server, shared team inboxes, and provider-scale spam filtering.
Finish by running the tests and listing the exact commands used.