Can I vibecode Xmind?

Build a highly usable, production-ready personal replacement for the core loop of Xmind from scratch in an empty repository.
Use exactly this tech stack without deviation: React, TypeScript (strict mode), Vite for the build tool, and IndexedDB for robust local storage. Do not suggest or offer alternative technologies.

Your primary objective is to build a high-performance, browser-based mind mapping editor. It must support intuitive drag-and-drop node placement, dynamic resizing, visual connection routing, comprehensive keyboard shortcuts, automatic saving, and high-quality SVG or PNG export capabilities.

Core Features & Workflows:
- Start from an empty folder and scaffold the complete working project.
- Make the default mode strictly single-user and private, running entirely within the user's browser.
- Store all user configuration and mind map data locally using IndexedDB. No server-side database should be required.
- Keep any necessary secrets in a `.env` file, provide a `.env.example`, and ensure no sensitive data is ever transmitted.
- Use realistic, clearly labelled sample data during the initial load that demonstrates the app's capabilities but is easy for the user to delete or ignore.
- Implement the smallest but most polished canvas interface possible that completes the core loop: create node -> connect -> style -> arrange -> export.
- Include crystal-clear empty states, smooth canvas interactions (pan/zoom), rigorous input validation, and distinct success/failure toasts.
- Add a robust JSON-based import and export mechanism so the user is never locked in and can back up their mind maps as files.
- Ensure accessible keyboard navigation, clear visual hierarchy, distinct focus states, and sensible color contrast across the UI.

Explicit Exclusions & Constraints:
- Do NOT add analytics, telemetry, advertisements, or third-party user accounts.
- Deliberately exclude paid-product advantages such as real-time multiplayer cursors, collaborative commenting, large pre-built template libraries, and high-fidelity import/export compatible with proprietary formats.
- Do NOT fake integrations, network effects, proprietary layout algorithms, compliance certifications, or security claims.
- The application must function 100% offline. If any external API is optionally used (e.g., for icons), the application must degrade gracefully without it.

Testing & Documentation:
- Write focused unit tests covering the IndexedDB data model wrapper, the node layout logic, and the core canvas interactions.
- Add at least one comprehensive end-to-end smoke test that proves the core loop (creating nodes, connecting them, and exporting) works correctly.
- Create an exhaustive README containing setup instructions, permission requirements, architectural overview, data location details (explaining IndexedDB), backup steps, and known limitations.
- Provide helper scripts in `package.json` for installation, development, testing, building, and running a production-style local preview.

Finalize your work by running the tests and build steps before finishing. If errors occur, fix them in code rather than merely describing what went wrong.