Can I vibecode Saner.AI?

text
Build a premium, intelligent personal substitute for Saner.AI designed to "calm the chaos" of cognitive overload.
Use exactly this stack: Tauri 2 + React + TypeScript + SQLite.
Primary job: Build a local-first AI personal knowledge and productivity assistant that merges notes, tasks, and daily planning into a unified, frictionless interface.

DESIGN & UI AESTHETICS (CRITICAL):
Create a breathtaking, zen-like UI that actively reduces mental friction. It must feel like a premium, state-of-the-art digital sanctuary.
- Adopt a minimalist, highly refined aesthetic with a carefully curated neutral color palette (soft creams, muted grays, or a deep, low-contrast dark mode) to minimize eye strain.
- Typography should be elegant and highly readable (e.g., serif headings paired with clean sans-serif body text).
- Use dynamic, fluid layouts that adapt to the user's current focus, removing unnecessary navigation elements when deep in thought.
- Implement rich micro-interactions: a soft, glowing pulse when the AI assistant is processing, smooth expanding transitions for notes, and satisfying, tactile animations when checking off tasks.
- The interface should feel alive but unobtrusive, using blur effects and soft shadows to establish spatial hierarchy.

KEY FEATURES TO IMPLEMENT:
- AI Auto-Organization: A system to automatically tag, link, and categorize captured notes and ideas without manual filing.
- Unified Chat Assistant Interface: A persistent "Skai"-like chat interface to query your personal knowledge base, retrieve past thoughts, and summarize notes.
- Proactive Daily Planning: A dashboard that aggregates tasks and notes to suggest a daily agenda, highlighting urgent items and quick wins.
- Focus Box Mode: A dedicated, distraction-free view for tackling single tasks or expanding on a single note, dimming all other UI elements.
- Universal Quick Capture: A frictionless, always-accessible input field to dump ideas instantly with support for markdown.

TECHNICAL REQUIREMENTS:
Start from an empty folder and create the complete working project.
Make the default mode single-user and private.
Store user data locally.
Integrate an open-source local LLM or API integration for the auto-organization and chat features.
Do not add analytics, telemetry, ads, or third-party accounts.
Put every secret and external credential in .env and provide .env.example.
Use realistic sample data that is clearly labelled.
Include clear empty, loading, validation, success, and failure states.
Add import and export so the user is not trapped.
Use accessible keyboard navigation, labels, and sensible contrast.
Validate untrusted input and never log secrets or private file contents.
Deliberately exclude: native mobile clients, conflict-safe multi-device sync, mature integrations.
Write focused unit tests for the data model and the most important workflow.
Add one end-to-end smoke test that proves the core loop works.
Create a README with setup, architecture, and limitations.
Add scripts for install, development, test, build, and production run.
Run the tests and build before finishing.