Can I vibecode Focusmate?

Build a virtual coworking and body-doubling desktop utility inspired by the core functionality of Focusmate.
Since a solo build cannot replicate the global community or network effects, focus on building a robust local productivity and accountability tool, optionally with a peer-to-peer WebRTC integration for direct 1-on-1 sessions.
Use exactly this stack: Tauri 2 + React + TypeScript + SQLite.

Core Features & Functional Requirements:
1. Session Management: Implement a scheduling and timer system supporting standard focus sessions of 25, 50, or 75 minutes. Include visual countdowns, chimes for session start/end, and progress tracking.
2. Task Modes & Goals: Before a session starts, require the user to input their primary goal and select a task mode (e.g., Desk Mode, Moving, or Anything). Allow them to log outcomes at the end of the session.
3. Virtual Coworking (Peer-to-Peer): Build a lightweight WebRTC video and chat interface that allows two users to connect directly via a shared link or room code. Include a 'Quiet Mode' where the microphone is disabled by default and users communicate goals solely through the session chat.
4. Video Features: The video interface should support picture-in-picture mode so users can keep their partner visible while working in other applications. Include camera toggle, mute, and screen sharing if possible.
5. Local Dashboard: Provide a local dashboard showing past sessions, completed goals, and productivity streaks.
6. Keyboard-First Controls: Ensure all timers, task inputs, and session controls can be operated entirely via keyboard shortcuts.

Technical Constraints:
- Start from an empty folder and create the complete working project using Tauri.
- Store all user data, session history, and preferences locally using SQLite.
- The default mode should be single-user (acting as a strict pomodoro/goal tracker) with the option to initiate a P2P connection.
- Do not add analytics, telemetry, ads, or rely on centralized servers for video (use direct WebRTC where possible, or a minimal signaling server provided via an env var).
- Put every secret and external credential in .env and provide .env.example.
- Include clear empty, loading, validation, success, and failure states, particularly for network connections and camera permissions.
- Validate untrusted input and never log secrets. Ensure WebRTC connections are secure.

Testing & Documentation:
- Write focused unit tests for the timer logic, state transitions (waiting, active, completed), and goal data models.
- Add an end-to-end smoke test that verifies the local timer and goal-setting loop works.
- Create a comprehensive README with setup instructions, permissions required (Camera/Microphone), architecture, and limitations.
- Add scripts for install, development, test, build, and a production-style local run.
- Run the tests and build before finishing, fixing any errors.