Can I vibecode Dabble?

text
Build a dedicated personal replacement for Dabble, starting from an entirely empty repository. You must use exactly the following technology stack: Tauri 2 for the desktop application framework, React and TypeScript for the frontend interface, SQLite for local relational data storage, and a small custom Rust filesystem layer for direct file access. Under no circumstances should you offer alternative technology stacks.

The core product loop you must implement is a comprehensive writing environment: allow the user to plan chapters, draft a manuscript, track various plot threads, and maintain the structured writing project entirely in local Markdown files. The application must synchronize these files and support exporting without ever requiring the document to be uploaded to a cloud server. The first-run experience must work seamlessly locally, initiated by a single well-documented command.

Store all user data locally on the user's machine by default. Make the export process (compiling chapters into a single manuscript) intuitive and straightforward. Manage any external secrets using a `.env` file, provide a corresponding `.env.example`, and ensure no credentials are ever committed to version control. 

Design a polished three-pane editor layout: one pane for the primary source text, a secondary pane for a suggestion/plot thread list, and a third pane for an accepted-result preview or chapter outline. Implement deterministic, local grammatical checks for repeated words, sentence length variations, passive voice constructions, and basic typography (e.g., smart quotes). Optionally, add an API-backed rewrite action that only transmits the explicitly selected passage to an LLM, ensuring privacy for the rest of the manuscript. 

Ensure every programmatic text change is presented as an accept-or-reject diff, and implement robust undo/redo functionality. Provide robust import and export capabilities for `.txt` and `.md` formats, strictly preserving headings, lists, and structure. Persist user-defined writing rules, ignored terms, and a list of recently opened documents in the SQLite database. 

The application must include clear states for empty workspaces, loading transitions, success confirmations, and recoverable error handling. Add stringent input validation, ensure filenames are sanitized for the local OS, and handle the unavailability of any optional APIs gracefully. Write focused unit tests for the core text transformation logic and implement at least one end-to-end happy path test. Create a comprehensive README covering setup, architecture, OS permissions, data location on disk, and backup strategies. Deliberately exclude user accounts, billing, telemetry, analytics, hosted control planes, browser extensions, Office/Docs plugins, and any form of collaborative editing or cloud sync. Finish by running the tests and documenting the exact terminal commands used.