Can I vibecode Gleek?

Build a usable personal replacement for the core loop of Gleek.
Use exactly this stack: React + TypeScript + Vite + IndexedDB.
Primary job: Build a browser-based keyboard-first diagramming editor with drag, resize, connect, keyboard shortcuts, autosave, and SVG or PNG export.
Start from an empty folder and create the complete working project.

Functional Requirements:
- Text-to-Diagram: Implement a text pane where users can type intuitive syntax (e.g., "A -> B: label") and instantly see the diagram update in a side-by-side view.
- Diagram Elements: Support rectangles, ellipses, diamonds (decisions), and database cylinders. 
- Connections: Support solid, dashed, and dotted lines, with optional directional arrows and text labels.
- Layout Engine: Use a lightweight layout algorithm (like dagre) to automatically arrange nodes, while allowing manual drag-and-drop overrides.
- Export & Save: Export the diagram as high-res PNG or SVG. Autosave the current syntax and node positions to IndexedDB.

Architecture & State:
- Make the default mode single-user and private.
- Store user data locally (IndexedDB) unless the core job requires the declared self-hosted database.
- Do not add analytics, telemetry, ads, or third-party accounts.
- Put every secret and external credential in .env and provide .env.example.

UI/UX & States:
- Implement the smallest polished interface that completes the core loop end to end. Clean minimalist UI with a resizable split pane.
- Include clear empty, loading, validation, success, and failure states. Handle syntax errors gracefully with inline error highlights in the text editor.
- Use accessible keyboard navigation, labels, focus states, and sensible contrast. Ensure robust keyboard shortcuts for saving, exporting, and zooming.

Security & Constraints:
- Validate untrusted input and never log secrets or private file contents.
- Deliberately exclude these paid-product advantages: multiplayer cursors and comments; large template libraries; high-fidelity import and export to other proprietary formats.
- Do not fake integrations, network effects, proprietary data, model quality, compliance, or security claims.

Testing & DevOps:
- Write focused unit tests for the text parser and layout logic.
- Add one end-to-end smoke test that proves the core loop works (rendering a basic diagram from text).
- Create a README with setup, permissions, architecture, data location, backup, and limitations.
- Add scripts for install, development, test, build, and a production-style local run.
- Run the tests and build before finishing, then fix errors rather than merely describing them.